You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: notes/linkLayer/linkLayerNotes-V4.tex
+16-3
Original file line number
Diff line number
Diff line change
@@ -63,15 +63,16 @@ \subsection{Higher layer to EGP}
63
63
$t_{\max}$ & Maximum acceptable waiting time before request is completed. \\
64
64
Purpose ID & Identifying the purpose or application at this node (optional, default 0). \\
65
65
Priority & Manual setting of a priority for entanglement production (optional).\\
66
-
Store & Instructs the EGP whether to store the entangled qubit into memory. \\
66
+
Store & Instructs the EGP whether to store the entangled qubit into memory (optional, default True).\\
67
+
Measure Directly & Instructs the EGP to return measurements on entangled qubits (optional, default False). \\
67
68
create ID & Sequence number identifying this CREATE command.
68
69
\end{tabular}
69
70
\end{description}
70
71
\subsection{EGP to higher layer}
71
72
Following the reception of the CREATE command, several actions of the EGP are possible. Let us start with the positive outcome, and then consider possible
72
73
errors. An OK message will be delivered at both nodes involved in the entanglement generation process.
73
74
\begin{description}
74
-
\item[OK] Entangled pair has successfully been produced deterministically (heralded). One message per pair created, delivered immediately (best effort) following pair creation.
75
+
\item[CK\_OK] Entangled pair has successfully been produced deterministically (heralded). One message per pair created, delivered immediately (best effort) following pair creation.
75
76
With high confidence, the minimum acceptable fidelity $F_{\min}$ has been met, and the entanglement has been generated
76
77
within the specified time frame $t_{\max}$. Information about the entanglement generation is provided, including an entanglement identifier. This identifier is required
77
78
to be globally unique, and agreed upon by $A$ and $B$. That is, $A$ and $B$ can locally use this entanglement identifier to determine which of their qubits is entangled with the remote
@@ -86,7 +87,7 @@ \subsection{EGP to higher layer}
86
87
87
88
\smallskip
88
89
\noindent
89
-
In addition the OK message also includes the following local information. We remark that Qubit IDs are exclusively local information (akin to the memory address
90
+
In addition the CK\_OK message also includes the following local information. We remark that Qubit IDs are exclusively local information (akin to the memory address
90
91
in a computer) and not in general shared between network nodes.\\
91
92
\noindent
92
93
\begin{tabular}{ll}
@@ -98,6 +99,18 @@ \subsection{EGP to higher layer}
98
99
$logical\_id$ & Logical ID of the qubit locally holding the entanglement.
99
100
\end{tabular}
100
101
\end{description}
102
+
\begin{description}
103
+
\item[MD\_OK] Measurement of of heralded entangled pair has successfully been performed. One message per pair created, delivered immediately (best effort) following heralding at midpoint.
104
+
The MD\_OK also includes an entanglement identifier so that measurement results can be related by peers at higher layers. The MD\_OK message includes the following local information in addition to the entanglement identifier. \\
105
+
\noindent
106
+
\begin{tabular}{ll}
107
+
create ID & The create ID that this entangled pair corresponds to. \\
108
+
Measurement Outcome & The value measured on the communication qubit. \\
109
+
Measurement Basis & The measurement basis used (chosen randomly from Z and X bases).\\
110
+
$t_{Create}$ & Time the bit was produced.\\
111
+
\end{tabular}
112
+
\end{description}
113
+
101
114
Entanglement generation may fail for wide number of reasons, some of which form an immediate error. It may also be that the entanglement later expires, or is discarded
102
115
of which the EGP will inform the higher layer. Let us start by listing the immediate failure modes, where in all such cases the create ID will be included allowing the
103
116
higher layer to identify which request has failed.\\
0 commit comments