2 References
and
Terminology 
2.1 Conventions
In this Technical Report, several words are used to signify the requirements of the specification. These words are always capitalized.
| MUST | This word, or the term “REQUIRED”, means that the definition is an absolute requirement of the specification. |
|---|---|
| MUST NOT | This phrase means that the definition is an absolute prohibition of the specification. |
| SHOULD | This word, or the term “RECOMMENDED”, means that there could exist valid reasons in particular circumstances to ignore this item, but the full implications need to be understood and carefully weighed before choosing a different course. |
| SHOULD NOT | This phrase, or the phrase “NOT RECOMMENDED” means that there could exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications need to be understood and the case carefully weighed before implementing any behavior described with this label. |
| MAY | This word, or the term “OPTIONAL”, means that this item is one of an allowed set of alternatives. An implementation that does not include this option MUST be prepared to inter-operate with another implementation that does include the option. |
| By Default | These words indicate that this is a default setting or operation of the unit that MUST be configurable if provided. This term is not included in RFC 2119 [59]. |
Other residential gateway type features not identified in this document may also be implemented in the device. An implementation that includes features not identified in this document must be prepared to inter-operate with implementations that do not include these features.
References to CPE or LAN devices indicate other equipment such as hosts including PCs and workstations.
In certain cases, TR-124 generically refers to new LAN or WAN interface performance monitoring data parameters that have not been specifically defined in the requirements at the time of the publishing of this document. As these requirements are not yet defined, it is expected that vendors may support parameter extensions and basic interface traffic performance statistics until such a time that the Broadband Forum defines further Technical Reports to support new interface parameter data models for possible use with TR-064i2, TR-069 and the Web GUI.
2.2 References
The following references constitute provisions of this Technical Report. At the time of publication, the editions indicated were valid. All references are subject to revision; users of this Technical Report are therefore encouraged to investigate the possibility of applying the most recent edition of the references listed below.
A list of currently valid Broadband Forum Technical Reports is published at www.broadband-forum.org.
NOTE – A number of IETF drafts are cited in this document. Due to the fact that home networking standards and technology are still being rapidly developed, this was considered necessary. If subsequent drafts or RFCs are published, they will obsolete the draft cited in this document.
[1]
3GPP TS
22.011, Service accessibility, 3GPP, 2002
[2]
3GPP TS
23.003, Numbering, addressing and identification, 3GPP,
2006
[3]
3GPP TS
23.122, Non-Access-Stratum (NAS) functions related to Mobile
Station (MS) in idle mode, 3GPP, 2003
[4]
3GPP
TS 23.211, Digital cellular telecommunications system (Phase
2+); Universal Mobile Telecommunications System (UMTS); LTE;
Architectural requirements, 3GPP, 2014
[5]
3GPP TS
23.316, Wireless and wireline convergence access support for the
5G System (5GS), 3GPP SA WG2
[6]
3GPP TS
23.401, General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN)
access, 3GPP, 2013
[7]
3GPP TS
23.501, System architecture for the 5G System (5GS); Stage
2, 3GPP SA WG2
[8]
3GPP TS
23.502, Procedures for the 5G System (5GS), 3GPP SA
WG2
[9]
3GPP TS
23.503, Policy and charging control framework for the 5G System
(5GS); Stage 2, 3GPP CT WG4, 2019
[10]
3GPP TS
24.193, 5G System;Access Traffic Steering, Switching and
Splitting (ATSSS); Stage 3, 3GPP CT WG1
[11]
3GPP TS
24.301, Non-Access-Stratum (NAS) protocol for Evolved Packet
System (EPS); Stage 3, 3GPP, 2013
[12]
3GPP TS
24.501, Non-Access-Stratum (NAS) protocol for 5G System (5GS);
Stage 3, 3GPP CT WG1
[13]
3GPP TS
33.501, Security architecture and procedures for 5G System,
3GPP SA WG3
[14]
3GPP TS
36.300, Evolved Universal Terrestrial Radio Access (E-UTRA) and
Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall
description; Stage 2, 3GPP, 2013
[15]
3GPP
TS 38.300, NR; NR and NG-RAN Overall Description; Stage 2,
3GPP, 2022
[16]
AF-TM-0121.000,
Traffic Management Specification 4.1, ATM Forum, 1999
[17]
G.9700, Fast
access to subscriber terminals (G.fast) - Power spectral density
specification, ITU-T, 2019
[18]
G.9701,
Fast access to subscriber terminals (G.fast)- Physical layer
specification, ITU-T, 2014
[19]
G.9807.1,
10-Gigabit-capable symmetric passive optical network (XGS-PON),
ITU-T, 2016
[20]
G.984.1,
Gigabit-capable Passive Optical Networks (GPON)): General
characteristics, ITU-T, 2003
[21]
G.984.2,
Gigabit-capable Passive Optical Networks (G-PON): Physical Media
Dependent (PMD) layer specification, ITU-T, 2003
[22]
G.984.3,
Gigabit-capable passive optical networks (G-PON): Transmission
convergence layer specification, ITU-T, 2010
[23]
G.987.1,
10-Gigabit-capable passive optical networks (XG-PON): General
requirements, ITU-T, 2016
[24]
G.987.2,
10-Gigabit-capable passive optical networks (XG-PON): Physical media
dependent (PMD) layer specification, ITU-T, 2016
[25]
G.987.3,
10-Gigabit-capable passive optical networks (XG-PON): Transmission
convergence (TC) layer specification, ITU-T, 2014
[26]
G.988,
ONU management and control interface (OMCI) specification,
ITU-T, 2010
[27]
G.992.1, Asymmetric
digital subscriber line (ADSL) transceivers, ITU-T
[28]
G.992.3, Asymmetric
digital subscriber line transceivers 2 (ADSL2), ITU-T
[29]
G.992.5, Asymmetric
Digital Subscriber Line (ADSL) transceivers - Extended bandwidth ADSL2
(ADSL2plus), ITU-T
[30]
G.993.2, Very high
speed digital subscriber line transceivers 2 (VDSL2), ITU-T
[31]
G.9954, Phoneline
networking transceivers - Enhanced physical, media access, and link
layer specifications (HPNA 3.0 and 3.1), ITU-T, 2007
[32]
G.9960,
Unified high-speed wire-line based home networking transceivers -
System architecture and physical layer specification, ITU-T
[33]
G.9961,
Unified high-speed wire-line based home networking transceivers -
Data link layer specification, ITU-T
[34]
G.9964,
Unified high-speed wire-line based home networking transceivers -
Power spectral density specification, ITU-T
[35]
G.997.1, Physical
layer management for digital subscriber line (DSL) transceivers,
ITU-T
[36]
G.998.1, ATM-based
Multi-Pair Bonding, ITU-T, 2005
[37]
G.998.2,
Ethernet-based Multi-Pair Bonding, ITU-T, 2005
[38]
I.610,
B-ISDN operation and maintenance principles and functions,
ITU-T, 1999
[39]
IEEE Std
802.11-2012, IEEE Standard for Information
technology--Telecommunications and information exchange between systems
Local and metropolitan area networks--Specific requirements Part 11:
Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY)
Specifications, IEEE, 2012
[40]
IEEE Std
802.11ax, Enhancements for High Efficiency WLAN, IEEE,
2021
[41]
IEEE Std
802.1Q-2014, IEEE Standard for Local and metropolitan area
networks--Bridges and Bridged Networks, IEEE, 2014
[42]
IEEE Std
802.3-2012, 802.3-2012, IEEE, 2013
[43]
OSGI-CMPN-6, OSGi Core, Release
6, OSGI Alliance, 2014
[44]
RFC 1034,
Domain names - concepts and facilities, IETF, 1987
[45]
RFC 1035,
Domain names - implementation and specification, IETF,
1987
[46]
RFC 1042,
Standard for the transmission of IP datagrams over IEEE 802
networks, IETF, 1988
[47]
RFC 1112,
Host extensions for IP multicasting, IETF, 1989
[48]
RFC 1122,
Requirements for Internet Hosts - Communication Layers, IETF,
1989
[49]
RFC 1123,
Requirements for Internet Hosts - Application and Support,
IETF, 1989
[50]
RFC 1191,
Path MTU discovery, IETF, 1990
[51]
RFC 1256,
ICMP Router Discovery Messages, IETF, 1991
[52]
RFC 1305,
Network Time Protocol (Version 3) Specification, Implementation and
Analysis, IETF, 1992
[53]
RFC 1332, The
PPP Internet Protocol Control Protocol (IPCP), IETF, 1992
[54]
RFC 1812,
Requirements for IP Version 4 Routers, IETF, 1995
[55]
RFC 1918,
Address Allocation for Private Internets, IETF, 1996
[56]
RFC 1928,
SOCKS Protocol Version 5, IETF, 1996
[57]
RFC 1990, The
PPP Multilink Protocol (MP), IETF, 1996
[58]
RFC 2091,
Triggered Extensions to RIP to Support Demand Circuits, IETF,
1997
[59]
RFC 2119, Key
words for use in RFCs to Indicate Requirement Levels, IETF,
1997
[60]
RFC 2131,
Dynamic Host Configuration Protocol, IETF, 1997
[61]
RFC 2132,
DHCP Options and BOOTP Vendor Extensions, IETF, 1997
[62]
RFC 2181,
Clarifications to the DNS Specification, IETF, 1997
[63]
RFC 2225,
Classical IP and ARP over ATM, IETF, 1998
[64]
RFC 2364, PPP
Over AAL5, IETF, 1998
[65]
RFC 2453, RIP
Version 2, IETF, 1998
[66]
RFC 2460,
Internet Protocol, Version 6 (IPv6) Specification, IETF,
1998
[67]
RFC 2473,
Generic Packet Tunneling in IPv6 Specification, IETF,
1998
[68]
RFC 2474,
Definition of the Differentiated Services Field (DS Field) in the
IPv4 and IPv6 Headers, IETF, 1998
[69]
RFC 2475, An
Architecture for Differentiated Services, IETF, 1998
[70]
RFC 2516, A
Method for Transmitting PPP Over Ethernet (PPPoE), IETF, 1999
[71]
RFC 2597,
Assured Forwarding PHB Group, IETF, 1999
[72]
RFC 2661,
Layer Two Tunneling Protocol ‘L2TP’, IETF,
1999
[73]
RFC 2663, IP
Network Address Translator (NAT) Terminology and Considerations,
IETF, 1999
[74]
RFC 2684,
Multiprotocol Encapsulation over ATM Adaptation Layer 5, IETF,
1999
[75]
RFC 2939,
Procedures and IANA Guidelines for Definition of New DHCP Options
and Message Types, IETF, 2000
[76]
RFC 3022,
Traditional IP Network Address Translator (Traditional NAT),
IETF, 2001
[77]
RFC 3027,
Protocol Complications with the IP Network Address Translator,
IETF, 2001
[78]
RFC 3046,
DHCP Relay Agent Information Option, IETF, 2001
[79]
RFC 3145,
L2TP Disconnect Cause Information, IETF, 2001
[80]
RFC 3203,
DHCP reconfigure extension, IETF, 2001
[81]
RFC 3246, An
Expedited Forwarding PHB (Per-Hop Behavior), IETF, 2002
[82]
RFC 3260, New
Terminology and Clarifications for Diffserv, IETF, 2002
[83]
RFC 3261,
SIP: Session Initiation Protocol, IETF, 2002
[84]
RFC 3315,
Dynamic Host Configuration Protocol for IPv6 (DHCPv6), IETF,
2003
[85]
RFC 3376,
Internet Group Management Protocol, Version 3, IETF, 2002
[86]
RFC 3544, IP
Header Compression over PPP, IETF, 2003
[87]
RFC 3550,
RTP: A Transport Protocol for Real-Time Applications, IETF,
2003
[88]
RFC 3579,
RADIUS (Remote Authentication Dial In User Service) Support For
Extensible Authentication Protocol (EAP), IETF, 2003
[89]
RFC 3596, DNS
Extensions to Support IP Version 6, IETF, 2003
[90]
RFC 3633,
IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP)
version 6, IETF, 2003
[91]
RFC 3646, DNS
Configuration options for Dynamic Host Configuration Protocol for IPv6
(DHCPv6), IETF, 2003
[92]
RFC 3810,
Multicast Listener Discovery Version 2 (MLDv2) for IPv6, IETF,
2004
[93]
RFC 3901, DNS
IPv6 Transport Operational Guidelines, IETF, 2004
[94]
RFC 3925,
Vendor-Identifying Vendor Options for Dynamic Host Configuration
Protocol version 4 (DHCPv4), IETF, 2004
[95]
RFC 3931,
Layer Two Tunneling Protocol - Version 3 (L2TPv3), IETF,
2005
[96]
RFC 3947,
Negotiation of NAT-Traversal in the IKE, IETF, 2005
[97]
RFC 3948, UDP
Encapsulation of IPsec ESP Packets, IETF, 2005
[98]
RFC 4072,
Diameter Extensible Authentication Protocol (EAP) Application,
IETF, 2005
[99]
RFC 4075,
Simple Network Time Protocol (SNTP) Configuration Option for
DHCPv6, IETF, 2005
[100]
RFC 4191,
Default Router Preferences and More-Specific Routes, IETF,
2005
[101]
RFC 4193,
Unique Local IPv6 Unicast Addresses, IETF, 2005
[102]
RFC 4213,
Basic Transition Mechanisms for IPv6 Hosts and Routers, IETF,
2005
[103]
RFC 4241, A
Model of IPv6/IPv4 Dual Stack Internet Access Service, IETF,
2005
[104]
RFC 4301,
Security Architecture for the Internet Protocol, IETF,
2005
[105]
RFC 4303, IP
Encapsulating Security Payload (ESP), IETF, 2005
[106]
RFC 4330,
Simple Network Time Protocol (SNTP) Version 4 for IPv4, IPv6 and
OSI, IETF, 2006
[107]
RFC 4361,
Node-specific Client Identifiers for Dynamic Host Configuration
Protocol Version Four (DHCPv4), IETF, 2006
[108]
RFC 4541,
Considerations for Internet Group Management Protocol (IGMP) and
Multicast Listener Discovery (MLD) Snooping Switches, IETF,
2006
[109]
RFC 4605,
Internet Group Management Protocol (IGMP) / Multicast Listener
Discovery (MLD)-Based Multicast Forwarding (‘IGMP/MLD
Proxying’), IETF, 2006
[110]
RFC 4632,
Classless Inter-domain Routing (CIDR): The Internet Address
Assignment and Aggregation Plan, IETF, 2006
[111]
RFC 4638,
Accommodating a Maximum Transit Unit/Maximum Receive Unit (MTU/MRU)
Greater Than 1492 in the Point-to-Point Protocol over Ethernet
(PPPoE), IETF, 2006
[112]
RFC 4681, TLS
User Mapping Extension, IETF, 2006
[113]
RFC 4704, The
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully
Qualified Domain Name (FQDN) Option, IETF, 2006
[114]
RFC 4861,
Neighbor Discovery for IP version 6 (IPv6), IETF, 2007
[115]
RFC 4862,
IPv6 Stateless Address Autoconfiguration, IETF, 2007
[116]
RFC 5072, IP
Version 6 over PPP, IETF, 2007
[117]
RFC 5172,
Negotiation for IPv6 Datagram Compression Using IPv6 Control
Protocol, IETF, 2008
[118]
RFC 5176,
Dynamic Authorization Extensions to Remote Authentication Dial In
User Service (RADIUS), IETF, 2008
[119]
RFC 5280,
Internet X.509 Public Key Infrastructure Certificate and Certificate
Revocation List (CRL) Profile, IETF, 2008
[120]
RFC 5625, DNS
Proxy Implementation Guidelines, IETF, 2009
[121]
RFC 5880,
Bidirectional Forwarding Detection (BFD), IETF, 2010
[122]
RFC 5881,
Bidirectional Forwarding Detection (BFD) for IPv4 and IPv6 (Single
Hop), IETF, 2010
[123]
RFC 5969,
IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol
Specification, IETF, 2010
[124]
RFC 5996,
Internet Key Exchange Protocol Version 2 (IKEv2), IETF,
2010
[125]
RFC 6092,
Recommended Simple Security Capabilities in Customer Premises
Equipment (CPE) for Providing Residential IPv6 Internet Service,
IETF, 2011
[126]
RFC 6106,
IPv6 Router Advertisement Options for DNS Configuration, IETF,
2010
[127]
RFC 6333,
Dual-Stack Lite Broadband Deployments Following IPv4
Exhaustion, IETF, 2011
[128]
RFC 6334,
Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Option for
Dual-Stack Lite, IETF, 2011
[129]
RFC 6422,
Relay-Supplied DHCP Options, IETF, 2011
[130]
RFC 6434,
IPv6 Node Requirements, IETF, 2011
[131]
RFC 6440, The
EAP Re-authentication Protocol (ERP) Local Domain Name DHCPv6
Option, IETF, 2011
[132]
RFC 6696, EAP
Extensions for the EAP Re-authentication Protocol (ERP), IETF,
2012
[133]
RFC 6704,
Forcerenew Nonce Authentication, IETF, 2012
[134]
RFC 6731,
Improved Recursive DNS Server Selection for Multi-Interfaced
Nodes, IETF, 2012
[135]
RFC 6887,
Port Control Protocol (PCP), IETF, 2013
[136]
RFC 6970,
Universal Plug and Play (UPnP) Internet Gateway Device - Port
Control Protocol Interworking Function (IGD-PCP IWF), IETF,
2013
[137]
RFC 7078,
Distributing Address Selection Policy Using DHCPv6, IETF,
2014
[138]
RFC 7291,
DHCP Options for the Port Control Protocol (PCP), IETF,
2014
[139]
RFC 7597,
Mapping of Address and Port with Encapsulation (MAP-E), IETF,
2015
[140]
RFC 7598,
DHCPv6 Options for Configuration of Softwire Address and Port-Mapped
Clients, IETF, 2015
[141]
RFC 7648,
Port Control Protocol (PCP) Proxy Function, IETF, 2015
[142]
RFC 768, User
Datagram Protocol, IETF, 1980
[143]
RFC 7753,
Port Control Protocol (PCP) Extension for Port-Set Allocation,
IETF, 2016
[144]
RFC 791,
Internet Protocol, IETF, 1981
[145]
RFC 792,
Internet Control Message Protocol, IETF, 1981
[146]
RFC 793,
Transmission Control Protocol, IETF, 1981
[147]
RFC 826, An
Ethernet Address Resolution Protocol: Or Converting Network Protocol
Addresses to 48.bit Ethernet Address for Transmission on Ethernet
Hardware, IETF, 1982
[148]
RFC 8822, 5G
Wireless Wireline Convergence User Plane Encapsulation (5WE), IETF,
2021
[149]
RFC 894, A
Standard for the Transmission of IP Datagrams over Ethernet
Networks, IETF, 1984
[150]
RFC 922,
Broadcasting Internet datagrams in the presence of subnets,
IETF, 1984
[151]
RFC 950,
Internet Standard Subnetting Procedure, IETF, 1985
[152]
T1.413-1998,
Telecommunications - Network and Customer Installation Interfaces -
Asymmetric Digital Subscriber Line (ASDL) Metallic Interface, ANSI,
1998
[153]
T1.413a-2001,
Supplement To T1.413-1998 - Network And Customer Installation
Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic
Interface, ANSI, 2001
[154]
T1.421-2001,
In-Line Filter For Use With Voiceband Terminal Equipment Operating
On The Same Wire Pair With High Frequency (Up To 12 MHz) Devices,
ANSI, 2001
[155]
T1.427.01-2004,
ATM-Based Multi-Pair Bonding, ANSI, 2004
[156]
T1.427.02-2005,
Ethernet-Based Multi-Pair Bonding, ANSI, 2005
[157]
TR-062,
Auto-Config for the Connection Between the DSL Broadband Network
Termination (B-NT) and the Network using ATM (TR-037 update),
Broadband Forum, 2003
[158]
TR-064
Issue 2, LAN-Side CPE Configuration, Broadband Forum,
2015
[159]
TR-067 Issue
2, ADSL Interoperability Test Plan, Broadband Forum,
2004
[160]
TR-069
Amendment 6, CPE WAN Management Protocol, Broadband Forum,
2018
[161]
TR-101 Issue
2, Migration to Ethernet-Based Broadband Aggregation,
Broadband Forum, 2011
[162]
TR-114 Issue
3, VDSL2 Performance Test Plan, Broadband Forum, 2018
[163]
TR-115 Issue
3, VDSL2 Functionality Test Plan, Broadband Forum,
2019
[164]
TR-122,
Base Requirements for Consumer-Oriented Analog Terminal Adapter
Functionality, Broadband Forum, 2006
[165]
TR-142,
Framework for TR-069 enabled PON devices, Broadband Forum,
2017
[166]
TR-156 Issue
4, Using GPON Access in the context of TR-101, Broadband
Forum, 2017
[167]
TR-181 Issue 2,
Device Data Model for CWMP Endpoints and USP Agents, Broadband
Forum, 2022
[168]
TR-328,
Virtual Business Gateway, Broadband Forum, 2017
[169]
TR-369 Issue 1 Amendment
2, User Services Platform, Broadband Forum, 2022
[170]
TR-456 Issue
2, AGF Functional Requirements, Broadband Forum, 2022
[171]
TR-470,
5G Wireless Wireline Convergence Architecture, Broadband Forum,
2020
The following information is given for the convenience of users of this Technical Report and does not constitute an endorsement by the Broadband Forum of these products:
Safari® is a registered trademark of Apple Computer, Inc.
HomePlug® is a registered trademark of HomePlug Powerline Alliance, Inc.
HomePNA® is a registered trademark of HomePNA, Inc.
IEEE® is a registered trademark of the Institute of Electrical and Electronics Engineers, Inc. (IEEE). This publication is not endorsed by the IEEE.
Internet Explorer® and Microsoft® are registered trademarks of Microsoft Corporation.
Java® and JavaScript® are registered trademarks of Oracle, Inc.
Mozilla® is a registered trademark of the Mozilla Foundation.
Wi-Fi® is a registered trademark of the Wi-Fi Alliance
WPA, WPA2,WPA3, Protected Setup, WMM and WMM-SA are trademarks of the Wi-Fi Alliance
2.3 Definitions
| Term | Definition |
|---|---|
| 5G-RG | An RG acting as UE with regard to the 5G core. It holds a secure element and exchanges NAS signaling with the 5G core. |
| 5G Access Network (5GAN) | This comprises 5G radio ANs (RANs) and 5G wireline ANs connecting to a 5G core. |
| 5G System (5GS) | A system consisting of 5G Access Network (AN), 5G Core Network and end-device. |
| Access & Mobility Function (AMF) | The AMF is a 5GC-CP function that terminates N1, the control interface with UEs, and N2, the control interface with access networks. It is responsible for mobility & access related functions. It acts as the security anchor point for a given UE. At PDU session establishment, it selects the SMF corresponding to the requested slice and targeted DN, and relays session related messages to this SMF. |
| ACS | Auto-Configuration Server. This is a component in the broadband network responsible for CWMP auto-configuration of the CPE for advanced services. |
| Agent | A generic term that refers (as appropriate) to either a CWMP Endpoint or to a USP Agent. |
| Allowed NSSAI | NSSAI provided by the serving PLMN network during e.g. a registration procedure, indicating the S-NSSAIs value that the UE could use in the serving PLMN of the current registration area. (definition from TS 23.501 [x]) |
| Backup | The ability to take over a task when a
source becomes unavailable. Examples: - A web server becomes unavailable. For incoming traffic, backup provides another web server to take over the operation. - A communication link becomes unavailable. Via backup, another link takes over the communication task. |
| Configurable | A requirement for configurability does not imply any particular configuration interface. When specific user or TR-069 or other configurability is required, the requirement is stated explicitly. |
| Configured NSSAI | An NSSAI that has been provisioned in the 5G-RG applicable to one or more PLMN (definition from TS 23.501 [7]). |
| Connection | As used in this document, a connection is the continuing ability to communicate over a pair of IP addresses. |
| Controller | A generic term that refers (as appropriate) to either a CWMP ACS or a USP Controller. |
| CPE | Customer Premises Equipment; refers (as appropriate) to any CWMP-enabled or USP-enabled device and therefore covers both Internet Gateway devices and LAN-side end devices. |
| CWMP | CPE WAN Management Protocol. Defined in TR-069 [160], CWMP is a communication protocol between an ACS and CWMP-enabled CPE that defines a mechanism for secure auto-configuration of a CPE and other CPE management functions in a common framework. |
| CWMP Endpoint | A CWMP termination point used by a CWMP-enabled CPE for communication with the ACS. |
| Device | Unless otherwise qualified, the term device refers to an RG. |
| Enabling | Likewise, controllability requirements, for example to enable or disable a feature, do not imply a control interface. |
| Failover | The ability to automatically switch to
another source when a source becomes unavailable. Examples: - A web server becomes unavailable. For incoming traffic, failover automatically provides another web server to take over the operation. - A communication link becomes unavailable. Via failover, another link automatically takes over the communication task. |
| GUI | The term GUI or web GUI implies access to the RG that is visible to the end user. The use of this term in a requirement is an assertion that control or information display is available to the end user. |
| Load balancing | The ability to divide the working load of
a task over multiple sources in an equal way. Examples: - A web service that is run by a web server. For incoming traffic this can be equally divided over multiple servers by a load balancer. - A communication link that is supporting a communication task. Various links can be used to equally divide the communication load by a load balancer. This can be for incoming and outgoing traffic. Thus, load balancing is only one form of load sharing: load balancing is load sharing where the load is equally divided over the sources. What defines “equal” depends on the use case and metrics used. |
| Load sharing | The ability to divide the working load of
a task over multiple sources. Examples: - A web service that is run by a web server. For incoming traffic this can be divided over multiple servers by load sharing. - A communication link that is supporting a communication task. Various links can be used to divide the communication load by load sharing. This can be for incoming and outgoing traffic. |
| Logs | Likewise, requirements for logging do not imply log configurability and retrieval on any particular interface unless stated explicitly. |
| Network Instance | Information identifying a domain. Used by the UPF for traffic detection and routing (definition from TS 23.501 [7]). |
| Network Slice | A logical network that provides specific network capabilities and network characteristics (definition from TS 23.501 [7]). |
| Network Slice Instance | A set of Network Function instances and the required resources (e.g. compute, storage and networking resources) which form a deployed Network Slice (definition from TS 23.501 [x]). |
| NSI ID | An identifier for a Network Slice instance (definition from TS 23.501 [7]). |
| Network Slice Selection Assistance Information (NSSAI) | The NSSAI is a collection of S-NSSAIs. An NSSAI may be a Configured NSSAI, a Requested NSSAI or an Allowed NSSAI. There can be at most eight S-NSSAIs in Allowed and Requested NSSAIs sent in signaling messages between the UE and the Network. |
| NSSP (Network Slice Selection Policy) | It is the set of SM-NSSAI that a UE is authorized to access. It is stored in the UE and corresponds to the NSSAI in the subscriber information in the network database. |
| Operator-specific configuration | Many requirements specify defaults, but then add the phrase, “or use an operator-specific configuration.” This phrase recognizes that operators may override TR-124 requirements when necessary to satisfy their specific needs. |
| PDU session | Temporal association between the UE and a Data Network that provides a PDU connectivity service. A session can be IP, Eth or unstructured. |
| Requested NSSAI | NSSAI provided by the UE to the Serving PLMN during registration (definition from TS 23.501 [7]). |
| RG | A residential gateway (RG) is a device that interfaces between the WAN and LAN IP environment for a consumer broadband customer. It may route or bridge traffic, depending on its configuration and specifications. The term RG is retained for historical continuity, even though some features may be directed at business applications. |
| Smart RG | A smart residential gateway is a residential gateway with additional smart home services. |
| Software application | A Software application consists of one or more software modules and configuration data, and provides specific function(s) using the open platform API of a Smart RG. |
| Software module | An installable software entity which includes executables, libraries, configuration and other data. |
| Subscribed S-NSSAI | S-NSSAI based on subscriber information, which a UE is subscribed to use in a PLMN (definition from TS 23.501 [7]). |
| USP | Universal Service Platform. Defined in TR-369 [169], USP is an evolution of CWMP that allows applications to manipulate Service Elements in a network of Controllers and Agents. |
| USP Agent | A USP Agent is a USP Endpoint that exposes Service Elements to one or more USP Controllers |
| USP Controller | A USP Controller is a USP Endpoint that manipulates Service Elements through one or more USP Agents. |
| Wireline 5G Access Network (W-5GAN) | This is a wireline AN that can connect to a 5G core via the AGF. The egress interfaces of a W-5GAN form the border between access and core. They are N2 for the control plane and N3 for the user plane. |
2.4 Abbreviations
This Technical Report defines the following abbreviations:
| 5WE | 5G WWC Encapsulation |
|---|---|
| AAA | Authentication, Authorization and Accounting |
| AAL | ATM Adaptation Layer |
| ac | alternating current |
| ADSL | Asynchronous Digital Subscriber Line |
| AFTR | Address family transition router |
| AGF | Access Gateway Function |
| ALG | Application Layer Gateway |
| AMF | Access Management Function |
| AN | Access Network |
| ANSI | American National Standards Institute |
| AS | Access Stratum |
| ASCII | American Standard Code for Information Interchange |
| ATA | Analog Terminal Adapter |
| ATM | Asynchronous Transfer Mode |
| BFD | Bidirectional forwarding detection |
| CP | Control Plane |
| CPE | Customer Premises Equipment |
| CRC | Cyclic Redundancy Check |
| CSA | Canadian Standards Association |
| DAD | Duplicate address detection |
| DHCP | Dynamic Host Configuration Protocol |
| DLNA | Digital living network alliance (www.dlna.org) |
| DNS | Domain Name Server |
| DoS | Denial of Service |
| DSCP | Differentiated Services Code Point |
| DSL | Digital Subscriber Line |
| DUID | DHCP Unique Identifier |
| DUID-EN | DUID based Enterprise Number |
| FCC | Federal Communications Commission |
| FQDN | Fully Qualified Domain Name |
| GMT | Greenwich Mean Time |
| GUI | Graphical User Interface |
| HTML | Hypertext Markup Language |
| HTTP | Hypertext Transfer Protocol |
| HTTPS | Secure Hypertext Transfer Protocol |
| Hz | Hertz |
| IAID | Identification Association Identifier |
| IEEE® | The Institute of Electrical and Electronics Engineers |
| IETF | The Internet Engineering Task Force |
| IMEI | International Mobile Equipment Identity |
| IMSI | International Mobile Subscriber Identity |
| INP | Impulse noise protection |
| IP | Internet Protocol |
| IPCP | Internet Protocol Control Protocol |
| ISO | International Organization for Standardization |
| ITU | International Telecommunication Union |
| Kbps | kilobits per second |
| LAN | Local Area Network |
| LCP | Link Control Protocol |
| LPF | Low-pass filter |
| MAC | Medium Access Control |
| MRU | Maximum Receive Unit |
| ms | millisecond |
| MTBF | Mean Time Between Failure |
| MTU | Maximum Transit Unit |
| NAS | Non-Access Stratum |
| NAT | Network Address Translation |
| NTP | Network Time Protocol |
| ONU | Optical Network Unit |
| PADI | PPPoE Active Discovery Initiation |
| PADO | PPPoE Active Discovery Offer |
| PC | Personal Computer |
| PCP | Priority Code Point |
| PD | Prefix Delegation |
| PDU | Protocol Data Unit |
| POTS | Plain Old Telephone Service |
| PPP | Point to Point Protocol |
| PVC | Permanent Virtual Circuit |
| QFI | QoS Flow Identifier |
| RA | Router Advertisement |
| RG | Residential Gateway |
| RQI | Reflective QoS Indication |
| RTSP | Real time streaming protocol |
| SIP | Session Initiation Protocol |
| SN | Serial Number |
| SNTP | Simple Network Time Protocol |
| SSL | Secure Sockets Layer |
| SUCI | Subscriber Concealed Identifier |
| SUPI | Subscriber Permanent Identifier |
| TCP | Transmission Control Protocol |
| TLS | Transport Layer Security |
| TR | Technical Report |
| UDP | User Datagram Protocol |
| UE | User Equipment |
| UL | Underwriters Laboratories |
| ULA | User licensing agreement |
| ULC | Underwriters Laboratories Canada |
| UP | User Plane |
| URSP | UE Route Selection Policy |
| USB | Universal Serial Bus |
| Vac | Volts ac |
| VCI | Virtual Circuit Identifier |
| Vdc | Volts dc |
| VDSL | Very high-speed Digital Subscriber Line |
| VID | VLAN Identifier |
| VLAN | Virtual LAN |
| VoIP | Voice over IP |
| VPI | Virtual Path Identifier |
| VSO | Vendor Specific Option |
| WAN | Wide Area Network |
| WEP | Wireless Encryption Protocol |
| Wi-Fi® | Wi-Fi Alliance wireless standards organization |
| WPA | Wi-Fi Protected Access |
| WWC | Wireline Wireless Convergence |