Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.316  Word version:  18.5.0

Top   Top   None   None   Next
1…   4…   4.5…   4.7…   4.10…   4.10b…   4.11…   5…   6…   7…   7.2.2…   7.2.3…   7.2.4…   7.3…   7.6…   7.7…   8…   9…   9.5…   10…   A…

 

1  Scopep. 8

The present document defines the enhancements to Stage 2 system architecture, procedure and flows, Policy and Charging Control for the 5G System defined in TS 23.501, TS 23.502 and TS 23.503 in order to support wireline access network and Fixed Wireless Access. The specifications defined in TS 23.501, TS 23.502 and TS 23.503 apply to the wireline access network and Fixed Wireless Access.
Up

2  Referencesp. 8

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]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[3]
TS 23.502: "Procedures for the 5G system, Stage 2".
[4]
TS 23.503: "Policy and Charging Control Framework for the 5G System".
[5]
BBF TR-124 issue 5: "Functional Requirements for Broadband Residential Gateway Devices".
[6]
BBF TR-101 issue 2: "Migration to Ethernet-Based Broadband Aggregation".
[7]
BBF TR-178 issue 1: "Multi-service Broadband Network Architecture and Nodal Requirements".
[8]
CableLabs DOCSIS MULPI: "Data-Over-Cable Service Interface Specifications DOCSIS 3.1, MAC and Upper Layer Protocols Interface Specification".
[9]
BBF TR-456 issue 2: "AGF Functional Requirements".
[10]
BBF WT-457: "FMIF Functional Requirements".
[11]
TS 33.501: "Security architecture and procedures for 5G System".
[12]
BBF TR-177 Issue 1 Corrigendum 1: "IPv6 in the context of TR-101".
[13]
RFC 6788:  "The Line-Identification Option".
[14]
TS 23.003: "Numbering, Addressing and Identification".
[15]  Void.
[16]
RFC 6603:  "Prefix Exclude Option for DHCPv6-based Prefix Delegation".
[17]  Void.
[18]
BBF TR-069: "CPE WAN Management Protocol".
[19]
BBF TR-369: "User Services Platform (USP)".
[20]
RFC 3046:  "DHCP Relay Agent Information Option".
[21]
RFC 4604:  "Using Internet Group Management Protocol Version 3 (IGMPv3) and Multicast Listener Discovery Protocol Version 2 (MLDv2) for Source-Specific Multicast".
[22]
TR 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[23]
TS 38.413: "NG RAN; NG Application Protocol (NGAP)".
[24]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[25]
TS 22.011: "Service accessibility".
[26]
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[27]
CableLabs WR-TR-5WWC-ARCH: "5G Wireless Wireline Converged Core Architecture".
[28]
RFC 3376:  "Internet Group Management Protocol, Version 3".
[29]
TS 23.273: "5G System (5GS) Location Services (LCS)".
[30]
BBF TR-198: "DQS:DQM systems functional architecture and requirements".
[31]
TS 23.203: "Policy and charging control architecture".
[32]
TS 33.126: "Lawful Interception Requirements".
[33]
RFC 2236:  "Internet Group Management Protocol, Version 2".
[34]
RFC 4861:  "Neighbor Discovery for IP version 6 (IPv6)".
[35]
RFC 1112:  "Internet Group Management Protocol".
[36]
RFC 2710:  "Multicast Listener Discovery Version for IPv6".
[37]
RFC 2010:  "Operational Criteria for Root Name Servers".
[38]
BBF TR-470: "5G FMC architecture".
[39]
TS 29.519: "Policy Data, Application Data and Structured Data for exposure".
[40]
TS 23.041: "Public Warning System".
[41]
IEEE Publication (2017): "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)". https://standards.ieee.org/content/dam/ieee-standards/standards/web/documents/tutorials/eui.pdf.
[42]
TS 29.413: "Application of the NG Application Protocol (NGAP) to non-3GPP access".
[43]  Void.
[44]
TS 24.502: "Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks".
[45]
TS 23.402: " Architecture enhancements for non-3GPP accesses".
[46]
BBF TR-181: "Device Data Model for TR-069".
[47]
RFC 8415:  "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)".
Up

3  Definitions and abbreviationsp. 10

3.1  Definitionsp. 10

For the purposes of the present document, the terms and definitions given in TR 21.905, TS 23.501 , TS 23.502 and TS 23.503 apply. A term defined in TS 23.501, TS 23.502 or TS 23.503 takes precedence over the definition of the same term, if any, in any other specifications.
RG Level Wireline Access Characteristics:
Wireline access technology specific QoS information corresponding to a specific wireline access subscription, which is provided by the AMF to the W-AGF at RG registration.
Wireline access Control Plane protocol (W-CP):
Protocol used to transport AS and NAS signalling between the 5G-RG and the W-AGF over the Y4 reference point. W-CP is specified by BBF and CableLabs. There is no assumption that W-CP refers to only a single protocol or only a specific protocol layer.
Wireline access User Plane protocol (W-UP):
Protocol used to carry PDU Session user plane traffic between the 5G-RG and the W-AGF over the Y4 reference point. W-UP is specified by BBF and CableLabs. There is no assumption that W-UP refers to only a single protocol or only a specific protocol layer.
Legacy Wireline access Control Plane protocol (L-W-CP):
L-W-CP is a legacy control plane protocol between the FN-RG and W-AGF. L-W-CP is specified by BBF and CableLabs. There is no assumption that L-W-CP refers to only a single protocol or only a specific protocol layer.
Legacy Wireline access User Plane protocol (L-W-UP):
L-W-UP is a legacy user plane protocol between the FN-RG and W-AGF. W-UP is specified by BBF and CableLabs. There is no assumption that L-W-UP refers to only a single protocol or only a specific protocol layer.
Authenticable Non-3GPP (AUN3) device:
A device that does not support NAS signalling, is connected to 5GC via a RG and can be authenticated by 5GC over the RG.
5GS specifications do not support a device using the same subscription to access 5GS as a UE and as an AUN3 device.
Non-Authenticable Non-3GPP (NAUN3) device:
A device that does not support NAS signalling, is connected to 5GC via a RG and for which authentication with 5GC is not supported.
Up

3.2  Abbreviationsp. 10

For the purposes of the present document, the abbreviations given in TR 21.905, TS 23.501, TS 23.502 and TS 23.503 apply. An abbreviation defined in TS 23.501, TS 23.502 or TS 23.503 takes precedence over the same abbreviation, if any, in any other specifications.
5G-RG
5G Residential Gateway
5G-BRG
5G Broadband Residential Gateway
5G-CRG
5G Cable Residential Gateway
ACS
Auto-Configuration Server
FN-RG
Fixed Network RG
FN-BRG
Fixed Network Broadband RG
FN-CRG
Fixed Network Cable RG
FWA
Fixed Wireless Access
IGMP
Internet Group Management Protocol
L-W-CP
Legacy Wireless access Control Plane Protocol
L-W-UP
Legacy Wireless access User Plane Protocol
MLD
Multicast Listener Discovery
RG
Residential Gateway
RG-LWAC
RG Level Wireline Access Characteristics
SNPN
Stand-alone Non Public Network
USP
User Services Platform
W-5GAN
Wireline 5G Access Network
W-5GCAN
Wireline 5G Cable Access Network
W-5GBAN
Wireline BBF Access Network
W-CP
Wireline access Control Plane protocol
W-UP
Wireline access User Plane protocol
Up

Up   Top   ToC