name: PTP
full_form: Precision Time Protocol
context: DS-TT and NW-TT indicate time synchronization information they support inside the Port management capabilities (see Table K.1-1). TSN AF and TSCTSF may determine the PTP functionalities supported by DS-TT and NW-TT by retrieving the following port management information or user plane node management information, respectively: - Supported PTP instance types; - Supported transport types; - Supported PTP delay mechanisms; - Grandmaster capability; - Supported PTP profiles; - Number of supported PTP instances. NOTE: If NW-TT or DS-TT do not indicate support for any of the PTP profiles and PTP instance types, then TSN AF or TSCTSF assume that the NW-TT or DS-TT only support acting as a PTP Relay instance with the gPTP GM connected on N6. If DS-TT and NW-TT support the PTP Relay instance type as defined by IEEE 802.1AS [104] then DS-TT and NW-TT shall include the IEEE 802.1AS [104] PTP profile in the "Supported PTP profiles" in PMIC and UMIC, respectively. The TSN AF or TSCTSF may retrieve the "Number of supported PTP instances" from NW-TT via UMIC and from DS-TT via PMIC.
description: Precision Time Protocol (PTP) is a protocol used for synchronizing clocks in a network. In the context of 3GPP specifications, PTP is utilized within the Time-Sensitive Networking (TSN) framework to ensure precise time synchronization across different network elements and user equipment. The protocol supports various instance types, transport mechanisms, delay compensation methods, and profiles, which are crucial for maintaining accurate timing in telecommunications networks.
explanation: PTP is classified as a Protocol because it defines the rules and standards for achieving precise time synchronization within telecommunications networks, adhering to the IEEE 802.1AS standard and supporting various functionalities such as grandmaster capability and relay instances.
section_title: K.2.1 Capability exchange
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Network Function,O,B-Network Function,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,B-Procedure,O,O,O,B-Technology,B-Network Function,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,B-Organization,O,O,O,O,O,O,O,O,O,B-Organization,O,O,B-Procedure,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,B-Technology,B-Network Function,O,B-Network Function,O,O,O,O,O,O,B-Procedure,O,O,O,O,O,O,O,O,O,O
biotag_Description: B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Organization,O,B-Procedure,O,O,O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O