The 5G-WWC set of requirements define a WAN behavior that is exclusive of the other behaviors defined in TR-124. For WWC this is referred to as 5G-RG mode of operation, and the non 5G behaviors are referred to as the FN-RG mode of operation. A device may be configured to exclusively use one mode of operation or the other, or may be a hybrid of the two via either VLAN or Ethertype separation of WAN traffic into distinct interfaces presenting a mix of 5G and non 5G interfaces to the device.

The following table illustrates the set of common and mode specific functionalities between the two modes of operation.

Note - WAN.ATM & WAN.ATM.MULTI are out of scope.

It is recommended that implementers read TR-470 [171] 5G FMC Architecture Overview in conjunction with interpreting these requirements; in particular, the section 5G-RG Overview of Operation.

ID	Requirement
5G-WWC.1	An RG that implements both modes of operation SHOULD be able to support both modes of operation simultaneously.
5G-WWC.2	An RG that implements both modes of operation MUST be able to be configured to disable the 5G-RG mode of operation
5G-WWC.3	An RG that implements both modes of operation MUST be able to be configured to disable the FN-RG mode of operation
5G-WWC.4	The RG SHOULD support URSP as specified in 3GPP TS 23.503 [9] with modification specified in 3GPP TS 23.316 [5].
5G-WWC.5	The RG MUST support the 3GPP network slicing as defined in 3GPP TS.23.501 [7] clause 5.15 where the UE is replaced by the 5G-RG.
5G-WWC.6	The RG MUST support the 3GPP NSSAI configuration and NSSAI storage aspects as defined in TS 3GPP TS.23.501 [7] clause 5.15.4 where the UE is replaced by the 5G-RG.
5G-WWC.7	The RG MUST support to retrieve Configuration and Management from Controller or from ACS via PDU Session as specified in clause 9.6 of 3GPP TS 23.316 [5].

4.9.1 5G-WWC.Identifiers – 5G WWC Identifiers

ID	Requirement
5G-WWC.Identifiers.1	The RG MUST be identified by 5G Subscription Permanent Identifier (SUPI)
5G-WWC.Identifiers.2	The SUPI for the RG MUST contain an IMSI.
5G-WWC.Identifiers.3	The SUPI format with IMSI for the RG MUST be as defined in 3GPP TS 23.003 [2] clause 2.2A
5G-WWC.Identifiers.4	When the RG needs to indicate its SUPI, for example during Registration procedure, the 5G-RG MUST provide the Subscription Concealed Identifier (SUCI)as defined in TS 33.501
5G-WWC.Identifiers.5	The SUCI format provided by the RG MUST be as defined in 3GPP TS 23.003 [2] clause 2.2B
5G-WWC.Identifiers.6	The RG MUST support Permanent Equipment Identifier (PEI)
5G-WWC.Identifiers.7	For an RG that only has a wireline WAN interface, the PEI MUST include the MAC address of WAN interface and the format is defined in 3GPP TS 23.003 [2]
5G-WWC.Identifiers.8	For an RG that has a wireless WAN interface (and may also have a wireline WAN interface), the PEI MUST include an IMEI. The format is defined in 3GPP TS 23.003 [2].
5G-WWC.Identifiers.9	The PEI MUST be stored in secure and tamper proof location in the RG as required by 3GPP TS 33.501 [13].

4.9.2 5G-WWC.FWA – 5G WWC Fixed Wireless Access

4.9.2.1 5G-WWC.FWA.IPTV – 5G WWC Fixed Wireless Access IPTV

4.9.3 5G-WWC.WAN – 5G WWC Wide Area Network

ID	Requirement
5G-WWC.WAN.1	The VLAN ID used for NAS, AS and 5WE encapsulated sessions MUST be able to be locally configured. Note: This is known as the 5G VLAN.
5G-WWC.WAN.2	The default VLAN ID used for NAS, AS and 5WE encapsulated PDU sessions is zero indicating an untagged or priority tagged UNI.
5G-WWC.WAN.3	The RG MUST support the procedures documented in Broadband Forum TR-456 [170] section ‘Procedure Call Flows’ subsection ‘For a 5G-RG’ and 3GPP TS 24.501 [12].

Note: A number of NAS procedures have error conditions that mandate the 5G-RG NAS implementation ‘back off’ for a period of time prior to re-attempting the operation. The set of procedures that result in these conditions is documented in 3GPP TS 24.501 [12]. The relevance of these various error, resource or subscription issue conditions to a 5G-RG in relation to the set of timers associated with NAS operations is discussed in Appendix 9.1 of Broadband Forum TR-456 [170].

4.9.3.1 5G-WWC.WAN.RADIO – 5G WWC Fixed Wireless Access Radio

ID	Requirement
5G-WWC.WAN.RADIO.1	The RG MUST support NAS protocol to interact with AMF as described in 3GPP TS 23.502 [8] specified in 3GPP TS 24.501 [12] in both cases with UE replaced with RG. In particular the following procedures (all clause references are 3GPP TS 23.502 [8]). Registration (clause 4.2.2.2) De-registration (clause 4.2.2.3) Service request (clause 4.2.3) PDU Session Establishment (clause 4.3.2) PDU Session Initiation/Establishment with ACS Discovery (clause 4.3.2.2.1) PDU Session Modification (clause 4.3.3) PDU Session Release (clause 4.3.4) AN Release (clause 7.2.5) CN-initiated selective deactivation of UP connection of an existing PDU session associated with W-5GAN access Service Request Configuration update (clause 4.2.4)
5G-WWC.WAN.RADIO.2	The RG MUST support 5G-AN Protocol layer, including both control plane and user plane, to interact with NG-RAN which specified in 3GPP TS 38.300 [15].
5G-WWC.WAN.RADIO.3	The RG MUST support the following EPC procedures on the E-UTRA interface as described in 3GPP TS 23.401 [6] and specified in [11], in both cases with UE replaced by RG (note all clause references are to 3GPP TS 23.401 [6]): UE attach procedure (clause 5.3.2) Detach procedure (clause 5.3.8) Dedicated bearer activation (clause 5.4.1) Bearer modification with bearer QoS update (clause 5.4.2) PDN GW initiated bearer modification without bearer QoS update (clause 5.4.3) Bearer deactivation (clause 5.4.4) UE requested bearer resource modification (clause 5.4.5) E-UTRAN initiated E-RAB modification procedure (clause 5.4.7) E-UTRAN initiated UE Context Modification procedure (clause 5.4.8)
5G-WWC.WAN.RADIO.4	The RG MUST support E-UTRA Protocol layer, including both control plane and user plane, to interact with E-UTRAN which specified in 3GPP TS 36.300 [14].
5G-WWC.WAN.RADIO.5	PLMN selections procedure defined in 3GPP TS 22.011 [1] and [4] MUST besupported.

4.9.3.2 5G-WWC.WAN.CP – 5G WWC WAN Control Plane

ID	Requirement
5G-WWC.WAN.CP.1	The RG MUST support the transport of NAS and AS information with the AGF as documented in “NAS and AS transport and information elements” section of Broadband Forum TR-456 [170].
5G-WWC.WAN.CP.2	The RG SHOULD incorporate a random timing delay prior to attempting to initiate establishing 5G control connectivity. This random timing delay helps to reduce connection failures when a group of users attempts to establish connections to a service provider at the same time (e.g. after power is restored to a neighborhood that had a blackout).
5G-WWC.WAN.CP.3	The RG MUST use the RG’s WAN I/F Ethernet MAC address for the PPPoE 5G control plane connection.
5G-WWC.WAN.CP.4	The RG that is configured to support both modes of operation MUST be able to initiate a PPPoE 5G control plane connection using a NULL length service-name tag.
5G-WWC.WAN.CP.5	The RG that is configured to only support the 5G-RG mode of operation MUST use a PADI with a service-name of 5G (encoded as defined in Broadband Forum TR-456 [170] Section 5.2) when initiating a control plane connection.
5G-WWC.WAN.CP.6	An RG that does not receive a PADO in response to a PADI solicitation SHOULD re-try immediately to establish the connection. After three unsuccessful attempts, the RG SHOULD wait for five minutes, then repeat the connection attempt three times. If the PADI still fails, the RG SHOULD back off to thirty minute intervals between groups.
5G-WWC.WAN.CP.7	The RG attempting to initiate a PPPoE 5G control plane connection MUST include the LCP 5G VSO in the LCP Configure-Request.
5G-WWC.WAN.CP.8	The RG that receives a Configure-REJ to an LCP configure request containing the LCP 5G VSO MUST be able to revert to the FN-RG mode of operation and if it is configured to use PPPoE in that mode, continue the negotiation accordingly.
5G-WWC.WAN.CP.9	The RG that receives a Configure-REJ to an LCP configure request containing the LCP 5G VSO that intends to revert to IPoE operation MUST issue a PADT to terminate the PPPoE session.
5G-WWC.WAN.CP.10	The RG configured to only use the 5G-RG mode of operation, upon receipt of a Configure-REJ to a configure request containing the LCP 5G VSO MUST resort to an exponential backoff process to reinitiate a PPPoE 5G control plane connection.
5G-WWC.WAN.CP.11	An RG that is only configured to only use 5G procedures, and is unable to establish a 5G control plane connection (LCP Configure-REJ received) will issue a PADT to fully terminate the current attempt and then retry immediately. If that attempt fails it will delay 5 minutes prior to terminating the attempt and retrying. If that attempt fails, after each failure it will terminate the current attempt and select a random interval between 5 and 20 minutes until the next retry.
5G-WWC.WAN.CP.12	Removed.
5G-WWC.WAN.CP.13	The RG MUST support NAS protocol to interact with AMF as specified in 3GPP TS 24.501 [12] with modification specified in 3GPP TS 23.316 [5] Note: The applicability of parameters in NAS messages and the applicability of specific NAS message is further defined in this document as well as 3GPP TS 23.316 [5], and 3GPP TS 24.501 [12].
5G-WWC.WAN.CP.14	The RG MUST maintain a registration management state and a connection management state. The possible values for the registration management state are RM-DEREGISTERED and RM-REGISTERED. The possible values for the connection management state are CM-IDLE and CM-CONNECTED. The initial RG state is RM-DEREGISTERED and CM-IDLE.
5G-WWC.WAN.CP.15	The 5G-RG must start a NAS initial Registration procedure, as documented in 3GPP TS 23.316 [5] Section 7.2.1.1 and Broadband Forum TR-456 [170] Section “Registration Management Procedure for 5G-RG”. Upon completion of these procedures the RG will be in the RM-REGISTERED, CM-CONNECTED state.
5G-WWC.WAN.CP.16	The RG MUST use LCP-ECHO with a default periodicity of 10 seconds to monitor NAS channel liveliness.
5G-WWC.WAN.CP.17	Upon detection of connectivity failure an RG in the RM-REGISTERED/CM-CONNECTED state MUST transition the connection management state to CM-IDLE and initiate a deregistration timer to either the default value or the value communicated in the in NAS Registration Accept message as documented in 3GPP TS 24.501 [12] clause 8.2.7.17
5G-WWC.WAN.CP.18	Upon expiry of the deregistration timer the RG MUST transition the registration management state to RM-DEREGISTERED and clean up all 5G context state.
5G-WWC.WAN.CP.19	An RG that has detected connectivity failure with the network MUST attempt to reconnect using the procedures outlined in requirement 5G-WWC.WAN.CP.16.
5G-WWC.WAN.CP.20	An RG that reconnects with the network while in the RM-REGISTERED state MUST use a NAS Service Request procedure, as documented int 3GPP TS 23.316 [5] Section 7.2.2.1 and Broadband Forum TR-456 [170] Section “5G-RG Service Request Procedure via W-5GAN”, to reestablish service.
5G-WWC.WAN.CP.21	An RG that reconnects with the network in the RM-DEREGISTERED state will re-establish service using the procedures outlined in requirements 1 through 15 above AND will cancel the deregistration timer.
5G-WWC.WAN.CP.22	An RG that receives a LCP Terminate-Request for the 5G Control plane connection will remove all PDU session state, all user plane state and terminate the control plane connection.
5G-WWC.WAN.CP.23	The RG MUST support RFC 4638 [111] procedures for negotiating PPP MTUs larger than 1492 bytes.
5G-WWC.WAN.CP.24	The RG MUST indicate the maximum PPP MTU it can support in the RFC 4638 [111] PPP-Max-Payload tag.
5G-WWC.WAN.CP.25	The RG MUST initiate LCP negotiations with the value it provided in the PPP-Max-Payload tag if echoed by the AGF, else falls back to 1492 as per RFC 2516 [70].
5G-WWC.WAN.CP.26	The RG MUST use the MIN of negotiated PPP MTU and IPv4 Link MTU Parameter received via PCO at PDU Session Establishment time as the MTU for 5WE encapsulated IPv4 packets
5G-WWC.WAN.CP.27	The RG MUST use the MIN of negotiated PPP MTU and MTU option in the IPv6 RA received at PDU Session Establishment time for 5WE encapsulated IPv6 packets

Note: PLMN selection defined in 3GPP TS 22.011 [1] and in [3] are not applicable as described in clause 4.2.1 3GPP TS 23.316 [5].

4.9.3.3 5G-WWC.WAN.UP – 5G WWC WAN User Plane

ID	Requirement
5G-WWC.WAN.UP.1	The RG MUST support the 5G WWC User Plane Encapsulation (5WE) as specified in RFC 8822 [148].
5G-WWC.WAN.UP.2	The RG MUST support the IPv4, IPv6, IPv4/v6 and Ethernet PDU session types.
5G-WWC.WAN.UP.3	The RG MUST use the same MAC address used for the PPPoE control plane connection for all PDU sessions. Note: Some ANs populate MAC anti-spoofing tables from the initial PADI received from an RG. Therefore for 5G operation the PPPoE control plane connection and the 5WE encapsulated PDU sessions are required to use a common MAC address.
5G-WWC.WAN.UP.4	The RG MUST use the same AGF MAC address for all PDU Sessions.
5G-WWC.WAN.UP.5	The RG MUST silently discard packets received with an unrecognized 5WE session ID value.
5G-WWC.WAN.UP.6	The RG MUST set the IPv4 MTU for the WAN interface to the minimum of the value negotiated using RFC 4638 [111] procedures and the IPv4 Link MTU parameter that the RG receives in the PDU SESSION ESTABLISHMENT ACCEPT message.
5G-WWC.WAN.UP.7	The RG MUST set the IPv6 MTU for the WAN interface to the minimum of the value negotiated using RFC 4638 [111] procedures and the MTU parameter that the RG receives in IPv6 RA messages received from the SMF.
5G-WWC.WAN.UP.8	The RG MUST set the Ethernet MTU for the WAN interface to the minimum of the value of the Ethernet Max Frame Payload MTU value received via PCO and the RFC 4638 [111] negotiated MTU after adjustment for Ethernet header size. Note: A resulting WAN MTU of less than 1500 bytes is an error. Reporting and recover procedures are FFS.
5G-WWC.WAN.UP.9	The RG MUST support a minimum WAN MTU of 2k octets, and SHOULD support a minimum WAN MTU of 9k octets.

4.9.3.3.1 5G-WWC.WAN.UP.QOS – 5G WWC WAN User Plane QoS

ID	Requirement
5G-WWC.WAN.UP.QOS.1	The RG MUST support an “upstream QOS classifier table” maintained at the granularity of PDU session, that stores QOS rules and is used to perform filter matching on upstream traffic in order to associate specific flows with QFI.
5G-WWC.WAN.UP.QOS.2	The RG MUST support population of the “upstream QOS classifier table” by NAS.
5G-WWC.WAN.UP.QOS.3	The RG MUST support population of the “upstream QOS classifier table” (including initializing an age out timer to the RQ timeout value for the session) with UE derived QOS rules with the filter information gleaned from the IP header and 5WE encoded QFI for packets received that have the RQI bit set in the 5WE header
5G-WWC.WAN.UP.QOS.4	When the RG receives a packet with RQI set where there already is a UE derived QOS rule for the gleaned filter information in the “upstream QOS classifier table” it MUST update the age out timer value to the RQ timeout value for the session and the QFI value to that gleaned from the current packet’s 5WE header.
5G-WWC.WAN.UP.QOS.5	When the RG forwards a packet upstream where it does not find a QOS rule filter match in the “upstream QOS classifier table”, it MUST mark the packet according to the default QFI for the PDU session.
5G-WWC.WAN.UP.QOS.6	When the RG forwards a packet upstream where it does find a filter match in the upstream QOS classifier table”, it MUST mark the packet according to the QFI associated with the QOS rule.
5G-WWC.WAN.UP.QOS.7	The RG MUST age out UE derived QOS rules populated as a result of downstream UP signaling (received RQI indication) upon expiry of the age out timer
5G-WWC.WAN.UP.QOS.8	The RG MUST remove all entries in the “upstream QOS classification table” associated with a PDU session at the time of session release.
5G-WWC.WAN.UP.QOS.9	The RG MUST use the QFI to DSCP/PCP mappings for the PDU session received in the AS session parameters information. If the information is not present, the RG will revert to local configuration. Note: That mapping is unique per session, and the same QFI value used in two separate sessions may have a different mapping per session.
5G-WWC.WAN.UP.QOS.10	When marking upstream packets according to the QFI to PCP/DSCP information received in the AS session parameters TLV, the RG MUST mark the Ethernet PCP according to the PCP information in the AS subscription parameters marking control sub-TLV: Include the PCP in the tag control information of a tagged UNI Include the PCP information in a priority tag if the use of priority tagging is indicated via the P-bit being set in the marking controls or in local configuration, no marking for an untagged UNI if not indicated
5G-WWC.WAN.UP.QOS.11	When remarking upstream packets according to the QFI to PCP/DSCP information received in the AS session parameters TLV, the RG MUST remark the IP DSCP if upstream remarking is indicated in the subscription parameters marking control sub-TLV.

4.9.3.4 5G-WWC.WAN.HO – 5G WWC Multi-access handover support

A device that is equipped with both a wireline and a radio interface (E-UTRA or NR) may implement resiliency on the basis of mobility hand-off. This can be in the wireline to wireless direction or vice versa.

ID	Requirement
5G-WWC.WAN.HO.1	The RG MUST support mobility between the NG-RAN and W-5GAN based upon handover procedures triggered by the 5G-RG, and defined in clause 7.6 of 3GPP TS 23.316 [5] as well as in 3GPP TS 23.502 [8] clause 4.9.2.2, for 3GPP to Non-3GPP transition for a single-access PDU session (where “UE” is replaced by “5G-RG” and “N3IWF” by “W-5GAN”).
5G-WWC.WAN.HO.2	The RG MUST support mobility between E-UTRAN and W-5GAN based on handover procedures triggered by the 5G-RG as described in clause 7.6.4 of 3GPP TS 23.316 [5] and clause 4.11.3 of 3GPP TS 23.502 [8] (where “UE” is replaced by “5G-RG” and “N3IWF” by “W-5GAN”).

4.9.3.5 5G-WWC.WAN.ATSSS – 5G WWC ATSSS

Access traffic steering switching and splitting (ATSSS) is used to permit a 5G-RG to simultaneously utilize both a 3GPP radio interface and non-3GPP wireline interface. The 3GPP radio interface may be with either a E-UTRAN (4G) or NG-RAN (5G). Requirements are specified for 5G operation, and 4G operation via EPC interworking.

Note that for the BBF WWC work, roaming on either interface is considered to be out of scope. What is in scope is referred to as Non-roaming and Roaming with Local Breakout architecture for ATSSS support in 3GPP TS.23.501 [7].

3GPP TS 23.502 [8] defines the procedures and 3GPP TS 24.193 [10] provides the stage 3 definition. Impacts to the NAS protocol for ATSSS is described in TS 24.501.

A rough narrative of operation is that:

1. 5G-RG registers with a common PLMN on both the 3GPP and non-3GPP interfaces. In case the non-3GPP connectivity is available, the 5G-RG attempts to register via the non-3GPP interface first, because the Multi-Access PDU session from the 5G-RG can be initiated via the 3GPP interface, which requests the WAgfInfo availability in AMF and SMF to enable the co-located UPF selection. A security context is established with the first registration that is simply referenced by the second association via the 5G-GUTI.

2. The 5G-RG establishes a multi-access (MA) PDU session. Note that both the 3GPP radio and wireline interfaces may be 5G, or the 3GPP radio interface may be via LTE and employing EPS interworking. When both interfaces are 5G, this can be done with a single MA-PDU session establish request, assuming that the 5G-RG is already registered in both accesses before initiating the PDU Session Establishment procedure. When the radio interface is a E-UTRA interface, the ‘legs’ of the MA-PDU session must be separately established. During session establishment the 5G-RG is provided with ATSSS Rules that contain traffic distribution policies.

3. The 5G RG distributes traffic across the set of upstream interfaces according to ATSSS Rules received from the 5G System.

ID	Requirement
5G-WWC.WAN.ATSSS.1	The RG MUST support ATSSS as is described in 3GPP TS.23.501 [7]
5G-WWC.WAN.ATSSS.2	The RG MUST support at least one of ATSSS-LL and MP-TCP proxy operation
5G-WWC.WAN.ATSSS.3	The RG MUST support the following MA-PDU session lifecycle maintenance procedures described in 3GPP TS 23.502 [8] and specified in 3GPP TS 24.501 [12] and TS 24.193 with UE replaced by RG. The clauses referenced below refer to TS 23.502. UE requested MA-PDU session establishment (Non roaming or roaming with local breakout) as per clause 4.22.2.1 UE Requested PDU Session Establishment with Network Modification to MA PDU Session as per clause 4.22.3 Access Network Performance Measurements as per clause 4.22.4 Reporting of Access Availability as per clause 4.22.5 Adding / Re-activating / De-activating User-Plane Resources as per clause 4.22.7 UE or network requested MA PDU Session Modification as per clause 4.22.8 Connection, Registration and Mobility Management procedures as per clause 4.22.9 UE or network requested MA PDU Session Release (non-roaming and roaming with local breakout) per clause 4.22.10.2
5G-WWC.WAN.ATSSS.4	The RG MUST support EPC Interworking procedures for ATSSS as described in clause 4.22.6 of 3GPP TS 23.502 [8] and specified in 3GPP TS 24.193 [10], in both cases with UE replaced by RG.
5G-WWC.WAN.ATSSS.5	The RG MUST attempt to register via the wireline access first. (note: this will ensure the SMF can have the wAgfInfo available for the co-located UPF selection.)

4.9.4 5G-WWC.LAN – 5G WWC LAN

4.9.4.1 5G-WWC.LAN.DHCPS – 5G WWC LAN DHCPv4

ID	Requirement
5G-WWC.LAN.DHCPS.1	The embedded DHCPv4 server MUST include DHCP Option 26 (IP interface MTU) with an MTU value that is the MIN of the negotiated PPP MTU and the IPv4 Link MTU Parameter received from the SMF via PCO.

4.9.4.2 5G-WWC.LAN.ADDRESSv6 – 5G WWC LAN SLAAC