EP1169679A2 - Creation de documents electroniques surs, procede d'approbation et de repartition dans un environnement de reseau ouvert et reparti - Google Patents

Creation de documents electroniques surs, procede d'approbation et de repartition dans un environnement de reseau ouvert et reparti

Info

Publication number
EP1169679A2
EP1169679A2 EP00916737A EP00916737A EP1169679A2 EP 1169679 A2 EP1169679 A2 EP 1169679A2 EP 00916737 A EP00916737 A EP 00916737A EP 00916737 A EP00916737 A EP 00916737A EP 1169679 A2 EP1169679 A2 EP 1169679A2
Authority
EP
European Patent Office
Prior art keywords
document
vip
information
application
eda
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.)
Withdrawn
Application number
EP00916737A
Other languages
German (de)
English (en)
Inventor
Joseph Silvester
Tommy Petrogiannis
François Leblanc
Guy Dumais
Benoit Goudreault-Edmond
Michael Laurie
Ed Milczarek
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Silanis Technology Inc
Original Assignee
Silanis Technology Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Silanis Technology Inc filed Critical Silanis Technology Inc
Publication of EP1169679A2 publication Critical patent/EP1169679A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting

Definitions

  • the present invention relates to a method for the secure creation, approval and distribution of electronic documents in an open and distributed network environment.
  • Figure 1 show the typical hybrid document environment prevalent in most organizations and corporations.
  • documents originate in one of two ways: they start their existence as a paper document or as an electronic document.
  • documents are approved using handwritten signatures and/or seals. These approvals are usually executed on paper documents.
  • the paper documents are distributed via fax, courier or mail service.
  • original documents are the documents that are signed or sealed, and tend to be stored by the organization for legal reasons. Therefore, documents that are approved on paper or originated on paper are extremely hard to eliminate once they have been created and approved.
  • VIP virtual identification profile
  • the invention also concerns a method for creating a secure document comprising the steps of:
  • the invention provides for a method for securely printing a secure document including security information, comprising the steps of: (a) providing the document within an application;
  • a system for creating, approving and distributing secure documents comprising: a central location for storing and updating a plurality of virtual identification profiles (VIP), each of said virtual identification profiles being linked to a single user, said virtual identification profile including personal information, identity verification data and relevant data, and a variable authentication code associated with a respective VIP; and at least one application for creating a document, said at least one application being in communication with said central location, said application verifying if said VIP contains pertinent data for the user and for inserting the pertinent data into the document at the time of creation and for approving the document once created.
  • VIP virtual identification profiles
  • Figure 1 [prior art] is a schematic representation of the typical current hybrid document environment
  • Figure 2 is a flowchart of the steps for creating a VIP according to the invention
  • Figure 3 is a flowchart of the steps for creating and verifying a document according to the invention.
  • Figure 4 is a schematic representation of an EDA according to the invention.
  • Figure 5 is a schematic representation of secure printing of a document according to the invention.
  • Figure 6 is a schematic representation of the system according to a preferred embodiment of the invention.
  • the main focus of the invention is to permit an organization to function in an open environment, i.e. a hybrid document environment as shown in Fig. 1.
  • the key to making this a reality is to use the document/data and/or the delivery system to deliver the secure or secret/controlled information.
  • Another important aspect of this invention is to allow users to work in the same environment as described in
  • FIG. 1 with minimal modifications to existing procedures and systems. Consequently, one important aspect of the invention is the provision of a mechanism to validate the contents of the document or the user identification data, using a Variable Authentication Code (VAC).
  • VAC Variable Authentication Code
  • This VAC will be mathematically related to the number of transactions that are done using the data and the different number of users.
  • a further important aspect of the invention is to embed in a document an embedded document application or to provide a link to the document application, as will be further described.
  • the first step of the present invention is to structure a virtual identification profile, hereinafter referred to as "VIP".
  • VIP contains personal and/or corporate information, verification data, relevant data and a DAC, which is a mathematical representation of the VIP.
  • Identification of the user can be done using various methods. Typically, depending on the security requirements, all or some of the following items can be used. However, basic information must be present in the VIP: personal information (name, address, etc.); verification data (such as a digitized signature or biometric data); relevant data (ID No.; private/public key pair; digital certificates). It should be apparent that the more items are used, the easier it will be to identify the individual at a later time:
  • identifying information such as seals, stamps, indicia, etc.
  • VAC Variable Authentication Code
  • the process begins 11 by determining whether or not a new VIP is being created 13. If so, the personal information of the user is obtained and inserted 15, verification data inserted 17, relevant data inserted 19, and data is updated or edited and the VAC is calculated 21. All the information in the VIP is encrypted and stored in a secure environment. It should be noted that the VIP can be a file, record in a database, etc.
  • the central location is appropriately marked 31. If the update is not successful 35, the creation or update is aborted.
  • the information present in the VIP cannot be added or deleted without user notification 23 and preferably a central location 25. However, certain information such as the VAC will be automatically changed with or without user knowledge or consent depending on the circumstances. Editing and manipulating the information contained in the VIP file will be strictly controlled and recorded by the central location.
  • all information can be stored together or separately, as the case may be. For example, medical records and access information could be stored in separate medical locations with appropriate links inside the VIP, as could be financial information, etc.
  • the data in the VIP is preferably stored in an onion model, i.e. in multiple layers.
  • the outermost layer contains public or low security information.
  • the next layer contains more secure information and the deeper one progresses into the model the more sensitive the data.
  • Each layer can be protected with different encryption schemes, so that decrypting one layer does not mean the entire VIP becomes compromised.
  • the VIPs have the ability to inherit data from other VIPs.
  • a Person A with VIP A is employed by company B having the company VIP B, then, by mutual agreement, certain elements or data contained in the VIPs could be exchanged.
  • the VIP A could inherit public data or data that is to be made available to the employees from the company's VIP B. This can be accomplished using existing methods such as tagging data that can be transferred etc. This exchange of data can be automatic or manual.
  • the VIP A could inherit the company address, telephone number, encryption code to be used for secure communications etc.
  • the Company VIP B could inherit pertinent data from the VIP A. This interactive inheritance could occur in various situations such as the one mentioned above.
  • the VAC will be modified depending the transactions that are performed using this identification file. Anytime independent transactions are performed where this identification file can be identified or linked to the real person, the VAC will be increased.
  • the VAC can be normalized to percentage and each transaction will create a change in the VAC. For example, transactions that are done with government organizations can increase the VAC of the person doing the transaction. As more certificates from other agencies are included, the VAC could be increased.
  • the same method could be employed if the person is approving secure documents containing high security contents. The assumption here is that these documents will be highly scrutinized by others: if illegal VIP files are used to approve, this would be reported and corrected. Also, the VAC could be decreased if the VIP file has not been used for certain time.
  • the VAC can be checked and verified before a transaction is completed.
  • the type of transaction the user will want to participate in will dictate the VAC required.
  • the user may need to provide more personal information to increase the VAC percentage to participate in these transactions or add more data to the VIP to increase the VAC.
  • the software will determine, depending on the detail in the VIP, what VAC will be assigned to the VIP. In all circumstances, the VAC is intimately related to the contents of the VIP.
  • the VIP does not have to be a physical file: it could be a record in a database, field, a database entry, web page, web site, a location in memory containing the information, etc. It could be stored in any format as long the information is available for use through a network.
  • file is used in the context of the present application as a generic term to indicate that the pertinent data is available and accessible for use and is structured.
  • document creation and approval can be done using established database access methods. For example, all users and their signatures or identification can be stored in a central database. During the creation of the user signature file, a unique record can be stored in the central database that is linked to the signature file. When a user attempts to sign a document in the closed environment, the approval software will check the unique marker in the signature file with the central database. If the central database does not contain the unique marker, then the user can be prevented from signing the document. A message can be sent to the appropriate authority indicating the fact that an unregistered or uncontrolled signature was being used in the closed environment system. However, for this method to work, the environment has to be closed and the central database needs to be accessible to all the users.
  • other identification information can be stored in a central database, such as biometric information, and compared against the person approving to verify the identity of the person.
  • a central database such as a manufacturing plant, where everyone is connected to a central database. Users can be asked to identify themselves, their identity can be validated using the central database and then appropriate access can be granted.
  • the closed environment model cannot apply. It has been found that some control and security found in closed systems can be present in an open environment by embedding the required security features and data in the document itself, according to a feature of the present invention (See Figure 3).
  • the document could be signed in a manner similar to code signing and appropriate control information such as public keys of the signers of the document could be inserted therein (assuming people will be approving the document).
  • appropriate control information such as public keys of the signers of the document could be inserted therein (assuming people will be approving the document).
  • Additional information could be added to the document in an encrypted fashion, such as the identity or the public keys of the signers or the biometric information of the signers could be inserted into the document.
  • the approval software can verify the user identity with the ones contained in the document; if they are the same it will permit the approval; if not, it will not allow the users to sign.
  • the above mentioned VIP file could contain the public key of the employer, in addition to private/public key identifying the user.
  • the same method can be used to protect the contents of the document.
  • the document can be protected using encryption technology.
  • the unlock passwords can be embedded in the document, again related to the users who have access to the document.
  • the application to unlock the document can be a part of the signing application.
  • the unlock procedure would be similar to the signing application, where the user would identify himself/herself using their VIP file and this would be used to unlock and decrypt the encrypted portions of the document.
  • the present invention provides for a method for creating a secure document. Under a given application (such as a word processor, spreadsheet, graphics, etc.), a command is given to initiate the creation of such a secure document 101. A determination is made as to whether the environment is closed or open 103.
  • Pertinent information includes, but is not limited to, organization identification, document serial number, public key, secret identification information, document security information, etc., and additional information inserted 109. Additional information includes, but is not limited to, approval, distribution, routing, archival, or embedded document application information, and that the document is made ready for use.
  • the application checks whether a central database is accessible 115. If so, the pertinent information is obtained and inserted in the document 117, and the process continues normally at step 105. If the central database is not accessible, the process continues at step 105.
  • step 109 If the VIP does not contain pertinent data, a low-level or uncontrolled document is created, and the process continues at step 109.
  • the present invention contrary to a closed environment where all of the pertinent information and additional information is self-contained and often centralized, provides a system and method where the document itself includes such information, and thus the relevant and additional information is decentralized.
  • the advantage is that documents can be approved, exchanged, printed, distributed, etc., more freely, while at the same time keeping a minimum amount of security.
  • the document contains information about the signer, and information about the origin of the document.
  • the contents of the document can be encrypted, and the access to this document can be controlled.
  • the document approval can be completed in a closed environment only.
  • the document is a secure document, which means it can only be approved in a controlled environment.
  • the security information can be loaded into the document at creation, then security checks can be conducted with information contained in the document. This is a procedure where the document is created outside the closed environment and then enters the closed environment for approvals to be finalized therein.
  • the users will approve the document outside and then approval will be kept pending until the document enters the closed environment and the appropriate security checks are conducted. Accordingly, the following steps can be followed:
  • the document could contain a marker indicating whether the document is a secure document or if document will contain pending approvals • Document is transmitted outside the closed environment
  • this invention discloses a method for embedding applications in the document, Embedded Document Application (EDA) as shown in Figure 4.
  • EDA Embedded Document Application
  • the EDA's are able to install and execute the application from inside the document.
  • an advantage of the present invention is that a user receiving a document created according to the invention does not require an external application to access all these approval and security functions or any other function a document may contain.
  • the document itself will contain the application, or a link to facilitate obtaining the application that is required to achieve all of the required functions.
  • the application can establish control with a central database directly or via email or another method to synchronize activity. If, for example, only a certain number of hardcopies of a document can be printed (see Figure 5), the application contained in the document or the external approval application will access security information within the document 301.
  • a determination will be made as to whether secure printing is enabled 303. If so, a determination is made as to whether a central database (or other central location) is accessible 305. If the database is accessible, the print counter is checked 307. If the counter is less than or equal to a predetermined number (meaning that the document can be printed), the print counter is incremented by one 309, security information verified and inserted 311 and the document printed 313.
  • the document can be freely printed. Consequently, security information is verified 319, and the document is printed 321. If the central database is not accessible, verification cannot be performed and so the print command is aborted 317. Similarly, if the print counter is greater than the predetermined number, the print command is absorbed 317.
  • a central database is used and the access to this database can be through direct connection, email, internet and/or the web.
  • messages to be displayed could be embedded in the document as are the commands on how and where to display them.
  • the document could contain an application (another EDA) that could learn information about the use and handling of the document. For example, this other EDA could determine the workflow of the document as it is routed from person to person. This information can then be stored in a central access area. When a new document is created, the EDA in the new document checks this central access area for details pertaining to workflow for this document and then uses this information to route the new document. Modifications and changes can be added to the central data access area.
  • the document could have embedded details of how and when it should be routed and distributed. This would enable the EDA to determine if the document cycle has been progressing according to plan i.e. the EDA could determine if the document has been approved by someone at pre-determined time etc. If not, appropriate notification can be sent to a central database and appropriate action could be initiated. Then, the appropriate user can be notified about the document and appropriate action can be taken. It is also possible to update or modify the actions that could be taken by the EDA application via the central database.
  • the document and the EDA could also, depending on the contents of the document, verify the validity of the user's VIP file or could demand a co-signer with appropriate VACs. All this can be done dynamically and is a matter of designing the appropriate structure to meet predetermined objectives.
  • the system determines if the application is present on the system 201. If not, the application is loaded 203, registered on the system 205 and may be optionally installed on the user system 207. According to the EDA, approval 209, process and behaviour functions 211 , security 213, or advertising, branding, corporate logos, etc. 215, actions are performed, and then the EDA is stored 217.
  • the EDA can exhibit different behaviour based on various criteria. For example, a corporation could embed an EDA into their documents that will contain security information, workflow information and also have the corporate logo. The corporation could have another document that could contain the corporate logo and advertising, that it might choose to send out to prospective customers.
  • the EDA can be tailored to have all or some of the functionality described above.
  • the EDA application contains all the data and executable code. All this information is embedded in the document.
  • the EDA object When the document is opened the EDA object will load its executable code into memory and execute the code.
  • this code could access data from a central database and change, modify and/or update data and functions.
  • EDA could load a small application into memory that can execute continuously on the system; this application can monitor all other documents that enter this system and perform the functions of the EDA or activate the document EDA in the document. This will address the issue of a document not being opened by the user.
  • the EDA application can have the capability of self promotion, such as the ability to inform the users where to find the application or to add the application to new documents.
  • distributing the document can be done using the following methods - electronic distribution or paper distribution or a combination of the two. Ideally, as mentioned earlier, it is best to eliminate paper altogether, however, there are situations where paper will nonetheless be required.
  • the document contains sensitive materials, then it is highly advisable for the document to be encrypted during distribution.
  • the encryption can be done using the keys supplied in the VIP file. For example, if the public key of the reader is known, the document can be encrypted with this public key and the recipient can only open it with their private key. Another option is to encrypt with the public key of an organization, then only people who have the private key of the organization can decrypt the document. There are variations on this theme can be used including certificates etc.
  • the document When going to paper, the document will be verified by the EDA or the approval application before placing a high quality signature on the document.
  • the approval applications will not place a high quality signature, branded image or seals in the document for printing unless the contents are verified.
  • the approval application will store low quality signature images or no signature images in the document when the document is closed or when the contents have been altered.
  • a user generates VIP files from controlled locations.
  • Appropriate VACs are generated based on the security required by the document.
  • the basic public information such as Name, Address and Telephone numbers are added. Additional private information such as Social Security Number, Driver's license, Passport, Medicare numbers can be added. Additional identification information such as picture, signature, biometric information could also be added to the file. As mentioned above, the more validated data the higher the VAC.
  • a very minimal VIP file creation would be the following.
  • a user's signature is digitized, a private/public key pair is generated, the application generates a certificate and inserts it into the VIP file (See Figure 1). Additional certificates if available could also be included into the file.
  • the entire file is then encrypted and protected using a user supplied password.
  • the application at a controlled location used to generate the VIP file can be given a certificate, and all subsequent files created at the controlled location will add this certificate to all VIP files or the application can be used with a default certificate. As mentioned earlier additional certificates can be added to this file. If other certificates are used, the public keys of these Certificate Authorities must be accessible to the approval application to verify the certificates; these public keys could be available through a central data base or these keys could be distributed through the embedded data contained in the documents.
  • a document is created for approval and distribution. If the document is a controlled document, appropriate security information can be embedded into the document, along with an EDA that will have the approval and possibly other functions. Optionally, if this electronic document is an official document, then company letterhead/identification information will be embedded into the document.
  • the EDA application Upon initiating an approval, the EDA application will request the person to supply their VIP file or enter an electronic signature. If the document requires biometric verification, this could be requested by the EDA and compared with the stored biometric data in the VIP or a central database or in the document etc. If everything is in order the signature is entered into the document along with other approval information.
  • the information is stored in a secure encrypted fashion.
  • the signature is stored using a special low quality format or a secure reduced noise format. In this last format, the hash of the document is preferably used to create a noise pattern which is filtered to various gradients - depending on the quality required - and then combined with the signature bitmap. This will render the signature on a gray murky background.
  • the DAC from the document has to be re-calculated and used to clean up the noise. If the DAC has been altered from the time of signing then the noise pattern will not be the same as when it was stored; therefore the background will not be able to be completely removed.
  • the EDA could display the signature, branded image or could display other information as well, such as advertising, corporate logos, messages etc.
  • the signature will remain in a safe state - in this state the signature will not be displayed in high quality mode unless verified.
  • the signature will only be displayed in a high quality mode if the document contents have not been altered from the time it was signed.
  • the signature will not print in high quality mode unless the document has been verified to be valid.
  • the EDA will display or print a high quality signature.
  • the EDA can display other information in the document such as advertising, corporate logos, messages etc. It is possible for this information to be updated periodically via a central database. This will enable the advertising, logos and messages to be updated dynamically, and the updates could be targeted to the actual users. The advertising or messages could be different for each person - if this is desired.
  • the document contains an EDA for signing then the next user can open the document and would be able to work with the signed document. If they have a separate approval application they will also be able to work with the signed document.
  • the user can electronically print the document, the EDA or the approval application will verify the contents of the document and then if the verification is valid, it will print the document with the signatures.
  • the signature is used as the control feature for the document. If the users needs to see or print the document with the signature, the EDA has to verify the document and only then will it display the high quality signature; otherwise the signature is displayed in low quality mode (note: the signature could be alternatively completely removed). It is also possible to use the EDA without any signatures but to use images that are part of a branded identity, such as corporate logos to achieve the same results. For example the EDA could display a watermark indicating the document is invalid - this watermark will only be removed by the EDA if the document contents are verified.
  • the EDA can be used in the following manner.
  • An VIP which is preferably a representation of a logo, is applied to a document, email message, web page or other electronic media. Certain elements of the VIP are tied to the document, email message, web page or other electronic media.
  • the document, email message, etc. is sent to another user or viewed by another user. If between the time the VIP elements were introduced and tied to the document and the subsequent receipt or viewing of the document, the document was modified, the EDA will not display the logo properly (i.e. with an indication that the document has been modified), or will not display it at all. Consequently, the present invention can enable companies to create secure electronic letterhead with which the company can promote its identity electronically, without fear of somebody simply cutting and pasting the logo from one document to another and therefore passing it off.
  • the present invention can provide an intelligent letterhead (or logo), which can have multiple views.
  • company A has created dynamic logo A, which includes slogan A1 , followed a few seconds later by slogan A2 and then slogan A3, which cycle again.
  • This intelligent logo is then tied to an electronic document according to the method and system of the present invention.
  • a recipient of the document will be able to verify that the document has not been modified since its creation, or has been modified according to established criteria (for example, multiple signings). However, should a person cut and paste the logo from the original document to another document, the logo will invalidate itself and indicate that the logo and the document to which it is attached are not genuine.
  • the logo is intimately tied to the VIP of the company, and is inserted into a document through an EDA.
  • the EDA can also be used to function as a security unit. Users do not typically encrypt most email messages. This is mostly due to ignorance of the danger that exists there and the relative difficulty of using encryption software.
  • the EDA application can be used to achieve this in a single step.
  • the users can specify if the document is specific to one person or if access to this document is limited to employees of a certain organization. If the document is meant for one person, the EDA could encrypt the contents using the public key of the intended recipient. Once the intended recipient receives the document the EDA will request that the person supply their VIP file; this will contain the private key required for decrypting the data.
  • the document could be encrypted using the public key of the organization; anyone wishing to access the contents must have the organizations private key. (Note: this private/public key pair could be used just for documents - otherwise there could be a security risk if multiple people have the private key).
  • Key management could also be accomplished by using the EDA; after a certain period of time all users could be forced to a central database for updating their VIP files; during this time appropriate keys could be replaced or updated.
  • the present invention also provides a system for creating, approving and distributing secure document.
  • the system includes a central location 401 (but could include more than one as mentioned previously).
  • the central location 401 is adapted to store and update a plurality of VIPs which can be created at the central location or other authorized location.
  • Each of the VIPs are linked to a single user (such as a person or corporate organization).
  • the VIP as mentioned above, includes at least personal information, identity verification data, and a VAC.
  • the system includes at least one application 403 for creating a document.
  • the application is in communication (which is meant to include intermittent or sporadic communication, such as for a mobile user) with the central location through a network 402. the application is adapted to verify if the VIP of the user creating the document contains pertinent information, and to insert such pertinent information into the document, and to approve the document once created. If the system is closed, it can also include a central database 405 which can also include pertinent information.
  • the document also includes approval, distribution, routing, archival, or EDA information. Consequently, an advantage of the present invention is that the document itself includes all of the above information. Consequently, the document can travel within closed and open systems, all the while maintaining a minimum level of security.
  • the recipient application 407 when the document is sent to a recipient application 407, such as another user (through e-mail), a fax machine 409 or a printer 411 , the recipient application 407 does not need to recognize what type of document it is and how to handle it. In fact, the document itself contains such information, either through the VIP or through an EDA. When action is to be taken with the document, such as printing, the appropriate verifications are performed based on the information contained in the document. It should be understood that the recipient application can be just about anything, including an electronic storage media (i.e. CD-ROM, DVD, etc.).
  • Approval Data In general approval data includes information about the person approving, DAC of the document, Audit trail, signatures, biometric information, etc. All or some of the information could be present. This data is usually encrypted for security reasons.
  • Distribution system implies various methods of distributing data such as email, networks, world wide web, transactions in a transaction processing system, messages or links etc. Distribution system involves using any or all, or combination of systems.
  • Electronic Document can represent electronic files composed of text, images, video, graphics, audio, email or any other data or a combination of all of the above.
  • the Electronic document can also contain multiple files containing all or some of the above mentioned items.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Economics (AREA)
  • Artificial Intelligence (AREA)
  • Data Mining & Analysis (AREA)
  • Health & Medical Sciences (AREA)
  • General Engineering & Computer Science (AREA)
  • General Health & Medical Sciences (AREA)
  • Computational Linguistics (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Storage Device Security (AREA)
  • Document Processing Apparatus (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un système et un procédé pour la création sûre, l'approbation et la répartition de documents électroniques dans un environnement de réseau ouvert et réparti. Les informations personnelles d'un utilisateur pour lequel un profil est créé, les données de vérification d'identité et les données appropriées concernant cet utilisateur sont obtenues pour créer un profil d'identification virtuel. Ces informations sont mises à jour et éditées et un code d'authentification variable lié à ces informations est calculé. Le profil est ensuite codé, et un emplacement central est mis à jour avec ces informations. Ce profil peut être utilisé dans un système qui comprend un emplacement central pour stocker et mettre à jour plusieurs profils, et au moins une application pour créer un document, cette application étant en communication avec l'emplacement central. Cette application vérifie si le profil contient des données pertinentes pour l'utilisateur et permettant d'insérer ces données dans le document lors de sa création et d'approuver le document ainsi créé. Par conséquent, si le document est transmis à quelqu'un d'autre ou est utilisé pour une autre application, une application encastrée peut vérifier le code d'authentification variable pour déterminer si ce document a été modifié depuis son approbation. Il est ainsi possible de lier une signature ou un logo faisant partie du profil d'identification virtuel pour répartir des documents électroniques dans un système ouvert, tout en assurant la sécurité.
EP00916737A 1999-04-12 2000-04-12 Creation de documents electroniques surs, procede d'approbation et de repartition dans un environnement de reseau ouvert et reparti Withdrawn EP1169679A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US12887199P 1999-04-12 1999-04-12
US128871P 1999-04-12
PCT/CA2000/000406 WO2000062140A2 (fr) 1999-04-12 2000-04-12 Creation de documents electroniques surs, procede d'approbation et de repartition dans un environnement de reseau ouvert et reparti

Publications (1)

Publication Number Publication Date
EP1169679A2 true EP1169679A2 (fr) 2002-01-09

Family

ID=22437404

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00916737A Withdrawn EP1169679A2 (fr) 1999-04-12 2000-04-12 Creation de documents electroniques surs, procede d'approbation et de repartition dans un environnement de reseau ouvert et reparti

Country Status (4)

Country Link
EP (1) EP1169679A2 (fr)
AU (1) AU3800500A (fr)
CA (1) CA2366562A1 (fr)
WO (1) WO2000062140A2 (fr)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6904524B1 (en) 1999-12-21 2005-06-07 American Management Systems, Inc. Method and apparatus for providing human readable signature with digital signature
US7043636B2 (en) 2000-09-26 2006-05-09 Telefonaktiebolaget Lm Ericsson (Publ) Data integrity mechanisms for static and dynamic data
AU2002215781A1 (en) * 2000-12-14 2002-06-24 Silanis Technology Inc. Method and system for the approval of an electronic document over a network
US8688461B1 (en) 2002-03-29 2014-04-01 Fannie Mae Electronic registry for authenticating transferable records
US7818657B1 (en) 2002-04-01 2010-10-19 Fannie Mae Electronic document for mortgage transactions
WO2004006071A1 (fr) * 2002-07-02 2004-01-15 Telefonaktiebolaget Lm Ericsson (Publ) Procede de securisation et de presentation d'un logotype dans un dispositif electronique
US8571973B1 (en) 2002-12-09 2013-10-29 Corelogic Solutions, Llc Electronic closing
US20060047963A1 (en) * 2004-08-24 2006-03-02 Julia Brown Method and system for expeditious processing of guaranteed signature documents and the like

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU662805B2 (en) * 1992-04-06 1995-09-14 Addison M. Fischer A method for processing information among computers which may exchange messages
CA2242130A1 (fr) * 1998-08-07 2000-02-07 Silanis Technology Inc. Methode d'approbation parallele de documents dans un reseau de distribution
CA2246095A1 (fr) * 1998-09-25 2000-03-25 Tommy Petrogiannis Procede pour creer une liaison inseparable entre un document electronique et des objets ole
CA2246006A1 (fr) * 1998-09-25 2000-03-25 Silanis Technology Inc. Approbation a distance de gabarit dans un environnement de reseau reparti
CA2246049A1 (fr) * 1998-09-25 2000-03-25 Silanis Technology Inc. Procede pour creer des reproductions verifiable authentifiee de documents electroniques

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0062140A2 *

Also Published As

Publication number Publication date
WO2000062140A2 (fr) 2000-10-19
AU3800500A (en) 2000-11-14
WO2000062140A3 (fr) 2001-08-30
CA2366562A1 (fr) 2000-10-19

Similar Documents

Publication Publication Date Title
ES2251415T3 (es) Metodo electronico para almacenar y recuperar documentos originales autentificados.
JP3754565B2 (ja) 電子印鑑マーク認証システム
US20030217275A1 (en) Method and system for digital rights management and digital signatures
US7162635B2 (en) System and method for electronic transmission, storage, and retrieval of authenticated electronic original documents
US6216116B1 (en) System and method for handling permits
US7383441B2 (en) Method and device for confirming the authenticity of a document and a safe for storing data
EP1783652B1 (fr) Procédé pour garantir l' authenticité d'un document électronique et système de publication des documents électroniques
US6671804B1 (en) Method and apparatus for supporting authorities in a public key infrastructure
KR20010043332A (ko) 인증된 문서의 전자 전송, 저장 및 검색을 위한 시스템 및방법
AU2006202519A1 (en) Poims
JPH11512841A (ja) 文書認証システムおよび方法
CA2242130A1 (fr) Methode d'approbation parallele de documents dans un reseau de distribution
WO2000062140A2 (fr) Creation de documents electroniques surs, procede d'approbation et de repartition dans un environnement de reseau ouvert et reparti
JP2000076360A (ja) 文書管理方法および装置並びに文書管理プログラムを格納した記憶媒体
GB2358115A (en) Method and system for remote printing of duplication resistent documents
AU2006100468B4 (en) Poims
Effross Notes on PKI and Digital Negotiability: Would the Cybercourier Carry Luggage
Rebel et al. Ensuring security and trust in electronic commerce
KR100827299B1 (ko) 문서 배포 제어를 자동화하기 위한 컴퓨터 시스템
US8117457B2 (en) Trusted hardcopy document
Reed What is a Signature?', 2000 (3)

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20011004

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17Q First examination report despatched

Effective date: 20031117

RIN1 Information on inventor provided before grant (corrected)

Inventor name: SILVESTER, JOSEPH

Inventor name: MILCZAREK, ED

Inventor name: GOUDREAULT-EDMOND, BENOIT

Inventor name: LEBLANC, FRANEOIS

Inventor name: LAURIE, MICHAEL

Inventor name: PETROGIANNIS, TOMMY

Inventor name: DUMAIS, GUY

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB IT SE

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20040528