US20170237568A1 - Method of protecting the identifying information of persons and computing devices, specifically those devices which are capable of sensing, capturing, receiving, transmitting, processing and storing digital information - Google Patents
Method of protecting the identifying information of persons and computing devices, specifically those devices which are capable of sensing, capturing, receiving, transmitting, processing and storing digital information Download PDFInfo
- Publication number
- US20170237568A1 US20170237568A1 US15/044,625 US201615044625A US2017237568A1 US 20170237568 A1 US20170237568 A1 US 20170237568A1 US 201615044625 A US201615044625 A US 201615044625A US 2017237568 A1 US2017237568 A1 US 2017237568A1
- Authority
- US
- United States
- Prior art keywords
- unique
- computing device
- identifier
- cloud server
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 25
- 150000003839 salts Chemical class 0.000 claims description 17
- 230000008569 process Effects 0.000 claims description 7
- 230000000977 initiatory effect Effects 0.000 claims 2
- 230000004224 protection Effects 0.000 abstract description 7
- 238000012546 transfer Methods 0.000 abstract description 2
- 238000005516 engineering process Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 238000011160 research Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3242—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving keyed hash functions, e.g. message authentication codes [MACs], CBC-MAC or HMAC
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- G06F17/30312—
-
- G06F17/30345—
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- H04L9/0861—Generation of secret information including derivation or calculation of cryptographic keys or passwords
- H04L9/0866—Generation of secret information including derivation or calculation of cryptographic keys or passwords involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
- H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
- H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/42—Anonymization, e.g. involving pseudonyms
Definitions
- the present invention is not related to any federally sponsored research or development.
- Cybersecurity and more specifically the protection of personal and computing device identifying information has become an individual and nation concern. Data and hardware breaches continue to rise. Identity theft, ransomware, medical device intrusion, cyber-carjacking, energy grid cyberattacks, financial services and banking hacks and theft of medical and health information raise significant concern among individuals, private sector enterprises and government.
- U.S. trading partners such as the European Union (EU) have expressed deep concern about the lack of robust of U.S. privacy protections related to EU citizens' private identifying data residing on servers and data warehouses in the U.S.
- the European Court of Justice recently invalidated the Safe Harbor provisions by which U.S. companies are able to move EU citizens' private and identifying information to the U.S. While a new data protection scheme between the U.S. and the EU is being worked out, U.S. companies face uncertain legal risk by continuing to process and move EU citizens' private identifying data to the U.S..
- the present invention improves prior art by never exposing personal or computing device identifying information, while such information is in transit from one computing device to another.
- the present invention de-identifies information prior to transmission and re-identifies information at the destination, safely behind a computing device system of firewalls.
- the present invention provides a level of protection against dictionary attacks as the unique privacy identifiers are never stored in any database, file or lookup table.
- the present invention enhances the connective promise of the IoT.
- the present invention provides an additional layer of security by complementing prior art such as encryption and tokenization.
- the present invention relates to the secure identification, authentication, protection and transfer of personal and computing device identifying information between computing devices.
- the present invention is a method that removes the need to expose personal or computing device identifying information, while such information is in transit between computing devices.
- a consistent identifier unique to the individual person or computing device is generated for every instance where information or data related to personally identifiable information (PII) or computing device identifying information (CDII) is requested, acquired, stored, analyzed, manipulated, processed, transmitted, data warehoused or shared within and across computer devices.
- PII personally identifiable information
- CDII computing device identifying information
- FIG. 1 is a representation of a process of generating a unique hardware identifier
- FIG. 2 Is a representation of a process of generating a unique privacy identifier
- FIG. 3 is a representation of a process of validating and matching a unique hardware identifier
- FIG. 4 is a representation of a process of validating and matching a unique privacy identifiers.
- unique hardware identifier generating software is installed on computing devices, [ 100 ]; a computing device selects immutable source identifying hardware values used to a generate unique hardware identifier, [ 110 ]; computing device generates a unique hardware identifier, [ 120 ]; computing device hashes the unique hardware identifier, [ 130 ]; a salt is applied to the hashed unique hardware identifier, [ 140 ]; and a computing device encrypts and stores the hashed and salted unique hardware identifier on a cloud or non-cloud server, [ 150 ].
- FIG. 2 install unique privacy identifier generating software on computing devices that will request or receive personal or computing device identifying information, [ 200 ]; a requesting computing device requests information from another computing device, [ 210 ]; a requesting computing device selects immutable source identifying values from a specific data record or device containing such values, [ 220 ]; a requesting computing device generates a unique privacy identifier using the selected immutable source values, [ 230 ]; a requesting computing device hashes a unique privacy identifier, [ 240 ]; a requesting computing device retrieves salt from a cloud or non-cloud server, [ 250 ]; a requesting computing device applies a salt to the unique privacy identifier, [ 260 ]; and the hashed and salted unique privacy identifier is prepared for transmission to a requested computing device, [ 270 ].
- a requesting computing device selects its immutable source identifying hardware values used to a generate unique hardware identifier, [ 300 ]; a requesting computing device generates a unique hardware identifier using the selected source values, [ 310 ]; a requesting computing device hashes the unique hardware identifier, [ 320 ]; a requesting computing device retrieves a salt from the cloud or non-cloud server, [ 330 ]; a requesting computing device applies a salt to its hashed unique hardware identifier, [ 340 ]; a requesting computer device validates its generated unique hardware identifier against a unique hardware identifier stored on a cloud or non-cloud server, [ 350 ]; a computing device compares the requesting computing device unique hardware identifier with a stored unique hardware identifier, [ 360 ]; if the unique hardware identifiers do not match a no connection or possible security violation is logged, [ 370 ]; and if the unique hardware identifiers match
- a requested computing device receives a unique privacy identifier form a cloud or non-cloud server, [ 400 ]; a requested computing device selects immutable identifying values from its information repositories behind the requested computing device's firewall in order to generate a unique privacy number, [ 410 ]; a requested computing device generates a unique privacy identifier using the selected immutable source values, [ 420 ]; a requested computing device retrieves a requesting computing device's unique privacy identifier from a cloud or non-cloud server, [ 430 ]; a requested computing device hashes its generated unique privacy identifier, [ 440 ]; a requested computing device retrieves a salt from a cloud or non-cloud server, [ 450 ]; a requested computing device removes the salt from the requesting computing device's unique privacy identifier, [ 460 ]; a requested computing device compares a requesting computing device's unique privacy identifier with a requested computing device's unique privacy
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Power Engineering (AREA)
- Storage Device Security (AREA)
Abstract
Description
- This application claims the benefit of U.S. Provisional Application No. 62/116,838 filed Feb. 16, 2015.
- STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
- The present invention is not related to any federally sponsored research or development.
- Cybersecurity and more specifically the protection of personal and computing device identifying information has become an individual and nation concern. Data and hardware breaches continue to rise. Identity theft, ransomware, medical device intrusion, cyber-carjacking, energy grid cyberattacks, financial services and banking hacks and theft of medical and health information raise significant concern among individuals, private sector enterprises and government.
- Accenture projects cyberattacks will cost the U.S. health system $305 billion over five years. The nascent Internet of Things (IoT), with tremendous potential to benefit society with the collection and analysis of big data, raises significant privacy concerns due to a lack security relative to personal and computing device identifying information contained in, received and transferred by, including but not limited to, wearables, medical devices, connected vehicles and smart home technology.
- U.S. trading partners such as the European Union (EU) have expressed deep concern about the lack of robust of U.S. privacy protections related to EU citizens' private identifying data residing on servers and data warehouses in the U.S. The European Court of Justice recently invalidated the Safe Harbor provisions by which U.S. companies are able to move EU citizens' private and identifying information to the U.S. While a new data protection scheme between the U.S. and the EU is being worked out, U.S. companies face uncertain legal risk by continuing to process and move EU citizens' private identifying data to the U.S..
- Current approaches to protecting identifying information include software and hardware encryption, including the use of public and private keys; trusted certificate technology; and tokenization. Use of these technologies, when used to harden data security, are effective but the tradeoff is the sub-optimal use and flexibility of the underlying data. Solutions to this problem of balance are often tipped in favor of greater flexibility in data use resulting in less protection for personal or computing device identifying information.
- The present invention improves prior art by never exposing personal or computing device identifying information, while such information is in transit from one computing device to another. The present invention de-identifies information prior to transmission and re-identifies information at the destination, safely behind a computing device system of firewalls. The present invention provides a level of protection against dictionary attacks as the unique privacy identifiers are never stored in any database, file or lookup table. The present invention enhances the connective promise of the IoT. Finally, the present invention provides an additional layer of security by complementing prior art such as encryption and tokenization.
- The present invention relates to the secure identification, authentication, protection and transfer of personal and computing device identifying information between computing devices. Specifically the present invention is a method that removes the need to expose personal or computing device identifying information, while such information is in transit between computing devices.
- In the preferred embodiment of the present invention, a consistent identifier unique to the individual person or computing device is generated for every instance where information or data related to personally identifiable information (PII) or computing device identifying information (CDII) is requested, acquired, stored, analyzed, manipulated, processed, transmitted, data warehoused or shared within and across computer devices.
- These as well as other features of the present invention will become more apparent upon reference to the drawings wherein:
-
FIG. 1 is a representation of a process of generating a unique hardware identifier; -
FIG. 2 Is a representation of a process of generating a unique privacy identifier; -
FIG. 3 is a representation of a process of validating and matching a unique hardware identifier; and -
FIG. 4 is a representation of a process of validating and matching a unique privacy identifiers. - The drawings referred to herein are for the purposes of illustrating the various aspects and uses of the present invention and are not meant to the scope of the present invention.
- Referring now to
FIG. 1 : unique hardware identifier generating software is installed on computing devices, [100]; a computing device selects immutable source identifying hardware values used to a generate unique hardware identifier, [110]; computing device generates a unique hardware identifier, [120]; computing device hashes the unique hardware identifier, [130]; a salt is applied to the hashed unique hardware identifier, [140]; and a computing device encrypts and stores the hashed and salted unique hardware identifier on a cloud or non-cloud server, [150]. - Referring now to
FIG. 2 : install unique privacy identifier generating software on computing devices that will request or receive personal or computing device identifying information, [200]; a requesting computing device requests information from another computing device, [210]; a requesting computing device selects immutable source identifying values from a specific data record or device containing such values, [220]; a requesting computing device generates a unique privacy identifier using the selected immutable source values, [230]; a requesting computing device hashes a unique privacy identifier, [240]; a requesting computing device retrieves salt from a cloud or non-cloud server, [250]; a requesting computing device applies a salt to the unique privacy identifier, [260]; and the hashed and salted unique privacy identifier is prepared for transmission to a requested computing device, [270]. - Referring now to
FIG. 3 : a requesting computing device selects its immutable source identifying hardware values used to a generate unique hardware identifier, [300]; a requesting computing device generates a unique hardware identifier using the selected source values, [310]; a requesting computing device hashes the unique hardware identifier, [320]; a requesting computing device retrieves a salt from the cloud or non-cloud server, [330]; a requesting computing device applies a salt to its hashed unique hardware identifier, [340]; a requesting computer device validates its generated unique hardware identifier against a unique hardware identifier stored on a cloud or non-cloud server, [350]; a computing device compares the requesting computing device unique hardware identifier with a stored unique hardware identifier, [360]; if the unique hardware identifiers do not match a no connection or possible security violation is logged, [370]; and if the unique hardware identifiers match, the requesting computing device passes its generated unique privacy identifier to a requested computing device containing the requested information, [380]. - Referring now to
FIG. 4 : a requested computing device receives a unique privacy identifier form a cloud or non-cloud server, [400]; a requested computing device selects immutable identifying values from its information repositories behind the requested computing device's firewall in order to generate a unique privacy number, [410]; a requested computing device generates a unique privacy identifier using the selected immutable source values, [420]; a requested computing device retrieves a requesting computing device's unique privacy identifier from a cloud or non-cloud server, [430]; a requested computing device hashes its generated unique privacy identifier, [440]; a requested computing device retrieves a salt from a cloud or non-cloud server, [450]; a requested computing device removes the salt from the requesting computing device's unique privacy identifier, [460]; a requested computing device compares a requesting computing device's unique privacy identifier with a requested computing device's unique privacy identifier, [470]; if the unique privacy identifiers do not match a no connection or possible security violation is logged, [480]; and if the unique privacy identifiers match, the information is re-identified and connected to the specific identified and matched record, [490]. - Additional modifications and improvements of the present invention may be apparent to those of ordinary skill in the art. Thus, the particular combination of steps and processes described and illustrated herein are intended to represent only certain embodiments of the present invention, and are not intended to serve as limitations of alternative methods within the spirit and scope of the invention.
Claims (14)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562116838P | 2015-02-16 | 2015-02-16 |
Publications (2)
Publication Number | Publication Date |
---|---|
US20170237568A1 true US20170237568A1 (en) | 2017-08-17 |
US10320785B2 US10320785B2 (en) | 2019-06-11 |
Family
ID=59562294
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/044,625 Active US10320785B2 (en) | 2015-02-16 | 2016-02-16 | Method of protecting the identifying information of persons and computing devices, specifically those devices which are capable of sensing, capturing, receiving, transmitting, processing and storing digital information |
Country Status (1)
Country | Link |
---|---|
US (1) | US10320785B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11210412B1 (en) * | 2017-02-01 | 2021-12-28 | Ionic Security Inc. | Systems and methods for requiring cryptographic data protection as a precondition of system access |
US20230342467A1 (en) * | 2022-04-20 | 2023-10-26 | Dell Products, L.P. | Storage identity validation for a supply chain |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR102413497B1 (en) | 2019-01-28 | 2022-06-24 | 크넥트아이큐 인크. | Systems and methods for secure electronic data transmission |
Family Cites Families (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7971017B1 (en) * | 2006-08-21 | 2011-06-28 | Rockwell Automation Technologies, Inc. | Memory card with embedded identifier |
US8850543B2 (en) * | 2012-12-23 | 2014-09-30 | Mcafee, Inc. | Hardware-based device authentication |
WO2014182957A1 (en) * | 2013-05-08 | 2014-11-13 | Acuity Systems, Inc. | Authentication system |
WO2014196969A1 (en) * | 2013-06-05 | 2014-12-11 | American Express Travel Related Services Company, Inc. | System and method for multi-factor mobile user authentication |
US9344407B1 (en) * | 2013-09-05 | 2016-05-17 | Amazon Technologies, Inc. | Centrally managed use case-specific entity identifiers |
US20150278545A1 (en) * | 2014-03-28 | 2015-10-01 | Aruba Networks, Inc. | Anonymization of client data |
-
2016
- 2016-02-16 US US15/044,625 patent/US10320785B2/en active Active
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11210412B1 (en) * | 2017-02-01 | 2021-12-28 | Ionic Security Inc. | Systems and methods for requiring cryptographic data protection as a precondition of system access |
US11841959B1 (en) * | 2017-02-01 | 2023-12-12 | Ionic Security Inc. | Systems and methods for requiring cryptographic data protection as a precondition of system access |
US20230342467A1 (en) * | 2022-04-20 | 2023-10-26 | Dell Products, L.P. | Storage identity validation for a supply chain |
Also Published As
Publication number | Publication date |
---|---|
US10320785B2 (en) | 2019-06-11 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11451544B2 (en) | Systems and methods for secure online credential authentication | |
EP3161992B1 (en) | Privacy-preserving querying mechanism on privately encrypted data on semi-trusted cloud | |
CN111143880B (en) | Data processing method and device, electronic equipment and readable medium | |
CN111147255B (en) | Data security service system, method and computer readable storage medium | |
US8533469B2 (en) | Method and apparatus for sharing documents | |
US11170128B2 (en) | Information security using blockchains | |
JP6678457B2 (en) | Data security services | |
CN110287739B (en) | Data security management method and system based on hardware private key storage technology | |
US20190141048A1 (en) | Blockchain identification system | |
US10992681B2 (en) | Authentication using blockchains | |
WO2019205389A1 (en) | Electronic device, authentication method based on block chain, and program and computer storage medium | |
Miriam et al. | Secured Cyber Security Algorithm for Healthcare System Using Blockchain Technology. | |
US10320785B2 (en) | Method of protecting the identifying information of persons and computing devices, specifically those devices which are capable of sensing, capturing, receiving, transmitting, processing and storing digital information | |
Deng et al. | Towards a cross‐context identity management framework in e‐health | |
Yadav et al. | A Survey on Secure Cloud-Based E-Health Systems. | |
Sokolova et al. | Security of the telemedicine system information infrastructure | |
KR20070065527A (en) | Data storing system and method for de-identification of information | |
Zhao et al. | Feasibility study on security deduplication of medical cloud privacy data | |
EP4057587B1 (en) | Data storage and retrieval | |
Dhyani | E-Health data risks & protection for public cloud: An elderly healthcare usecase for Swedish municipality | |
Saranya et al. | A study on the public auditing mechanisms for privacy preserving and maintaining data integrity in cloud computing | |
Sankar et al. | Different Approaches on Security, Privacy and Efficient Sharing of Electronic Health Records Using Blockchain Technology | |
Vinnarasi et al. | E-Health Security on Could Computing and its Challenges | |
KR101473410B1 (en) | Method for Accessing Recording Area of Digital Certificate | |
Chuchra et al. | Modeling Implementation of TBDSA-Token based Data Security Algorithm in Cloud Computing |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: KNECTIQ INC., MINNESOTA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MORRIS, KENNETH WAYNE;REEL/FRAME:048422/0765 Effective date: 20190222 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PETITION RELATED TO MAINTENANCE FEES GRANTED (ORIGINAL EVENT CODE: PTGR); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
CC | Certificate of correction | ||
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
FEPP | Fee payment procedure |
Free format text: SURCHARGE FOR LATE PAYMENT, SMALL ENTITY (ORIGINAL EVENT CODE: M2554); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: M2551); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY Year of fee payment: 4 |