Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.501  Word version:   16.4.0

Top   Up   Prev   Next
1…   3…   4…   4.2.4   4.2.5…   4.2.8…   4.2.8.2.2   4.2.8.2.3…   4.2.8.4…   4.2.9…   4.3…   4.3.3   4.3.4   4.3.5   4.4…   4.4.6…   4.4.8   5…   5.3…   5.3.3…   5.4…   5.5…   5.6…   5.6.7…   5.7…   5.7.2…   5.7.3…   5.7.4   5.7.5…   5.8…   5.8.2.11…   5.9…   5.10…   5.11…   5.15…   5.16…   5.17…   5.18…   5.19…   5.21…   5.22…   5.27…   5.28…   5.29…   5.30…   5.31…   5.32…   5.33…   5.34…   5.35…   6…   6.3…   7…   7.2…   8…   8.2.4   8.2.5…   8.3…   A…   D…   E…   F   G…   G.3   G.4…   J…

 

5.28  Support of integration with TSN [R16]Word-p. 266
5.28.1  5GS TSN bridge management
5GS functions acts as one or more TSN Bridges of the TSN network. The 5GS Bridge is composed of the ports on a single UPF (i.e. PSA) side, the user plane tunnel between the UE and UPF, and the ports on the DS-TT side. For each 5GS Bridge of a TSN network, the ports on NW-TT support the connectivity to the TSN network, the ports on DS-TT side are associated to the PDU Session providing connectivity to the TSN network.
The granularity of the 5GS TSN bridge is per UPF. The bridge ID of the 5GS TSN bridge is bound to the UPF ID of the UPF as identified in TS 23.502. The TSN AF stores the binding relationship between a port on UE/DS-TT side and a PDU Session during reporting of 5GS TSN bridge information. The TSN AF also stores the information about ports on the UPF/NW-TT side. The UPF/NW-TT forwards traffic to the appropriate egress port based on the traffic forwarding information.
There is only one PDU Session per DS-TT port for a given UPF. All PDU Sessions which connect to the same TSN network via a specific UPF are grouped into a single 5GS bridge. The capabilities of each port on UE/DS-TT side and UPF/NW-TT side are integrated as part of the configuration of the 5GS Bridge and are notified to TSN AF and delivered to CNC for TSN bridge registration and modification.
NOTE 1:
It is assumed that all PDU sessions which connect to the same TSN network via a specific UPF are handled by the same TSN AF.
Up
NOTE 2:
If a UE establishes multiple PDU Sessions terminating in different UPFs, then the UE is represented by multiple 5GS TSN bridges.
In order to support TSN traffic scheduling over 5GS Bridge, the 5GS supports the following functions:
  • Configuring the bridge information in 5GS as defined at clause 5.28.2.
  • Report the bridge information of 5GS Bridge to TSN network after PDU session establishment.
  • Map the configuration information obtained from TSN network into 5GS QoS information (e.g. 5QI, TSC Assistance Information) of a QoS Flow in corresponding PDU Session for efficient time-aware scheduling, as defined at clause 5.28.2.
The bridge information of 5GS Bridge is used by the TSN network to make appropriate management configuration for the 5GS Bridge. The bridge information of 5GS Bridge includes at least the following:
  • Information for 5GS Bridge:
  • Bridge Address (unique MAC address that identifies the bridge used to derive the bridge ID);
  • Bridge Name;
  • Number of Ports;
  • list of port numbers.
  • Capabilities of 5GS Bridge as defined in 802.1Qcc [95]:
  • 5GS Bridge delay per port pair per traffic class, including 5GS Bridge delay (dependent and independent of frame size, and their maximum and minimum values: independentDelayMax, independentDelayMin, dependentDelayMax, dependentDelayMin), ingress port number, egress port number and traffic class.
  • Propagation delay per port (txPropagationDelay), including transmission propagation delay, egress port number.
  • Topology of 5GS Bridge as defined in IEEE 802.1AB [97]:
    • Chassis ID subtype and Chassis ID of the 5GS Bridge.
  • Traffic classes and their priorities per port as defined in IEEE 802.1Q [98].
  • Stream Parameters as defined in clause 12.31.1 in IEEE 802.1Q [98], in order to support PSFP information:
  • Maximum number of filters, which defines the maximum number of streams that the bridge can handle;
  • Maximum number of gates, which can be equal or less than the maximum number of filters;
  • Maximum number of meters (optional) if meassurements are required;
  • Maximum length of the PSFPAdminControlList parameter that can be handled.
The following parameters: independentDelayMax and independentDelayMin, how to calculate them is left to implementation and not defined in this specification.
Bridge ID of the 5GS Bridge, port numbers of the Ethernet port in NW-TT could be preconfigured on the UPF. The UPF is selected for a PDU Session serving TSC based on subscribed DNN, traffic classes and VLANs. Port number of Ethernet port on the DS-TT for the PDU Session is assigned by the UPF during PDU session establishment. The port number of the DS-TT Ethernet port for a PDU Session shall be reported to the SMF from the UPF and further stored at the SMF. SMF provides the port numbers and MAC addresses of the Ethernet ports in DS-TT of the related PDU session and port numbers and MAC addresses of the Ethernet ports in NW-TT to the TSN AF via PCF. If a PDU session for which SMF has reported port numbers to TSN AF is released, then SMF informs TSN AF accordingly.
The TSN AF is responsible to receive the bridge information of 5GS Bridge from 5GS, as well as register or update this information to the TSN network.
Up
5.28.2  5GS Bridge configurationWord-p. 267
In order to schedule TSN traffic over 5GS Bridge, the configuration information of 5GS Bridge is mapped to 5GS QoS within the corresponding PDU Session. The QoS parameters mapping for TSN is described in TS 23.503, clause 6.1.3.23.
The configuration information of 5GS Bridge as defined in IEEE 802.1Q [98], includes the following:
  • Bridge ID of 5GS Bridge.
  • Configuration information of scheduled traffic on ports of DS-TT and NW-TT:
  • Egress ports of 5GS Bridge, e.g., ports on DS-TT and NW-TT;
  • Traffic classes and their priorities.
NOTE 1:
In this Release of the specification, only support simplified IEEE 802.1Q [98], Annex Q.2 for 5GS.
The configuration information of 5GS Bridge as defined in IEEE 802.1Q [98], includes the following:
  • Chassis ID of 5GS Bridge;
  • Traffic forwarding information as defined in IEEE 802.1Q [98] clause 8.8.1:
    • Destination MAC address and VLAN ID of TSN stream;
    • Port number in the Port MAP as defined in IEEE 802.1Q [98] clause 8.8.1.
  • Configuration information per stream according to IEEE 802.1Q [98] clause 8.6.5.1:
    • Ingress port number of 5GS Bridge, i.e., ports on DS-TT/NW-TT;
    • Stream priority.
NOTE 2:
In order to support IEEE 802.1Q [98] clause 8.6.5.1, it is required to support the Stream Identification function as specified by IEEE 802.1CB-2017 [83].
The SMF report the MAC address of the DS-TT port of the related PDU Session to TSN AF via PCF as the MAC address of the PDU Session. The association between the MAC address used by the PDU Session, 5GS Bridge ID and port number on DS-TT is maintained at TSN AF and further used to assist to bind the TSN traffic with the UE's PDU session.
In the case of provisioning traffic forwarding information, the TSN AF determines the DS-TT MAC address used by the PDU Session for the TSN traffic based on the DS-TT port number in the traffic forwarding information. The TSN AF uses the traffic forwarding information received from the CNC to determine the destination MAC addresses and corresponding egress ports, and requests the PCF to reserve resources for an AF session with support for Time Sensitive Networking (TSN) as defined in clause 6.1.3.23 in TS 23.503.
With the Traffic forwarding information as defined in IEEE 802.1Q [98] clause 8.8.1 and PSFP information as defined in IEEE 802.1Q [98] clause 8.6.5.1, the TSN AF identifies the ingress port and egress port for a stream and derives the DS-TT MAC address of corresponding PDU session carrying this stream. The TSN AF uses PSFP information as defined in IEEE 802.1Q [98] clause 8.6.5.1 to derive the TSN QoS information for UL traffic.
Up
5.28.3  Port management information exchange in 5GSWord-p. 268
5.28.3.1  General
Bridge management information is exchanged between CNC and TSN AF. A subset of bridge management information, referred to as port management information, is related to Ethernet ports located in DS-TT or NW-TT.
5GS shall support transfer of standardized and deployment-specific port management information transparently between TSN AF and DS-TT or NW-TT, respectively inside a Port Management Information Container. Table 5.28.3.1-1 lists standardized port management information.
Port management information
Applicability (see Note 6)
DS-TT
NW-TT
Supported operations by TSN AF (see Note 1)
Reference

General
Port management capabilities (see Note 2)
X
X
R

Bridge delay related information
txPropagationDelay
X
X
R
IEEE 802.1Qcc [95] clause 12.32.2.1

Traffic class related information
Traffic class table
X
X
RW
IEEE 802.1Q [98] clause 12.6.3 and clause 8.6.6.

Gate control information
GateEnabled
X
X
RW
IEEE 802.1Q [98] Table 12-29
AdminBaseTime
X
X
RW
IEEE 802.1Q [98] Table 12-29
AdminControlList
X
X
RW
IEEE 802.1Q [98] Table 12-29
AdminCycleTime (see Note 3)
X
X
RW
IEEE 802.1Q [98] Table 12-29
AdminControlListLength (see Note 3)
X
X
RW
IEEE 802.1Q [98] Table 12-28
Tick granularity
X
X
R
IEEE 802.1Q [98] Table 12-29

Traffic forwarding information
Static Filtering Entry (NOTE 7)
X
RW
IEEE 802.1Q [98] clause 8.8.1

General Neighbor discovery configuration (NOTE 4)
adminStatus
D
X
RW
IEEE 802.1AB [97] clause 9.2.5.1
lldpV2LocChassisIdSubtype
D
X
RW
IEEE 802.1AB [97] Table 11-2
lldpV2LocChassisId
D
X
RW
IEEE 802.1AB [97] Table 11-2
lldpV2MessageTxInterval
D
X
RW
IEEE 802.1AB [97] Table 11-2
lldpV2MessageTxHoldMultiplier
D
X
RW
IEEE 802.1AB [97] Table 11-2

NW-TT port neighbor discovery configuration
lldpV2LocPortIdSubtype
X
RW
IEEE 802.1AB [97] Table 11-2
lldpV2LocPortId
X
RW
IEEE 802.1AB [97] Table 11-2

DS-TT port neighbor discovery configuration
lldpV2LocPortIdSubtype
D
N
RW
IEEE 802.1AB [97] Table 11-2
lldpV2LocPortId
D
N
RW
IEEE 802.1AB [97] Table 11-2

Neighbor discovery information for each discovered neighbor of NW-TT
lldpV2RemChassisIdSubtype
X
R
IEEE 802.1AB [97] Table 11-2
lldpV2RemChassisId
X
R
IEEE 802.1AB [97] Table 11-2
lldpV2RemPortIdSubtype
X
R
IEEE 802.1AB [97] Table 11-2
lldpV2RemPortId
X
R
IEEE 802.1AB [97] Table 11-2
TTL
X
R
IEEE 802.1AB [97] clause 8.5.4

Neighbor discovery information for each discovered neighbor of DS-TT (NOTE 5)
lldpV2RemChassisIdSubtype
D
N
R
IEEE 802.1AB [97] Table 11-2
lldpV2RemChassisId
D
N
R
IEEE 802.1AB [97] Table 11-2
lldpV2RemPortIdSubtype
D
N
R
IEEE 802.1AB [97] Table 11-2
lldpV2RemPortId
D
N
R
IEEE 802.1AB [97] Table 11-2
TTL
D
N
R
IEEE 802.1AB [97] clause 8.5.4.1

Per-Stream Filtering and Policing information (NOTE 10)
Stream Filter Instance Table (NOTE 8)
IEEE 802.1Q [98] Table 12-32
StreamHandleSpec
X
X
RW
IEEE 802.1Q [98] Table 12-32
PrioritySpec
X
X
RW
IEEE 802.1Q [98] Table 12-32
StreamGateInstanceID
X
X
RW
IEEE 802.1Q [98] Table 12-32
Stream Gate Instance Table (NOTE 9)
IEEE 802.1Q [98] Table 12-33
StreamGateInstance
X
X
R
IEEE 802.1Q [98] Table 12-33
PSFPAdminBaseTime
X
X
RW
IEEE 802.1Q [98] Table 12-33
PSFPAdminControlList
X
X
RW
IEEE 802.1Q [98] Table 12-33
PSFPAdminCycleTime
X
X
RW
IEEE 802.1Q [98] Table 12-33
PSFPTickGranularity
X
X
R
IEEE 802.1Q [98] Table 12-33

NOTE 1:
R = Read only access; RW = Read/Write access.
NOTE 2:
Indicates which standardized and deployment-specific port management information is supported by DS-TT or NW-TT.
NOTE 3:
AdminCycleTime and AdminControlListLength are optional for gate control information.
NOTE 4:
If DS-TT supports neighbor discovery, then TSN AF sends the general neighbor discovery configuration for DS-TT Ethernet ports to DS-TT. If DS-TT does not support neighbor discovery, then TSN AF sends the general neighbor discovery configuration for DS-TT Ethernet ports to NW-TT and NW-TT performs neighbor discovery on behalf on DS-TT.
NOTE 5:
If DS-TT supports neighbor discovery, then TSN AF retrieves neighbor discovery information for DS-TT Ethernet ports from DS-TT. If DS-TT does not support neighbor discovery, then TSN AF retrieves neighbor discovery information for DS-TT Ethernet ports from NW-TT, which performs neighbor discovery on behalf on DS-TT.
NOTE 6:
X = applicable; D = applicable when validation and generation of LLDP frames is processed at the DS-TT; N = applicable when validation and generation of LLDP frames is processed centrally at NW-TT.
NOTE 7:
NW-TT uses Static Filtering Entry information to determine the NW-TT egress port for forwarding UL TSC traffic.
NOTE 8:
There is a Stream Filter Instance Table per Stream.
NOTE 9:
There is a Stream Gate Instance Table per Gate.
NOTE 10:
The use of PSFP information is mandatory at the TSN AF and is optional at both DS-TT and NW-TT. TSN AF uses the PSFP information at TSN bridge configuration time to identify the DS-TT MAC address of the PDU Session as described in clause 5.28.2 and for determination of the TSCAI information as described in Annex I. The PSFP information can be used at the DS-TT (if supported) and at the NW-TT (if supported) for the purpose of per-stream filtering and policing as defined in IEEE 802.1Q [98] clause 8.6.5.1.

Exchange of port management information between TSN AF and NW-TT or DS-TT allows TSN AF to:
  1. retrieve port management information for a DS-TT or NW-TT Ethernet port;
  2. send port management information for a DS-TT or NW-TT Ethernet port;
  3. subscribe to and receive notifications if specific port management information for a DS-TT or NW-TT Ethernet port changes.
Exchange of port management information between TSN AF and NW-TT or DS-TT is initiated by DS-TT or NW-TT to:
  • notify TSN AF if port management information has changed that TSN AF has subscribed for.
Exchange of port management information is initiated by DS-TT to:
  • provide port management capabilities, i.e. provide information indicating which standardized and deployment-specific port management information is supported by DS-TT.
TSN AF indicates inside the Port Management Information Container whether it wants to retrieve or send port management information or intends to (un-)subscribe for notifications.
Up
5.28.3.2  Transfer of port management informationWord-p. 272
Port management information is transferred transparently via 5GS between TSN AF and DS-TT or NW-TT, respectively, inside a Port Management Information Container as follows:
  • To convey port management information from DS-TT or NW-TT to TSN AF:
    • DS-TT provides a Port Management Information Container and the DS-TT port MAC address to the UE, which includes the Port Management Information container as an optional Information Element of an N1 SM container and triggers the UE requested PDU Session Establishment procedure/PDU Session Modification procedure to forward the Port Management Information container to the SMF. SMF forwards the Port Management Information container and the port number of the related DS-TT Ethernet port to TSN AF as described in TS 23.502, clause 4.3.3.2;
    • NW-TT provides a Port Management Information Container to the UPF, which triggers the N4 Session Level Reporting Procedure to forward the Port Management Information Container to SMF. SMF in turn forwards the container and the port number of the related NW-TT Ethernet port to TSN AF as described in TS 23.502, clause 4.16.5.1. If NW-TT provides a Port Management Information Container for an Ethernet port shared by multiple PDU sessions, then UPF forwards the Port Management Information Container only for one of those PDU sessions.
  • To convey port management information from TSN AF to DS-TT or NW-TT:
    • TSN AF provides a Port Management Information Container, MAC address reported for a PDU Session (i.e. MAC address of the DS-TT port related to the PDU session) and the port number of the Ethernet port to manage to the PCF, which forwards the information to SMF based on the MAC address using the PCF initiated SM Policy Association Modification procedure as described in TS 23.502, clause 4.16.5.2. SMF determines whether the port number relates to a DS-TT or NW-TT Ethernet port and based on this forwards the Port Management Information Container to DS-TT or NW-TT using the network requested PDU Session Modification procedure as described in TS 23.502, clause 4.3.3.2. If the port number identifies an NW-TT Ethernet port shared by multiple PDU sessions, PCF and SMF forward the Port Management Information Container only for one of those PDU sessions.
Up
5.28.4  QoS mapping tables
The mapping tables between the traffic class and 5GS QoS Profile is provisioned and further used to find suitable 5GS QoS profile to transfer TSN traffic over the PDU Session. QoS mapping procedures are performed in two phases: (1) QoS capability report phase as described in clause 5.28.1, and (2) QoS configuration phase as in clause 5.28.2
  1. The TSN AF shall be pre-configured (e.g. via OAM) with a mapping table. The mapping table contains TSN traffic classes, pre-configured bridge delays (i.e. the preconfigured delay between UE and UPF/NW-TT) and priority levels. Once the PDU session has been setup and after retrieving the information related to UE-DS-TT residence time, the TSN AF deduces the port pair(s) consisting of one NW-TT port and one DS-TT port and determines the bridge delay per port pair per traffic class based on the pre-configured bridge delay and the UE-DS-TT residence time. The TSN AF updates bridge delays per port pair and traffic class and reports the bridge delays and other relevant TSN information such as the Traffic Class Table for every port, according to the IEEE 802.1Q [98] and IEEE 802.1Qcc [95] to the CNC.
  2. CNC distributes the TSN QoS requirements and TSN scheduling parameters to 5GS Bridge via TSN AF.
The PCF mapping table provides a mapping from TSN QoS information (see TS 23.503, clauses 6.2.1.2 and 6.1.3.23) to 5GS QoS profile. Based on trigger from TSN AF, the PCF may trigger PDU session modification procedure to establish a new 5G QoS Flow or use the pre-configured 5QI for 5G QoS Flow for the requested traffic class according to the selected QoS policies and the TSN AF traffic requirements.
Figure 5.28.4-1 illustrates the functional distribution of the mapping tables.
Up
The minimum set of TSN QoS-related parameters that are relevant for mapping the TSN QoS requirements are used by the TSN AF: traffic classes and their priorities per port, TSC Burst Size of TSN streams, 5GS bridge delays per port pair and traffic class (independentDelayMax, independentDelayMin, dependentDelayMax, dependentDelayMin), propagation delay per port (txPropagationDelay) and UE-DS-TT residence time.
Once the CNC has received the necessary information, it proceeds to calculate scheduling and paths. The configuration information is then set in the bridge as described in clauses 5.28.2 and 5.28.3. The most relevant information received is the scheduling for every traffic class and port of the bridge. At this point, it is possible to retrieve the TSN QoS requirements by identifying the traffic class of the port. The traffic class to TSN QoS and delay requirement mapping can be performed using the QoS mapping table in the TSN AF as specified in TS 23.503. Subsequently in the PCF, the 5G QoS Flow can be configured by selecting a 5QI as specified in TS 23.503. This feedback approach uses the reported information to the CNC and the feedback of the configuration information coming from the CNC to perform the mapping and configuration in the 5GS.
If the Maximum Burst Size of the aggregated TSC streams in the traffic class is provided by CNC via TSN AF to PCF, PCF can derive the required MDBV taking the Maximum Burst Size as input. If the default MDBV associated with a 5QI in the QoS mapping table can not satisfy the aggregated TSC Burst Size, the PCF provides the derived MDBV in the PCC rule and then the SMF performs QoS Flow binding as specified in clause 6.1.3.2.4 of TS 23.503.
QoS mapping table in the PCF between TSN parameters and 5GS parameters should match the delay, aggregated TSC burst size and priority, while preserving the priorities in the 5GS. An operator enabling TSN services via 5GS can choose up to eight traffic classes to be mapped to 5GS QoS profiles.
Once the 5QIs to be used for TSN streams are identified by the PCF as specified in TS 23.503, then it is possible to enumerate as many bridge port traffic classes as the number of selected 5QIs.
Up

Up   Top   ToC