WO2016032596A2 - Traitement protégé d'informations protégées dans un environnement non protégé - Google Patents

Traitement protégé d'informations protégées dans un environnement non protégé Download PDF

Info

Publication number
WO2016032596A2
WO2016032596A2 PCT/US2015/035940 US2015035940W WO2016032596A2 WO 2016032596 A2 WO2016032596 A2 WO 2016032596A2 US 2015035940 W US2015035940 W US 2015035940W WO 2016032596 A2 WO2016032596 A2 WO 2016032596A2
Authority
WO
WIPO (PCT)
Prior art keywords
secure
data
task
sub
tasks
Prior art date
Application number
PCT/US2015/035940
Other languages
English (en)
Other versions
WO2016032596A3 (fr
Inventor
James R. MOCK
Tracy W. SHELBY
Devin T. SHERRY
Michael V. Gentry
Peter E. Clark
Michael C. Hudgins
Michael G. Metzger
Original Assignee
Dst Technologies, 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
Priority claimed from US14/305,245 external-priority patent/US20140298409A1/en
Application filed by Dst Technologies, Inc. filed Critical Dst Technologies, Inc.
Publication of WO2016032596A2 publication Critical patent/WO2016032596A2/fr
Publication of WO2016032596A3 publication Critical patent/WO2016032596A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
    • 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/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling

Definitions

  • HIT human intelligence tasks
  • Companies whose business workflow depends on HIT's often need to employ a substantial and/or highly skilled work force in order to complete these types of tasks.
  • an Internet search engine company needing to describe and catalog a library of pictures so that they may be searchable may require a large work force in order to perform the task on a large amount of data in a reasonable amount of time.
  • Figure 1 depicts of a system for processing secure information in a non-secure environment according to one embodiment.
  • Figure 2 depicts an exemplary project, and components thereof, as utilized by the system of Figure 1.
  • Figure 3 depicts a flow chart showing exemplary operation of the system of
  • Figure 4 depicts an exemplary computer system for use with the system of
  • an accessible and secured process sourcing and work management system for processing secure information in a non-secure environment is disclosed.
  • the system may be a used as, or in conjunction with a business rules management system ("BRMS”) for processing and performing tasks related to the secure information.
  • BRMS business rules management system
  • the system may be deployed organizationally, locally, regionally and/or globally in either a publicly accessible and/or restricted access implementation.
  • the system permits a user, referred to herein as a customer or requestor, to submit a project, involving a human intelligence task (“HIT”), referred to as a task or task specification, to be performed with respect to secure, confidential or sensitive information, referred to herein as secure information, and have that project completed in a non-secure
  • the system may be incorporated into the requestor's workflow, receiving projects therefrom and providing the results thereto. Further, a system is disclosed for implementing a processing workflow for such tasks, the system permitting, based on projects submitted by requestors, the "posting" or distribution of jobs, and subsequent management thereof, to be performed by a workforce operating in or via a non- secure-environment, while protecting the underlying security, confidentiality or sensitivity of the overall project. Further, the workflows may be generated or otherwise processed in conjunction with a BRMS for business and/or customer requirements or requests.
  • the workforce may include an at-will population of participants selected from the general public or from a subset thereof and may be limited to a selective workforce such as a bonded workforce, i.e. a workforce whose participants have been vetted as to their skill set and who are obligated, by a fiduciary obligation, or other legally and/or regulatory enforceable means, to act in best interests of their employer.
  • a selective workforce such as a bonded workforce, i.e. a workforce whose participants have been vetted as to their skill set and who are obligated, by a fiduciary obligation, or other legally and/or regulatory enforceable means, to act in best interests of their employer.
  • a workflow is defined as the activities, e.g. tasks or procedural steps, entities involved, i.e. actors or participants, such as people, organizations, machines, etc., inputs and outputs, states, requisite tools, and the relationships
  • workflow elements The various activities, entities, inputs, outputs, tools and relationships which make up the workflow are referred to as workflow elements. While computers and computer programs may be included as workflow elements, the disclosed embodiments are directed to workflows which further include workflow elements involving human decision making, human judgment, human-to- human interaction, or other subjective, arbitrary or illogical bases.
  • Figure 1 depicts a block diagram of a system 100 for processing secure information in a non-secure environment according to one embodiment.
  • a non-secure environment refers to a logical and/or physical electronic and/or business- process environment in which a business, government or other entity, such as a project requestor described below, may have little or no substantial control over the information, or access thereto, that is being processed and/or stored therein due to a lack of suitable physical, electronic and/or legal safeguards, such as tamper detection mechanisms, security protocols, confidentiality agreements, government provided legal protections, etc.
  • Non- secure environments may include any environment located outside of a particular entity's secure environment, and may include another secure environment coupled therewith via a non-secure medium.
  • non-secure environments include personal computers coupled with the Internet via publicly accessible communications links or otherwise not under the control of an entity which operates a secure environment connected therewith.
  • a company may operate a secure Intranet to which only company employees have access from secure communications links.
  • This Intranet may be further securely coupled with the Internet to provide access thereto while protecting the Intranet from non- employee access.
  • the Internet and any entity connected thereto which is not under suitable control of the company, such as via suitable communications security protocols may be considered a non-secure environment.
  • the system 100 includes a project receiver 108 for receiving a project 102 from a project requestor (not shown), such as an internal or external customer of the operator of the system 100.
  • a project 102 may be a whole or part of a collection of objects provided as documents or electronic images thereof.
  • the documents or document images may be sorted, classified, and/or analyzed to determine a project 102 and/or specific objects included therein using techniques described in U.S. Patent Application Serial Nos. 13/220,387 and 13/220,397, captioned above and which are herein incorporated by reference in their entirety.
  • a project 102 may involve the receipt and identifying of forms or form images.
  • the form images may then be analyzed to determine patterns therein.
  • the patterns may be indicative of elements or character groupings indicative of types of data including confidential data. These elements and/or character groupings may be associated and/or extracted from the forms as secure objects, or collections of secure objects.
  • the system 100 is provided by a service provider (not shown) to requestors who are customers of the service provider.
  • the service provider may charge the customers for use of the system 100 or seek other compensation for the use thereof.
  • the system 100 may be
  • the project receiver 108 is a web site or web service executing on a web server and accessible by users via a network 122 using a web browser program, such as Internet Explorer published by Microsoft Corporation, located in Redmond, Washington. Other browser programs may also be used, such as Firefox, published by the Mozilla Organization.
  • the network 122, as well as networks 124, 126 and 128, may be a secure network, such as an Intranet or Extranet, or may be a non-secure network, such as a publicly accessible network, e.g. the Internet.
  • security protocols such as Secure Sockets Layer, encryption protocols or combinations thereof, may be used.
  • the network 122 may be implemented via a medium that is wired, wireless or a combination thereof.
  • the system 100 may operate with respect to a set of processes and/or procedures for completing workflows and/or certain tasks relating to a project 102.
  • the processes or procedures may be implemented using a BRMS to manage the performance of the project 102.
  • the processes and/or procedures as implemented in the BRMS may relate to customer specific requests or requirements.
  • a BRMS may involve or be considered a collection of rules, related to client or requestor specific operation of the system 100. For example, as described in more detail further below, a customer may request that a workforce having particular attributes, such as a bonded workforce, be used in the performance of a project 102. Jobs, tasks, and/or sub-tasks relating to such a project 102 will then be distributed to participants in a workforce that are associated with that general attribute.
  • the BRMS may also provide procedural guidance to the system 100.
  • the results of two or more tasks may indicate that further tasks may be presented to additional participants for completion of a job 210 and/or project.
  • the tasks may be the same tasks, or different tasks.
  • the same task may be presented to two participants, and if different/inconsistent results are provided by the participants, the task may be provided to a third participant for completion or comparison wherein, for example, the majority result is deemed to be the correct result.
  • a new task could be generated for the third participant to review and arbitrate among the results, and decide which, if any, result is correct.
  • the project receiver 108 allows a requestor to submit a project 102 to the system 100 for processing and subsequently receive the results 214 thereof.
  • a project 102 includes a specification of the task 106 to be performed and at least one object, such as a secure object 104, or specification thereof, on which the specified task 106 is to be performed. It will be appreciated, that a project 102 is a logical construct which includes a task specification 106 and a secure object 104.
  • the task specification 106 may be provided to the system 100, such as via the project receiver 108, independently, both temporally and spatially, of, or in conjunction with, the secure object 104 and that a given task specification 106 may pertain to more than one secure object 104, each of which may be provided to the project receiver 108 along with or independent from the task specification 106.
  • the task specification 106 may be implied based on or inferred from other factors, such as the secure object 104 or other parameters related to the requestor or the system 100.
  • the system 100 may be dedicated to converting handwritten text to computer comprehensible data and therefore the task 106 may be inferred from the dedicated nature of the system 100 to perform such a conversion on any handwritten text provided thereby obviating the need to explicitly specify the task 106.
  • a secure object 104 includes at least a portion thereof which is considered secure, confidential and/or sensitive at least by the requestor.
  • Task specifications 106 also referred to as tasks 106, are the specification, explicit and/or implicit, of actions, e.g. instructions or directions, to be taken with respect to the secure object 104.
  • Tasks 106 include those tasks which a human being is capable of performing and which a computer may be incapable of performing at all or in an effective and/or efficient manner, such as data entry, conversion, translation, verification, transcription, analysis, identification, description, categorization, classification, selection, indexing, correction, adjustment, isolation, relation, quality assessment or assurance, or combinations thereof.
  • Exemplary tasks 106 include: objective tasks, such as transcription, conversion, translation and/or data entry of audible, handwritten or otherwise machine unintelligible information and/or verification of a machine based transcription, conversion and/or translation; or subjective tasks including reviewing, opening on and/or processing of audio, visual, tactile, olfactory, gustatory or other information, such as audio or photo analysis, identification, categorization, classification and/or selection, e.g.
  • tasks 106 may include quality control tasks such as verifying the quality of the performance of one of the tasks 106 described above.
  • the tasks 106 include the task of transcribing handwritten information provided on a form (the secure object 104), such as a name, address or social security number, into computer intelligible data.
  • the task 106 may include verifying a machine translation or transcription, such as verification of the results of an optical character recognition process.
  • the secure object 104 includes the data or information, or a specification thereof, on which the task 106 is to be performed and may include visual, audio or other information or data, in analog or digital form, or combinations thereof. As will be described below, at least some portion of the secure object 104 is considered, e.g. comprehended, at least by the requestor, as secure, confidential or otherwise sensitive, while other portions may not be considered as such. Exemplary secure objects 104 may include one or more data files, facsimile pages, pictures, images, audio recordings, or combinations thereof. In one embodiment, the secure object 104 includes one or more digitally scanned images of handwritten documents and/or hand-filled-in forms, such as a document having pre-printed or otherwise defined regions for the entry of information.
  • the secure object 104 may include digital data representative of the conversion of a handwritten document or hand-filled-in form into a machine intelligible format, such as into a data file generated by optical character recognition for use by a computer program or storage in a database. It will be appreciated that the system 100 may also be utilized with projects 102 involving objects that contain no secure, confidential or sensitive information. Such non-secure objects (not shown) may be processed the same as secure objects 104 as will be described or they may be processed in a different manner.
  • a secure object 104 is further capable of being separated, automatically, manually or a combination thereof, into one or more secure and/or non- secure sub-objects 204, each sub-object including data 208 and a context 206 associated therewith.
  • the context 206 at least characterizes the data 208 as being secure, confidential or sensitive, where this characterization is not otherwise discernable from the data 208 alone.
  • the context 206 may include an attribute associated with the data 208, such as a characteristic of the data 208 or a label, tag or data type associated with the data 208, identification of the source or destination of the data 208, a relationship with other data 208 of another sub-object 204, or a combination thereof.
  • the context 206 may include a label identifying the data 208 as representative of a name, a social security number, a telephone number, credit card number, personal identification number, address or portion thereof, birth date, identity of a relative, etc.
  • Other examples of contexts 206 include the number of numeric digits, such as six digits, which may indicate that the data 208 is a calendar date, ten digits, which may indicate that the data 208 represents a telephone number with area code, nine digits which may indicate that the data 208 represents a social security number, or sixteen digits which may indicate that the data 208 represents a credit card number.
  • the context 206 thereof may imply a calendar date.
  • contexts 206 that identify data as secure, confidential and/or sensitive are separable from the associated data 208 such that such contexts 206 may not be discerned from the data 208 alone, e.g. a user viewing the data 208 would not comprehend the context 206 of that data 208, e.g. that the data 208 represented a social security number for example.
  • a user viewing the data 208 would not comprehend the context 206 of that data 208, e.g. that the data 208 represented a social security number for example.
  • the described hierarchical arrangement/structure of the secure object 104 is for descriptive convenience and may be implementation dependent. Accordingly, any suitable arrangement/structure of the secure object 104 may be utilized with the disclosed system 100.
  • the system 100 is particularly suited to those tasks 106 that are capable of being performed on data 208 without knowledge and/or independent of the context 206 thereof, or at least those tasks 106 that are capable of being performed on data 208 without knowledge and/or independent of a context 206 that characterizes that data 208 as secure, confidential and/or sensitive.
  • the completion of a task 106 of transcribing hand-written social security numbers into computer intelligible data does not require knowledge that the information in fact represents social security numbers but instead merely requires the recognition of the numeric digits and the arrangement thereof.
  • completion of a task 106 transcribing an audio recording of a meeting does not require knowledge of the identities of the speakers or that the transcriber even possess the entire recording.
  • the specified task 106 may be further divided into one or more sub-tasks 202 corresponding to the one or more sub-objects 204, each sub- task 202 being capable of being performed on the context 206 independent data 208 such that the performance of all the sub-tasks 202 is substantially equivalent to the
  • the task 106 may be sub-divided into sub-tasks 202, each of which is to transcribe a portion of the audio recording, i.e. the secure sub-objects 204 consist of portions of the audio recording.
  • the audio recording may be divided into portions based on time, e.g. 5 minute segments, or by speakers, e.g. each speaker is separated out.
  • a job 210 The packaging of a particular sub-task 202, either explicitly or implicitly as will be described, along with one or more of the associated data 208 with respect to which the sub-task 202 is to be performed, and without the context 206 associated therewith, is referred to herein as a job 210.
  • data 208 derived from more than one project 102 and/or secure object 104 may be packaged in a single job 210, such as to improve efficiency where one or more requestors submit more than one similar project 102 or secure object 104 with similar tasks 106 to be performed.
  • a particular field, suitable de- contextualized, such as the zip code field, from all or a subset of the forms may be packaged together as a single job 210 for performance of the transcription task by a single participant. While the disclosed embodiments will be discussed with reference to distributing jobs 210 without the context 206 associated with the data 208 of the job 210, it will be appreciated that where the context 206 does not characterize the data 208 as secure, confidential or otherwise sensitive, the context 206 may be included in the job 210. It will be appreciated that a job 210 is a logical construct which includes a sub-task specification 202 and associated data 208.
  • the sub-task 202 may be provided by the system 100, such as via the distributor 116, independently, both temporally and spatially, of, or in conjunction with, the associated data 208 and that a given sub-task 202 may pertain to more than one associated data 208, each of which may be provided to a participant along with or independent from the sub-task 202.
  • the sub-task 202 may be implied based on or inferred from other factors, such as the associated data 208 or other parameters related to the requestor, the participant, such as their past experience or capabilities, or the system 100.
  • the system 100 may be dedicated to converting handwritten text to computer comprehensible data and therefore the sub-task 202 may be inferred from the dedicated nature of the system 100 to perform such a conversion on any handwritten text provided thereby obviating the need to explicitly specify the sub-task 202.
  • Jobs 210 may further include additional information such as instructions and/or an offer of compensation to whoever elects to perform the sub-task 202.
  • the job 210 may further include a client or server-side executable computer program, such as an applet or other locally offline or on-line executable program, which facilitates performance of the sub-task 202 on the data 208, such a viewer/data entry program and/or interface.
  • a job 210 may merely include one or more references, such as a secure or unsecure hypertext link or other network reference, to the sub-task 202 and/or data 208 where the sub-task 202 and/or data 208 are available via the referenced location, such as via a website.
  • the referenced location may permit the downloading of the sub-task 202 and/or data 208 so that the sub-task 202 may be performed locally by the participant or the referenced location may provide an execution/application environment in which the participant performs the sub-task 202 on the data 208, such as an on-line application environment, or a combination thereof.
  • the system 100 distributes the job(s) 210 to, or via, a non-secure environment to a workforce (not shown) where the particular sub-tasks 202 will be performed with respect to the associated data 208.
  • the results thereof are referred to as the job results 212, job fragments or fragments, and may include non-performance of the sub-task 202 or other information, such as where the participant is unable to perform the sub-task 202, e.g. due to a system error such as incomplete or unintelligible data 208, or refuses, forgets or otherwise fails to perform the sub-task 202, e.g. within a prescribed time period.
  • the job results 212 of each distributed job 210 are returned to the system 100 subsequent to completion (or the lack thereof).
  • Job results 212 representative of an incomplete or incorrect completion of the sub-task 202 may be re-distributed for successful completion to the same or a different participant.
  • the workforce refers to the participating human actors, a.k.a. participants, who will complete the sub-tasks 202 of the jobs 210.
  • the workforce participants may include employees of the requestor, employees of the operator of the system 100, independent contractors, ad hoc employees, volunteers or combinations thereof.
  • Workforce participants may participate by accessing the system 100 via a network 126, 128, such as via the Internet, to obtain or "pull" jobs 210, jobs 210 may be "pushed" by the system to workforce participants, or a combination thereof, and to return the job results 212.
  • the various workforce participants may have varying skills sets or other attributes, such as availability, cost, quality of work product, or other individual or collective characteristics, or combinations thereof, etc.
  • a group or subset of the workforce may be associated with an attribute indicating that the participants of the subset are bonded or insured or that the subgroup is an unverified crowd or group of participants.
  • attributes may be evaluated and/or tracked by the system 100 and utilized to selectively match jobs 210 with workforce participants.
  • workforce participants may be located in, or communicate with the system 100 via, a non-secure environment.
  • Participant attributes may be used to determine, group or otherwise associate participants into one or more overlapping or non-overlapping subsets of the workforce. It will be appreciated that at least one of the subsets may be the entire set of participants. The subsets may be determined such that the participants in the subset may have particular associated attributes that particularly qualify the participants in the subset to perform the jobs 210. As such, jobs 210 may be assigned specifically to a participant in a subset of the workforce based on the attributes determined for inclusion in the subset of the workforce. For example, subsets of participants may be determined based on employment status, a type or qualification for particular jobs 210, or a status of a participant with regard to a level of clearance available for access to various levels of confidential data.
  • an employment status may involve an attribute indicating that the participant is an employee of an entity from which the secure object 104 is received, an employee of an entity which receives the secure object 104, an independent contractor, an ad hoc employee, a volunteer, or a combination thereof.
  • specific training may be provided for specific types or categories jobs 210 and a participant attribute may indicate whether a participant has undergone adequate or necessary training for a particular job 210 or job type.
  • Job types may involve any characterization of the job 210.
  • a job 210 may be characterized by an amount of projected effort to complete, time to complete, an amount of complexity in completion, required proficiency, or any combination of these.
  • a job 210 may be considered simple or complex.
  • participants in a subset of a workforce may have attributes associated that indicate that the participants are qualified for simple tasks, complex tasks, or both.
  • a subset of a workforce may be a large general pool of participants that is associated with an attribute indicating the pool may perform simple jobs, whereas a different subset may be associated with an attribute that indicates that the different subset may perform complex tasks.
  • a subset may also be associated with attributes indicating particular entities generating jobs 210, or secure objects 102, for which the subset may perform jobs.
  • the project receiver 108 is further coupled with an object separator 110 and a task divider 114.
  • the phrase "coupled with” is defined to mean directly connected to or indirectly connected through one or more intermediate components. Such intermediate components may include both hardware and software based components.
  • the project receiver 108 separates the received project 102 into the task 106 or the specification thereof, and the secure object 104 with respect to which the task 106 is to be performed. Where the task 106 is separately provided, implied or inferred, such as in advance with another secure object 104, the project receiver 108 obtains or otherwise identifies the task 106 associated with the secure object 104.
  • the project receiver 108 may store or otherwise buffer the task 106 or secure object 104 until the other is received.
  • the task 106 is provided/communicated to the task divider 1 14 and the secure object 104 is provided/communicated to the object separator 110.
  • the object separator is further coupled with an object disassociator 112.
  • the object disassociator 112 and task divider 114 are both coupled with a distributor 116.
  • the system 100 further includes a results receiver 118 and a compiler 120 coupled with the results receiver 118.
  • the object separator 110 receives the secure object 104 and divides it into one or more secure sub-objects 204, each including data 208 and a context 206 associated therewith, as was described above.
  • the secure object 104 includes a digital representation, such as a scan, of a form document having predefined fields for the entry of handwritten information
  • the object separator 110 may utilize a template or overlay which identifies the various regions of the document associated with the form fields allowing each region, i.e. each field, to be identified and separated out.
  • the template or overlay may be defined using Extensible Markup Language (“XML”) or other suitable methodology.
  • Each of the secure sub-objects 204 is then provided to the object disassociator 112 which disassociates the data 208 from the context 206, such as by separating the label or tag from the data 208 which it describes, or by modifying the data 208, e.g. decomposing it into smaller portions, so as to obfuscate any attributes thereof, or combinations thereof.
  • the disassociated context 206 may be stored (not shown) for later use, such as when the job results 212 are returned for the particular sub- task 202 performed on the associated data 208.
  • the disassociated data 208 is then provided to the distributor 116 as will be described.
  • the object separator 110 and object disassociator 112 may be combined and perform the separation of the secure object 104 into one or more secure sub-objects 204 and the
  • the disassociation of the data 208 from its associated context 206 may be an automated process wherein the object disassociator 112 identifies the data 208 and the context 206, such as by utilizing a template or overlay, pattern recognition, programmed identification methodology, such as an XML specification, or other automated mechanism.
  • the disassociation of the data 208 from its associated context 206 may be a manual process wherein the object disassociator 112 receives a specification separately identifying the data 208 and context 206, from the requestor and/or from the operator of the system 100.
  • the disassociation of the data 208 from its associated context 206 may be a combination of a manual and automated process wherein the object disassociator 112 receives a specification identifying the data 208 and context 206, from the requestor and/or from the operator of the system 100, such that the context 206 may be automatically disassociated from the data 208 by the object disassociator 112.
  • the task divider 114 receives the specified, implied or inferred task 106 and divides the task 106 into sub-tasks 202, each of which may be performed with respect to the disassociated data 208 of each secure sub-object 204.
  • the task divider 114 generates the sub-tasks 202 such that the compiled results of the performance of all of the sub-tasks 202 substantially approximates the result that would be achieved if the task 106 were to be performed on the secure object 104.
  • each sub-task 202 is substantially the same as the task 106, wherein the data with respect to which each sub- task 202 is to be performed varies.
  • each sub-task 202 may be to similarly transcribe a portion thereof, e.g. one sub-task 202 may be to transcribe the first half of each social security number while another sub-task 202 is transcribe the remaining portion.
  • different sub- tasks 202 may need to be performed on different data 208 to achieve substantially the same results as the performance of the task 106 on the secure object 104.
  • the task divider 114 may also determine characteristics or attributes of the task 106 or sub-tasks 202 or otherwise determine characteristics or attributes of the participants recommended or necessary for performance of the task 106.
  • the task divider 114 may determine that a task 106 or sub-task 202 is simple in nature or otherwise may be performed by a participant having a lower skill/proficiency level or less experience than other participants.
  • the sub-tasks 202 are provided/communicated to the distributor 116.
  • the distributer may further distribute tasks 106 or sub-tasks 202 based on the task characteristics.
  • the task divider 114 automatically divides the task 106 in to sub-tasks 202, such as based on the secure sub-objects 204 and/or the disassociated data 208.
  • the division of tasks 106 into sub-tasks 202 may be a manual, or a combination of a manual and automated, process whereby the requestor and/or the system 100 operator provide a specification to the task divider 114, such as within the task 106 itself, specifying the division of the task 106 into sub-tasks 202. It will be appreciated that in systems 100 where the task 106 and sub-tasks 202 may be implied or inferred throughout, such as in system 100 which is dedicated to single task 106 or sub-task 202, the functionality of the task divider may also be implied or inferred rather than explicitly provided for.
  • the distributor 116 receives the disassociated data 208 and the sub-tasks 202 associated therewith if specified, generates one or more jobs 210 based thereon and arranges, automatically, manually or a combination thereof, to have the jobs 210 performed/completed, such as by one or more available participants of the workforce, defined above.
  • Each job 210 may include a sub-task 202, where explicitly specified, plus the disassociated data 208 with respect to which the sub-task 202 is to be performed.
  • the jobs 210 are then distributed to a workforce to be completed.
  • the distributor 116 distributes jobs 210 based on task or job attributes, or otherwise based on the determined recommended or requisite participant attributes, such as complexity.
  • simple jobs may be distributed to a dedicated subset of participants in a workforce associated with attributes indicating the subset may work on simple job types.
  • This subset of participants may only be assigned simple jobs, or the subset of participants may also be assigned jobs based on other associated attributes.
  • job attributes may be matched with participant attributes to distribute jobs.
  • a job may be associated with a simple complexity attribute and may be distributed to a participant associated with a participant attribute that indicates that the participant works on simple complexity jobs.
  • a subset of the workforce is dedicated to working on simple complexity jobs, tasks, and/or sub-tasks. Alternatively, or in addition thereto, multiple jobs and/or tasks may be related by an attribute.
  • the attribute may indicate that multiple jobs and/or tasks are related to a singular type of information from an object, such as an address.
  • a participant attribute may indicate that a participant may perform jobs and/or tasks relating to an information type. For example, a single participant may be provided multiple jobs and/or tasks relating to address data of an object.
  • a system 100 may involve a data structure which stores participant attributes and permits job attributes to be correlated therewith to determine participants to which the task will be distributed.
  • the data structure may be composed of a matrix of job and participant attributes providing associations there between and aligning participant attributes with job attributes to facilitate selection of suitable participants for a given job. Such a matrix may be utilized to identify suitable jobs for a given participant and/or suitable participants for a give job.
  • the distributor 116 includes a network 126, e.g. Internet, accessible web site which users may access using a personal computer and web browser program.
  • the web site may permit the user to take and/or accept (a.k.a. "pull") one or more jobs 210.
  • the distributor 116 may be in communication with a standing workforce, e.g. users or employees that have volunteered or have been hired or otherwise engaged to be available to accept and complete jobs 210.
  • the distributor 116 may send jobs 210 to selected users to be completed (a.k.a. "push").
  • the distributor 116 maybe in communication with a commercial job 210 distribution system, such as the Mturk system made available by Amazon.com, where jobs 210 are communicated to be ultimately disseminated to users for completion. Jobs 210 may be distributed and/or queued for distribution on a priority or other basis, such as first-in-first-out. Further, the distributor may limit the presentation of available jobs 210 and/or couple incentives with higher priority jobs 210 to ensure the priority distribution thereof. As was described above, each job 210 contains data 208 that has been disassociated with its context 206.
  • the distributor 116 may further implement additional security protocols, such as a protocol to prevent a particular user from performing multiple jobs 210 generated from the same project 102 on the chance that the context 206 of the data 208 of one job 201 may be discernable from the collective jobs 210 the user is performing. Further aspects and alternatives to the distributor 116 will be discussed below.
  • the results receiver 118 may include a network 128, e.g. Internet, accessible web site which a user accesses to submit the results of a job 210.
  • the results receiver 118 may be any suitable interface for receiving the job results 212 of a given job 210 and may be a part of the distributor 116.
  • the distributor 116 and results receiver 118 are combined into a web site to which a user accesses to obtain a job 210, perform the sub-task 202 therein on and/or off-line with the web site and provide the results 212 thereof.
  • the contents of the job results 212 are dependent upon the implementation of the system 100 but will generally include the resultant work product of the performance of the sub-task 202 on the disassociated data 208.
  • the job results 212 may a digital data file containing machine intelligible data. Where the participant is unable or incapable of performing the sub-task 202, the lack of performance and any underlying reasons therefore may be provided as job results 212.
  • the received job results 212 are provided/communicated to the compiler 120 which assembles the job results 212 for all of jobs 210 generated from a given project 102, automatically, manually or a combinations thereof, into the overall task results 214.
  • the results receiver 118 and/or compiler 120 may further evaluate the job results 212 prior to assembly, such as to detect any errors or otherwise perform quality control checking. For example, in one embodiment, each job 210 may be distributed to more than one participant, where the job results 212 of each performance are compared to ensure accuracy, etc. Alternatively, test jobs 210, where the correct job results 212 are already known to the system 100 may be utilized to ensure quality. Where the evaluation reveals unacceptable job results 212 or the indication of non-performance of the sub-task 202, the results receiver 118 and/or compiler 120 may be in communication with the distributor 116, or otherwise arrange to redistribute the particular job 210 to the same or a different participant to be performed again.
  • a job 210 may be distributed to more than one participant and the results compared for accuracy or quality assessment. Where results differ between participants completing a job 210, the job 210 may be further distributed to other participants for completion.
  • the other participant, or participants may be of a same subset as the participants to whom the job 210 was originally distributed. In another embodiment, the other participant may be of a different subset as the participants to whom the job 210 was originally distributed.
  • the different subset may be a subset having participants with different attributes, such as employment status or confidentiality access rating.
  • the different subset may have participants with attributes indicating that they are able to perform jobs 210 requiring a higher confidentiality rating.
  • the other participant having attributes indicating a higher confidentiality rating may be provided more information for a job 210, than was provided in a task or sub-task provided to the original participants having differing results.
  • the original participants may have data indicating three characters or digits of an entered social security number, whereas the other participant may have data indicating more characters or digits of the social security number.
  • original participants may be provided data that has been separated from confidential contexts as indicated herein. The original participant may not be able to complete a task based on such separated data. In this instance, another participant may be provided more data to complete the task.
  • the other participant may have an associated attribute that indicates that the participant may view confidential data, and as such may be considered a secure participant.
  • the other participant may then be provided the task with data that has not been separated from confidential context.
  • Such techniques may provide more data for better determination of results.
  • Further processing of jobs or tasks may also involve distributing results of a particular job or task as performed by one or more participants to a different participant for review and comparison.
  • the different participant may have differ associated participant attributes, or belong to a different subset of the workforce than the original participants.
  • multiple participants are provided tasks as well as data related thereto, and a correct result may be considered a result that was provided by the largest number of participants. Also, if results provided from multiple participants are not determinative of whether the result is correct, the data for a task may be provided to more participants.
  • Errors in results of jobs 210 or tasks may be determined in other ways.
  • a results receiver 118 and/or compiler 120 may be configured to validate results of jobs or tasks performed by one or more participants by comparing the results with a repository of known or valid results for the job or task. When a result is determined not to match results from the repository, a result may be determined to be incorrect.
  • a different participant may be provided the job or task to ascertain an answer from the repository that is suitable for the job or task.
  • the different participant may have different associated attributes, or belong to a different subset of participants, than the participant that originally performed the job or task.
  • Further processing of a job or task as indicated above may be considered a new job or task, or as a sub-task of the original job or task.
  • Results provided by participants may provide further information that may be used for a determination of additional or fewer tasks to be performed to complete a job 210.
  • a task of a job 210 may be distributed to participants wherein the result of the task will determine whether future tasks are to be determined for the job as well as what those future tasks may be.
  • a task may be distributed that involves categorizing a job, or an object or document upon which a job 210 is based. Such categorization may involve determining a completion level or status for the object.
  • a task may involve determining an existence of a signature for a document.
  • this task determines that the document does not include a necessary signature
  • the document is categorized or characterized as incomplete or not in good order, and future tasks for the job 210 are not determined, generated, and/or distributed.
  • accuracy or quality results for a job, task, and/or sub-task may further characterize the job 210, or provide for further processing of jobs as described above.
  • results may also indicate that more jobs, tasks, and/or sub-tasks should be generated. For example, as indicated above, provided results may be considered incorrect and a new the job, task, and/or sub-task is generated to determine a correct result.
  • jobs, tasks, and/or sub-tasks may involve result dependencies for generation.
  • a result or a combination of results may indicate a birthday.
  • the birthday indicates that a subject of the birthday is currently younger than a certain age
  • jobs, tasks, and/or sub- tasks may be generated to determine data relating to a caretaker or responsible adult for the underage subject. This data may be provided by the object from which the original task was generated from, or other related or non- related objects.
  • Characterizing or categorizing results of jobs 210 from participants may also allow for grouping of other object processing steps. Groups of objects having similar or consistent information may be determined based on results. Subsequent processing steps, and jobs 210 generated for their completion, may be performed based on the groupings of objects.
  • the system 100 may receive multiple jobs 210 at the project receiver that relate to multiple objects.
  • the multiple objects may be pages of multiple documents provided to the system 100 in bulk with no grouping information.
  • the system may group pages determined to contain consistent or similar data into object groups or documents.
  • the documents grouped from individual pages may then be treated as such for additional document processing steps to be performed before, during, or after the object processing by the system 100.
  • the task results 214 may also be provided to the original requestor who requested completion of the particular project 102.
  • the compiler 120 may include a network 124, e.g. Internet, accessible web site which a project requestor accesses to receive their task results 214.
  • the compiler 120 may be a part of the project receiver 108 creating unified interface for receiving project 102 submissions and providing the results 214 therefrom.
  • system 100 may be implemented in hardware, software or a combination thereof, and that one or more of the components thereof may be combined or, alternatively, sub-divided into other functional units, to implement the described functionality. Further, the system 100 may include other components which are not shown.
  • the described functionality is implemented in computer program logic stored in a memory device, such as a computer memory or computer storage device, and executable by one or more processors to implement the described functionality.
  • the described functionality may be implemented on a web server as one or more network accessible web pages coupled with suitable back-end logic.
  • Figure 3 depicts a flow chart showing exemplary operation of the system 100 of Figure 1 for completing a task 106 in a non-secure environment with respect to a secure object 104.
  • the secure object 104 may comprise computer incomprehensible information, the task 106 comprising converting the computer incomprehensible information into computer comprehensible information.
  • the secure object 104 may comprise a representation of a handwriting, a picture, an image, a facsimile, a document, an audio recording, a video recording, or combinations thereof.
  • exemplary tasks 106 may include data entry, conversion, translation, verification, transcription, analysis, identification, description, indexing, categorization, classification, selection, separation, isolation, recognition, sorting, correction, relation, opening, assessment, judgment or combinations thereof.
  • the operation of the system 100 includes: receiving, in a secure environment, a specification of the task 106 and the secure object 104 with respect to which the task 106 is to be performed (block 302); dividing the secure object 104 into at least one or more secure sub-objects 204 each comprising data 208 and a context 206 associated therewith, the context 206 characterizing the data 208 as secure (block 304); and disassociating each data 208 of the one or more sub-objects 204 from the associated context 206, the secure characterization of the data 208 being substantially non-discernable from the disassociated data 208 (block 306).
  • the context 206 comprises an attribute of the associated data 208 and the disassociating further comprises separating the attribute from the data 208.
  • the attribute may include a characteristic of the data 208, a label associated with the data 208, a tag associated with the data 208, a type associated with the data 208, a source of the data 208, a destination of the data 208, the data 208 of another secure sub object 204 or a combination thereof.
  • the attribute may include a number of alphanumeric digits in the data 208 wherein the disassociating further comprises dividing the data 208 into at least two disassociated data, each of the at least two disassociated data 208 comprising a sub-set of the number of alphanumeric digits such that the number of alphanumeric digits in the data 208 cannot be discerned from each sub-set alone. Further, subsets may be overlapping. In an embodiment, the disassociated data 208 comprise sub-sets of a number of
  • alphanumeric digits that contain overlapping digits.
  • a sub-set of a social security number which typically involves eight alphanumeric digits may involve two subsets, the first sub-set having the first five alphanumeric digits of the number and the second sub-set having the last five alphanumeric digits of the number.
  • This particular example indicates that a single alphanumeric digit will be included in both sub-sets, and thus the sub-sets will include overlapping data.
  • overlapping sub-zones of received data may be determined which may contain some common data. Data contained in each sub-zone may define the data of each subset. For example, a hand written number may exist in an object 204.
  • Sub-zones of an object area established for the hand written number may be established and together contain the entirety of the hand written number. Therefore, some of the data in the overlapping areas of the sub-zones may be provided in multiple subsets of data. This may provide for redundancy and improve accuracy in the completion of the task.
  • the operation of the system 100 further includes: dividing the task 106 into one or more sub-tasks 202 to be performed with respect to the disassociated data 208 of each of the one or more secure sub-objects 204 (block 308); and distributing to the nonsecure environment at least one of the disassociated data 208 and a specification of the respective sub-task 202 to be performed with respect thereto, such that the ability to discern the secure characterization of the data 208 in the non-secure environment is substantially reduced (block 310).
  • the distributing may include arranging for the performance of the sub-task with respect to at least one of the disassociated data with an available participant of a workforce, the available participant being unaware of the secure characterization of the data distributing the at least one of the disassociated data and a specification of the respective sub-task to be performed with respect thereto to the available participant.
  • the operation of the system 100 further includes: receiving the results 212 of the performance of each sub-task 202 (block 312); and compiling the results, the compilation 214 being substantially similar to a result of the completion of the task on the secure object 104 (block 314).
  • project management functionality may be provided which allows a requestor to manage the completion of one or more projects 102 by the system 100.
  • Such functionality includes capabilities to specify a project 102 submission, such as to specify the task 106 to be performed and the secure object 104 with respect to which the task 106 is to be performed, the completion deadline, escalation, priority handling, the skills required or desired of participants, etc.
  • Escalation relates to the actions to be taken if a suitable participant cannot be located to handle the jobs 210 within a designated time period.
  • the requestor may allow the jobs 210 to be distributed to a general population of participants if the results can be returned within a defined time limit.
  • the jobs 210 should be distributed to a selectively chosen population, such as the requestor's own employees, who are likely to complete the jobs 210 in the desired time frame.
  • Priority handling relates to the order in which the jobs 210 are distributed and may control the queue order of the jobs 210 for distribution and/or the incentive, such as the compensation level, offered for completion of the jobs 210. Thereby, higher priority jobs 210 may be handled more quickly.
  • the interface may permit the requestor to designate how the task 106 and/or secure object 104 will be divided into sub-tasks 202 and sub-objects 204, e.g. by providing a template, etc., such as to ensure the protection of the underlying secure information.
  • a user interface may be provided, such as a world wide web page based interface, which permits a requestor to specify and submit a particular project 102, such as by uploading the secure object 104.
  • the interface may further permit specification of the types of workers, e.g. the skill sets necessary, to complete the task 106, the expected results and/or the compensation that may be offered for such completion.
  • the interface is an application program interface which permits a requestor's workflow management systems to directly interface with the system 100, submit projects 102 for completion and receive the results 214 thereof.
  • the interface may further permit monitoring and tracking of the progress of completion of the project 102, such as by reporting the job results 212 received for a given project 102.
  • the interface may provide an account management function permitting a requestor to view the status of their account, such as how much they presently owe the operator of the system 100 for services rendered.
  • the interface may also permit the reporting of errors or problems and/or the selection of optional services such as quality control services.
  • a requestor may request double-blind keying of data where multiple duplicate jobs 210 are distributed and the results thereof compared to ensure the quality of the task results 214.
  • one or more jobs 210 may include the task 202 of validating the results 212 of another job 210.
  • Job 210 management functionality may further be provided to manage the distribution of jobs 210 to a workforce, or otherwise arrange for one or more workforce participants to complete the jobs 210, and the receipt of the job results 212 therefrom.
  • Such functionality may include tracking, auditing and or quality control functions to ensure that all of the jobs 210 are completed in a satisfactory and timely manner.
  • the distributor 116 may pull the job 210 back or otherwise cancel the job 210 and redistribute the job 210 to another worker for completion.
  • selective job 210 distribution is implemented whereby the distributor 116 tracks the capabilities and/or qualifications, such as the skill sets, of the various workforce participants and distributes jobs 210 to those participants based on a correlation between specified requirements of the jobs 210 and the capabilities/qualifications of the participants.
  • the distributor 116 may be aware of which participants are fluent in the French language and thereby, distribute tasks 202 involving translation of the French language only to those participants that are qualified.
  • functionality may be provided to allow participants to specify their capabilities or qualifications, or otherwise measure or improve these capabilities or qualifications, such as by tests, e.g. test jobs 210 where the job results 210 are known to the system 100 in advance and may be compared with the actual job results 210, or training.
  • the distributor 116 offers compensation for satisfactory completion of jobs 210 so as to incentivise workforce participants to take on jobs 210.
  • the distributor 116 may implement a "Dutch" auction or other compensation mechanism to incentivise participation.
  • Other mechanisms of job 210 distribution which may be implemented include subscription based systems whereby workforce participants subscribe to be notified when jobs 210 are available, or alternatively, to have available jobs 210 pushed to them automatically.
  • system 100 may merely act as a broker between the requestors and the workforce participants.
  • the system 100 may offer compensation itself, recouping such expenses via the fees charged to requestors.
  • workforce participants may be compensated via any available compensation mechanism, such as cash, check, direct deposit or PayPal.
  • the system 100 may be aware of employment, tax and other regulatory requirements of the jurisdictions in which the system 100 operates and in which the workforce
  • participant perform the jobs 210.
  • Such requirements may be considered in the manner in which participants are compensated as well as the nature of that compensation.
  • the system 100 may withhold suitable income taxes on behalf of a jurisdiction.
  • certain non-monetary benefits such as health or worker
  • compensation insurance may be provided in lien of monetary compensation in
  • Workforce management functionality may also be provided to manage the workforce participants available for the performance of jobs 210.
  • Such functionality may include interfaces, such as world wide web based interfaces, allowing individuals to elect, enroll or otherwise sign up to participate, withdraw from participation, receive training on how to participate or perform tasks 202, review ratings or reviews of their performance, review ratings/raking of their performance relative to other workforce participants, obtain jobs 210, or notification thereof, to perform, submit job results 212, receive and/or monitor earned compensation, or combinations thereof
  • enrollment may require the participant to pass a test, such as a test job 210, in order to demonstrate their qualifications or capabilities to participate. Such testing may occur on a one-time or recurring basis.
  • the computer system 400 can include a set of instructions that can be executed to cause the computer system 400 to perform any one or more of the methods or computer based functions disclosed herein.
  • the computer system 400 may operate as a standalone device or may be connected, e.g., using a network, to other computer systems or peripheral devices. Any of the components discussed above, including, but not limited to the project receiver 108, the object separator 110, the object disassociator 112, the task divider 114, the distributor 116, the results receiver 118 and/or the compiler 120 may be a computer system 400 or a component in the computer system 400.
  • the computer system 400 may operate in the capacity of a server or as a client user computer in a client-server user network
  • the computer system 400 can also be implemented as or incorporated into various devices, such as a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a mobile device, a palmtop computer, a laptop computer, a desktop computer, a communications device, a wireless telephone, a land-line telephone, a control system, a camera, a scanner, a facsimile machine, a printer, a pager, a personal trusted device, a web appliance, a network router, switch or bridge, or any other machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • PC personal computer
  • PDA personal digital assistant
  • the computer system 400 can be implemented using electronic devices that provide voice, video or data communication. Further, while a single computer system 400 is illustrated, the term "system” shall also be taken to include any collection of systems or sub-systems that individually or jointly execute a set, or multiple sets, of instructions to perform one or more computer functions.
  • the computer system 400 may include a processor 402, e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both.
  • the processor 402 may be a component in a variety of systems. For example, the processor 402 may be part of a standard personal computer or a workstation.
  • the processor 402 may be one or more general processors, digital signal processors, application specific integrated circuits, field programmable gate arrays, servers, networks, digital circuits, analog circuits, combinations thereof, or other now known or later developed devices for analyzing and processing data.
  • the processor 402 may implement a software program, such as code generated manually (i.e., programmed).
  • the computer system 400 may include a memory 404 that can communicate via a bus 408.
  • the memory 404 may be a main memory, a static memory, or a dynamic memory.
  • the memory 404 may include, but is not limited to computer readable storage media such as various types of volatile and non-volatile storage media, including but not limited to random access memory, read-only memory, programmable read-only memory, electrically programmable read-only memory, electrically erasable read-only memory, flash memory, magnetic tape or disk, optical media and the like.
  • the memory 404 includes a cache or random access memory for the processor 402.
  • the memory 404 is separate from the processor 402, such as a cache memory of a processor, the system memory, or other memory.
  • the memory 404 may be an external storage device or database for storing data. Examples include a hard drive, compact disc (“CD”), digital video disc (“DVD”), memory card, memory stick, floppy disc, universal serial bus (“USB”) memory device, or any other device operative to store data.
  • the memory 404 is operable to store instructions executable by the processor 402.
  • the functions, acts or tasks illustrated in the figures or described herein may be performed by the programmed processor 402 executing the instructions stored in the memory 404.
  • the functions, acts or tasks are independent of the particular type of instructions set, storage media, processor or processing strategy and may be performed by software, hardware, integrated circuits, firm-ware, micro-code and the like, operating alone or in combination.
  • processing strategies may include multiprocessing, multitasking, parallel processing and the like.
  • the computer system 400 may further include a display unit 414, such as a liquid crystal display (LCD), an organic light emitting diode (OLED), a flat panel display, a solid state display, a cathode ray tube (CRT), a projector, a printer or other now known or later developed display device for outputting determined
  • the display 414 may act as an interface for the user to see the functioning of the processor 402, or specifically as an interface with the software stored in the memory 404 or in the drive unit 406.
  • the computer system 400 may include an input device 416 configured to allow a user to interact with any of the components of system 400.
  • the input device 416 may be a number pad, a keyboard, or a cursor control device, such as a mouse, or a joystick, touch screen display, remote control or any other device operative to interact with the system 400.
  • the computer system 400 may also include a disk or optical drive unit 406.
  • the disk drive unit 406 may include a computer-readable medium 410 in which one or more sets of instructions 412, e.g.
  • the instructions 412 may embody one or more of the methods or logic as described herein.
  • the instructions 412 may reside completely, or at least partially, within the memory 404 and/or within the processor 402 during execution by the computer system 400.
  • the memory 404 and the processor 402 also may include computer-readable media as discussed above.
  • the present disclosure contemplates a computer-readable medium that includes instructions 412 or receives and executes instructions 412 responsive to a propagated signal, so that a device connected to a network 420 can communicate voice, video, audio, images or any other data over the network 420. Further, the instructions 412 may be transmitted or received over the network 420 via a communication port 918.
  • the communication port 418 may be a part of the processor 402 or may be a separate component.
  • the communication port 418 may be created in software or may be a physical connection in hardware.
  • the communication port 418 is configured to connect with a network 420, external media, the display 414, or any other components in system 400, or combinations thereof.
  • the connection with the network 420 may be a physical connection, such as a wired Ethernet connection or may be established wirelessly as discussed below.
  • the additional connections with other components of the system 900 may be physical connections or may be established wirelessly.
  • the network 420 may include wired networks, wireless networks, or combinations thereof, and may be representative of the network 122, 124, 126, 128 in Figure 1.
  • the wireless network may be a cellular telephone network, an 802.11, 802.16, 802.20, or WiMax network.
  • the network 420 may be a public network, such as the Internet, a private network, such as an intranet, or combinations thereof, and may utilize a variety of networking protocols now available or later developed including, but not limited to TCP/IP based networking protocols.
  • computer-readable medium includes a single medium or multiple media, such as a centralized or distributed database, and/or associated caches and servers that store one or more sets of instructions.
  • computer-readable medium shall also include any medium that is capable of storing, encoding or carrying a set of instructions for execution by a processor or that cause a computer system to perform any one or more of the methods or operations disclosed herein.
  • the computer-readable medium can include a solid-state memory such as a memory card or other package that houses one or more non-volatile read-only memories. Further, the computer-readable medium can be a random access memory or other volatile re- writable memory.
  • the computer-readable medium can include a magneto-optical or optical medium, such as a disk or tapes or other storage device to capture carrier wave signals such as a signal communicated over a transmission medium.
  • a digital file attachment to an e-mail or other self-contained information archive or set of archives may be considered a distribution medium that is a tangible storage medium. Accordingly, the disclosure is considered to include any one or more of a computer-readable medium or a distribution medium and other equivalents and successor media, in which data or instructions may be stored.
  • dedicated hardware implementations such as application specific integrated circuits, programmable logic arrays and other hardware devices, can be constructed to implement one or more of the methods described herein.
  • Applications that may include the apparatus and systems of various embodiments can broadly include a variety of electronic and computer systems.
  • One or more embodiments described herein may implement functions using two or more specific interconnected hardware modules or devices with related control and data signals that can be
  • the present system encompasses software, firmware, and hardware implementations.
  • the methods described herein may be implemented by software programs executable by a computer system.
  • implementations can include distributed processing, component/object distributed processing, and parallel processing.
  • virtual computer system processing can be constructed to implement one or more of the methods or functionality as described herein.
  • invention merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept.
  • inventive concept merely for convenience and without intending to voluntarily limit the scope of this application to any particular invention or inventive concept.
  • specific embodiments have been illustrated and described herein, it should be appreciated that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown.
  • This disclosure is intended to cover any and all subsequent adaptations or variations of various embodiments. Combinations of the above

Abstract

Procédé d'établissement de sources et système de gestion de travail protégés pour traiter des informations protégées dans un environnement non protégé. Le système permet à un utilisateur, désigné ici comme client ou demandeur, de soumettre un projet impliquant une tâche d'intelligence humaine ("HIT"), désignée comme tâche ou spécification de tâches, qui doit être effectuée par rapport à des informations protégées, sensibles ou confidentielles, désignées ici comme informations protégées, et mener à bien le projet dans un environnement non protégé sans affecter la sécurité, la confidentialité ou la sensibilité des informations protégées. Le système peut être intégré au flux de travail du demandeur, en recevoir des projets et lui fournir des résultats. En outre, l'invention concerne un système de mise en oeuvre d'un flux de travail de traitement pour ces tâches, le système permettant d'effectuer, sur la base des projets soumis par demandeurs, la "publication" ou la répartition des tâches puis une gestion de celles-ci, par un effectif fonctionnant dans ou via un environnement non protégé, tout en protégeant la sécurité, la confidentialité ou la sensibilité sous-jacentes du projet global.
PCT/US2015/035940 2014-06-16 2015-06-16 Traitement protégé d'informations protégées dans un environnement non protégé WO2016032596A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US14/305,245 2014-06-16
US14/305,245 US20140298409A1 (en) 2006-12-20 2014-06-16 Secure Processing of Secure Information in a Non-Secure Environment

Publications (2)

Publication Number Publication Date
WO2016032596A2 true WO2016032596A2 (fr) 2016-03-03
WO2016032596A3 WO2016032596A3 (fr) 2016-05-12

Family

ID=55400796

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/035940 WO2016032596A2 (fr) 2014-06-16 2015-06-16 Traitement protégé d'informations protégées dans un environnement non protégé

Country Status (1)

Country Link
WO (1) WO2016032596A2 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8793756B2 (en) * 2006-12-20 2014-07-29 Dst Technologies, Inc. Secure processing of secure information in a non-secure environment
US20120053992A1 (en) * 2010-08-30 2012-03-01 Ricoh Company, Ltd. Techniques for pricing a task
US20120054112A1 (en) * 2010-08-30 2012-03-01 Ricoh Company, Ltd. Techniques for creating microtasks for content privacy preservation

Also Published As

Publication number Publication date
WO2016032596A3 (fr) 2016-05-12

Similar Documents

Publication Publication Date Title
US8793756B2 (en) Secure processing of secure information in a non-secure environment
US10586072B2 (en) Data processing systems for measuring privacy maturity within an organization
US10567439B2 (en) Data processing systems and methods for performing privacy assessments and monitoring of new versions of computer code for privacy compliance
US11025675B2 (en) Data processing systems and methods for performing privacy assessments and monitoring of new versions of computer code for privacy compliance
US20140298409A1 (en) Secure Processing of Secure Information in a Non-Secure Environment
Cascarino Auditor's Guide to IT Auditing,+ Software Demo
Li et al. Towards privacy compliance: A design science study in a small organization
US20200257784A1 (en) Data processing and scanning systems for assessing vendor risk
US11416589B2 (en) Data processing and scanning systems for assessing vendor risk
Badawy Data-driven framework for evaluating digitization and artificial intelligence risk: a comprehensive analysis
Li Implementation of Anti-Money Laundering Information Systems
Plant DevOps under control: development of a framework for achieving internal control and effectively managing risks in a DevOps environment
WO2016032596A2 (fr) Traitement protégé d'informations protégées dans un environnement non protégé
Kern Dynamic quality management for cloud labor services: methods and applications for gaining reliable work results with an on-demand workforce
Chapple et al. (ISC) 2 CCSP Certified Cloud Security Professional Official Study Guide
POLICY Open Data
Steinberg Official (ISC) 2 Guide to the CISSP-ISSMP CBK
Abbasi GDPR implementation in an airline contact center
Tisdale Architecting a cybersecurity management framework: Navigating and traversing complexity, ambiguity, and agility
US20220036389A1 (en) Privacy management systems and methods
Laksana Machine Learning Design on Human Resource System
Jung Transforming Vulnerabilities into Context-Aware, Visible Risks
Xavier Clearing the Cloudiness of SaaS: A SaaS Continuity Control Certification Framework
Alduraibi INVESTIGATING THE IMPACT OF LEAN SIX SIGMA PRINCIPLES ON ESTABLISHING AND MAINTAINING DATA GOVERNANCE SYSTEMS IN SMES: AN EXPLORATORY STUDY USING GROUNDED THEORY AND ISM APPROACH
Carruthers et al. Cloud Data Management Capabilities (CDMC)

Legal Events

Date Code Title Description
NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15836108

Country of ref document: EP

Kind code of ref document: A2