Method for efficient and secure data migration between data processing systems
Claim Score by NHIP
Abstract
The present invention provides a method for transferring encrypted information from one storage area to other storage area wherein cryptographic data protection scheme having protection attributes are applied on the data. A crypto container having cryptographic properties represents cryptographically protected data. The attributes that have been attached to the container at the time when data is added or removed from the container determine the scheme of data protection being applied. Crypto container can be converted or serialized for storage or transmission, here the conversion spread only to the protected data parts which possibly includes crypto containers in protected form but may not the attached crypto attributes. These attributes must be stored or transmitted in another form.

Term
Projected expiry 11 June 2029.
- Priority and filed
- Published
- Today
- Projected expiry
21 claims: 5 independent, 16 dependent
- 1A data migration system for protected data comprising:a first mechanism for attaching a first set of protection attributes to protected data in a first dataset and exporting it from a first device, a second mechanism for transferring the set of protection attributes and the protected data from the first device to a second device, and a third mechanism for importing the first set of protection attributes to the second device and for protecting the first set of protection attributes in accordance with a protection method used by the second device and storing said protected data from first device in unaltered form along with said protection attributes.
- 6Broadest claimClaim Score 68, broad(NHIP)A method for transferring encrypted data from a first dataset into a second dataset wherein the data from the first dataset has been encrypted using a first encryption key, said method comprising the steps of:attaching a first set of protection attributes to the encrypted data from the first dataset, transferring the encrypted data from the first dataset into the second dataset as it is, without decrypting or re-encrypting it;importing said set of protection attributes into the second dataset and protecting said set of protection attributes in accordance with the protection policies used in said second dataset;and storing said set of protection attributes protected in accordance with the protection policies used in the second dataset, in association with said encrypted data from the first dataset.
- 8A method for transferring authenticated data from a first dataset into a second dataset wherein the data from the first dataset has been authenticated using a first authentication key, said method comprising the steps of:attaching a first set of protection attributes to the authenticated data from the first dataset, transferring the authenticated data from the first dataset into the second dataset as it is, without verifying authentication or re-computing authentication information;importing said set of protection attributes into the second dataset and protecting said set of protection attributes in accordance with the protection policies used in said second dataset;and storing said set of protection attributes protected in accordance with the protection policies used in the second dataset, in association with said authenticated data from the first dataset.
- 10A data migration system for protected comprising:a first mechanism for attaching to a plurality of protected data individual first sets of protection attributes, and exporting these from a first device. a second mechanism for transferring the plurality of sets of protection attributes and protected data from the first device to a second device, and a third mechanism that imports a plurality of protection attributes each of them protecting its separate data, and storing said protected data from the first device in unaltered form along with said set of protection attributes as a new crypto container.
- 20A data migration system for protected data comprising:a first mechanism reading from a first device a set of data consisting of a plurality of protected data along with their associated protection attributes. a second mechanism splitting said protection attributes and data read in a first mechanism into subsets of pairs of protection attributes and corresponding data, and in a third mechanism protects each set of protection attributes in each subset with a set of protection attributes associated with the subset and stores each subset of protected protection attributes along with its associated protected data in unaltered form.
Independent claims5
54 paragraphs in 5 sections, as filed
FIELD OF INVENTION
0001The present invention relates to a method for efficient and secure data migration between data processing systems. More particularly, the invention relates to the field of cryptography for secure transmission or migration of data between data storage systems.
BACKGROUND OF THE INVENTION
0002In storage systems cryptography may be used to protect data at rest (i.e., when residing on a storage medium) and data in motion (i.e., when traversing a network between components of a storage system). Cryptography refers to the art or science of converting information from its normal comprehensible format into an incomprehensible format rendering it unreadable without secret knowledge and thereby protecting it from illegitimate access. Such unreadable format of data or converted data is called ciphertext. The following two types of cryptographic methods mentioned below are known:
0003a) Symmetric cryptography (Secret-key cryptosystems)
0004b) Asymmetric cryptography (Public-key cryptosystems)
0000A wide variety of cryptographic algorithms are known for both types of cryptography mentioned before. These cryptographic algorithms result in a wide variety of cryptographically secure systems each based on one of the two types of cryptographic methods listed above or on a combination of them.
0005<figref idref="DRAWINGS">FIG. 1</figref> shows an example of symmetric cryptography wherein plaintext is encrypted with a shared or secret key at one site. The result is called ciphertext; it is then transferred to another site, which decrypts it with the help of the key known and shared between the two sites. Note that in this process the same key is used for encryption and decryption therefore the process is called symmetric-key cryptography. The parties in the example are called Alice, Bob, and Eve. Alice and Bob are friends exchanging encrypted messages. Eve is an eavesdropper, trying to read the messages being exchanged between Bob and Alice. In symmetric algorithms as shown, Bob needs to send the encryption key information to Alice or they have to agree on a single key in order to exchange protected messages. [The letters above each party indicate what he or she knows. M represents a message being sent from Bob to Alice, and K(M) represents the enciphered message. To decipher the message, Alice simply applies K to K(M).]
0006<figref idref="DRAWINGS">FIG. 2</figref> illustrates an example of asymmetric cryptography. In asymmetric algorithms each party uses two keys, a public key and a private key. The public keys are published to every one—even Eve knows them—while each party keeps its private key secret. When Bob wants to send a message M to Alice he encrypts the plaintext with the public key of Alice P<sub>A</sub>. Then the encrypted data P<sub>A</sub>(M) is sent to Alice who decrypts said data with the private key of Alice Pr<sub>A </sub>that is known only to her. Even though Eve knows P<sub>A </sub>and P<sub>A</sub>(M), Eve can't recover the message without Alice's private key. [Again, letters near each box indicate what each party knows. M is the message Bob sends to Alice (he knows it since he wrote it, and Alice knows it since she has deciphered it). P<sub>A</sub>(M) represents the message enciphered with Alice's public key. To get M from P<sub>A</sub>(M), Alice applies Pr<sub>A </sub>to P<sub>A</sub>(M).]. The most widely used asymmetric cryptographic algorithm today is the Rivest-Shamir-Adleman (RSA) algorithm.
0007<figref idref="DRAWINGS">FIG. 3</figref> shows an embodiment of a layered data processing system. Typical examples of layered data processing systems are data storage systems and data communication systems. A layered data processing system consists of a stack of data processing layers that offer the same set of interfaces for reading and writing data. An application writes data to the layer at the top and reads data from the layer at the top. Intermediate layers transform the data in a layer-specific way. The layer at the bottom handles the physical transmission or storage of the data.
0008<figref idref="DRAWINGS">FIG. 4</figref> shows one layer in a layered data processing system. The layer may receive write input data from the layer or an application above, transform it in a layer-specific way, and output the result to the layer below. The layer may also receive read input data from below, transform it in a layer-specific way, and output the result to the layer above. The data storage systems of common computer operating systems are typically organized as layered data processing systems. They consist of the data processing layers mentioned below and illustrated in <figref idref="DRAWINGS">FIG. 5</figref>. An application accesses the stored data through a file system interface (fs), which provides the means to write and read data to and from files in byte-sequences of arbitrary length, to group files into directories, and to organize directories and files into a hierarchy. The file system layer (fs) typically translates file system operations into operations on byte containers of variable size, which are known as “inodes” in traditional UNIX file systems or as “objects” in object storage areas. The object layer (obj) transforms these operations into accesses to a block interface, which provides only read and write operations on fixed-length data blocks or sectors, which are typically 512 bytes long. Many data storage devices, such as disks, offer the block interface at the block layer (blk). The layer of the host-bus adaptor (hba) transfers the data to the disk subsystem. A disk subsystem usually contains additional layers internally, for example layers for adding error-correcting or error-detecting codes and for accessing the magnetic media.
0009A similar layered structure is found also in data communication systems, such as telephone networks and computer data networks, and in many other data processing systems. Commonly known data communication systems might be placed inbetween any layers of a data storage system in order to allow for remote data storage using a networking infrastructure.
0010Layered data storage systems and layered data communication systems are collectively referred to as layered data processing systems.
0011Cryptographic protection schemes can be applied at any layer of a layered data processing system. Depending on the layer, they provide different security guarantees to the overall system. A security mechanism protects data only at the layer in which the mechanism is applied between the communication end-points at the said layer. Also data processed at some layer is typically opaque i.e., the layer does not know anything about the structure of the data. However, there are data processing systems that make certain heuristic assumptions about the form of the arriving data, in particular to achieve greater efficiency. For example, analog telephone modems and tape drives apply data compression to save bandwidth and gain efficiency.
0012In the case of a layered data storage system mentioned before, cryptographic protection is commonly applied at the block layer or at the file layer.
0013If encryption is provided at the block layer, where data is divided into blocks of fixed length, encryption is performed on all blocks of data with a single key. The benefits of this system are simplicity and efficiency. The drawback is that anyone with access to the block storage device can decrypt all the information. Encryption at the block layer can be advantageous for instance in tape archival devices where a single key per tape is required.
0014If encryption is provided at the file-system layer a different key is used for every file. The advantage of this system is that fine-grained protection is possible because access to the file-encryption key can be controlled depending on the access permission of the file. An attacker with access to any layer below, for example the block layer, gains only access to the files that it is allowed to read.
0015Numerous methods have been developed for transmitting data in a secure manner between layered data processing systems using cryptography. Most methods in the prior art for transmitting and migrating data from a first data processing system to a second data processing system decrypt on the first processing system the encrypted data stored on the said first processing system with a key associated to the said first data processing system before the actual transmission or migration of data to the second processing system takes place. The said data is encrypted again on the second data processing system after it reaches its destination, the second data processing system, with a key associated with said second data processing system. This incurs an additional overhead of decrypting the data before migration and performing the process of data encryption more than once.
0016An example of the aforementioned situation is when data stored on a cryptographic file system is written to a tape archival device for backup. Typically a backup application first reads the data from the file system and thereby decrypts the data with the associated file key. Later, it re-encrypts the data with the key maintained by the tape backup device. In such cases, additional overhead is incurred due to transformation of data from one encrypted format to another which can be avoided. Analogously, data communication systems might re-encrypt already encrypted data unnecessarily.
0017The aforementioned problem is further aggravated due to a layered structure found in most of the storage systems and, more generally, also in other layered data processing systems. Such data processing systems are connected through their standard interfaces at the top layer, so the data must be decrypted before leaving the first system, and re-encrypted again at the destination. This incurs an overhead that can be prohibitive for large amounts of data.
0018It would therefore be desirable to provide a method for efficient and secure data migration between layered data processing systems.
OBJECTIVES AND SUMMARY OF THE INVENTION
0019It is an objective of the present invention to overcome the aforementioned drawbacks and provide a secure and efficient data migration method in storage systems.
0020It is an objective of the present invention to reduce the overhead of encryption-decryption-encryption process.
0021It is an objective of the present invention to provide efficient security to smaller and high capacity removable storage devices.
0022It is still another objective of the present invention to enhance the interface of the data processing system with the help of protection attributes.
0023It is still another objective of the present invention to provide security in distributed storage environments in an end-to-end view.
0024It is yet another objective of the present invention to provide secure and efficient method for electronic data migration.
0025It is yet another objective of the present invention to assure that already encrypted data is sufficiently secure encrypted by using protection policies.
0026It is yet another objective of the present invention to provide a method for defeating attacks such as fabrication and interception on storage systems.
0027The foregoing objectives are achieved by a method for cryptographically securing data in a secure computing environment which facilitates secure and efficient migration of data between data processing systems.
0028The present invention relates to data processing systems that employ cryptography for protection of data, wherein the encrypted data is migrated or transferred in its encrypted format keeping most of the features of the encrypted data intact, to another data processing system and the said transferred data need not be encrypted again at the destination. The invention thereby enables migration or transfer of data between layered data processing systems, such as disk storage and tape storage, without performing decryption or encryption of the bulk data more than once. Protection can be provided cryptographically at any given layer of a layered data processing system. The type and level of security depends on the granularity and the layer at which data is protected. Layers can be augmented with protection policies to ensure that already encrypted data is sufficiently secure encrypted. A security mechanism protects data only at the layer in which the mechanism is applied and between the communication end-points at the given layer.
BRIEF DESCRIPTION OF THE DRAWINGS
0029The present invention is described with the help of accompanying drawings:
0030<figref idref="DRAWINGS">FIG. 1</figref> shows an example of symmetric cryptography known in the prior art.
0031<figref idref="DRAWINGS">FIG. 2</figref> shows an example of asymmetric cryptography known in the prior art.
0032<figref idref="DRAWINGS">FIG. 3</figref> shows a layer of a layered data processing system known in the prior art.
0033<figref idref="DRAWINGS">FIG. 4</figref> shows a layered data processing system known in the prior art.
0034<figref idref="DRAWINGS">FIG. 5</figref> shows the layered structure of a storage system known in the prior art.
0035<figref idref="DRAWINGS">FIG. 6</figref> shows an overview of a storage system of the invention
0036<figref idref="DRAWINGS">FIG. 7</figref> shows an embodiment of the invention of the process of transferring protected data between layered data processing systems.
0037<figref idref="DRAWINGS">FIG. 8</figref> shows an embodiment of a layer in a layered data processing system of the invention.
0038<figref idref="DRAWINGS">FIG. 9</figref> shows an embodiment of two layered data storage system interconnected with a data communication system.
0039<figref idref="DRAWINGS">FIG. 10</figref> shows an embodiment of the process applying protection policies in a data processing layer.
0040<figref idref="DRAWINGS">FIG. 11</figref> shows an embodiment of a recursive data processing layer.
DETAILED DESCRIPTION OF THE INVENTION
0041This invention is aimed at achieving faster and more efficient operations for moving data between layered data processing systems that use cryptographic protection internally. <figref idref="DRAWINGS">FIG. 6</figref> shows an overview two data storage systems which are connected with each other through a trusted and an untrusted channel. Each of the data storage system is further connected to at least one trusted and at least one untrusted storage device. (The figure only shows one instance of the trusted and untrusted storage devices per data storage system). The data storage devices might be connected to further data storage devices not shown on the figure. As shown in <figref idref="DRAWINGS">FIG. 7</figref>, protected (i.e., encrypted or authenticated) data is transferred between data processing systems keeping the format of the protected data intact and adding protection attributes, such as encryption keys or message-authentication keys for a message-authentication code (MAC) separately. The invention is to enhance a layered data processing system to work with separate interfaces for data and protection attributes. More precisely, the invention enhances the interface of the layered data storage system by adding set of protection attributes (<b>7</b>.<b>1</b>), which express the cryptographic operations that were applied to the stored data at the time of storing it. Data that is modified in this way is called protected data. The protected data may have been encrypted with a symmetric cryptosystem or with an asymmetric cryptosystem. In this case, the protection attributes consist of the secret or of the public key that was applied to the data. Protected data may also be authenticated using a MAC or signed using a digital signature scheme. Here, the protection attributes include the secret MAC-key and the authentication tag or the digital signature and the signature private key. In this way it is possible to reconstruct the raw data from the protected data and the protection attributes such as message authentication code, encryption keys, digital signatures etc. Hence the protected data together with the protection attributes provide for a different representation of the data. Such cryptographically protected data can be represented as an abstract Crypto Container data type that separates between data and protection attributes. A crypto container consists of protection attributes and protected data. A protection attribute describes the cryptographic protection scheme that has been applied to the protected data in the container.
0042The protected data is then transferred to the second data processing system (<b>7</b>.<b>2</b>) in this form. The protection attributes are themselves not protected but exported and imported as they are (in cleartext). It must be ensured that the protection attributes are only exported in a trusted environment. Hence, if the environment consists of an untrusted data channel the transfer of protection attributes between data processing layers has to be done through a secure channel. Importing protected data is more efficient because it is not necessary to protect the data a second time. At the second system protection attributes alone are encrypted in the format of the second system (<b>7</b>.<b>3</b>). the unaltered data from the first system and the encrypted protection attributes are then stored on the second system (<b>7</b>.<b>4</b>)
0043<figref idref="DRAWINGS">FIG. 7</figref> shows one layer of the enhanced data processing system. The layer now provides for a separation between protected data and protection attributes (PA) for the write input from above and for the read input from below, respectively. Likewise, the layer may output protected data separated from protection attributes for the write output to the lower layer and for the read output to the layer above.
0044Transmission of protected data between layered processing systems may involve a further layered data processing system that involves cryptographic protection. In this case, the cryptographic protection can be applied to the protection attributes, but may be skipped for the protected data, which is more efficient.
0045It should be noted that the said protected data and the said protection attributes together are not protected but provide for a different representation of the data. This is to allow reconstruction of the plain data from the protected data and the protection attributes.
0046The basic aim of the aforementioned representation of the data is to gain efficiency when transferring protected data between data processing systems with different protection schemes. The efficiency arises from the fact that the data to be exported from one data processing system to the target data processing system is not required to be decrypted at the first system and can be transferred in the original encrypted format along with the protection attributes.
0047The target data processing system does not need to encrypt the protected data again but can encrypt merely the protection attributes with a key owned by the target data processing system.
0048The advantage of this secure and efficient method for migration or transfer of data between data processing systems is that one can avoid going through the complicated decryption process before data migration between data processing systems.
0049<figref idref="DRAWINGS">FIG. 9</figref> shows a preferred embodiment of this invention consisting of at least two data storage systems, at least two data communication systems, at least one trusted and one untrusted storage device. A user or an application of the data storage system <b>1</b> writes data to the data storage system. To illustrate this, three data messages A, B, C are shown; however, any arbitrary number of data messages can be written to the data storage system. The protection of the data messages at this point is dependent on the configuration of the system and might be given through existing means such as login password or a Kerberos ticket (J. Kohl and C. Neuman, The Kerberos Authentication Service, RFC 1510, September 1993). The write connector for protection attributes is therefore dashed. The data storage system applies protection attributes to the entering data A, B, and C according to the protection policy PP<b>1</b>, stores the protection attributes on one or more trusted storage devices and stores the data on one or more untrusted storage devices. The process of applying the protection policies is explained later in this document. When the data has to be transferred through data communication systems to second data storage system the data storage system <b>1</b> writes the protection attributes PA<sub>A</sub>, PA<sub>B</sub>, and PA<sub>C</sub>, and the protected data PA<sub>A</sub>(A), PA<sub>B</sub>(B), and PA<sub>C</sub>(C), as crypto containers CC<b>1</b>, CC<b>2</b>, and CC<b>3</b> to the next layer.
0050Data communication systems <b>1</b> and <b>2</b> share the same crypto object attributes PA<sub>D </sub>which have been exchanged using any known key distribution protocol through a trusted channel. Upon receipt of one or more crypto containers the data communication system <b>1</b> may wrap several crypto containers into a single one or split crypto containers into two or more containers. It also may apply additional encryption based on the protection policy PP<b>2</b>. The actual start and end point of incoming crypto containers which go into a new outgoing crypto container CC<b>4</b> depends on the functionality of the data communication system and is not further specified here. In the figure, the three crypto containers CC<b>1</b>-<b>3</b> are wrapped into crypto container CC<b>4</b>, whereby the protection attributes are encrypted by the encryption attributes PA<sub>D</sub>. The data which is already sufficiently protected according to PP<b>2</b>, here PA<sub>A</sub>(A) and PA<sub>B</sub>(B), are not reencrypted. Only PA<sub>C</sub>(C) which is not sufficiently protected is encrypted using the protection attributes PA<sub>D</sub>. The new crypto container CC<b>4</b> is then written to the next layer, residing in the data communication system <b>2</b>. The data communication system <b>2</b> communicates with the data storage system <b>2</b> through a trusted environment. Therefore the crypto container CC<b>4</b> can be unwrapped and no protection policies need to be applied to write the restored crypto container CC<b>5</b> to the data storage system <b>2</b>. Similar as above, the data storage system <b>2</b> may wrap or split crypto containers. In this embodiment the data storage system <b>2</b> illustrates a tape archival device which splits the crypto container CC<b>5</b> into two different crypto containers CC<b>6</b> and CC<b>7</b>. Here again, the data storage system may apply additional encryption based on the protection policy PP<b>2</b> as it is shown for PA<sub>F</sub>(PA<sub>C</sub>(C)). For each crypto container the data is stored on a separate storage devices named tape devices whereas the crypto attributes PA<sub>E </sub>and PA<sub>F </sub>are stored on a trusted storage device. The read process is analogous to the write process and is not further explained here.
0051The process of applying protection policies in a data processing layer is shown in <figref idref="DRAWINGS">FIG. 10</figref>. A crypto container consisting of crypto attributes PA<sub>X </sub>and data PA<sub>X</sub>(X) is first checked whether the data PA<sub>X</sub>(X) is sufficiently protected according to the protection policies PPY of the data processing layer. If the data PA<sub>X</sub>(X) is not sufficiently protected the protection attributes PA<sub>Y </sub>provided by the current layer have to be applied to the data to build the new data Y=PA<sub>Y</sub>(PA<sub>X</sub>(X)). In a next step the protection attributes PA<sub>X </sub>of the crypto container are protected with the protection attributes of the data processing layer PA<sub>Y</sub>. In case the data is already sufficiently protected, only the protection attributes PA<sub>X </sub>are protected with the protection attributes of the data processing layer PA<sub>Y </sub>and the new data Y=P<sub>A</sub>(X) remains unchanged. Finally the new crypto container PA<sub>Y</sub>(PA<sub>X</sub>),Y is ready for further processing by the data processing layer.
0052In another embodiment of the present invention one or more data processing layers may be merged into a single processing layer. <figref idref="DRAWINGS">FIG. 11</figref> shows two data processing layer, a first one consisting of an encryption device and a second one of storage devices which are merged into one single data processing layer.
0053The above description related to specific embodiments of the invention and was described with the help of specific language for the purpose of promoting an understanding of the principles of the invention. It must nevertheless be understood that no limitation of the scope of the invention is thereby intended. The scope of the invention shall include such alterations and modifications in the embodiments and such further applications of the principles of the invention as would normally occur to one skilled in the art to which the invention relates.
Contents5
12 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| WO2013088485A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2013212711A1 | Cited by | United States of America | Pre-grant |
| US9509501B2 | Cited by | United States of America | Applicant |
| US8904557B2 | Cited by | United States of America | Search report |
| WO2013112538A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US9798486B1 | Cited by | United States of America | Search report |
| US9594921B2 | Cited by | United States of America | Search report |
| US9003203B2 | Cited by | United States of America | Applicant |
| US2013232542A1 | Cited by | United States of America | Pre-grant |
| US9336408B2 | Cited by | United States of America | Applicant |
| US10375116B2 | Cited by | United States of America | Search report |
| US2005081039A1 | Cites | United States of America | Pre-grant |
| US7240197B1 | Cites | United States of America | Pre-grant |
2 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 55224106 | United States of America | A | |
| US20060552241 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2008098217A1 | United States of America | A1 | |
| US7802102B2 | United States of America | B2 |
36 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Maintenance Fee Reminder MailedREM. | REM. | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Email NotificationEML_NTR | EML_NTR | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| New or Additional Drawing FiledC614 | C614 | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Receipt of all Acknowledgement LettersL130 | L130 | |
| Receipt of Acknowledgment LetterL197 | L197 | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Agency Referral Letter MailedML196 | ML196 | |
| Application Is Now CompleteCOMP | COMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Referred by L&R for Third-Level Security Review. Agency Referral Letter GeneratedL196 | L196 | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.)FEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| Surcharge for late paymentSULP | SULP | |
| Maintenance fee reminder mailedREMI | REMI | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 20080098217
- Publication, DOCDB
- 2008098217
- Publication, EPODOC
- US2008098217
- Application
- 11552241
- Application, DOCDB
- 55224106
- Application, EPODOC
- US20060552241
Titles
- English
- METHOD FOR EFFICIENT AND SECURE DATA MIGRATION BETWEEN DATA PROCESSING SYSTEMS
Classification
- CPC, 2
- G06F21/6218
- G06F16/119
- IPC, 10
- H04N7 16
- H04L9 32
- H04L9 00
- G06F12 14
- G06F17 30
- G06F7 04
- G06F11 30
- G06K9 00
- H03M1 68
- H04K1 00
- USPC, 7
- 713165000
- 707E17032
- 713167000
- 713181000
- 713189000
- 726026000
- 726027000