Transcription
Technical ReportTR-456AGF Functional RequirementsIssue: 1Issue Date: August 2020 The Broadband Forum. All rights reserved.
AGF Functional RequirementsTR-456 Issue 1NoticeThe Broadband Forum is a non-profit corporation organized to create guidelines for broadband networksystem development and deployment. This Technical Report has been approved by members of the Forum.This Technical Report is subject to change. This Technical Report is owned and copyrighted by theBroadband Forum, and all rights are reserved. Portions of this Technical Report may be owned and/orcopyrighted by Broadband Forum members.Intellectual PropertyRecipients of this Technical Report are requested to submit, with their comments, notification of any relevantpatent claims or other intellectual property rights of which they may be aware that might be infringed by anyimplementation of this Technical Report, or use of any software code normatively referenced in thisTechnical Report, and to provide supporting documentation.Terms of Use1. LicenseBroadband Forum hereby grants you the right, without charge, on a perpetual, non-exclusive and worldwidebasis, to utilize the Technical Report for the purpose of developing, making, having made, using, marketing,importing, offering to sell or license, and selling or licensing, and to otherwise distribute, products complyingwith the Technical Report, in all cases subject to the conditions set forth in this notice and any relevantpatent and other intellectual property rights of third parties (which may include members of BroadbandForum). This license grant does not include the right to sublicense, modify or create derivative works basedupon the Technical Report except to the extent this Technical Report includes text implementable incomputer code, in which case your right under this License to create and modify derivative works is limited tomodifying and creating derivative works of such code. For the avoidance of doubt, except as qualified by thepreceding sentence, products implementing this Technical Report are not deemed to be derivative works ofthe Technical Report.2. NO WARRANTIESTHIS TECHNICAL REPORT IS BEING OFFERED WITHOUT ANY WARRANTY WHATSOEVER, AND INPARTICULAR, ANY WARRANTY OF NONINFRINGEMENT AND ANY IMPLIED WARRANTIES AREEXPRESSLY DISCLAIMED. ANY USE OF THIS TECHNICAL REPORT SHALL BE MADE ENTIRELY ATTHE USER’S OR IMPLEMENTER'S OWN RISK, AND NEITHER THE BROADBAND FORUM, NOR ANYOF ITS MEMBERS OR SUBMITTERS, SHALL HAVE ANY LIABILITY WHATSOEVER TO ANY USER,IMPLEMENTER, OR THIRD PARTY FOR ANY DAMAGES OF ANY NATURE WHATSOEVER, DIRECTLYOR INDIRECTLY, ARISING FROM THE USE OF THIS TECHNICAL REPORT, INCLUDING BUT NOTLIMITED TO, ANY CONSEQUENTIAL, SPECIAL, PUNITIVE, INCIDENTAL, AND INDIRECT DAMAGES.3. THIRD PARTY RIGHTSWithout limiting the generality of Section 2 above, BROADBAND FORUM ASSUMES NO RESPONSIBILITYTO COMPILE, CONFIRM, UPDATE OR MAKE PUBLIC ANY THIRD PARTY ASSERTIONS OF PATENTOR OTHER INTELLECTUAL PROPERTY RIGHTS THAT MIGHT NOW OR IN THE FUTURE BEINFRINGED BY AN IMPLEMENTATION OF THE TECHNICAL REPORT IN ITS CURRENT, OR IN ANYFUTURE FORM. IF ANY SUCH RIGHTS ARE DESCRIBED ON THE TECHNICAL REPORT, BROADBANDFORUM TAKES NO POSITION AS TO THE VALIDITY OR INVALIDITY OF SUCH ASSERTIONS, ORTHAT ALL SUCH ASSERTIONS THAT HAVE OR MAY BE MADE ARE SO LISTED.All copies of this Technical Report (or any portion hereof) must include the notices, legends, and otherprovisions set forth on this page.August 2020 The Broadband Forum. All rights reserved2 of 108
AGF Functional RequirementsTR-456 Issue 1Issue HistoryIssue NumberIssue DateIssue EditorsChanges125 August2020Bouchat Christele,NokiaOriginalNewton, Jonathan,Vodafone GroupComments or questions about this Broadband Forum Technical Report should be directed toinfo@broadband-forum.org.Editors:Christele Bouchat, NokiaJonathan Newton, Vodafone GroupWork Area Director:David Allan, EricssonProject Stream Leaders:Manuel Paul, Deutsche TelekomGregory Dalle, Juniper NetworksAugust 2020 The Broadband Forum. All rights reserved3 of 108
AGF Functional RequirementsTR-456 Issue 1Table of ContentsExecutive Summary . 71Purpose and Scope. 81.1Purpose . 81.2Scope . 82References and Terminology . 92.1Conventions . 92.1.1Special Convention for this document. 92.2References . 92.3Definitions . 122.3.1Definitions of 3GPP concepts: . 132.4Abbreviations . 153WWC architecture with AGF. 184High-level requirements of an AGF. 195NAS and AS Transport and Information Elements . 205.1Theory of operation . 205.2PPPoE procedures. 225.3LCP procedures . 235.4EAP procedures . 245.5VNSCP & VSNP Procedures . 245.6VSNP Fragmentation Sub-Layer . 255.7NAS and AS channel TLV . 275.8AS Reliability. 306Functional features and requirements. 326.1Authentication/Authorization/identity management. 326.2Security. 336.2.1N1 (NAS) Security for AGF in adaptive mode . 336.2.2N2 Security . 336.2.3User Plane Data Security (N3). 346.3User plane . 346.3.1User plane for 5G-RG . 346.3.2User plane for FN-RG . 376.3.3Fragmentation and reassembling . 386.4Control plane . 396.4.1Control plane for 5G-RG. 406.4.2Control plane for FN-RG. 426.5QoS . 436.5.1RG level QoS Provisioning . 436.6AGF functions for core network signaling. 496.7N2 connections . 506.8AGF support for slicing and AMF selection . 506.9Connection Management State on AGF . 526.10 Detection of FN-RG equipment change . 536.11 FN-RG IP session initiation requirements . 536.12 Authentication for FN-RG . 586.13 Combined AGF/UPF . 597Migration consideration . 607.1The Line ID based state machine . 60August 2020 The Broadband Forum. All rights reserved4 of 108
AGF Functional Requirements8TR-456 Issue 1Procedures and call flows . 638.1For a FN-RG . 638.1.1FN-RG IP Session Initiation with PPPoE . 638.1.2FN-RG IP session initiation using L2TP . 678.1.3FN-RG IP Session Initiation with DHCPv4 . 708.1.4FN-RG IP Session Initiation with DHCPv6 . 738.1.5FN-RG IP Session Initiation with RS followed by DHCPv6 . 768.1.6Registration Management Procedure for FN-RG. 798.1.7Service Request Procedure for FN-RG . 818.1.8Session Initiation Procedure for FN-RG . 838.1.9Deregistration Procedure for FN-RG. 848.1.10 FN-RG or Network Requested PDU Session Modification via W-5GAN . 868.1.11 FN-RG or Network Requested PDU Session Release via W-5GAN . 868.1.12 FN-RG AN Release via W-5GAN . 878.1.13 Configuration Update Procedure for FN-RG . 878.2For a 5G-RG . 918.2.1Registration Management Procedure for 5G-RG. 918.2.25G-RG Service Request Procedure via W-5GAN. 958.2.35G-RG PDU Session Initiation/Establishment via W-5GAN . 988.2.4ACS Discovery . 998.2.5Deregistration Procedure for 5G-RG.1008.2.65G-RG or Network Requested PDU Session Modification via W-5GAN .1018.2.75G-RG or Network Requested PDU Session Release via W-5GAN .1028.2.85G-RG AN Release via W-5GAN .1048.2.9CN-initiated selective deactivation of UP connection of an existing PDU session associatedwith W-5GAN access .
20.08.2020 · computer code, in which case your right under this License to create and modify derivative works is limited to modifying and creating derivative works of such code. For the avoidance of doubt, except as qualified by the preceding sentence, products implementing this Technical Report are not deemed to be derivative works of the Technical Report.
