封包時間戳記
簡介
每當收到或傳輸封包時,許多網路介面卡 (NIC 或網路介面卡) 可以在硬體中產生時間戳記。 時間戳記是使用 NIC 自己的硬體時鐘來產生。 這項功能特別由 PTP (PTP) 使用,這是時間同步處理通訊協定。 PTP 會布建在通訊協定本身內使用這類硬體時間戳記。
例如,時間戳記可用來計算在電腦網路堆疊內封包所花費的時間,再傳送至網路或從網路接收。 PTP 接著可以使用這些計算來改善時間同步的精確度。 網路介面卡的封包時間戳記支援有時特別適用于 PTP 通訊協定。 在其他情況下,會提供更一般的支援。
時間戳記 API 可讓 Windows 支援 PTP 第 2 版通訊協定網路介面卡的硬體時間戳記功能。 整體來說,這些功能包括提供網路介面卡驅動程式支援時間戳記的能力,以及讓使用者模式應用程式透過 Windows 通訊端 取用與封包相關聯的時間戳記, (請參閱 Winsock 時間戳記) 。 此外,也提供產生軟體時間戳記的功能,這可讓網路驅動程式在軟體中產生時間戳記。 這類軟體時間戳記是由 NIC 驅動程式所產生的,其核心模式相當於 QueryPerformanceCounter (QPC) 。 不過,不支援同時 啟用硬體和軟體時間戳記 。
特別是,本主題所述的網際網路通訊協定協助程式 (IP 協助程式) 封包時間戳記 API 提供使用者模式應用程式判斷網路介面卡時間戳記功能的能力,以及以交叉時間戳記的形式查詢網路介面卡的時間戳記, (如下所述) 。
支援精確度時間通訊協定第 2 版
如前所述,Windows 中時間戳記支援的主要目標是支援有效時間通訊協定第 2 版 (PTPv2) 通訊協定。 在 PTPv2 中,並非所有訊息都需要時間戳記。 特別是,PTP 事件訊息會使用時間戳。 目前,支援的範圍是透過使用者資料包通訊協定的 PTPv2 (UDP) 。 不支援透過原始乙太網路進行 PTP。
PTPv2 在 2 個步驟 模式中運作時支援時間戳記。 2 步驟 是指 PTP 封包中的實際時間戳不會在硬體中即時產生,而是改為從硬體擷取,並以個別訊息的方式傳達為個別 (訊息,例如,使用後續訊息) 。
總而言之,您可以在 PTPv2 應用程式中使用網際網路通訊協定協助程式 (IP 協助程式) 封包時間戳記 API,以及 Winsock 的時間戳記支援,以改善其時間同步處理精確度。
擷取網路介面卡的時間戳記功能
PTP 時間同步處理服務之類的應用程式必須判斷網路介面卡的時間戳記功能。 接著,應用程式可以使用擷取的功能來決定是否要使用時間戳。
即使網路介面卡 支援 時間戳記,還是需要預設關閉功能。 配接器會在指示時開啟時間戳記。 Windows 為應用程式提供 API 來擷取硬體的功能,以及開啟哪些功能。
若要擷取網路介面卡支援的時間戳記功能,您可以呼叫 GetInterfaceSupportedTimestampCapabilities 函式、提供網路介面卡的本機唯一識別碼 (LUID) ,並傳回擷取 INTERFACE_TIMESTAMP_CAPABILITIES 物件形式的支援時間戳記功能。
從 GetInterfaceSupportedTimestampCapabilities 傳回的程式碼會指出呼叫是否成功,以及是否已擷取填入 的INTERFACE_TIMESTAMP_CAPABILITIES 值。
若要擷取網路介面卡目前啟用的時間戳記功能,您可以呼叫 GetInterfaceActiveTimestampCapabilities 函式,提供網路介面卡的本機唯一識別碼 (LUID) ,並傳回以 INTERFACE_TIMESTAMP_CAPABILITIES 物件的形式擷取已啟用的時間戳記功能。
同樣地,從 GetInterfaceActiveTimestampCapabilities 傳回的程式碼表示成功或失敗,以及是否已擷取有效的 INTERFACE_TIMESTAMP_CAPABILITIES 值。
網路介面卡可支援各種時間戳記功能。 例如,有些配接器可以在傳送和接收期間為每個封包時間戳記,而其他配接器則僅支援 PTPv2 封包。 INTERFACE_TIMESTAMP_CAPABILITIES結構描述網路介面卡支援的確切功能。
從網路介面卡擷取跨時間戳記
使用硬體時間戳記時,PTP 應用程式需要建立關聯性 (例如,使用適當的數學技術) 網路介面卡的硬體時鐘與系統時鐘。 這是必要的,因此,表示一個時鐘單位中時間的值可以轉換成另一個時鐘的單位。 交叉時間戳記是為了此目的而提供,您的應用程式可以定期取樣交叉時間戳記,以建立這類關聯性。
若要這樣做,請呼叫 CaptureInterfaceHardwareCrossTimestamp 函式,提供網路介面卡的本機唯一識別碼 (LUID) ,並以 INTERFACE_HARDWARE_CROSSTIMESTAMP 物件的形式傳回從網路介面卡擷取時間戳記。
時間戳記功能變更通知
若要通知網路介面卡變更的時間戳記功能,請呼叫 RegisterInterfaceTimestampConfigChange 函式,並提供您已實作的回呼函式指標,以及選擇性呼叫端配置的內容。
RegisterInterfaceTimestampConfigChange 會傳回控制碼,您可以接著傳遞至 UnregisterInterfaceTimestampConfigChange 以取消註冊回呼函式。
程式碼範例 1 — 擷取時間戳記功能和交叉時間戳記
// main.cpp in a Console App project.
#include <stdio.h>
#include <winsock2.h>
#include <iphlpapi.h>
#pragma comment(lib, "Iphlpapi")
BOOL
IsPTPv2HardwareTimestampingSupportedForIPv4(PINTERFACE_TIMESTAMP_CAPABILITIES timestampCapabilities)
{
// Supported if both receive and transmit side support is present
if (((timestampCapabilities->HardwareCapabilities.PtpV2OverUdpIPv4EventMessageReceive) ||
(timestampCapabilities->HardwareCapabilities.PtpV2OverUdpIPv4AllMessageReceive) ||
(timestampCapabilities->HardwareCapabilities.AllReceive))
&&
((timestampCapabilities->HardwareCapabilities.PtpV2OverUdpIPv4EventMessageTransmit) ||
(timestampCapabilities->HardwareCapabilities.PtpV2OverUdpIPv4AllMessageTransmit) ||
(timestampCapabilities->HardwareCapabilities.TaggedTransmit) ||
(timestampCapabilities->HardwareCapabilities.AllTransmit)))
{
return TRUE;
}
return FALSE;
}
BOOL
IsPTPv2HardwareTimestampingSupportedForIPv6(PINTERFACE_TIMESTAMP_CAPABILITIES timestampCapabilities)
{
// Supported if both receive and transmit side support is present
if (((timestampCapabilities->HardwareCapabilities.PtpV2OverUdpIPv6EventMessageReceive) ||
(timestampCapabilities->HardwareCapabilities.PtpV2OverUdpIPv6AllMessageReceive) ||
(timestampCapabilities->HardwareCapabilities.AllReceive))
&&
((timestampCapabilities->HardwareCapabilities.PtpV2OverUdpIPv6EventMessageTransmit) ||
(timestampCapabilities->HardwareCapabilities.PtpV2OverUdpIPv6AllMessageTransmit) ||
(timestampCapabilities->HardwareCapabilities.TaggedTransmit) ||
(timestampCapabilities->HardwareCapabilities.AllTransmit)))
{
return TRUE;
}
return FALSE;
}
enum SupportedTimestampType
{
TimestampTypeNone = 0,
TimestampTypeSoftware = 1,
TimestampTypeHardware = 2
};
// This function checks and returns the supported timestamp capabilities for an interface for
// a PTPv2 application
SupportedTimestampType
CheckActiveTimestampCapabilitiesForPtpv2(NET_LUID interfaceLuid)
{
DWORD result = NO_ERROR;
INTERFACE_TIMESTAMP_CAPABILITIES timestampCapabilities;
SupportedTimestampType supportedType = TimestampTypeNone;
result = GetInterfaceActiveTimestampCapabilities(
&interfaceLuid,
×tampCapabilities);
if (result != NO_ERROR)
{
printf("Error retrieving hardware timestamp capabilities: %d\n", result);
goto Exit;
}
if (IsPTPv2HardwareTimestampingSupportedForIPv4(×tampCapabilities) &&
IsPTPv2HardwareTimestampingSupportedForIPv6(×tampCapabilities))
{
supportedType = TimestampTypeHardware;
goto Exit;
}
else
{
if ((timestampCapabilities.SoftwareCapabilities.AllReceive) &&
((timestampCapabilities.SoftwareCapabilities.AllTransmit) ||
(timestampCapabilities.SoftwareCapabilities.TaggedTransmit)))
{
supportedType = TimestampTypeSoftware;
}
}
Exit:
return supportedType;
}
// Helper function which does the correlation between hardware and system clock
// using mathematical techniques
void ComputeCorrelationOfHardwareAndSystemTimestamps(INTERFACE_HARDWARE_CROSSTIMESTAMP *crossTimestamp);
// An application would call this function periodically to gather a set
// of matching timestamps for use in converting hardware timestamps to
// system timestamps
DWORD
RetrieveAndProcessCrossTimestamp(NET_LUID interfaceLuid)
{
DWORD result = NO_ERROR;
INTERFACE_HARDWARE_CROSSTIMESTAMP crossTimestamp;
result = CaptureInterfaceHardwareCrossTimestamp(
&interfaceLuid,
&crossTimestamp);
if (result != NO_ERROR)
{
printf("Error retrieving cross timestamp for the interface: %d\n", result);
goto Exit;
}
// Process crossTimestamp further to create a relation between the hardware clock
// of the NIC and the QPC values using appropriate mathematical techniques
ComputeCorrelationOfHardwareAndSystemTimestamps(&crossTimestamp);
Exit:
return result;
}
int main()
{
}
程式碼範例 2- 註冊時間戳記功能變更通知
此範例示範您的應用程式如何使用端對端時間戳記。
// main.cpp in a Console App project.
#include <stdlib.h>
#include <stdio.h>
#include <winsock2.h>
#include <mswsock.h>
#include <iphlpapi.h>
#include <mstcpip.h>
#pragma comment(lib, "Ws2_32")
#pragma comment(lib, "Iphlpapi")
// Globals and function declarations used by the application.
// The sample functions and skeletons demonstrate:
// - Checking timestamp configuration for an interface to determine if timestamping can be used
// - If timestamping is enabled, starts tracking changes in timestamp configuration
// - Performing correlation between hardware and system timestamps using cross timestamps
// on a separate thread depending on the timestamp type configured
// - Receiving a packet and computing the latency between when the timestamp
// was generated on packet reception, and when the packet was received by
// the application through the socket
// The sample tries to demonstrate how an application could use timestamps. It is not thread safe
// and does not do exhaustive error checking.
// Lot of the functions are provided as skeletons, or only declared and invoked
// but are not defined. It is up to
// the application to implement these suitably.
// An application could use the functions below by e.g.
// - Call InitializeTimestampingForInterface for the interface it wants to track for timestamping capability.
// - Call EstimateReceiveLatency to estimate the receive latency of a packet depending on the timestamp
// type configured for the interface.
enum SupportedTimestampType
{
TimestampTypeNone = 0,
TimestampTypeSoftware = 1,
TimestampTypeHardware = 2
};
// interfaceBeingTracked is the interface the PTPv2 application
// intends to use for timestamping purpose.
wchar_t* interfaceBeingTracked;
// The active timestamping type determined for
// interfaceBeingTracked.
SupportedTimestampType timestampTypeEnabledForInterface;
HANDLE correlationThread;
HANDLE threadStopEvent;
HIFTIMESTAMPCHANGE TimestampChangeNotificationHandle = NULL;
// Function from sample above to check if an interface supports timestamping for PTPv2.
SupportedTimestampType CheckActiveTimestampCapabilitiesForPtpv2(NET_LUID interfaceLuid);
// Function from sample above to retrieve cross timestamps and process them further.
DWORD RetrieveAndProcessCrossTimestamp(NET_LUID interfaceLuid);
// Helper function which registers for timestamp configuration changes.
DWORD RegisterTimestampChangeNotifications();
// Callback function which is invoked when timestamp configuration changes
// for some network interface.
INTERFACE_TIMESTAMP_CONFIG_CHANGE_CALLBACK TimestampConfigChangeCallback;
// Function which does the correlation between hardware and system clock
// using mathematical techniques. It is periodically invoked and provided
// a sample of cross timestamp to compute a correlation.
void ComputeCorrelationOfHardwareAndSystemTimestamps(INTERFACE_HARDWARE_CROSSTIMESTAMP *crossTimestamp);
// Helper function which converts a hardware timestamp from the NIC clock
// to system timestamp (QPC) values. It is assumed that this works together
// with the ComputeCorrelationOfHardwareAndSystemTimestamps function
// to derive the correlation.
ULONG64 ConvertHardwareTimestampToQpc(ULONG64 HardwareTimestamp);
// Start function of thread which periodically samples
// cross timestamps to correlate hardware and software timestamps.
DWORD WINAPI CorrelateHardwareAndSystemTimestamps(LPVOID);
// Helper function which starts a new thread at CorrelateHardwareAndSystemTimestamps.
DWORD StartCorrelatingHardwareAndSytemTimestamps();
// Helper function which restarts correlation when some change is detected.
DWORD RestartCorrelatingHardwareAndSystemTimestamps();
// Stops the correlation thread.
DWORD StopCorrelatingHardwareAndSystemTimestamps();
DWORD
FindInterfaceFromFriendlyName(wchar_t* friendlyName, NET_LUID* interfaceLuid)
{
DWORD result = 0;
ULONG flags = 0;
ULONG outBufLen = 0;
PIP_ADAPTER_ADDRESSES pAddresses = NULL;
PIP_ADAPTER_ADDRESSES currentAddresses = NULL;
result = GetAdaptersAddresses(0,
flags,
NULL,
pAddresses,
&outBufLen);
if (result == ERROR_BUFFER_OVERFLOW)
{
pAddresses = (PIP_ADAPTER_ADDRESSES)malloc(outBufLen);
result = GetAdaptersAddresses(0,
flags,
NULL,
pAddresses,
&outBufLen);
if (result != NO_ERROR)
{
goto Done;
}
}
else if (result != NO_ERROR)
{
goto Done;
}
currentAddresses = pAddresses;
while (currentAddresses != NULL)
{
if (wcscmp(friendlyName, currentAddresses->FriendlyName) == 0)
{
result = ConvertInterfaceIndexToLuid(currentAddresses->IfIndex, interfaceLuid);
goto Done;
}
currentAddresses = currentAddresses->Next;
}
result = ERROR_NOT_FOUND;
Done:
if (pAddresses != NULL)
{
free(pAddresses);
}
return result;
}
// This function checks if an interface is suitable for
// timestamping for PTPv2. If so, it registers for timestamp
// configuration changes and initializes some globals.
// If hardware timestamping is enabled it also starts
// correlation thread.
DWORD
InitializeTimestampingForInterface(wchar_t* friendlyName)
{
DWORD error;
SupportedTimestampType supportedType = TimestampTypeNone;
NET_LUID interfaceLuid;
error = FindInterfaceFromFriendlyName(friendlyName, &interfaceLuid);
if (error != 0)
{
return error;
}
supportedType = CheckActiveTimestampCapabilitiesForPtpv2(interfaceLuid);
if (supportedType != TimestampTypeNone)
{
error = RegisterTimestampChangeNotifications();
if (error != NO_ERROR)
{
return error;
}
if (supportedType == TimestampTypeHardware)
{
threadStopEvent = CreateEvent(
NULL,
FALSE,
FALSE,
NULL
);
if (threadStopEvent == NULL)
{
return GetLastError();
}
error = StartCorrelatingHardwareAndSytemTimestamps();
if (error != 0)
{
return error;
}
}
interfaceBeingTracked = friendlyName;
timestampTypeEnabledForInterface = supportedType;
return error;
}
return ERROR_NOT_SUPPORTED;
}
DWORD
RegisterTimestampChangeNotifications()
{
DWORD retcode = NO_ERROR;
// Register with NULL context
retcode = RegisterInterfaceTimestampConfigChange(TimestampConfigChangeCallback, NULL, &TimestampChangeNotificationHandle);
if (retcode != NO_ERROR)
{
printf("Error when calling RegisterIfTimestampConfigChange %d\n", retcode);
}
return retcode;
}
// The callback invoked when change in some interface’s timestamping configuration
// happens. The callback takes appropriate action based on the new capability of the
// interface. The callback assumes that there is only 1 NIC. If multiple NICs are being
// tracked for timestamping then the application would need to check all of them.
VOID
WINAPI
TimestampConfigChangeCallback(
_In_ PVOID /*CallerContext*/
)
{
SupportedTimestampType supportedType;
NET_LUID interfaceLuid;
DWORD error;
error = FindInterfaceFromFriendlyName(interfaceBeingTracked, &interfaceLuid);
if (error != NO_ERROR)
{
if (timestampTypeEnabledForInterface == TimestampTypeHardware)
{
StopCorrelatingHardwareAndSystemTimestamps();
timestampTypeEnabledForInterface = TimestampTypeNone;
}
return;
}
supportedType = CheckActiveTimestampCapabilitiesForPtpv2(interfaceLuid);
if ((supportedType == TimestampTypeHardware) &&
(timestampTypeEnabledForInterface == TimestampTypeHardware))
{
// NIC could have been restarted, restart the correlation between hardware and
// system timestamps.
RestartCorrelatingHardwareAndSystemTimestamps();
}
else if (supportedType == TimestampTypeHardware)
{
// Start thread correlating hardware and software timestamps
StartCorrelatingHardwareAndSytemTimestamps();
}
else if (supportedType != TimestampTypeHardware)
{
// Hardware timestamps are not enabled, stop correlation
StopCorrelatingHardwareAndSystemTimestamps();
}
timestampTypeEnabledForInterface = supportedType;
}
DWORD
StartCorrelatingHardwareAndSytemTimestamps()
{
// Create a new thread which starts at CorrelateHardwareAndSoftwareTimestamps
correlationThread = CreateThread(
NULL,
0,
CorrelateHardwareAndSystemTimestamps,
NULL,
0,
NULL);
if (correlationThread == NULL)
{
return GetLastError();
}
}
// Thread which periodically invokes functions to
// sample cross timestamps and use them to compute
// correlation between hardware and system timestamps.
DWORD WINAPI
CorrelateHardwareAndSystemTimestamps(LPVOID /*lpParameter*/)
{
DWORD error;
NET_LUID interfaceLuid;
DWORD result;
result = FindInterfaceFromFriendlyName(interfaceBeingTracked, &interfaceLuid);
if (result != 0)
{
return result;
}
while (TRUE)
{
error = RetrieveAndProcessCrossTimestamp(interfaceLuid);
// Sleep and repeat till the thread gets a signal to stop
result = WaitForSingleObject(threadStopEvent, 5000);
if (result != WAIT_TIMEOUT)
{
if (result == WAIT_OBJECT_0)
{
return 0;
}
else if (result == WAIT_FAILED)
{
return GetLastError();
}
return result;
}
}
}
DWORD
StopCorrelatingHardwareAndSystemTimestamps()
{
SetEvent(threadStopEvent);
return 0;
}
// Function which receives a packet and estimates the latency between the
// point at which receive timestamp (of appropriate type) was generated
// and when the packet was received in the app through the socket.
// The sample assumes that there is only 1 NIC in the system. This is the NIC which is tracked through
// interfaceBeingTracked for correlation purpose, and through which packets are being
// received by the socket.
// The recvmsg parameter is of type LPFN_WSARECVMSG and an application can
// retrieve it by issuing WSAIoctl
// with SIO_GET_EXTENSION_FUNCTION_POINTER control
// and WSAID_WSARECVMSG. Please refer to msdn.
void EstimateReceiveLatency(SOCKET sock, LPFN_WSARECVMSG recvmsg)
{
DWORD numBytes;
INT error;
CHAR data[512];
CHAR control[WSA_CMSG_SPACE(sizeof(UINT64))] = { 0 };
WSABUF dataBuf;
WSABUF controlBuf;
WSAMSG wsaMsg;
UINT64 socketTimestamp = 0;
ULONG64 appLevelTimestamp;
ULONG64 packetReceivedTimestamp;
dataBuf.buf = data;
dataBuf.len = sizeof(data);
controlBuf.buf = control;
controlBuf.len = sizeof(control);
wsaMsg.name = NULL;
wsaMsg.namelen = 0;
wsaMsg.lpBuffers = &dataBuf;
wsaMsg.dwBufferCount = 1;
wsaMsg.Control = controlBuf;
wsaMsg.dwFlags = 0;
// Configure rx timestamp reception.
TIMESTAMPING_CONFIG config = { 0 };
config.Flags |= TIMESTAMPING_FLAG_RX;
error =
WSAIoctl(
sock,
SIO_TIMESTAMPING,
&config,
sizeof(config),
NULL,
0,
&numBytes,
NULL,
NULL);
if (error == SOCKET_ERROR)
{
printf("WSAIoctl failed %d\n", WSAGetLastError());
return;
}
error =
recvmsg(
sock,
&wsaMsg,
&numBytes,
NULL,
NULL);
if (error == SOCKET_ERROR)
{
printf("recvmsg failed %d\n", WSAGetLastError());
return;
}
if (timestampTypeEnabledForInterface != TimestampTypeNone)
{
// Capture system timestamp (QPC) upon message reception.
LARGE_INTEGER t1;
QueryPerformanceCounter(&t1);
appLevelTimestamp = t1.QuadPart;
printf("received packet\n");
// Look for socket rx timestamp returned via control message.
BOOLEAN retrievedTimestamp = FALSE;
PCMSGHDR cmsg = WSA_CMSG_FIRSTHDR(&wsaMsg);
while (cmsg != NULL)
{
if (cmsg->cmsg_level == SOL_SOCKET && cmsg->cmsg_type == SO_TIMESTAMP)
{
socketTimestamp = *(PUINT64)WSA_CMSG_DATA(cmsg);
retrievedTimestamp = TRUE;
break;
}
cmsg = WSA_CMSG_NXTHDR(&wsaMsg, cmsg);
}
if (retrievedTimestamp)
{
// Compute socket receive path latency.
LARGE_INTEGER clockFrequency;
ULONG64 elapsedMicroseconds;
if (timestampTypeEnabledForInterface == TimestampTypeHardware)
{
packetReceivedTimestamp = ConvertHardwareTimestampToQpc(socketTimestamp);
}
else
{
packetReceivedTimestamp = socketTimestamp;
}
QueryPerformanceFrequency(&clockFrequency);
// Compute socket receive path latency.
elapsedMicroseconds = appLevelTimestamp - packetReceivedTimestamp;
elapsedMicroseconds *= 1000000;
elapsedMicroseconds /= clockFrequency.QuadPart;
printf("RX latency estimation: %lld microseconds\n",
elapsedMicroseconds);
}
else
{
printf("failed to retrieve RX timestamp\n");
}
}
}
int main()
{
}