Skip to content

Commit 0b94517

Browse files
committed
Issue #161: Updated link layer notes to distinguish Create+Keep OK's (CK_OK) from Measure Directly OK's (MD_OK).
1 parent e7869da commit 0b94517

File tree

2 files changed

+16
-3
lines changed

2 files changed

+16
-3
lines changed

notes/linkLayer/linkLayerNotes-V4.pdf

1.11 KB
Binary file not shown.

notes/linkLayer/linkLayerNotes-V4.tex

+16-3
Original file line numberDiff line numberDiff line change
@@ -63,15 +63,16 @@ \subsection{Higher layer to EGP}
6363
$t_{\max}$ & Maximum acceptable waiting time before request is completed. \\
6464
Purpose ID & Identifying the purpose or application at this node (optional, default 0). \\
6565
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). \\
6768
create ID & Sequence number identifying this CREATE command.
6869
\end{tabular}
6970
\end{description}
7071
\subsection{EGP to higher layer}
7172
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
7273
errors. An OK message will be delivered at both nodes involved in the entanglement generation process.
7374
\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.
7576
With high confidence, the minimum acceptable fidelity $F_{\min}$ has been met, and the entanglement has been generated
7677
within the specified time frame $t_{\max}$. Information about the entanglement generation is provided, including an entanglement identifier. This identifier is required
7778
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}
8687

8788
\smallskip
8889
\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
9091
in a computer) and not in general shared between network nodes.\\
9192
\noindent
9293
\begin{tabular}{ll}
@@ -98,6 +99,18 @@ \subsection{EGP to higher layer}
9899
$logical\_id$ & Logical ID of the qubit locally holding the entanglement.
99100
\end{tabular}
100101
\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+
101114
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
102115
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
103116
higher layer to identify which request has failed.\\

0 commit comments

Comments
 (0)