IP Library › Granted Patent US 12,547,583
Granted Patent B2
US 12,547,583 · App. 18/417,497 · Granted Feb 10, 2026

Quantum file management system

Inventors: Stephen Coady (Dublin, IE); Leigh Griffin (Waterford, IE)
Assignee: Red Hat, LLC
G06F16/11G06F16/13G06F16/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,547,583
App. No.
18/417,497
Granted
Feb 10, 2026
Kind
B2
Abstract

A quantum file management system is disclosed. A quantum file manager receives, from a requestor, a request to access a quantum file that comprises a plurality of qubits. The quantum file manager determines, for each respective qubit of the plurality of qubits, a qubit identifier of the respective qubit. The quantum file manager sends, to the requestor in response to the request, information that includes the qubit identifier for each respective qubit of the plurality of qubits.

Claims (46)

1 . A method, comprising:

in response to a request from a requestor to access a quantum file that encodes contextually-related data across a plurality of qubits, identifying, by a quantum file manager executing on one or more quantum computing systems, a quantum file registry record that stores a qubit identifier for each qubit in the quantum file, wherein the plurality of qubits encode the contextually-related data in a particular sequential order, and wherein the quantum file comprises a field comprising order data indicative of the particular sequential order;

accessing, by the quantum file manager, the quantum file registry record to determine, for each respective qubit of the plurality of qubits, information that includes the qubit identifier of the respective qubit and a status of the respective qubit;

providing, by the quantum file manager to the requestor, the qubit identifier for each respective qubit of the plurality of qubits, the status for each respective qubit of the plurality of qubits, and the order data indicative of the particular sequential order;

receiving, by the quantum file manager, location change information that indicates that data stored on a first qubit of the plurality of qubits has been moved to a second qubit that is not in the plurality of qubits;

removing, from the quantum file registry record, information regarding the first qubit; and

adding, to the quantum file registry record, information identifying the second qubit.

2 . The method of claim 1 , further comprising:

determining, for each respective qubit of the plurality of qubits, that the respective qubit is in an entanglement state of entangled or not entangled; and

wherein the status is based on the entanglement state of the respective qubit.

3 . The method of claim 2 , wherein, for each respective qubit of the plurality of qubits, the status identifies the entanglement state of the respective qubit.

4 . The method of claim 3 , wherein an entanglement state of the first qubit of the plurality of qubits is that the first qubit is entangled, and an entanglement state of a third qubit of the plurality of qubits is that the third qubit is not entangled.

5 . The method of claim 1 , wherein the qubit identifier for the first qubit of the plurality of qubits identifies a first quantum computing system and the qubit identifier for a third qubit of the plurality of qubits identifies a second quantum computing system.

6 . The method of claim 1 , further comprising identifying, by the quantum file manager, a linking service for the quantum file.

7 . The method of claim 6 , wherein identifying, by the quantum file manager, the linking service for the quantum file further comprises accessing, by the quantum file manager, a quantum file reference that corresponds to the quantum file, wherein the quantum file reference identifies the linking service.

8 . The method of claim 1 , further comprising:

prior to receiving the request to access the quantum file, receiving, by the quantum file manager from a file creation requestor, a file creation request to create the quantum file, the file creation request including a quantum assembly language (QASM) file identifier that identifies a QASM file;

analyzing, by the quantum file manager, the QASM file to determine a number of qubits for the quantum file;

obtaining, from a qubit registry, qubit identification information that identifies a plurality of available qubits;

generating a quantum file reference that corresponds to the quantum file, the quantum file reference comprising information that identifies the available qubits; and

returning, to the file creation requestor, an identifier that identifies the quantum file reference.

9 . The method of claim 8 , wherein the file creation request includes the identifier.

10 . The method of claim 8 , wherein the first qubit of the plurality of qubits is implemented by a first quantum computing system and a third qubit of the plurality of qubits is implemented by a second computing system.

11 . The method of claim 8 , wherein the information that identifies the available qubits comprises a plurality of qubit identifiers, each qubit identifier corresponding to one of the plurality of qubits.

12 . The method of claim 1 , further comprising:

prior to receiving the request to access the quantum file, receiving, by the quantum file manager from a file creation requestor, a file creation request to create the quantum file, the file creation request identifying the plurality of qubits;

determining, based at least in part on the file creation request, a quantity of metadata qubits for maintaining metadata about the quantum file; and

generating a quantum file reference, using the metadata qubits, that corresponds to the quantum file, the quantum file reference comprising information that identifies the plurality of qubits.

13 . The method of claim 12 , wherein generating the quantum file reference using the metadata qubits comprises storing, to the metadata qubits, the information that identifies the plurality of qubits.

14 . The method of claim 12 , further comprising obtaining, from a qubit registry, qubit identification information that identifies the metadata qubits.

15 . A quantum computing system, comprising:

a memory; and

at least one processor device coupled to the memory to:

in response to a request from a requestor to access a quantum file that encodes contextually-related data across a plurality of qubits, identify, by a quantum file manager, a quantum file registry record that stores a qubit identifier for each qubit in the quantum file, wherein the plurality of qubits encode the contextually-related data in a particular sequential order, and wherein the quantum file comprises a field comprising order data indicative of the particular sequential order;

access, by the quantum file manager, the quantum file registry record to determine, for each respective qubit of the plurality of qubits, information that includes the qubit identifier of the respective qubit and a status of the respective qubit;

provide, by the quantum file manager to the requestor, the qubit identifier for each respective qubit of the plurality of qubits, the status for each respective qubit of the plurality of qubits, and the order data indicative of the particular sequential order;

receive, by the quantum file manager, location change information that indicates that data stored on a first qubit of the plurality of qubits has been moved to a second qubit that is not in the plurality of qubits;

remove, from the quantum file registry record, information regarding the first qubit; and

add, to the quantum file registry record, information identifying the second qubit.

16 . A computer program product stored on a non-transitory computer-readable storage medium and including instructions to cause a processor device to:

in response to a request from a requestor to access a quantum file that encodes contextually-related data across a plurality of qubits, identify, by a quantum file manager executing on one or more quantum computing systems, a quantum file registry record that stores a qubit identifier for each qubit in the quantum file, wherein the plurality of qubits encode the contextually-related data in a sequential order, and wherein the quantum file comprises a field comprising order data indicative of the particular sequential order;

access, by the quantum file manager, the quantum file registry record to determine, for each respective qubit of the plurality of qubits, information that includes the qubit identifier of the respective qubit and a status of the respective qubit;

provide, by the quantum file manager to the requestor, the qubit identifier for each respective qubit of the plurality of qubits, the status for each respective qubit of the plurality of qubits, and the order data indicative of the particular sequential order;

receive, by the quantum file manager, location change information that indicates that data stored on a first qubit of the plurality of qubits has been moved to a second qubit that is not in the plurality of qubits;

remove, from the quantum file registry record, information regarding the first qubit; and

add, to the quantum file registry record, information identifying the second qubit.

Assignments (2)
MERGER AND CHANGE OF NAME Recorded Jan 20, 2026
From: RED HAT, INC.; RED HAT, LLC
To: RED HAT, LLC
Reel/Frame 074456/0595 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 23, 2024
From: COADY, STEPHEN; GRIFFIN, LEIGH
To: RED HAT, INC.
Reel/Frame 066207/0684 →
Continuity (2)
Continuation 16859571 · Apr 27, 2020
Related Publication 20240184742A1 · Jun 6, 2024
References Cited (109)
US 7451292B2 · Routt · 2008 [cited by applicant]
US 7639035B2 · Berkley · 2009 [cited by applicant]
US 7853011B2 · Kuang et al. · 2010 [cited by applicant]
US 8102185B2 · Johansson et al. · 2012 [cited by applicant]
US 8434027B2 · Jones · 2013 [cited by applicant]
US 8600051B2 · Noh · 2013 [cited by applicant]
US 8959115B2 · Marathe · 2015 [cited by applicant]
US 9264226B2 · Harrison et al. · 2016 [cited by applicant]
US 9495644B2 · Chudak et al. · 2016 [cited by applicant]
US 9509506B2 · Hughes et al. · 2016 [cited by applicant]
US 9537953B1 · Dadashikelayeh et al. · 2017 [cited by applicant]
US 9774401B1 · Borrill · 2017 [cited by applicant]
US 9847913B2 · Kanda et al. · 2017 [cited by applicant]
US 9887976B2 · Hughes et al. · 2018 [cited by applicant]
US 10331658B2 · Pennefather et al. · 2019 [cited by applicant]
US 10592216B1 · Richardson et al. · 2020 [cited by applicant]
US 20030121028A1 · Coury et al. · 2003 [cited by applicant]
US 20050193221A1 · Yoneyama · 2005 [cited by applicant]
US 20120093521A1 · Harrison et al. · 2012 [cited by applicant]
US 20120124092A1 · Teranishi et al. · 2012 [cited by applicant]
US 20130308956A1 · Meyers et al. · 2013 [cited by applicant]
US 20140254660A1 · La · 2014 [cited by applicant]
US 20140365843A1 · Ashikhmin · 2014 [cited by applicant]
US 20160071021A1 · Raymond · 2016 [cited by applicant]
US 20160321316A1 · Pennefather · 2016 [cited by examiner]
US 20170351974A1 · Rose et al. · 2017 [cited by applicant]
US 20180091440A1 · Dadashikelayeh et al. · 2018 [cited by applicant]
US 20180144262A1 · Roetteler et al. · 2018 [cited by applicant]
US 20180181685A1 · Roetteler et al. · 2018 [cited by applicant]
US 20180336371A1 · Fortmann et al. · 2018 [cited by applicant]
US 20180365585A1 · Smith et al. · 2018 [cited by applicant]
US 20190042971A1 · Zou · 2019 [cited by applicant]
US 20190179730A1 · Geller et al. · 2019 [cited by applicant]
US 20190378032A1 · Kliuchnikov et al. · 2019 [cited by applicant]
US 20200074346A1 · Griffin · 2020 [cited by examiner]
US 20200125402A1 · Griffin et al. · 2020 [cited by applicant]
US 20200133947A1 · Wang · 2020 [cited by applicant]
US 20200184025A1 · Horii et al. · 2020 [cited by applicant]
US 20200184031A1 · Horii · 2020 [cited by applicant]
US 20200201655A1 · Griffin et al. · 2020 [cited by applicant]
US 20200227522A1 · Leipold et al. · 2020 [cited by applicant]
US 20200272926A1 · Chaplin et al. · 2020 [cited by applicant]
US 20200301562A1 · Gupta et al. · 2020 [cited by applicant]
US 20200313063A1 · Pollanen et al. · 2020 [cited by applicant]
US 20200358187A1 · Tran et al. · 2020 [cited by applicant]
US 20200374211A1 · Griffin et al. · 2020 [cited by applicant]
US 20200387821A1 · Griffin et al. · 2020 [cited by applicant]
US 20210027188A1 · Nickerson et al. · 2021 [cited by applicant]
US 20210036846A1 · Grice et al. · 2021 [cited by applicant]
US 20210058243A1 · Starodubtsev · 2021 [cited by applicant]
US 20210182234A1 · Beigi · 2021 [cited by examiner]
US 20210182724A1 · Zou et al. · 2021 [cited by applicant]
US 20210303155A1 · Meister et al. · 2021 [cited by applicant]
US 20210334237A1 · Coady · 2021 [cited by examiner]
US 20220269976A1 · Wang · 2022 [cited by examiner]
US 20230040289A1 · Sels · 2023 [cited by examiner]
CN 105164704 · 2018 [cited by applicant]
CN 109816112 · 2019 [cited by applicant]
CN 114503027 · 2022 [cited by applicant]
JP 6465876 · 2019 [cited by applicant]
WO WO2016206498 · 2016 [cited by applicant]
WO WO2018111242 · 2018 [cited by applicant]
Barnum, H. et al., “Authentication of Quantum Messages,” Forty-third Annual Institute of Electrical and Electronics Engineers Symposium on Foundations of Computer Science, Nov. 2002, 10 pages. [cited by applicant]
Bushwick, S., “New Encryption System Protects Data from Quantum Computers,” Scientific American, Oct. 8, 2019, https://www.scientificamerican.com/ article/new-encryption-system-protects-data-from-quantum-computers/, 5 p… [cited by applicant]
Chen, S., “What if Quantum Computers Used Hard Drives made of DNA?” Wired, Mar. 15, 2017, https://www.wired.com/2017/03/quantum-computers-used-hard-drives-made-dna/, 10 pages. [cited by applicant]
Cheng, S.T. et al., “Quantum Switching and Quantum Merge Sorting,” Institute of Electrical and Electronics Engineers Transactions on Circuits and Systems I: Regular Papers, vol. 53, Issue 2, Feb. 2006, 10 pages. [cited by applicant]
Choi, C., “A Data Bus for Quantum Computers,” Institute of Electrical and Electronics Engineers Spectrum, Nov. 9, 2017, https://spectrum.ieee.org/tech-talk/computing/hardware/a-quantum-bus-for-quantum-computers, 3 pages. [cited by applicant]
Gühne, O., et al., “Entanglement Detection,” Physics Reports, vol. 474, No. 1, Feb. 27, 2009, 90 pages. [cited by applicant]
Lee, C., “New Form of Qubit Control May Yield Longer Computation Times,” Ars Technica, Jan. 26, 2018, Wired Media Group, 5 pages. [cited by applicant]
Mina, M., et al., “EntangleNet: Theoretical Reestablishment of Entanglement in Quantum Networks,” Applied Science, vol. 8, Issue 10, Oct. 16, 2018, 17 pages. [cited by applicant]
Pathumsoot, P., et al., “Modeling of Measurement-based Quantum Network Coding on IBM Q Experience Devices,” arXiv: 1910.00815v2 [quant-ph], Nov. 12, 2019, 10 pages. [cited by applicant]
Schoute, E., et al., “Shortcuts to Quantum Network Routing,” Jul. 9, 2016, available online at https://obj.umiacs.umd.edu/extended_abstracts/QCrypt_2016_paper_203.pdf, 2 pages. [cited by applicant]
Sillanpaa, M. et al., “Coherent Quantum State Storage and Transfer Between Two Phase Qubits Via a Resonant Cavity,” Nature, vol. 449, Sep. 2007, Nature Publishing Group, pp. 438-442. [cited by applicant]
Toyoizumi, H., “Performance Evaluation of Quantum Merging: Negative Queue Length,” Waseda University, accessed Apr. 2020 from http://www.f.was eda.jp/toyoizumi/research/papers/Performance%20Evaluation.%20of%20Qua ntum%2… [cited by applicant]
Whitehouse, L., “Data deduplication methods: Block-level versus byte-level dedupe,” Nov. 24, 2008, https://www.techtarget.com/searchdatabackup/tip /Data-deduplication-methods-Block-level-versus-byte-level-dedupe, 2 page… [cited by applicant]
Yamasaki, H. et al., “Quantum State Merging for Arbitrarily Small-Dimensional Systems,” Institute of Electrical and Electronics Engineers Transactions on Information Theory, vol. 65, No. 6, Jun. 2019, pp. 3950-3972. [cited by applicant]
Yang, C., et al., “Entanglement Generation and Quantum Information Transfer Between Spatially-Separated Qubits In Different Cavities,” New Journal of Physics, vol. 15, Nov. 1, 2013, 19 pages. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 16/227,747, mailed Jun. 10, 2021, 7 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 15/930,025, mailed Oct. 1, 2021, 10 pages. [cited by applicant]
Applicant-Initiated Interview Summary for U.S. Appl. No. 15/930,025, mailed Dec. 17, 2021, 3 pages. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 16/912,200, mailed Oct. 13, 2022, 9 pages. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 16/912,091, mailed Sep. 14, 2022, 10 pages. [cited by applicant]
Notice of Allowance and Examiner-Initiated Interview Summary for U.S. Appl. No. 15/930,025, mailed Apr. 8, 2022, 13 pages. [cited by applicant]
Notice of Allowance, Examiner's Amendment, and Examiner-Initiated Interview Summary for U.S. Appl. No. 16/912,045, mailed Oct. 4, 2022, 12 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/909,477, mailed Sep. 30, 2022, 34 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/912,200, mailed May 12, 2022, 39 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/912,045, mailed Apr. 14, 2022, 9 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/859,571, mailed May 20, 2022, 21 pages. [cited by applicant]
Final Office Action and Examiner Interview Summary for U.S. Appl. No. 16/859,571, mailed Dec. 8, 2022, 14 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/859,571, mailed Oct. 28, 2021, 9 pages. [cited by applicant]
Final Office Action for U.S. Appl. No. 16/912,091, mailed Jun. 20, 2022, 14 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/912,091, mailed Jan. 27, 2022, 14 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/884,928, mailed Nov. 4, 2022, 49 pages. [cited by applicant]
Notice of Allowance for U.S. Appl. No. 16/909,477, mailed Feb. 2, 2023, 13 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/883,280, mailed Jan. 18, 2023, 22 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/859,571, mailed Jun. 8, 2023, 17 pages. [cited by applicant]
Final Office Action for U.S. Appl. No. 16/884,928, mailed May 22, 2023, 39 pages. [cited by applicant]
Notice of Allowance and Notice of Allowability for U.S. Appl. No. 17/883,280, mailed Aug. 30, 2023, 11 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 16/884,928, mailed Oct. 5, 2023, 28 pages. [cited by applicant]
Corrected Notice of Allowability for U.S. Appl. No. 16/859,571, mailed Oct. 6, 2023, 13 pages. [cited by applicant]
Notice of Allowance and Notice of Allowability for U.S. Appl. No. 16/859,571, mailed Sep. 26, 2023, 20 pages. [cited by applicant]
U.S. Appl. No. 16/227,747, filed Dec. 20, 2018. [cited by applicant]
U.S. Appl. No. 15/930,025, filed May 12, 2020. [cited by applicant]
U.S. Appl. No. 16/884,928, filed May 27, 2020. [cited by applicant]
U.S. Appl. No. 16/859,571, filed Apr. 27, 2020. [cited by applicant]
U.S. Appl. No. 16/912,045, filed Jun. 25, 2020. [cited by applicant]
U.S. Appl. No. 16/912,091, filed Jun. 25, 2020. [cited by applicant]
U.S. Appl. No. 16/912,200, filed Jun. 25, 2020. [cited by applicant]
U.S. Appl. No. 16/909,477, filed Jun. 23, 2020. [cited by applicant]