Trusted content server
Summary by NHIP
Trusted Content Server Apparatus
The apparatus provides access to authenticated electronic documents over a network using a server, user interface, computer network, and database connected via three disjunct network interfaces. A verification server links the computer network and database through separate interfaces to iteratively traverse the database, retrieve indexed seed values, and check document authenticity without allowing direct communication between the user interface, network, and database.
Claim Score by NHIP
Abstract
A method and apparatus for providing access to authenticated electronic documents over a network. The apparatus comprises a server computer, a user interface connected to the server via a first network interface for providing user access to the server, a computer network containing the electronic documents connected to the server via a second network interface, a database connected to the server via a third network interface, for storing data for authenticating the electronic documents. The first network interface, second network interface and the third network interface are disjunct respective to each other such that the user, the computer network and the database are not in communication therebetween. The apparatus further comprises a verification server having first and second network interfaces for connecting the computer network and the database thereto, wherein the first and second network interfaces are disjunct such that the database is not accessible to the computer network.

Term
Term ended
Expired 16 September 2023, 3 years ago.
- Priority and filed
- Granted
- Expired
- Today
18 claims: 2 independent, 16 dependent
- 1An apparatus for providing access to a plurality of authenticated electronic documents over a network comprising:a server computer;a user interface connected to said server via a first network interface for providing user access to said server;a computer network connected to said server via a second network interface, said electronic documents being accessible through said computer network;a database connected to said server computer via a third network interface, said database storing indexed information for authenticating the content of each of said plurality of electronic documents, the indexed information including seed values corresponding to each of said electronic documents;said first network interface, said second network interface and said third network interface being disjunct respective to each other such that said user interface, said computer network and said database are not in communication therebetween;a verification server comprising first and second network interfaces for connecting said computer network and said database thereto, said first and second network interfaces being disjunct such that said database is not accessible through said computer network, said verification server for iteratively traversing said database and retrieving said indexed information corresponding to a next one of said electronic documents, retrieving said electronic document via said computer network, checking the authenticity of the content of said electronic document using said corresponding seed values and updating the database with a status of the authenticity of said electronic document;said server computer configured so that upon receipt of a user request for a document, said server queries said database as to whether said requested document is indexed therein and returns a denial if said requested document is not indexed in said database, otherwise said server retrieves said requested document via said computer network, confirms the authenticity thereof using said seed values corresponding to the requested document and returns the contents of the requested document to the user if the requested document is determined to be authentic;wherein said apparatus provides a user access to a plurality of authenticated electronic documents available through said computer network and prevents the user from directly accessing said computer network.
- 14Broadest claimClaim Score 55, average(NHIP)A method for providing access to a select group of authenticated electronic documents over a network comprising the steps of:reviewing the content of each of a plurality of electronic documents to determine whether said electronic document is acceptable based on a review of the subject matter thereof;generating seed values for each of said electronic documents deemed acceptable for use thereafter in authenticating copies of the content of said electronic document;initializing a database by storing indexed information for identifying and authenticating each of said electronic documents deemed acceptable, the indexed information including the seed values corresponding to said electronic documents;receiving a request from a user for an electronic document;searching and retrieving from said database said indexed information for said requested document, returning a denial for said request if said requested document is not indexed in said database;accessing said network and retrieving the content of said requested document;calculating a checksum for the content of said retrieved document;comparing said checksum with said authenticating information for authenticating the content of said retrieved document;returning the content of said retrieved document to said user if the content of said retrieved document is authenticated;returning a refusal to said user if the content of said retrieved document is not authenticated;and updating said authenticating information for said document in said database based on the results of said comparing.
Independent claims2
28 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
0001The present invention relates to a method and apparatus for providing trusted access to a network, and more particularly, to a method and apparatus for providing access to authenticated documents over a network.
BACKGROUND
0002Advances in technology provide increasing capabilities for electronic file duplication and transport making the sharing over a network of electronic documents increasingly easy. The ability to provide nearly instant access to information to millions of users has revolutionized the way many businesses are run. However, it is well known to those who practice in the art that electronic files are easily corrupted, that even secure systems connected to network can be attacked and breached with the subsequent corruption of files. As such, in the current environment, users who receive files from many network sources are unable to verify the authenticity of the files received.
0003Many applications in a wide range of fields require the ability to provide trusted access to networks. For example, schools or other institutions may need to provide students access to the Internet without fear of exposing the students to inappropriate material. In the financial and insurance industries many documents are forwarded electronically without any guarantee as to the authenticity of the contents thereof.
0004Known in the art are filtering techniques which attempt to programmatically identify objectionable or non-authentic material both in print and picture formats. Some create lists to objectionable sites to which access is denied. These methods are often prone to error and circumvention as the lists which allow or block access are constantly required to be updated and are vulnerable to low level network traffic which could allow objectionable or other unauthorized material into the system being filtered. Therefore, there is a need for an apparatus and method for providing trusted access to networks wherein the contents of electronic documents received over a network can be authenticated.
SUMMARY OF THE INVENTION
0005Accordingly, an apparatus and method for providing access to authenticated electronic documents over a network is disclosed. The apparatus includes a server computer having a user interface connected thereto via a first network interface for providing user access to the server. A second network interface connects the server to a computer network containing the electronic documents. A third network interface connects a database to the server. The database stores data for authenticating the electronic documents. The first network interface, second network interface and third network interface are disjunct respective to each other such that the user, the computer network and the database are not in communication therebetween. A verification server having first and second network interfaces connect the computer network and the database to the verification server respectively. The first and second network interfaces connected to the verification server are disjunct, such that the database is not accessible to the computer network. The apparatus according to the present invention provides a user access to authenticated electronic documents contained on a computer network.
0006Additionally, a method of providing access to authenticated electronic documents over a network is disclosed. The method includes the steps of: 1) Initializing a database by storing indexed information for identifying and authenticating the electronic documents therein; 2) Receiving a user request for an electronic document; 3) Searching for and retrieving information for identifying and authenticating the requested document from the database; 4) Accessing the network and retrieving the content of the requested document; 5) Calculating a checksum or sum value for the content of the retrieved document; 6) Comparing the sum value calculated for the retrieved document with the authenticating information retrieved from the database for the particular document; 7) Determining if the document is authentic; 8) Returning the contents of the document to the user if the contents are determined authentic; 9) Returning a refusal to the user if the content of the retrieved document is not authentic or if the requested document is not indexed in the database; and 10) Updating the database accordingly with the status of the authenticity of the electronic document. The method according to the present invention allows a user to access authenticated electronic documents contained on a computer network.
0007One advantage associated with the present invention is the ability to provide trusted access to a computer network.
0008Another advantage associated with the invention is the ability to provide access to selected and authenticated electronic documents contained within a computer network.
0009Another advantage associated with the invention is the ability to identify the content of electronic documents as trusted or not trusted which is based on a review by individuals. Each document for which access is provided is reviewed individually as to the subject matter or accuracy of the content thereof and after approval, the document is indexed accordingly in the database including randomly generated seed values which are used thereafter to verify the authenticity of the document. Additionally, denial to objectionable material or other not authorized material is automatic as the network is not accessible to the user directly.
0010Another advantage associated with the present invention is the use of disjunct interfaces to connect the user interface, the network, and the database to the server computer and the verification server to eliminate unauthorized access to the network or the database.
0011Another advantage is the use of the verification server to iteratively traverse the database containing indexed information for the electronic documents for which access is provided and to retrieve the content of each document, check the authenticity thereof and update the database according with the authenticity status of the particular document, thereby providing for access to authentic electronic documents.
0012Another advantage is the use of a two pass method of calculating checksums for authenticating the content of electronic documents.
BRIEF DESCRIPTION OF THE DRAWINGS
0013<figref idref="DRAWINGS">FIGS. 1-3</figref> are block diagrams of various embodiments of the apparatus of the present invention;
0014<figref idref="DRAWINGS">FIG. 4</figref> is a flow chart representing the method for providing access to authenticated documents over a network according to the present invention;
0015<figref idref="DRAWINGS">FIG. 5</figref> is a is a flow chart representing one embodiment of the method of calculating checksums for authenticating the content of electronic documents according to the present invention;
0016<figref idref="DRAWINGS">FIG. 6</figref> is a flow chart representing one embodiment of the verification server of the present invention; and
0017<figref idref="DRAWINGS">FIG. 7</figref> is a diagram of one embodiment of the format of a database according to the present invention.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
0018A detailed description of the preferred embodiments of the invention follows. It is to be understood that the disclosed embodiments are merely exemplary of the invention, which may be embodied in various forms. Therefore, specific structural and functional details disclosed are not to be interpreted as limiting, but rather as a representative basis for teaching one skilled in the art to variously employ the present invention in virtually any appropriately detailed system or structure. It should be understood that the drawings included herewith represent preferred embodiments of the invention only and are included to facilitate an understanding of the invention and not to limit the scope thereof.
0019Referring to the drawings, wherein like numerals represent like elements throughout the several views, <figref idref="DRAWINGS">FIG. 1</figref> is a diagram of an apparatus constructed according to one embodiment of the present invention, generally <b>100</b>, including user <b>10</b> having access to computer <b>12</b>. Computer <b>12</b> is connectable to server <b>16</b> via public network <b>14</b>. Server computer <b>16</b> comprises a first network interface <b>18</b> connected to public network <b>14</b> for providing user access to server <b>16</b> and connecting server <b>16</b> to public network <b>14</b>. A second network interface <b>20</b> connects server <b>16</b> to private network <b>15</b> for retrieving data from networks <b>15</b>. A third network interface <b>22</b> connects server <b>16</b> to database <b>24</b>. Network interfaces <b>18</b>, <b>20</b>, and <b>22</b> are disjunct with respect to each other, such that user <b>10</b>, networks <b>14</b> and <b>15</b>, and database <b>24</b> are not in direct communication therebetween. Server <b>16</b> can be configured using individual network cards for each of the interfaces <b>18</b>, <b>20</b>, and <b>22</b> to eliminate the possibility of unauthorized data transmissions between user <b>10</b>, network <b>14</b>, and database <b>24</b>. The network can be public network <b>14</b> such as the Internet or any type of private network <b>15</b>. Verification server <b>28</b> is connected to database <b>24</b> via network interface <b>30</b> and networks <b>14</b> and/or <b>15</b> via interface <b>32</b>. Interfaces <b>30</b> and <b>32</b> are disjunct relative to each other such that database <b>24</b> is not accessible to networks <b>14</b> or <b>15</b>. Interface <b>32</b> for connecting verification server <b>28</b> to public network <b>14</b> or private network <b>15</b> could be separate interfaces as shown in <figref idref="DRAWINGS">FIG. 1</figref> or verification server <b>28</b> could be configured to interface both public network <b>14</b> and private network <b>15</b> using the same interface.
0020<figref idref="DRAWINGS">FIG. 2</figref> diagrams an embodiment of the present invention, generally <b>100</b>, which includes router <b>36</b> connected to user machines <b>12</b>, public network <b>14</b>, private network <b>15</b> and high speed switch <b>38</b>. Router <b>36</b> and switch <b>38</b> are for forwarding data interior to apparatus <b>100</b> as well as to and from the networks <b>14</b> and <b>15</b> connected thereto. Router <b>36</b> can be configured as a firewall for security purposes.
0021<figref idref="DRAWINGS">FIG. 3</figref> shows an embodiment of the present invention, generally <b>100</b>, comprising router <b>46</b> connected to high speed switch <b>38</b> and public network <b>14</b>. The <figref idref="DRAWINGS">FIG. 3</figref> embodiment includes router <b>46</b> configured to accept point to point tunneling type connections, on private internet provider addresses from a request router <b>44</b>. Request router <b>44</b> is connected to user machines <b>12</b> and router <b>46</b> via network <b>14</b>. Point to point tunneling type connections refers to a protocol that allows entities to extend their own networks through private “tunnels” over a public network such as the Internet, such that, in effect an entity can securely use a public network as its own local network. This type of interconnection is known in the art and may be referred to as a virtual private network. The <figref idref="DRAWINGS">FIG. 3</figref> embodiment of the present invention is configured to utilize point to point type connections such that a virtual private network is established between apparatus <b>100</b> and user machines <b>12</b>. Referring again to the <figref idref="DRAWINGS">FIG. 3</figref> embodiment of the present invention, a third router <b>48</b> is connected to switch <b>38</b>, public network <b>14</b> and private network <b>15</b> for retrieving data from networks <b>14</b> and <b>15</b>.
0022Referring to <figref idref="DRAWINGS">FIG. 4</figref> a flowchart is generally indicated at <b>50</b>. The flowchart <b>50</b> represents a method used according to the present invention for providing access to authenticated documents contained in computer network <b>14</b> or <b>15</b> utilizing user machines <b>12</b> and apparatus <b>100</b>. The method utilized by server <b>16</b> begins at <b>52</b>. A user request for content from the network is input at <b>54</b>. The user request could be a programmatic request from a remote computer. Database <b>24</b> is accessed at <b>56</b> and authenticating information for the particular content requested is searched for and retrieved therefrom. At <b>58</b> a determination is made whether or not database <b>24</b> contains information regarding the particular content requested as well as the authenticity status of the content if it exists in the database <b>24</b>. If the authenticity status of the requested content is negative or if the requested content is not indexed in database <b>24</b>, then a refusal is returned to the user at <b>70</b>. If the requested content is indexed in database <b>24</b> and the authenticity status therefor is determined positive at <b>58</b>, network <b>14</b> or <b>15</b> is accessed at <b>60</b> and the requested content is copied therefrom. A checksum is calculated at <b>62</b> using the authenticating information retrieved from database <b>24</b> at <b>56</b> and a predetermined algorithm. At <b>64</b> a comparison is made between the checksum calculated at <b>62</b> and the stored checksum for the particular content retrieved from database <b>24</b> at <b>56</b>, if the checksums are equal, the requested content is returned to the user at <b>72</b> and the method is terminated. Otherwise, if the checksums are not equal at <b>64</b>, the authenticity status for the content requested is updated to a negative or not trusted status at <b>66</b>. The content requested and determined not authentic at <b>64</b>, and therefore not trusted, is forwarded to a quality assurance department at <b>68</b>. A refusal is returned to user machine <b>12</b> at <b>70</b> and the method is terminated.
0023Referring to <figref idref="DRAWINGS">FIG. 5</figref> a flowchart is generally indicated at <b>75</b>. The flowchart <b>75</b> represents a method used according to the present invention for calculating a checksum for a document. The method for calculating a checksum, utilized by server <b>16</b> and verification server <b>28</b> begins at <b>76</b>. Counters for the number of characters in the document (start) and the checksum value (TCS sum) are initialized to zero at <b>78</b>. Also, at <b>78</b> a length counter (length) is initialized to the number of characters in the document. Database <b>24</b> is accessed at <b>80</b> to determine if seed values exist for the content for which a checksum is being calculated. If seed values exist in database <b>24</b> for the particular document, LR seed value (LR) for the length right, and RL seed value for the return length are retrieved from database <b>24</b>. If no seed values exist for the document, seed values are determined for length right (LR) and return length (RL) at <b>82</b> using a random number generator, and stored in database <b>24</b>. A character by character traversal of the content of the document begins at <b>84</b> with the retrieval of the first character. At <b>86</b> a determination is made to see if more characters exist or if the traversal of the content is complete. If the traversal of the content of the document is complete, the checksum, TCS sum is returned at <b>88</b> and the method for calculating a checksum for a document terminates at <b>88</b>. Otherwise, if the character traversal is not complete, at <b>90</b>, the ASCII value of the character is used to increase the TCS value as follows: First, the value of (LR seed*start*character) is added to the value of TCS sum where character is the ASCII value of the character; Secondly, the value of (RL seed*length*character) is added to the value of TCS sum where character is the ASCII value of the character. At <b>92</b>, the start and length counters are incremented and decreased by one respectively. The next character in the document is retrieved at <b>94</b>, and returned to the end of content determination step at <b>86</b>. The method terminates and the TCS sum is returned, at <b>88</b>, when the traversal of the characters in the document is complete.
0024Alternatively, a two-pass method for calculating the checksum uses predetermine seed numbers and includes the steps of a) retrieving indexed seed numbers for the document from database <b>24</b>; b) traversing a forward pass of the data stream of the content of the retrieved document and calculating a first value for each position in said data stream using the seed numbers; c) traversing a reverse pass of the data stream of the content of the retrieved document and calculating a second value for each position in the data stream using the seed numbers; and d) summing the first value and second values.
0025Referring to <figref idref="DRAWINGS">FIG. 6</figref> a flowchart is generally indicated at <b>95</b>. Flowchart <b>95</b> represents a method used by verification server <b>28</b> according to the present invention. Verification server <b>28</b> constantly cycles through database <b>24</b> and retrieves the information stored therein for identifying and authenticating the particular documents contained in the network <b>14</b> or <b>15</b>. Verification server <b>28</b> retrieves from network <b>14</b> or <b>15</b> the content of the document identified and checks the authenticity thereof using the information retrieved from database <b>24</b> and the checksum calculation shown in FIG. <b>5</b> and described above. A preferred method of authentication utilized by verification server <b>28</b> is outlined in flowchart <b>95</b>. The method starts at <b>98</b>. Database <b>24</b> is accessed and the list of identification and authentication information for all documents indexed in database <b>24</b> is retrieved at <b>102</b>. In particular, the information retrieved at <b>102</b> includes the TCS sum, authentication status, seed values, and address information for each document indexed in the list. The first entry from the list is read at <b>104</b>. A determination is made at <b>106</b>, whether or not the entry read at <b>104</b> is the end of the list. If the entry is determined to be the end of the list at <b>106</b>, verification server <b>28</b> returns to database <b>24</b> at <b>102</b> and retrieves the entire list stored therein. Otherwise, at <b>108</b>, the content identified by the current entry is retrieved and copied from network <b>14</b> or <b>15</b>. At <b>110</b>. a checksum is calculated for the content retrieved using the algorithm described above and shown in FIG. <b>5</b>. One skilled in the art will recognize that any appropriate algorithm could be utilized and that the one identified in <figref idref="DRAWINGS">FIG. 5</figref> is merely a preferred algorithm identified by the Applicant. At <b>112</b> a determination is made whether or not the content retrieved is authentic by comparing the checksum calculated at <b>110</b> with the checksum value read from database <b>24</b> for the particular document. If the checksums are determined to be equivalent, the retrieved content is determined authentic, and the server <b>28</b> reads the next entry in the list and returns to <b>106</b>. Otherwise, if the checksums at compared at <b>112</b> are not equal, the content is determined not authentic and the authenticity status for the entry is updated to negative or not trusted in database <b>24</b>. If determined not authentic, or not trusted, the content of the document is forwarded to a quality assurance department for further review at <b>116</b>. Thus, according to the present invention, verification server <b>28</b> continuously traverses database <b>24</b> checking the authenticity of each entry indexed therein.
0026Referring to <figref idref="DRAWINGS">FIG. 7</figref>, tables <b>105</b> and <b>115</b> represent one embodiment of the format of database <b>24</b> for each indexed document stored therein, according to the present invention. At <b>122</b>, an identification for the document is stored in the form of an integer. At <b>124</b>, the checksum (TCS sum), is stored for the content of the document as an integer. The authenticity status for the content of the document is stored as a character at <b>126</b>. At <b>128</b>, and <b>130</b> seed values (LR) for the length right, and (RL) for the return length, respectively are stored in database <b>24</b>. Identification integer <b>122</b> is also used to access the content identification represented by table <b>115</b> wherein the Universal Resource Locator (URL) addresses are stored at <b>136</b> for each document indexed in database <b>24</b> which is contained in public network <b>14</b>. If the document is contained in a private network an appropriate address therefor would be stored at <b>136</b>. A content identifier for each document is stored at <b>136</b> in database <b>24</b>.
0027The applicant has suggested that some of the many uses of the trusted content server of the present invention are applications involving internet access for schools, applications related to the financial industry as well as many other industries wherein the authenticity of the content of documents is important. One skilled in the art will recognize that there are many applications wherein the present invention can be used to authentic the content of documents stored on a network.
0028Thus, while the present invention has been described with preferred embodiments thereof, it will be understood that many modifications will be readily apparent to those skilled in the art. Therefore, it is intended that this invention be limited only by the following claims and the equivalents thereof.
Contents5
8 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US9892100B2 | Cited by | United States of America | Applicant |
| US9984052B2 | Cited by | United States of America | Applicant |
| US2006288015A1 | Cited by | United States of America | Pre-grant |
| US8607323B2 | Cited by | United States of America | Search report |
| US8813021B1 | Cited by | United States of America | Applicant |
| US8701023B1 | Cited by | United States of America | Applicant |
| US2007124667A1 | Cited by | United States of America | Pre-grant |
| US2016364376A1 | Cited by | United States of America | Search report |
| US2016364376A1 | Cited by | United States of America | Search report |
| US8549390B2 | Cited by | United States of America | Search report |
| US2007214105A1 | Cited by | United States of America | Pre-grant |
| US9477647B2 | Cited by | United States of America | Applicant |
| US2004034793A1 | Cited by | United States of America | Pre-grant |
| US2012227101A1 | Cited by | United States of America | Pre-grant |
| US8166533B2 | Cited by | United States of America | Search report |
| US2016364376A1 | Cited by | United States of America | Pre-grant |
| US4349695A | Cites | United States of America | Applicant |
| US4393269A | Cites | United States of America | Applicant |
| US4509851A | Cites | United States of America | Search report |
| US5142577A | Cites | United States of America | Applicant |
| US5226091A | Cites | United States of America | Search report |
| US5511122A | Cites | United States of America | Applicant |
| US5539826A | Cites | United States of America | Applicant |
| US5673318A | Cites | United States of America | Applicant |
| US5706427A | Cites | United States of America | Applicant |
| US5841970A | Cites | United States of America | Applicant |
| US5987232A | Cites | United States of America | Applicant |
| US6018801A | Cites | United States of America | Applicant |
| US6044373A | Cites | United States of America | Applicant |
| US6076163A | Cites | United States of America | Applicant |
| US6098190A | Cites | United States of America | Search report |
| US6138239A | Cites | United States of America | Applicant |
| US6145084A | Cites | United States of America | Applicant |
| US6398245B1 | Cites | United States of America | Search report |
| US6526092B1 | Cites | United States of America | Search report |
| US6708157B2 | Cites | United States of America | Search report |
| US6715075B1 | Cites | United States of America | Search report |
| US6721721B1 | Cites | United States of America | Search report |
| US6779039B1 | Cites | United States of America | Search report |
| US6807534B1 | Cites | United States of America | Search report |
2 members in 1 office
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 90312401 | United States of America | A | |
| US20010903124 | – | – | – |
Members2
| Document | Office | Kind | |
|---|---|---|---|
| US2003014666A1 | United States of America | A1 | |
| US6941477B2This record | 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 | |
|---|---|
| Entity status set to undiscounted (initial default setting or status change) | |
| Change in Power of Attorney (May Include Associate POA) | |
| Correspondence Address Change | |
| Recordation of Patent Grant Mailed | |
| Patent Issue Date Used in PTA CalculationAllowed | |
| Issue Notification MailedAllowed | |
| Receipt into Pubs | |
| Dispatch to FDC | |
| Application Is Considered Ready for Issue | |
| Issue Fee Payment Verified | |
| Applicant Has Filed a Verified Statement of Small Entity Status in Compliance with 37 CFR 1.27 | |
| Issue Fee Payment Received | |
| Receipt into Pubs | |
| Workflow - File Sent to Contractor | |
| Mail Notice of AllowanceAllowed | |
| Mail Examiner's Amendment | |
| Notice of Allowance Data Verification CompletedAllowed | |
| Examiner's Amendment Communication | |
| Interview Summary Record | |
| IFW TSS Processing by Tech Center Complete | |
| Date Forwarded to Examiner | |
| Response after Non-Final Action | |
| Workflow incoming amendment IFW | |
| Mail Non-Final RejectionNon-final rejection | |
| Non-Final RejectionNon-final rejection | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Case Docketed to Examiner in GAU | |
| Reference capture on IDS | |
| Information Disclosure Statement (IDS) Filed | |
| Information Disclosure Statement (IDS) Filed | |
| Application Dispatched from OIPE | |
| Application Is Now Complete | |
| Correspondence Address Change | |
| IFW Scan & PACR Auto Security Review | |
| Initial Exam Team nn |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Fee payment procedurePAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| RefundREFUND - PAYMENT OF MAINTENANCE FEE, 8TH YR, SMALL ENTITY (ORIGINAL EVENT CODE: R2552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYREFU | REFU | |
| AssignmentAS | AS | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF |
Numbers
- Publication
- 06941477
- Publication, DOCDB
- 6941477
- Publication, EPODOC
- US6941477
- Application
- 9903124
- Application, DOCDB
- 90312401
- Application, EPODOC
- US20010903124
Titles
- English
- Trusted content server
Patent term adjustment
- A delay
- +797 daysthe office missed an examination deadline
- Net adjustment
- 797 days
Classification
- CPC, 2
- H04L63/12
- G06F21/645
- IPC, 2
- G06F21 00
- H04L29 06
- USPC, 4
- 726004000
- 705051000
- 707999010
- 713182000