5.28 Support of integration with TSN
23.5013GPPRelease 18System architecture for the 5G System (5GS)TS
5.28.0 General
5GS supports interoperation with Time Sensitive Networking (TSN). Two basic deployment scenarios for integration of TSN are supported:
– Integration of 5GS into a TSN data network (DN): In this scenario, 5GS is deployed in a TSN DN to provide wireless connectivity. From the perspective of the TSN DN, the 5GS is modelled as a Layer 2 Ethernet Bridge of the TSN DN.
– Integration of 5GS with TSN enabled transport network (TN): In this scenario, a TSN TN is deployed to realize the N3 interface between (R)AN and UPF. From the perspective of the TSN TN, (R)AN and UPF act as End Stations of the TSN TN.
Clauses 5.28.1 to 5.28.4 define the 5GS integration in TSN DN as a 5GS bridge and clause 5.28a defines the 5GS integration with a TSN TN.
5.28.1 5GS bridge management
5GS acts as a Layer 2 Ethernet Bridge. When integrated with IEEE TSN network, 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 port 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 for each network instance or DNN/S-NSSAI. The bridge ID of the 5GS TSN bridge is bound to the UPF ID of the UPF as identified in TS 23.502 [3]. 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. From the TSN AF point of view, a 5GS TSN bridge has a single NW-TT entity within UPF and the NW-TT may have multiple ports that are used for traffic forwarding.
NOTE 1: How to realize single NW-TT entity within UPF is up to implementation.
NOTE 2: Ethernet PDU Session type in this release of the specification may be subject to the constraint that it supports a single N6 interface in a UPF associated with the N6 Network Instance.
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 3: 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.
Figure 5.28.1-1: Per UPF based 5GS bridge
NOTE 4: 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 IEEE 802.1Q features related to TSN, including TSN scheduled traffic (clause 8.6.8.4 in IEEE Std 802.1Q-2018 [98]) over 5GS Bridge, the 5GS supports the following functions:
– Configure the bridge information in 5GS.
– Report the bridge information of 5GS Bridge to TSN network after PDU Session establishment.
– Receiving the configuration from TSN network as defined in clause 5.28.2.
– 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 ID
Bridge ID is to distinguish between bridge instances within 5GS. The Bridge ID can be derived from the unique bridge MAC address as described in IEEE Std 802.1Q [98], or set by implementation specific means ensuring that unique values are used within 5GS;
– Number of Ports;
– list of port numbers.
– Capabilities of 5GS Bridge as defined in IEEE Std 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.
– VLAN Configuration Information.
NOTE 5: This Release of the specification does not support the modification of VLAN Configuration Information at the TSN AF.
– Topology of 5GS Bridge as defined in IEEE Std 802.1AB [97]:
– LLDP Configuration Information.
– Chassis ID subtype and Chassis ID of the 5GS Bridge.
– LLDP Discovery Information for each discovered neighbor of each NW-TT port and DS-TT port.
– Traffic classes and their priorities per port as defined in IEEE Std 802.1Q [98].
– Stream Parameters as defined in clause 12.31.1 in IEEE Std 802.1Q [98], in order to support PSFP:
– MaxStreamFilterInstances: The maximum number of Stream Filter instances supported by the bridge;
– MaxStreamGateInstances: The maximum number of Stream Gate instances supported by the bridge;
– MaxFlowMeterInstances: The maximum number of Flow Meter instances supported by the bridge (optional);
– SupportedListMax: The maximum value supported by the bridge of the AdminControlListLength and OperControlListLength parameters.
The following parameters: independentDelayMax and independentDelayMin, how to calculate them is left to implementation and not defined in this specification.
DS-TT and NW-TT report txPropagationDelay to the TSN AF relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC). If the TSN AF has subscribed for notifications on txPropagationDelay and if the difference to the previously reported txPropagationDelay is larger than the txPropagationDelayDeltaThreshold received in PMIC, the corresponding DS-TT or NW-TT informs the TSN AF about the updated txPropagationDelay using PMIC signalling.
NOTE 6: Configuration of TSN time domain number and txPropagationDelayDeltaThreshold via PMIC is optional for NW-TT. NW-TT can instead be pre-configured with the threshold and the single time domain that is used by the CNC for bridge configuration and reporting.
Bridge ID of the 5GS Bridge, port number(s) of the Ethernet port(s) in NW-TT could be preconfigured on the UPF. The UPF is selected for a PDU Session serving TSC as described in clause 6.3.3.3.
This release of the specification requires that each DS-TT port is assigned with a globally unique MAC address.
NOTE 7: The MAC address of the DS-TT port must not be used in user data traffic; it is used for identification of the PDU Session and the associated bridge port within the 3GPP system.
When there are multiple network instances within a UPF, each network instance is considered logically separate. The network instance for the N6 interface (clause 5.6.12) may be indicated by the SMF to the UPF for a given PDU Session during PDU Session establishment. UPF allocates resources based on the Network Instance and S-NSSAI and it is supported according to TS 29.244 [65]. DNN/S-NSSAI may be indicated by the SMF together with the network instance to the UPF for a given PDU Session during PDU Session establishment procedure.
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 CNC.
5.28.2 5GS Bridge configuration
The configuration information of 5GS Bridge as defined in clause 8.6.8.4 of IEEE Std 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, scheduled traffic (clause 8.6.8.4 in IEEE 802.1Q-2018 [98]) is only supported with protected windows, (see clause Q.2 in IEEE 802.1Q [98]), therefore, it is enough to support AdminControlList, AdminBaseTime, AdminCycleTime and TickGranularity for the configuration of the 5GS.
The configuration information of 5GS Bridge as defined in IEEE Std 802.1Q [98], includes the following:
– Chassis ID of 5GS Bridge;
– Traffic forwarding information as defined in clause 8.8.1 of IEEE Std 802.1Q [98]:
– Destination MAC address and VLAN ID of TSN stream;
– Port number in the Port MAP as defined in clause 8.8.1 of IEEE Std 802.1Q [98].
– Configuration information per stream according to clause 8.6.5.1 of IEEE Std 802.1Q [98] including:
– Stream filters.
– Stream gates.
NOTE 2: In order to support clause 8.6.5.1 of IEEE Std 802.1Q [98], it is required to support the Stream Identification function as specified by IEEE Std 802.1CB [83].
The SMF report the MAC address of the DS-TT port of the related PDU Session to TSN AF via PCF. The association between the DS-TT MAC address, 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.
Two models are supported to configure 5GS QoS for TSN traffic:
– Based on the assumption that PSFP information is always provided by CNC: In this case the QoS Flows are setup based on the PSFP information provided by CNC;
NOTE 3: PSFP information may be provided by CNC if TSN AF has declared PSFP support to CNC. TSN AF indicates the support for PSFP to CNC only if each DS-TT and NW-TT of the 5GS bridge has indicated support of PSFP.
– Without requiring PSFP information provided by the CNC.: In this case, pre-configured QoS Flows are used and configured e.g. during PDU session establishment as described in clause 5.28.4. Additional QoS Flows are setup as necessary based on the PSFP, if available, as described in this clause.
When PSFP information is available, TSN AF identifies the ingress and egress port for the TSN stream as described in Annex I and determines the DS-TT port MAC address(es) identifying the corresponding PDU session(s) carrying the TSN stream. Flow direction of a TSN stream is determined as follows: if the ingress port is a DS-TT port, then the Flow direction is UL; otherwise if the ingress port(s) is (are) NW-TT port, the Flow direction is DL. Flow direction is part of the TSCAI as defined in clause 5.27.2.
The TSN AF uses the stream filter instances of PSFP information to derive the service data flow for TSN streams. The TSN AF uses the Priority values in the stream filter instances in PSFP information (if available) as defined in clause 8.6.5.1 of IEEE Std 802.1Q [98], the 5GS bridge delay information (see clause 5.27.5) and may additionally use scheduled traffic information as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98], to derive the TSN QoS information (i.e. priority and delay) for a given TSN stream or flow of aggregated TSN streams as specified in clause 5.28.4.
The TSN AF identifies the egress port(s) for the TSN stream using local configuration or static filtering entry that matches the TSN stream. If the TSN AF determines that the TSN stream is for UE-UE communication (i.e. ingress and egress ports are in DS-TTs), the TSN AF divides the stream into one uplink stream and one or more downlink streams and provides the streams on AF Session basis to the PCF(s). The SMF applies local switching as specified in clause 5.8.2.13 or clause 5.8.2.5.3 in order to enable UPF locally forward uplink stream from one PDU session as downlink stream in another PDU session.
When CNC configures the PSFP information to the TSN AF, TSN AF determines the TSC Assistance Container as described in clause 5.27.2. The TSN AF associates the TSN QoS information and TSC Assistance Container (if available) with the corresponding service data flow description and provides to the PCF and the SMF as defined in clause 6.1.3.23 of TS 23.503 [45].
NOTE 4: When the TSN stream priority information from PSFP is not available (priority value in stream filters is set to wild card), in certain configurations it can be possible to use the scheduled traffic information as defined in clause 8.6.8.4 of IEEE Std 802.1Q [98] to derive the Priority of the TSN stream. For example, when there is a single downlink stream for a given DS-TT port, it can be possible to determine the affected DS-TT port in the downlink and the associated TSN stream priority based on the scheduled traffic information of the affected egress port, and to derive an estimated MDBV based on the gate open interval and the assumed ingress port bitrate.
If TSN AF provides PSFP and/or scheduled traffic information to DS-TT and NW-TT then DS-TT and NW-TT execute on this information relative to the time base of the TSN GM clock (identified by the TSN time domain number received in PMIC).
NOTE 5: Configuration of TSN time domain number via PMIC is optional for NW-TT. NW-TT can instead be pre-configured with the single time domain that is used by the CNC for bridge configuration and reporting.
5.28.3 Port and user plane node management information exchange in 5GS
5.28.3.1 General
Port number of the DS-TT for the PDU Session is assigned by the UPF during PDU session establishment. The port number of the DS-TT port for a PDU Session shall be reported to the SMF from the UPF and further stored at the SMF. The SMF provides the DS-TT port number via PCF to the TSN AF or TSCTSF. TSN AF or TSCTSF maintains an association between the DS-TT port number and the DS-TT port MAC address (with Ethernet type PDU session) or IP address (applicable for TSCTSF only, with IP type PDU Session) of the UE. If a PDU session for which SMF has reported a DS-TT port number to TSN AF or TSCTSF is released, then SMF informs TSN AF or TSCTSF accordingly.
NOTE 1: Port number can refer either to Ethernet port or PTP port. In Ethernet type PDU Sessions, it is assumed that the PTP port number is the same as the associated Ethernet port number.
5GS shall support transfer of standardized and deployment-specific port management information transparently between TSN AF or TSCTSF and DS-TT or NW-TT, respectively inside a Port Management Information Container. NW-TT may support one or more ports. In this case, each port uses separate Port Management Information Container. 5GS shall also support transfer of standardized and deployment-specific user plane node management information transparently between TSN AF or TSCTSF and NW-TT, respectively inside a User Plane Node Management Information Container. Table 5.28.3.1-1 and Table 5.28.3.1-2 list standardized port management information and user plane node management information, respectively.
If TSN AF is deployed, i.e. if 5GS is integrated with an IEEE TSN network, the port and user plane node management information is exchanged between CNC and TSN AF. The port management information is related to ports located in DS-TT or NW-TT. The user plane node management information container is related to 5GS bridge management.
If TSN AF is not deployed, the port and user plane node management information is exchanged between TSCTSF and DS-TT/NW-TT.
NOTE 2: The time synchronization parameters used in Port Management Information Container and User Plane Node Management Information Container are from IEEE Std 1588 [126], Edition 2019, and from IEEE Std 802.1AS [104]. Since the IEEE time synchronization data sets are not exposed, care needs to be taken when interoperating with devices supporting Edition 2008, IEEE Std 1588-2008 [107] (which can be the case when operating under the SMPTE profile, ST 2059-2:2015 [127]) and using a common management.
Table 5.28.3.1-1: Standardized port management information
|
Port management information |
Applicability (see NOTE 6) |
Supported operations by TSN AF |
Supported operations by TSCTSF |
Reference |
|
|
DS-TT |
NW-TT |
(see NOTE 1) |
(see NOTE 1) |
||
|
General |
|||||
|
Port management capabilities (see NOTE 2) |
X |
X |
R |
R |
|
|
Bridge delay related information |
|||||
|
txPropagationDelay |
X |
X |
R |
– |
IEEE Std 802.1Qcc [95] clause 12.32.2.1 |
|
txPropagationDelayDeltaThreshold (see NOTE 23) |
X |
X |
RW |
||
|
Traffic class related information |
|||||
|
Traffic class table |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] clause 12.6.3 and clause 8.6.6. |
|
Gate control information |
|||||
|
GateEnabled |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-29 |
|
AdminBaseTime |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-29 |
|
AdminControlList |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-29 |
|
AdminCycleTime (see NOTE 3) |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-29 |
|
AdminControlListLength (see NOTE 3) |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-29 |
|
AdminCycleTimeExtension |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-29 |
|
Tick granularity |
X |
X |
R |
– |
IEEE Std 802.1Q [98] Table 12-29 |
|
SupportedListMax |
X |
X |
R |
– |
IEEE Std 802.1Q [98] Table 12-29 |
|
General Neighbor discovery configuration (NOTE 4) |
|||||
|
adminStatus |
D |
X |
RW |
– |
IEEE Std 802.1AB [97] clause 9.2.5.1 |
|
lldpV2LocChassisIdSubtype |
D |
X |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
lldpV2LocChassisId |
D |
X |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
lldpV2MessageTxInterval |
D |
X |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
lldpV2MessageTxHoldMultiplier |
D |
X |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
NW-TT port neighbor discovery configuration |
|||||
|
lldpV2LocPortIdSubtype |
X |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
lldpV2LocPortId |
X |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
DS-TT port neighbor discovery configuration |
|||||
|
lldpV2LocPortIdSubtype |
D |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
lldpV2LocPortId |
D |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
Neighbor discovery information for each discovered neighbor of NW-TT (NOTE 26) |
|||||
|
lldpV2RemChassisIdSubtype |
X |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
lldpV2RemChassisId |
X |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
lldpV2RemPortIdSubtype |
X |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
lldpV2RemPortId |
X |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
TTL |
X |
R |
– |
IEEE Std 802.1AB [97] clause 8.5.4 |
|
|
Neighbor discovery information for each discovered neighbor of DS-TT (NOTE 5) |
|||||
|
lldpV2RemChassisIdSubtype |
D |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
lldpV2RemChassisId |
D |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
lldpV2RemPortIdSubtype |
D |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
lldpV2RemPortId |
D |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
|
TTL |
D |
R |
– |
IEEE Std 802.1AB [97] clause 8.5.4.1 |
|
|
Stream Parameters (NOTE 11) |
|||||
|
MaxStreamFilterInstances |
X |
R |
– |
IEEE Std 802.1Q [98] clause 12.31.1.1 |
|
|
MaxStreamGateInstances |
X |
R |
– |
IEEE Std 802.1Q [98] clause 12.31.1.2 |
|
|
MaxFlowMeterInstances |
X |
R |
– |
IEEE Std 802.1Q [98] clause 12.31.1.3 |
|
|
SupportedListMax |
X |
R |
– |
IEEE Std 802.1Q [98] clause 12.31.1.4 |
|
|
Per-Stream Filtering and Policing information (NOTE 10) |
|||||
|
Stream Filter Instance Table (NOTE 8) |
– |
IEEE Std 802.1Q [98] Table 12-32 |
|||
|
> StreamFilterInstanceIndex |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-32 |
|
> Stream Identification type |
X |
X |
RW |
– |
IEEE 802.1CB [83] clause 9.1.1.6 |
|
> Stream Identification Controlling Parameters |
X |
X |
RW |
– |
IEEE 802.1CB [83] clauses 9.1.2, 9.1.3, 9.1.4 (NOTE 12) |
|
> PrioritySpec |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-32 |
|
> StreamGateInstanceID |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-32 |
|
Stream Gate Instance Table (NOTE 9) |
IEEE Std 802.1Q [98] Table 12-33 |
||||
|
StreamGateInstanceIndex |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-33 |
|
PSFPAdminBaseTime |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-33 |
|
PSFPAdminControlList |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-33 |
|
PSFPAdminCycleTime |
X |
X |
RW |
– |
IEEE Std 802.1Q [98] Table 12-33 |
|
PSFPTickGranularity |
X |
X |
R |
– |
IEEE Std 802.1Q [98] Table 12-33 |
|
PSFPAdminCycleTimeExtension |
X |
X |
R |
– |
IEEE Std 802.1Q [98] Table 12-33 |
|
Time Synchronization Information |
|||||
|
TSN Time domain number (NOTE 24) |
X |
X |
RW |
||
|
Supported PTP instance types (NOTE 13) |
X |
R |
R |
IEEE Std 1588 [126] clause 8.2.1.5.5 |
|
|
Supported transport types (NOTE 14) |
X |
R |
R |
||
|
Supported delay mechanisms (NOTE 15) |
X |
R |
R |
IEEE Std 1588 [126] clause 8.2.15.4.4 |
|
|
PTP grandmaster capable (NOTE 16) |
X |
R |
R |
||
|
gPTP grandmaster capable (NOTE 17) |
X |
R |
R |
||
|
Supported PTP profiles (NOTE 18) |
X |
R |
R |
||
|
Number of supported PTP instances |
X |
R |
R |
||
|
PTP instance specification |
|||||
|
PTP Instance ID (NOTE 25) |
X |
X |
RW |
RW |
|
|
> PTP profile (NOTE 19) |
X |
RW |
RW |
||
|
> Transport type (NOTE 20) |
X |
RW |
RW |
||
|
> Grandmaster enabled (NOTE 21) |
X |
RW |
RW |
||
|
IEEE Std 1588 [126] data sets (NOTE 22) |
|||||
|
> defaultDS.clockIdentity |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.2.2 |
|
|
> defaultDS.clockQuality.clockClass |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.3.1.2 |
|
|
> defaultDS.clockQuality.clockAccuracy |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.3.1.3 |
|
|
> defaultDS.clockQuality.offsetScaledLogVariance |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.3.1.4 |
|
|
> defaultDS.priority1 |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.4.1 |
|
|
> defaultDS.priority2 |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.4.2 |
|
|
> defaultDS.domainNumber |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.4.3 |
|
|
> defaultDS.sdoId |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.4.5 |
|
|
> defaultDS.instanceEnable |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.5.2 |
|
|
> defaultDS.instanceType |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.5.5 |
|
|
> portDS.portIdentity |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.2.1 |
|
> portDS.portState |
X |
X |
R |
R |
IEEE Std 1588 [126] clause 8.2.15.3.1 |
|
> portDS.logMinDelayReqInterval |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.3.2 |
|
> portDS.logAnnounceInterval |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.1 |
|
> portDS.announceReceiptTimeout |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.2 |
|
|
> portDS.logSyncInterval |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.3 |
|
> portDS.delayMechanism |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.4 |
|
> portDS.logMinPdelayReqInterval |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.5 |
|
> portDS.versionNumber |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.6 |
|
> portDS.minorVersionNumber |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.7 |
|
> portDS.delayAsymmetry |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.8 |
|
> portDS.portEnable |
X |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.5.1 |
|
> timePropertiesDS.currentUtcOffset |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.4.2 |
|
|
> timePropertiesDS.timeSource |
X |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.4.9 |
|
|
> externalPortConfigurationPortDS.desiredState |
RW |
RW |
IEEE Std 1588 [126] clause 15.5.3.7.15.1 |
||
|
IEEE Std 802.1AS [104] data sets (NOTE 22) |
|||||
|
> defaultDS.clockIdentity |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.2 |
|
|
> defaultDS.clockQuality.clockClass |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.4.2 |
|
|
> defaultDS.clockQuality.clockAccuracy |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.4.3 |
|
|
> defaultDS.clockQuality.offsetScaledLogVariance |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.4.4 |
|
|
> defaultDS.priority1 |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.5 |
|
|
> defaultDS.priority2 |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.6 |
|
|
> defaultDS.timeSource |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.15 |
|
|
> defaultDS.domainNumber |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.16 |
|
|
> defaultDS.sdoId |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.4.3 |
|
|
> defaultDS.instanceEnable |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.19 |
|
|
> portDS.portIdentity |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.2 |
|
|
> portDS.portState |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.3 |
|
|
> portDS.ptpPortEnabled |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.4 |
|
> portDS.delayMechanism |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.5 |
|
> portDS.isMeasuringDelay |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.6 |
|
> portDS.asCapable |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.7 |
|
> portDS.meanLinkDelay |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.8 |
|
> portDS.meanLinkDelayThresh |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.9 |
|
> portDS.delayAsymmetry |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.10 |
|
> portDS.neighborRateRatio |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.11 |
|
> portDS.initialLogAnnounceInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.12 |
|
> portDS.currentLogAnnounceInterval |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.13 |
|
> portDS.useMgtSettableLogAnnounceInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.14 |
|
> portDS.mgtSettableLogAnnounceInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.15 |
|
> portDS.announceReceiptTimeout |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.16 |
|
|
> portDS.initialLogSyncInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.17 |
|
> portDS.currentLogSyncInterval |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.18 |
|
> portDS.useMgtSettableLogSyncInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.19 |
|
> portDS.mgtSettableLogSyncInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.20 |
|
> portDS.syncReceiptTimeout |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.21 |
|
|
> portDS.syncReceiptTimeoutTimeInterval |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.22 |
|
|
> portDS.initialLogPdelayReqInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.23 |
|
> portDS.currentLogPdelayReqInterval |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.24 |
|
> portDS.useMgtSettableLogPdelayReqInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.25 |
|
> portDS.mgtSettableLogPdelayReqInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.26 |
|
> portDS.initialLogGptpCapableMessageInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.27 |
|
> portDS.currentLogGptpCapableMessageInterval |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.28 |
|
> portDS.useMgtSettableLogGptpCapableMessageInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.29 |
|
> portDS.mgtSettableLogGptpCapableMessageInterval |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.30 |
|
> portDS.initialComputeNeighborRateRatio |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.31 |
|
> portDS.currentComputeNeighborRateRatio |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.32 |
|
> portDS.useMgtSettableComputeNeighborRateRatio |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.33 |
|
> portDS.mgtSettableComputeNeighborRateRatio |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.34 |
|
> portDS.initialComputeMeanLinkDelay |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.35 |
|
> portDS.currentComputeMeanLinkDelay |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.36 |
|
> portDS.useMgtSettableComputeMeanLinkDelay |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.37 |
|
> portDS.mgtSettableComputeMeanLinkDelay |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.38 |
|
> portDS.allowedLostResponses |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.39 |
|
> portDS.allowedFaults |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.40 |
|
> portDS.gPtpCapableReceiptTimeout |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.41 |
|
> portDS.versionNumber |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.42 |
|
> portDS.nup |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.43 |
|
> portDS.ndown |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.44 |
|
> portDS.oneStepTxOper |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.45 |
|
> portDS.oneStepReceive |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.46 |
|
> portDS.oneStepTransmit |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.47 |
|
> portDS.initialOneStepTxOper |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.48 |
|
> portDS.currentOneStepTxOper |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.49 |
|
> portDS.useMgtSettableOneStepTxOper |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.50 |
|
> portDS.mgtSettableOneStepTxOper |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.51 |
|
> portDS.syncLocked |
X |
X |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.52 |
|
> portDS.pdelayTruncatedTimestampsArray |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.53 |
|
> portDS.minorVersionNumber |
X |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.54 |
|
> timePropertiesDS.currentUtcOffset |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.5.2 |
|
|
> externalPortConfigurationPortDS.desiredState |
X |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.12.2 |
|
|
NOTE 1: R = Read only access; RW = Read/Write access; ― = not supported. 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 using the User Plane Node Management Information Container (refer to Table 5.28.3.1-2) and NW-TT performs neighbor discovery on behalf on DS-TT. When a parameter in this group is changed, it is necessary to provide the change to every DS-TT and the NW-TT that belongs to the 5GS TSN bridge. It is mandatory that the general neighbor discovery configuration is identical for all DS-TTs and the NW-TTs that belongs to the bridge. NOTE 5: If DS-TT supports neighbor discovery, then TSN AF retrieves neighbor discovery information for DS-TT Ethernet ports from DS-TT. TSN AF indicates the neighbor discovery information for each discovered neighbor of DS-TT port to CNC. If DS-TT does not support neighbor discovery, then TSN AF retrieves neighbor discovery information for DS-TT Ethernet ports from NW-TT, using the User Plane Node Management Information Container (refer to Table 5.28.3.1-2), the NW-TT performing 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. NOTE 7: Void. NOTE 8: There is a Stream Filter Instance Table per Stream. NOTE 9: There is a Stream Gate Instance Table per Gate. NOTE 10: TSN AF indicates the support for PSFP to the CNC only if each DS-TT and NW-TT of the 5GS bridge has indicated support of PSFP. DS-TT indicates support of PSFP using port management capabilities, i.e. by indicating support for the Per-Stream Filtering and Policing information and by setting higher than zero values for MaxStreamFilterInstances, MaxStreamGateInstances, MaxFlowMeterInstances, SupportedListMax parameters. When available, TSN AF uses the PSFP information for determination of the traffic pattern 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 clause 8.6.5.1 of IEEE Std 802.1Q [98]. NOTE 11: TSN AF composes a Stream Parameter Table towards the CNC. It is up to TSN AF how it composes the Stream Parameter Table based on the numerical values as received from DS-TT and NW-TT port(s) and for the bridge for each individual parameter. NOTE 12: The set of Stream Identification Controlling Parameters depends on the Stream Identification type value as defined in IEEE Std 802.1CB [83] Table 9-1 and clauses 9.1.2, 9.1.3, 9.1.4. NOTE 13: Enumeration of supported PTP instance types. Allowed values as defined in clause 8.2.1.5.5 of IEEE Std 1588 [126]. NOTE 14: Enumeration of supported transport types. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). NOTE 15: Enumeration of supported PTP delay mechanisms. Allowed values as defined in clause 8.2.15.4.4 of IEEE Std 1588 [126]. NOTE 16: Indicates whether DS-TT supports acting as a PTP grandmaster. NOTE 17: Indicates whether DS-TT supports acting as a gPTP grandmaster. NOTE 18: Enumeration of supported PTP profiles, each identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. NOTE 19: PTP profile to apply, identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. NOTE 20: Transport type to use. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). NOTE 21: Indicates whether to act as grandmaster or not, i.e. whether to send Announce, Sync and optionally Follow_Up messages. NOTE 22: The IEEE Std 802.1AS [104] data sets apply if the IEEE 802.1AS PTP profile is used; otherwise the IEEE Std 1588 [126] data sets apply. NOTE 23: Indicates how much the txPropagationDelay needs to change so that DS-TT/NW-TT report a change in txPropagationDelay to TSN AF. This is optional for NW-TT. NOTE 24: Indicates the gPTP domain (identified by a domain number) that is assumed by the CNC as the reference clock for time information in the scheduled traffic (gate control) information, PSFP information and bridge delay related information. This is optional for NW-TT. NOTE 25: PTP Instance ID uniquely identifies a PTP instance within the user plane node. NOTE 26: TSN AF indicates the neighbor discovery information for each discovered neighbor of NW-TT port to CNC. |
|||||
Table 5.28.3.1-2: Standardized user plane node management information
|
User plane node management information |
Supported operations by TSN AF |
Supported operations by TSCTSF |
Reference |
|
(see NOTE 1) |
(see NOTE 1) |
||
|
Information for 5GS Bridge |
|||
|
User plane node Address |
R |
R |
|
|
User plane node ID |
R |
R |
|
|
NW-TT port numbers |
R |
R |
|
|
Traffic forwarding information |
|||
|
Static Filtering Entry (NOTE 3) |
RW |
– |
IEEE Std 802.1Q [98] clause 8.8.1 |
|
General Neighbor discovery configuration (NOTE 2) |
|||
|
adminStatus |
RW |
– |
IEEE Std 802.1AB [97] clause 9.2.5.1 |
|
lldpV2LocChassisIdSubtype |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
lldpV2LocChassisId |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
lldpV2MessageTxInterval |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
lldpV2MessageTxHoldMultiplier |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
DS-TT port neighbor discovery configuration for DS-TT ports (NOTE 4) |
|||
|
>DS-TT port neighbor discovery configuration for each DS-TT port |
|||
|
>> DS-TT port number |
RW |
– |
|
|
>> lldpV2LocPortIdSubtype |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
>> lldpV2LocPortId |
RW |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
Discovered neighbor information for DS-TT ports (NOTE 4) |
|||
|
>Discovered neighbor information for each DS-TT port (NOTE 4) |
|||
|
>> DS-TT port number |
R |
– |
|
|
>> lldpV2RemChassisIdSubtype |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
>> lldpV2RemChassisId |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
>> lldpV2RemPortIdSubtype |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
>> lldpV2RemPortId |
R |
– |
IEEE Std 802.1AB [97] Table 11-2 |
|
>> TTL |
R |
– |
IEEE Std 802.1AB [97] clause 8.5.4.1 |
|
Stream Parameters (NOTE 5) |
|||
|
MaxStreamFilterInstances |
R |
– |
IEEE Std 802.1Q [98] |
|
MaxStreamGateInstances |
R |
– |
IEEE Std 802.1Q [98] |
|
MaxFlowMeterInstances |
R |
– |
IEEE Std 802.1Q [98] |
|
SupportedListMax |
R |
– |
IEEE Std 802.1Q [98] |
|
Time synchronization information |
|||
|
Supported PTP instance types (NOTE 6) |
R |
R |
|
|
Supported transport types (NOTE 7) |
R |
R |
|
|
Supported delay mechanisms (NOTE 8) |
R |
R |
|
|
PTP grandmaster capable (NOTE 9) |
R |
R |
|
|
gPTP grandmaster capable (NOTE 10) |
R |
R |
|
|
Supported PTP profiles (NOTE 11) |
R |
R |
|
|
Number of supported PTP instances |
R |
R |
|
|
Time synchronization information for PTP instances (NOTE 16) |
|||
|
> PTP instance specification |
|||
|
>> PTP Instance ID (NOTE 17) |
RW |
RW |
|
|
>> PTP profile (NOTE 12) |
RW |
RW |
|
|
>> Transport type (NOTE 13) |
RW |
RW |
|
|
>> Grandmaster candidate enabled |
RW |
RW |
|
|
IEEE Std 1588 [126] data sets (NOTE 15) |
|||
|
>> defaultDS.clockIdentity |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.2.2 |
|
>> defaultDS.clockQuality.clockClass |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.3.1.2 |
|
>> defaultDS.clockQuality.clockAccuracy |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.3.1.3 |
|
>> defaultDS.clockQuality.offsetScaledLogVariance |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.3.1.4 |
|
>> defaultDS.priority1 |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.4.1 |
|
>> defaultDS.priority2 |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.4.2 |
|
>> defaultDS.domainNumber |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.4.3 |
|
>> defaultDS.sdoId |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.4.5 |
|
>> defaultDS.instanceEnable |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.5.2 |
|
>> defaultDS.externalPortConfigurationEnabled |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.5.3 |
|
>> defaultDS.instanceType |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.1.5.5 |
|
>> timePropertiesDS.currentUtcOffset |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.4.2 |
|
>> timePropertiesDS.timeSource |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.4.9 |
|
IEEE Std 802.1AS [104] data sets (NOTE 15) |
|||
|
>> defaultDS.clockIdentity |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.2 |
|
>> defaultDS.clockQuality.clockClass |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.4.2 |
|
>> defaultDS.clockQuality.clockAccuracy |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.4.3 |
|
>> defaultDS.clockQuality.offsetScaledLogVariance |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.4.4 |
|
>> defaultDS.priority1 |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.5 |
|
>> defaultDS.priority2 |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.6 |
|
>> defaultDS.timeSource |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.15 |
|
>> defaultDS.domainNumber |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.16 |
|
>> defaultDS.sdoId |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.18 |
|
>> defaultDS.externalPortConfigurationEnabled |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.4.3 |
|
>> defaultDS.instanceEnable |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.2.19 |
|
>> timePropertiesDS.currentUtcOffset |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.5.2 |
|
Time synchronization information for DS-TT ports |
|||
|
> Time synchronization information for each DS-TT port |
|||
|
> DS-TT port number |
RW |
RW |
|
|
>> Time synchronization information for each PTP Instance |
|||
|
>> PTP Instance ID (NOTE 17) |
RW |
RW |
|
|
>> Grandmaster on behalf of DS-TT enabled (NOTE 14) |
RW |
RW |
|
|
IEEE Std 1588 [126] data sets (NOTE 15) |
|||
|
>> portDS.portIdentity |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.2.1 |
|
>> portDS.portState |
R |
R |
IEEE Std 1588 [126] clause 8.2.15.3.1 |
|
>> portDS.logMinDelayReqInterval |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.3.2 |
|
>> portDS.logAnnounceInterval |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.1 |
|
>> portDS.announceReceiptTimeout |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.2 |
|
>> portDS.logSyncInterval |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.3 |
|
>> portDS.delayMechanism |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.4 |
|
>> portDS.logMinPdelayReqInterval |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.5 |
|
>> portDS.versionNumber |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.6 |
|
>> portDS.minorVersionNumber |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.7 |
|
>> portDS.delayAsymmetry |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.4.8 |
|
>> portDS.portEnable |
RW |
RW |
IEEE Std 1588 [126] clause 8.2.15.5.1 |
|
>> externalPortConfigurationPortDS.desiredState |
RW |
RW |
IEEE Std 1588 [126] clause 15.5.3.7.15.1 |
|
IEEE Std 802.1AS [104] data sets (NOTE 15) |
|||
|
>> portDS.portIdentity |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.2 |
|
>> portDS.portState |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.3 |
|
>> portDS.ptpPortEnabled |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.4 |
|
>> portDS.delayMechanism |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.5 |
|
>> portDS.isMeasuringDelay |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.6 |
|
>> portDS.asCapable |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.7 |
|
>> portDS.meanLinkDelay |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.8 |
|
>> portDS.meanLinkDelayThresh |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.9 |
|
>> portDS.delayAsymmetry |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.10 |
|
>> portDS.neighborRateRatio |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.11 |
|
>> portDS.initialLogAnnounceInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.12 |
|
>> portDS.currentLogAnnounceInterval |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.13 |
|
>> portDS.useMgtSettableLogAnnounceInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.14 |
|
>> portDS.mgtSettableLogAnnounceInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.15 |
|
>> portDS.announceReceiptTimeout |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.16 |
|
>> portDS.initialLogSyncInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.17 |
|
>> portDS.currentLogSyncInterval |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.18 |
|
>> portDS.useMgtSettableLogSyncInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.19 |
|
>> portDS.mgtSettableLogSyncInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.20 |
|
>> portDS.syncReceiptTimeout |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.21 |
|
>> portDS.syncReceiptTimeoutTimeInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.22 |
|
>> portDS.initialLogPdelayReqInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.23 |
|
>> portDS.currentLogPdelayReqInterval |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.24 |
|
>> portDS.useMgtSettableLogPdelayReqInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.25 |
|
>> portDS.mgtSettableLogPdelayReqInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.26 |
|
>> portDS.initialLogGptpCapableMessageInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.27 |
|
>> portDS.currentLogGptpCapableMessageInterval |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.28 |
|
>> portDS.useMgtSettableLogGptpCapableMessageInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.29 |
|
>> portDS.mgtSettableLogGptpCapableMessageInterval |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.30 |
|
>> portDS.initialComputeNeighborRateRatio |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.31 |
|
>> portDS.currentComputeNeighborRateRatio |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.32 |
|
>> portDS.useMgtSettableComputeNeighborRateRatio |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.33 |
|
>> portDS.mgtSettableComputeNeighborRateRatio |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.34 |
|
>> portDS.initialComputeMeanLinkDelay |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.35 |
|
>> portDS.currentComputeMeanLinkDelay |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.36 |
|
>> portDS.useMgtSettableComputeMeanLinkDelay |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.37 |
|
>> portDS.mgtSettableComputeMeanLinkDelay |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.38 |
|
>> portDS.allowedLostResponses |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.39 |
|
>> portDS.allowedFaults |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.40 |
|
>> portDS.gPtpCapableReceiptTimeout |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.41 |
|
>> portDS.versionNumber |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.42 |
|
>> portDS.nup |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.43 |
|
>> portDS.ndown |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.44 |
|
>> portDS.oneStepTxOper |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.45 |
|
>> portDS.oneStepReceive |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.46 |
|
>> portDS.oneStepTransmit |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.47 |
|
>> portDS.initialOneStepTxOper |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.48 |
|
>> portDS.currentOneStepTxOper |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.49 |
|
>> portDS.useMgtSettableOneStepTxOper |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.50 |
|
>> portDS.mgtSettableOneStepTxOper |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.51 |
|
>> portDS.syncLocked |
R |
R |
IEEE Std 802.1AS [104] clause 14.8.52 |
|
>> portDS.pdelayTruncatedTimestampsArray |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.53 |
|
>> portDS.minorVersionNumber |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.8.54 |
|
>> externalPortConfigurationPortDS.desiredState |
RW |
RW |
IEEE Std 802.1AS [104] clause 14.12.2 |
|
NOTE 1: R = Read only access; RW = Read/Write access; ― = not supported. NOTE 2: General neighbor discovery information is included only when NW-TT performs neighbor discovery on behalf of DS-TT. When a parameter in this group is changed, it is necessary to provide the change to every DS-TT and the NW-TT that belongs to the 5GS TSN bridge. NOTE 3: If the Static Filtering Entry information is present, UPF/NW-TT can use Static Filtering Entry information for forwarding TSC traffic, as specified in clause 5.8.2.5.3. NOTE 4: DS-TT discovery configuration and DS-TT discovery information are used only when DS-TT does not support LLDP and NW-TT performs neighbor discovery on behalf of DS-TT. TSN AF indicates the discovered neighbor information for each DS-TT port to CNC. NOTE 5: TSN AF indicates the support for PSFP to the CNC only if each DS-TT and NW-TT of the 5GS bridge have indicated support of PSFP. The support of PSFP at the NW-TT ports is expressed by setting higher than zero values for MaxStreamFilterInstances, MaxStreamGateInstances, MaxFlowMeterInstances, SupportedListMax parameters. NOTE 6: Enumeration of supported PTP instance types. Allowed values as defined in clause 8.2.1.5.5 of IEEE Std 1588 [126]. NOTE 7: Enumeration of supported transport types. Allowed values: IPv4 (as defined in IEEE Std 1588 [126] Annex C), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). NOTE 8: Enumeration of supported PTP delay mechanisms. Allowed values as defined in clause 8.2.15.4.4 of IEEE Std 1588 [126]. NOTE 9: Indicates whether NW-TT supports acting as a PTP grandmaster. NOTE 10: Indicates whether NW-TT supports acting as a gPTP grandmaster. NOTE 11: Enumeration of supported PTP profiles, each identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. NOTE 12: PTP profile to apply, identified by PTP profile ID, as defined in clause 20.3.3 of IEEE Std 1588 [126]. NOTE 13: Transport type to use. Allowed values: IPv4 (as defined in Annex C of IEEE Std 1588 [126]), IPv6 (as defined in IEEE Std 1588 [126] Annex D), Ethernet (as defined in Annex E of IEEE Std 1588 [126]). NOTE 14: Indicates whether to act as grandmaster on behalf of a DS-TT port or not if 5GS is determined to be the grandmaster clock, i.e. whether to send Announce, Sync and optionally Follow_Up messages on behalf of DS-TT. NOTE 15: The IEEE Std 802.1AS [104] data sets apply if the IEEE 802.1AS PTP profile is used; otherwise, the IEEE Std 1588 [126] data sets apply. NOTE 16: Specifies the default data set for each PTP instance identified by PTP instance ID within the user plane node. NOTE 17: PTP Instance ID uniquely identifies a PTP instance within the user plane node. |
|||
Exchange of port and user plane node management information between TSN AF or TSCTSF and NW-TT or between TSN AF or TSCTSF and DS-TT allows TSN AF or TSCTSF to:
1) retrieve port management information for a DS-TT or NW-TT port or user plane node management information;
2) send port management information for a DS-TT or NW-TT port or user plane node management information;
3) subscribe to and receive notifications if specific port management information for a DS-TT or NW-TT port changes or user plane node management information changes.
4) delete selected entries in the following data structures:
– "DS-TT port neighbour discovery configuration for DS-TT port" in UMIC using the DS-TT port number to reference the selected entry.
– "Stream Filter Instance Table" in PMIC using the Stream Filter Instance ID to reference the selected entry.
– "Stream Gate Instance Table" in PMIC using the Stream Gate Instance ID to reference the selected entry.
– "Static Filtering Entries table" in UMIC using the (MAC address, VLAN ID) pair to reference the selected entry.
5) delete PTP Instances in a DS-TT port or NW-TT port using the PTP Instance ID to reference the selected entry as described in clause K.2.2.1.
Exchange of port management information between TSN AF or TSCTSF and NW-TT or DS-TT is initiated by DS-TT or NW-TT to:
– notify TSN AF or TSCTSF if port management information has changed that TSN AF or TSCTSF has subscribed for.
Exchange of user plane node management information between TSN AF or TSCTSF and NW-TT is initiated by NW-TT to:
– notify TSN AF or TSCTSF if user plane node management information has changed that TSN AF or TSCTSF 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 or TSCTSF indicates inside the Port Management Information Container or user plane node Management Information Container whether it wants to retrieve or send port or user plane node management information or intends to (un-)subscribe for notifications.
5.28.3.2 Transfer of port or user plane node management information
Port management information is transferred transparently via 5GS between TSN AF or TSCTSF and DS-TT or NW-TT, respectively, inside a Port Management Information Container (PMIC). User plane node management information is transferred transparently via 5GS between TSN AF or TSCTSF and NW-TT inside a user plane node Management Information Container (UMIC). The transfer of port or user plane node management information is as follows:
– To convey port management information from DS-TT or NW-TT to TSN AF or TSCTSF:
– DS-TT provides a PMIC and the DS-TT port MAC address (if available) to the UE, which includes the PMIC as an optional Information Element of an N1 SM container and triggers the UE requested PDU Session Establishment procedure or PDU Session Modification procedure to forward the PMIC to the SMF. SMF forwards the PMIC and the port number of the related DS-TT port to TSN AF or TSCTSF as described in clauses 4.3.2.2 and 4.3.3.2 of TS 23.502 [3];
– NW-TT provides PMIC(s) and/or UMIC to the UPF, which triggers the N4 Session Level Reporting Procedure to forward the PMIC(s) and/or UMIC to SMF. UPF selects an N4 session corresponding to any of the N4 sessions for this NW-TT. SMF in turn forwards the PMIC(s) and the port number(s) of the related NW-TT port(s), or the UMIC, to TSN AF or TSCTSF as described in clause 4.16.5.1 of TS 23.502 [3].
NOTE 1: There has to be at least one established PDU session for DS-TT port before the UPF can report PMIC/UMIC information towards the TSN AF or TSCTSF.
– To convey port management information from TSN AF or TSCTSF to DS-TT:
– TSN AF or TSCTSF provides a PMIC, DS-TT port MAC address or UE IP address (applicable for TSCTSF only) reported for a PDU Session (i.e. MAC address of the DS-TT port or IP address related to the PDU session) and the port number of the DS-TT port to manage to the PCF by using the AF Session level Procedure, which forwards the information to SMF based on the MAC or IP address using the PCF initiated SM Policy Association Modification procedure as described in clause 4.16.5.2 of TS 23.502 [3]. SMF determines that the port number relates to a DS-TT port and based on this forwards the PMIC to DS-TT using the network requested PDU Session Modification procedure as described in clause 4.3.3.2 of TS 23.502 [3].
– To convey port or user plane node management information from TSN AF or TSCTSF to NW-TT:
– TSN AF or TSCTSF selects a PCF-AF session corresponding to any of the DS-TT MAC or IP addresses (applicable for TSCTSF only) for the related PDU sessions of this bridge and provides a PMIC(s) and the related NW-TT port number(s) and/or UMIC to the PCF. The PCF uses the PCF initiated SM Policy Association Modification procedure to forward the information received from TSN AF or TSCTSF to SMF as described in clause 4.16.5.2 of TS 23.502 [3]. SMF determines that the included information needs to be delivered to the NW-TT either by determining that the port number(s) relate(s) to a NW-TT port(s) or based on the presence of UMIC, and forwards the container(s) and/or related port number(s) to NW-TT using the N4 Session Modification procedure described in clause 4.4.1.3 of TS 23.502 [3].
5.28.3.3 VLAN Configuration Information
The CNC obtains the 5GS bridge VLAN configuration from TSN AF according to clause 12.10.1.1 of IEEE Std 802.1Q [98]. The TSN AF and UPF/NW-TT are pre-configured with same 5GS bridge VLAN configuration.
NOTE: In this Release, the VLAN Configuration Information are pre-configured at the TSN AF and the NW-TT and is not exchanged between the TSN AF and the UPF/NW-TT.
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) in the 5GS bridge 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 as described in clause 5.27.5. 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 (clause 12.6.3 in IEEE Std 802.1Q [98]) for every port, according to the IEEE Std 802.1Q [98] and IEEE Std 802.1Qcc [95] to the CNC.
(2) CNC may distribute PSFP information and transmission gate scheduling parameters to 5GS Bridge via TSN AF, which can be mapped to TSN QoS requirements by the TSN AF.
The PCF mapping table provides a mapping from TSN QoS information (see clauses 6.2.1.2 and 6.1.3.23 of TS 23.503 [45]) 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.
Figure 5.28.4-1: QoS Mapping Function distribution between PCF and TSN AF
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 retrieves 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 PSFP information and the schedule of transmission gates 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 TSN stream. The traffic class to TSN QoS and delay requirement (excluding the UE-DS-TT residence time) mapping can be performed using the QoS mapping table in the TSN AF as specified in TS 23.503 [45]. Subsequently in the PCF, the 5G QoS Flow can be configured by selecting a 5QI as specified in TS 23.503 [45]. 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 standardized 5QI or a pre-configured 5QI in the QoS mapping table cannot 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 [45].
Maximum Flow Bit Rate is calculated over PSFPAdminCycleTime as described in Annex I and provided by the TSN AF to the PCF. The PCF sets the GBR and MBR values to the Maximum Flow Bitrate value.
The Maximum Flow Bit Rate is adjusted according to Averaging Window associated with a pre-configured 5QI in the QoS mapping table or another selected 5QI (as specified in TS 23.503 [45]) to obtain GBR of the 5GS QoS profile. GBR is then used by SMF to calculate the GFBR per QoS Flow. 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 [45], then it is possible to enumerate as many bridge port traffic classes as the number of selected 5QIs.
When PSFP information is not available to the TSN AF for a given TSN stream (e.g. because of lack of PSFP support in the DS-TTs or the NW-TTs, or exceeding the number of supported table entries for PSFP functions, or because CNC does not provide PSFP information), the 5GS can support the TSN streams using pre-configured mapping from stream priority (i.e. PCP as defined in IEEE Std 802.1Q [98]) to QoS Flows.