US20130173642A1 - Method and apparatus for consent document management - Google Patents
Method and apparatus for consent document management Download PDFInfo
- Publication number
- US20130173642A1 US20130173642A1 US13/720,410 US201213720410A US2013173642A1 US 20130173642 A1 US20130173642 A1 US 20130173642A1 US 201213720410 A US201213720410 A US 201213720410A US 2013173642 A1 US2013173642 A1 US 2013173642A1
- Authority
- US
- United States
- Prior art keywords
- consent
- objects
- combination
- user response
- user
- 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.)
- Abandoned
Links
Images
Classifications
-
- G06F17/27—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/20—Natural language analysis
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
An approach is provided for consent document management. The consent platform causes, at least in part, a creation of one or more consent document objects representing one or more consent documents, metadata associated with the consent documents, or a combination thereof. Next, the consent platform processes and/or facilitates a processing of one or more responses to the one or more consent documents to cause, at least in part, a creation of one or more user response objects, wherein the one or more user response objects record the one or more responses on a per user basis.
Description
- This application claims the benefit of the earlier filing date under 35 U.S.C. §119(e) of U.S. Provisional Application Serial No. 61/581,903 filed Dec. 30, 2011, entitled “Method and Apparatus for Consent Document Management,” the entirety of which is incorporated herein by reference.
- Service providers and device manufacturers (e.g., wireless, cellular, etc.) are continually challenged to deliver value and convenience to consumers by, for example, providing compelling network services. Prior to receiving the benefits of such services, end-users generally must agree to terms and conditions, privacy policies, etc., associated with these services. Documents, containing these terms and conditions, privacy policies, etc., are typically downloaded from the Internet, hard-coded into applications providing such services, attained from files on the local device hosting such applications, etc. However, these documents are not necessarily the latest versions or locally correct. Moreover, the storage of such documents and responses to such documents are not performed in a centralized manner. As such, users may be prevented from accessing consent-related records, be required to resubmit previous responses, etc., for instance, when they switch or replace applications, services, or devices.
- Therefore, there is a need for an approach for consent document management.
- According to one embodiment, a method comprises causing, at least in part, a creation of one or more consent document objects representing one or more consent documents, metadata associated with the consent documents, or a combination thereof. The method also comprises processing and/or facilitating a processing of one or more responses to the one or more consent documents to cause, at least in part, a creation of one or more user response objects, wherein the one or more user response objects record the one or more responses on a per user basis.
- According to another embodiment, an apparatus comprises at least one processor, and at least one memory including computer program code for one or more computer programs, the at least one memory and the computer program code configured to, with the at least one processor, cause, at least in part, the apparatus to cause, at least in part, a creation of one or more consent document objects representing one or more consent documents, metadata associated with the consent documents, or a combination thereof. The apparatus is also caused to process and/or facilitate a processing of one or more responses to the one or more consent documents to cause, at least in part, a creation of one or more user response objects, wherein the one or more user response objects record the one or more responses on a per user basis.
- According to another embodiment, a computer-readable storage medium carries one or more sequences of one or more instructions which, when executed by one or more processors, cause, at least in part, an apparatus to cause, at least in part, a creation of one or more consent document objects representing one or more consent documents, metadata associated with the consent documents, or a combination thereof. The apparatus is also caused to process and/or facilitate a processing of one or more responses to the one or more consent documents to cause, at least in part, a creation of one or more user response objects, wherein the one or more user response objects record the one or more responses on a per user basis.
- According to another embodiment, an apparatus comprises means for causing, at least in part, a creation of one or more consent document objects representing one or more consent documents, metadata associated with the consent documents, or a combination thereof. The apparatus also comprises means for processing and/or facilitating a processing of one or more responses to the one or more consent documents to cause, at least in part, a creation of one or more user response objects, wherein the one or more user response objects record the one or more responses on a per user basis.
- In addition, for various example embodiments of the invention, the following is applicable: a method comprising facilitating a processing of and/or processing (1) data and/or (2) information and/or (3) at least one signal, the (1) data and/or (2) information and/or (3) at least one signal based, at least in part, on (or derived at least in part from) any one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.
- For various example embodiments of the invention, the following is also applicable: a method comprising facilitating access to at least one interface configured to allow access to at least one service, the at least one service configured to perform any one or any combination of network or service provider methods (or processes) disclosed in this application.
- For various example embodiments of the invention, the following is also applicable: a method comprising facilitating creating and/or facilitating modifying (1) at least one device user interface element and/or (2) at least one device user interface functionality, the (1) at least one device user interface element and/or (2) at least one device user interface functionality based, at least in part, on data and/or information resulting from one or any combination of methods or processes disclosed in this application as relevant to any embodiment of the invention, and/or at least one signal resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.
- For various example embodiments of the invention, the following is also applicable: a method comprising creating and/or modifying (1) at least one device user interface element and/or (2) at least one device user interface functionality, the (1) at least one device user interface element and/or (2) at least one device user interface functionality based at least in part on data and/or information resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention, and/or at least one signal resulting from one or any combination of methods (or processes) disclosed in this application as relevant to any embodiment of the invention.
- In various example embodiments, the methods (or processes) can be accomplished on the service provider side or on the mobile device side or in any shared way between service provider and mobile device with actions being performed on both sides.
- For various example embodiments, the following is applicable: An apparatus comprising means for performing the method of any of originally filed claims 1-10, 21-30, and 46-48.
- Still other aspects, features, and advantages of the invention are readily apparent from the following detailed description, simply by illustrating a number of particular embodiments and implementations, including the best mode contemplated for carrying out the invention. The invention is also capable of other and different embodiments, and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the invention. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive.
- The embodiments of the invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings:
-
FIG. 1 is a diagram of a system capable of consent document management, according to one embodiment; -
FIG. 2 is a diagram of the components of a consent platform, according to one embodiment; -
FIG. 3 is a flowchart of a process for consent document management, according to one embodiment; -
FIG. 4 is a flowchart of a process for presenting consent document objects and user response objects on various applications and devices, according to one embodiment; -
FIG. 5 is a flowchart of a process for providing notifications in response to inconsistent consent behavior, according to one embodiment; -
FIG. 6 is a diagram of consent document objects, according to one embodiment; -
FIG. 7 provides high-level class diagrams for various base components, according to one embodiment; -
FIGS. 8A-8C are diagrams of user interfaces utilized in the processes ofFIGS. 3-5 , according to various embodiments; -
FIG. 9 is a diagram of hardware that can be used to implement an embodiment of the invention; -
FIG. 10 is a diagram of a chip set that can be used to implement an embodiment of the invention; and -
FIG. 11 is a diagram of a mobile terminal (e.g., handset) that can be used to implement an embodiment of the invention. - Examples of a method, apparatus, and computer program for consent document management are disclosed. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It is apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention.
-
FIG. 1 is a diagram of a system capable of consent document management, according to one embodiment. As discussed, typical approaches to providing consent documents (e.g., documents that contain terms and conditions, privacy or security policies, marketing consents, etc.) typically do not offer a mechanism to ensure that users are supplied with the latest versions of the consent documents (e.g., notwithstanding the particular version of the application, device, etc.), that the consent documents are appropriate for the specific jurisdiction, etc. For example, a local installation file for a particular application may contain a consent document that was appropriate when the application was installed for the first time. Due to circumstantial changes, a new version of the consent document may later be adopted for the current and future versions of the application. Nonetheless, when the local installation file is reused to reinstall the application, the user will generally be presented with the older version of the consent document contained within the local installation file. In addition, the storage of such documents and responses to such documents are generally not performed in a centralized manner. In some instances, the particular responses (e.g., accept, decline, etc.) are not recorded at all, but merely act to enable or prevent installation of an application (e.g., if “Accept,” allow installation; otherwise, close installer program). As such, users may be prevented from accessing consent-related records, be required to resubmit previous responses, etc., for instance, when they switch or replace applications, services, or devices. - To address this problem, a
system 100 ofFIG. 1 introduces the capability to manage consent documents as well as responses to consent documents, for instance, through the use of consent document objects and user response objects. Specifically, thesystem 100 may create consent document objects representing consent documents and/or metadata associated with the consent documents. Thesystem 100 may further process responses to the consent documents to create user response objects that record the responses on a per user basis (e.g., each user response object records the responses of an individual user rather than the responses of user groups, collective responses, etc.). Consent document objects and user response objects may, for instance, be centrally stored for access by various applications, devices, users, etc. The following details and embodiments illustrate situations in which the consent document objects and user response objects can be effectively utilized to enable distribution and maintenance of consent documents, solicitation and recording of responses to these consent documents, and enforcement of associated agreed-upon terms/policies. - As shown in
FIG. 1 , thesystem 100 comprises a user equipment (UE) 101 (or multiple UEs 101 a-101 n) having connectivity to aconsent platform 103 via acommunication network 105. The UE 101 may include or have access to an application 107 (e.g., applications 107 a-107 n) to enable the UE 101 to interact with, for instance, theconsent platform 103, which may: (1) cause a creation of consent document objects representing consent documents and/or metadata associated with the consent documents; (2) process responses to the consent documents to create user response objects that record the responses on a per user basis; (3) present the consent document objects and/or the user response objects on an application and/or a device based on one or more user interface capabilities determined for the application and/or the device; (4) query the consent document objects and/or the user response objects for the consent documents and/or the responses based on predetermined criteria; (5) process the consent document objects and/or the user response objects to determine consent behavior of one or more users associated with the consent document objects and/or the user response objects; or (6) perform other functions. Theconsent platform 103 may include or have access to adocument database 109 to access or store consent document objects, consent documents, metadata associated with the consent documents, etc. Theconsent platform 103 may also include or have access to asettings database 111 to access or store user response objects, specific settings for various application/device, settings related to sharing and access control, etc. Data stored in thedocument database 109 and thesettings database 111 may, for instance, be provided by the UEs 101, aservice platform 113, one or more services 115 (or services 115 a-115 k), one or more content providers 117 (or content providers 117 a-117 m), and/or other services available over thecommunication network 105. It is noted that theconsent platform 103 may be a separate entity of thesystem 100, a part of the one or more services 115 of theservice platform 113, or included within the UE 101 (e.g., as part of the application 107). - By way of example, the
communication network 105 ofsystem 100 includes one or more networks such as a data network, a wireless network, a telephony network, or any combination thereof. It is contemplated that the data network may be any local area network (LAN), metropolitan area network (MAN), wide area network (WAN), a public data network (e.g., the Internet), short range wireless network, or any other suitable packet-switched network, such as a commercially owned, proprietary packet-switched network, e.g., a proprietary cable or fiber-optic network, and the like, or any combination thereof. In addition, the wireless network may be, for example, a cellular network and may employ various technologies including enhanced data rates for global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS), etc., as well as any other suitable wireless medium, e.g., worldwide interoperability for microwave access (WiMAX), Long Term Evolution (LTE) networks, code division multiple access (CDMA), wideband code division multiple access (WCDMA), wireless fidelity (WiFi), wireless LAN (WLAN), Bluetooth®, Internet Protocol (IP) data casting, satellite, mobile ad-hoc network (MANET), and the like, or any combination thereof - The
UE 101 is any type of mobile terminal, fixed terminal, or portable terminal including a mobile handset, station, unit, device, multimedia computer, multimedia tablet, Internet node, communicator, desktop computer, laptop computer, notebook computer, netbook computer, tablet computer, personal communication system (PCS) device, personal navigation device, personal digital assistants (PDAs), audio/video player, digital camera/camcorder, positioning device, television receiver, radio broadcast receiver, electronic book device, game device, or any combination thereof, including the accessories and peripherals of these devices, or any combination thereof. It is also contemplated that theUE 101 can support any type of interface to the user (such as “wearable” circuitry, etc.). - In another embodiment, the
consent platform 103 may determine one or user interface capabilities of one or more applications, one or more devices, or a combination thereof. Theconsent platform 103 may then cause, at least in part, a presentation of the one or more consent document objects, the one or more user response objects, or a combination thereof based, at least in part, on the one or more user interface capabilities. By way of example, an installer application running on a particular mobile device may request presentation of a consent document object on the mobile device. In response, theconsent platform 103 may identify user interface capability values associated with the user interface capabilities of the installer application and the mobile device (e.g., the presentation request may include identifiers for the installer application and the mobile device that can be used to look up the user interface capability values, the presentation request may include the user interface capability values, etc.). Moreover, theconsent platform 103 may identify the user interface capability values associated with the consent document object, and then match the user interface capability values of the installer application and the mobile device with the user interface capability values of the consent document object. As a result, the consent document object may be presented on the user interface of the installer application based on the matching of the respective user interface capability values (e.g., by converting the consent document object into application-specific or device-specific content based on the matching, and transmitting the application-specific or device-specific content to the requesting application/device). It is noted that various features of theconsent platform 103 may also exist at the mobile device. For example, after the mobile device is provided with the consent document object (e.g., representing a consent document and metadata associated with the consent document), the mobile device may perform the identification, matching, and presentation steps, as described above. - In another embodiment, the
consent platform 103 may determine to query the one or more consent document objects, the one or more user response objects, or a combination thereof for the one or more consent documents, the one or more responses, or a combination thereof based, at least in part, on one or more predetermined criteria. The one or more predetermined criteria may, for instance, include a document identifier, a jurisdiction identifier, a language identifier, a version identifier, a user identifier, or a combination thereof. In one scenario, an application may, for instance, request the latest version of its corresponding privacy policy for Finland in Swedish. Consequently, theconsent platform 103 may search through the one or more consent documents (e.g., by querying the document database 109) for the desired privacy policy, for instance, based on an associated document identifier (e.g., corresponding to the application) and the terms “latest,” “Finland,” and “Swedish.” - In another scenario, an application may be programmed to determine whether a user has already consented to the application's latest terms and conditions prior to the user initiating use of the application. Thus, the application may query the one or more user response objects (e.g., by querying the settings database 111) based on a user identifier associated with the user and the associated document identifier. In this way, the user does not need to resubmit consent every time that the application is reinstalled on the same device, installed on another device, etc. In a further scenario, the application may also check (e.g., periodically, upon detection of a new version, etc.) to see if the user has consented to the latest version of the associated consent document. If, for instance, the application detects that a new version of the associated consent document is available, the application may query the one or more user response objects to determine whether the user has already accepted the latest version's terms and conditions. Accordingly, the
consent platform 103 may be utilized to ensure that users have accepted the latest versions of terms and conditions, privacy and security policies, marketing consents, etc., prior to using respective applications, services, etc. Similarly, such an approach may be utilized to ensure that users have agreed to the appropriate consent documents according to the jurisdiction, the language, etc. - In another embodiment, the
consent platform 103 may determine context information associated with the one or more responses upon a detection of the one or more responses, wherein the one or more user response objects include, at least in part, the context information. In one use case, for instance, a user response object may contain a timestamp representing the date and time that a response (e.g., some level of acceptance, decline, etc.) was submitted by a user. It is noted that the timestamps included with the user response objects may be useful in a number of circumstances, including a determination of which particular terms, policies, etc., should apply in various situations. By way of example, content sharing policies may differ from one version of a consent document to another version of the consent document. If, for instance, the laws of a certain jurisdiction prohibits the retroactive application of new/modified terms to previous user activities/actions (e.g., previously uploaded pictures), then user activities/actions that occurred prior to the recorded time-stamped acceptance of the new/modified terms will be governed by the old/unmodified terms (e.g., a picture taken before the acceptance of the new policy will be based on the old policy). In another scenario, the user response object may include location information with respect to the location of the user when the user submitted the response. - In another embodiment, the
consent platform 103 may determine one or more timelines associated with the one or more user response objects based, at least in part, on the context information. As discussed, the one or more use response objects may include the context information, such as timestamps representing the dates and times that associated responses were submitted by respective users. Thus, in one scenario, the one or more timelines for the one or more user response objects may be according to the timestamps. In a further scenario, a user may log into his/her account to check the user's consent history with respect to all of the applications and services that the user has previously utilized. To facilitate user readability, the user response objects (e.g., representing the responses that the user has given) may be rendered for the user based on the timeline determined for the user response objects of the user. - In another embodiment, the
consent platform 103 may process and/or facilitate a processing of the one or more consent document objects, the one or more user response objects, or a combination thereof to determine consent behavior of one or more users associated with the one or more consent document objects, the one or more user response objects, or a combination thereof. By way of example, theconsent platform 103 may determine consent behavior of a particular user by querying the one or more consent document objects and the one or more user response objects (e.g., by querying thedocument database 109 and the settings database 111) and analyzing the various responses to associated consent documents. - In another embodiment, the
consent platform 103 may determine an inconsistency between at least one of the one or more user response objects and the consent behavior. Theconsent platform 103 may then cause, at least in part, a notification relating to at least one of the one or more responses associated with the at least one user response object based, at least in part, the inconsistency. In one use case, a user may be provided with an alert (e.g., via email, messenger, etc.) when it is determined that someone (or something) under the user's account has agreed to terms and conditions that are similar to terms and conditions that the user has consistently rejected in the past. If, for instance, the user did not accept the particular terms and conditions, the user may be provided with an option to decline the terms and conditions (e.g., by logging into his/her user account to cancel the acceptance). In this way, users may be protected from unauthorized consent to certain terms and conditions, for instance, that enable unauthorized access to user data (e.g., unauthorized consent caused by malware programs). - In another embodiment, the
consent platform 103 may cause, at least in part, an association of the one or more consent document objects with one or more rules relating, at least in part, to a delivery, a presentation, an enforcement, or a combination thereof of the one or more consent document objects. By way of example, these rules may describe the supersession relationships between various consent document objects, such that a particular consent document object may supersede other consent document objects. Superseded consent document objects may, however, still be valid and enforceable, for instance, with respect to their associated policies that are not inconsistent with the associated policies of superseding consent document objects. In other words, the rules may dictate whether the terms and conditions, policies, etc., of certain consent document objects preempts the terms and conditions, policies, etc., of various other consent document objects. - In another embodiment, at least one of the one or more consent documents, at least one of the one or more responses, or a combination thereof are a supplement for at least another one of the one or more consent documents, at least another one of the one or more user response objects, or a combination thereof. In one scenario, a particular service provider may require that users agree to a primary consent document containing terms of service/use for applications distributed by the service provider before downloading and installing such applications. In addition, each of the applications may require that users agree to their own respective secondary consent documents before the respective applications may be downloaded or installed. The secondary consent documents may, however, be limited to supplementing the primary consent document based on the one or more rules associated with corresponding consent document objects. For example, the rules may enable the secondary consent documents to add to or modify certain portions of the primary consent document, while prohibiting the addition or modification of terms that are inconsistent with various other portions of the primary consent document. In this way, the
consent platform 103 may enable dynamic tailoring of the required consent documents by application (or application developers) while ensuring that certain terms and conditions of the service provider are not overridden. - In a further embodiment, the
consent platform 103 may cause, at least in part, a linking of the one or more consent document objects, the one or more user response objects, or a combination thereof to represent a composite of the respective consent documents, the respective responses, or a combination thereof. By way of example, a consent document object associated with the primary consent document may be linked with a consent document object associated with a secondary consent document to represent the complete consent document (e.g., the combination of the primary consent document and the secondary consent document) that a user is required to consent to in order to download and install a particular application from the service provider. Thus, theconsent platform 103 may enforce the terms of the combined consent documents (e.g., based on the supersession or preemption rules) associated with the consent document objects based on the linking - By way of example, the
UE 101, theconsent platform 103, theservice platform 113, the services 115, and the content providers 117 communicate with each other and other components of thecommunication network 105 using well known, new or still developing protocols. In this context, a protocol includes a set of rules defining how the network nodes within thecommunication network 105 interact with each other based on information sent over the communication links. The protocols are effective at different layers of operation within each node, from generating and receiving physical signals of various types, to selecting a link for transferring those signals, to the format of information indicated by those signals, to identifying which software application executing on a computer system sends or receives the information. The conceptually different layers of protocols for exchanging information over a network are described in the Open Systems Interconnection (OSI) Reference Model. - Communications between the network nodes are typically effected by exchanging discrete packets of data. Each packet typically comprises (1) header information associated with a particular protocol, and (2) payload information that follows the header information and contains information that may be processed independently of that particular protocol. In some protocols, the packet includes (3) trailer information following the payload and indicating the end of the payload information. The header includes information such as the source of the packet, its destination, the length of the payload, and other properties used by the protocol. Often, the data in the payload for the particular protocol includes a header and payload for a different protocol associated with a different, higher layer of the OSI Reference Model. The header for a particular protocol typically indicates a type for the next protocol contained in its payload. The higher layer protocol is said to be encapsulated in the lower layer protocol. The headers included in a packet traversing multiple heterogeneous networks, such as the Internet, typically include a physical (layer 1) header, a data-link (layer 2) header, an internetwork (layer 3) header and a transport (layer 4) header, and various application (
layer 5,layer 6 and layer 7) headers as defined by the OSI Reference Model. -
FIG. 2 is a diagram of the components of a consent platform, according to one embodiment. By way of example, theconsent platform 103 includes one or more components for consent document management. It is contemplated that the functions of these components may be combined in one or more components or performed by other components of equivalent functionality. In this embodiment, theconsent platform 103 includescontrol logic 201,memory 203, adocument delivery module 205, asettings module 207, aquery module 209, anenforcement module 211, and acommunication interface 213. - The
control logic 201 executes at least one algorithm for executing functions of theconsent platform 103. For example, thecontrol logic 201 may interact with thedocument delivery module 205 to create consent document objects representing consent documents and/or metadata associated with the consent documents. Thecontrol logic 201 may also work with thesettings module 207 to process responses to the consent documents to create user response objects that record the responses on a per user basis. Additionally, thedocument delivery module 205 and thesettings module 207 may work together to determine user interface capabilities of a application, a device, etc., for presentation of the consent document objects and the user response objects on the application, the device, etc. As such, in some embodiments, thedocument delivery module 205 may be responsible for the management and presentation of necessary legal documents (e.g., the consent documents), such as terms and conditions, privacy and security policies, marketing consents, etc. Thedocument delivery module 205 may, for instance, utilize the data infrastructure (e.g., of the document database 109) to store the consent document objects, the consent documents, metadata associated with the consent documents, etc., as necessary. In certain embodiments, thesettings module 207 may be responsible for the management and presentation of individual user's settings related to consent acceptance (e.g., user response objects), specific sharing settings and access control, specific application and device settings, etc. Thesettings module 207 may make such settings globally available for the individual users, for instance, by storing the settings in thesettings database 111. - Moreover, the
control logic 201 may direct thequery module 209 to query consent document objects and/or user response objects in thedocument database 109, thesettings database 111, etc., for consent documents and/or responses based on predetermined criteria. As mentioned, the predetermined criteria may include a document identifier, a jurisdiction identifier, a language identifier, a version identifier, a user identifier, etc. Query requests may, for instance, be initiated by thedocument delivery module 205, thesettings module 207, etc., to perform queries such as the “latest version of the privacy policy for Finland in Swedish.” In various embodiments, query requests may further be utilized as a mechanism to update the consent document objects and the user response objects as well as the consent documents, the metadata associated with the consent documents, and individual user settings. - Furthermore, the
control logic 201 may interact with theenforcement module 211 to apply the various settings to various data flows. For example, theenforcement module 211 may implement a filtering function based on the various settings when collecting information with respect to the consent document objects and the user response objects. In some embodiments, theenforcement module 211 may also enforce the rules relating to a delivery, a presentation, and/or an enforcement of the consent document objects. Thecontrol logic 201 may additionally utilize thecommunication interface 213 to communicate with other components of theconsent platform 103, theUEs 101, theservice platform 113, the services 115, the content providers 117, and other components of thesystem 100. For example, thecommunication interface 213 may transmit query requests from thedocument delivery module 205 or thesettings module 207 to thequery module 209. Thecommunication interface 213 may further include multiple means of communication. In one use case, thecommunication interface 213 may be able to communicate over short message service (SMS), multimedia messaging service (MMS), internet protocol, email, instant messaging, voice sessions (e.g., via a phone network), or other types of communication. -
FIG. 3 is a flowchart of a process for consent document management, according to one embodiment. In one embodiment, theconsent platform 103 performs theprocess 300 and is implemented in, for instance, a chip set including a processor and a memory as shown inFIG. 10 . As such, thecontrol logic 201 can provide means for accomplishing various parts of theprocess 300 as well as means for accomplishing other processes in conjunction with other components of theconsent platform 103. - In
step 301, thecontrol logic 201 may cause, at least in part, a creation of one or more consent document objects representing one or more consent documents, metadata associated with the one or more consent documents, or a combination thereof. In one scenario, these consent document objects may be stored in a central database (e.g., the document database 109) that is accessible by a number of applications and devices. As such, these applications and devices may check the central database for the most relevant adaptation of the consent document (e.g., the latest version of a consent document for a particular application or device, the appropriate consent document for the jurisdiction and the user's predetermined language, etc.). - In
step 303, thecontrol logic 201 may process and/or facilitate a processing of one or more responses to the one or more consent documents to cause, at least in part, a creation of one or more user response objects, wherein the one or more user response objects record the one or more responses on a per user basis. As an example, these user response objects may be stored in thesettings database 111 for access by various applications and devices, for instance, to check for previously acceptance of particular consent documents by users when reinstalling applications on a device, reinitiating service on the device, installing the applications or services on another device, etc. In this way, users can avoid having to go through the consent process multiple times with respect to the same consent document. -
FIG. 4 is a flowchart of a process for presenting consent document objects and user response objects on various applications and devices, according to one embodiment. In one embodiment, theconsent platform 103 performs theprocess 400 and is implemented in, for instance, a chip set including a processor and a memory as shown inFIG. 10 . As such, thecontrol logic 201 can provide means for accomplishing various parts of theprocess 400 as well as means for accomplishing other processes in conjunction with other components of theconsent platform 103. - In
step 401, thecontrol logic 201 may determine to query the one or more consent document objects, the one or more user response objects, or a combination thereof for the one or more consent documents, the one or more responses, or a combination thereof based, at least in part, on one or more predetermined criteria. As mentioned, the one or more predetermine criteria may include, at least in part, a document identifier, a jurisdiction identifier, a language identifier, a version identifier, a user identifier, or a combination thereof. These criteria may, for instance, be utilized to determine consent document objects or user response objects to render the content of consent documents or user responses to consent documents on an application, a service, a device, etc. (e.g., presenting the content of a consent document to a user for review prior to accepting the consent document, providing the user with a list of consent documents that the user has accepted, etc.). - As such, when the consent document objects and/or user response objects are determined, the
control logic 201 may, atstep 403, determine one or user interface capabilities of one or more applications, one or more devices, or a combination thereof. Subsequently, instep 405, thecontrol logic 201 may cause, at least in part, a presentation of the one or more consent document objects, the one or more user response objects, or a combination thereof based, at least in part, on the one or more user interface capabilities. As discussed, the determined user interface capabilities may be utilized to process the content document objects or the user response objects to produce content specifically formatted for the particular application or device rendering the content (e.g., the processed/converted objects). -
FIG. 5 is a flowchart of a process for providing notifications in response to inconsistent consent behavior, according to one embodiment. In one embodiment, theconsent platform 103 performs theprocess 500 and is implemented in, for instance, a chip set including a processor and a memory as shown inFIG. 10 . As such, thecontrol logic 201 can provide means for accomplishing various parts of theprocess 500 as well as means for accomplishing other processes in conjunction with other components of theconsent platform 103. - In
step 501, thecontrol logic 201 may process and/or facilitate a processing of the one or more consent document objects, the one or more user response objects, or a combination thereof to determine consent behavior of one or more users associated with the one or more consent document objects, the one or more user response objects, or a combination thereof. As mentioned, the consent behavior of a particular user may be determined by querying the one or more consent document objects and the one or more user response objects (e.g., by querying thedocument database 109 and the settings database 111) and analyzing the various responses to associated consent documents. - In
step 503, thecontrol logic 201 may determine whether an inconsistency between at least one of the one or more user response objects and the consent behavior. If, for instance, an inconsistency between the at least one use response object and the consent behavior is determined, the control logic may, as instep 505, cause, at least in part, a notification relating to at least one of the one or more responses associated with the at least one user response object based, at least in part, the inconsistency. In one scenario, for instance, a malware program may cause a notion of acceptance to a particular consent document under the guise of a particular user. Nonetheless, if the notion of acceptance is determined to be inconsistent with the user's consent behavior, then an alert may be provided as an email, a SMS message, etc., to inform the user that such notion of acceptance has occurred. As additional protection, the user may then be provided with an option to cancel the acceptance caused by the malware program. -
FIG. 6 is a diagram of consent document objects, according to one embodiment. As shown, the consent document objects 601 and 603 provide means to represent attributes, such as Version, Title, Country, Language, Content, Options, and Status. Version may, for instance, refer to a version numbering for the consent document associated with the consent document object. Title may refer to a short human-readable title for the consent document. Country may refer to the jurisdiction that the consent document is direct to, and Language may refer to the language that the consent document is written in. Values for the Country and Language attributes may, for instance, be represented by International Organization for Standardization (ISO) codes (e.g., “FI,” “EN,” etc.). Content may refer to a reference to the text of the consent document. Options may refer to a list of selection criteria that a user can make with respect to the consent document (e.g., “accept, decline”, “all, city, country, none”, etc.). Status may refer to the current internal status of the consent document object (e.g., “valid, depreciated”). - Identification of consent document objects may, for instance, be performed based on a document identifier, a jurisdiction identifier, a language identifier, a version identifier, etc. In some embodiments, the document identifier may not be a unique identifier since a single consent document may be used across multiple versions (e.g., a primary consent document may be supplemented by later secondary consent documents representing later versions), countries, and languages. Thus, in such cases, the unique identification of each consent document object may be based on a plurality of the above multiple attributes.
-
FIG. 7 provides high-level class diagrams for various base components, according to one embodiment. As shown, and as previously indicated, a consent document object (e.g., represented by class diagram 701) may include a number of attributes, such as Version, Title, Country, Language, Content, Options, and Status. Moreover, a consent document object may further be defined as any number of consent document object types, such as terms and conditions, privacy policies, and marketing consent (e.g., represented by class diagrams 703, 705, and 707). As discussed, the consent document objects may also be associated with one or more rules (e.g., represented by class diagram 709) related to a delivery, a presentation, or an enforcement of the consent document objects. - The settings data model (e.g., represented by class diagram 711) may include several categories of settings and policies, such as acceptance (or user response objects), policies, and settings (e.g., represented by class diagrams 713, 715, and 717). With regard to the settings data model, settings and policies are made on a per user basis (e.g., by association of class diagrams 711 and 719). That is, for any given user, a number of individual settings and policies can be made, but each user's settings are separate and non-mixable with any other user's settings and policies. As such, the recording of responses (e.g., the notion of acceptance) is also made on a per user basis. As indicated, the possible answers for an acceptance may be derived from a given consent document's values for the options attribute. Additionally, or alternatively, a timestamp may be recorded with each of the settings. As an example, a user response object may record the date and time that a user accepts a particular consent document, for instance, based on when the response was detected. Furthermore, an enforcement function, object, or component (e.g., represented by class diagram 721) may apply the settings of individual users against the actions of the associated applications, devices, etc. For example, a filtering function may be implemented based on the various settings when collecting information with respect to the consent document objects and the user response objects.
-
FIGS. 8A-8C are diagrams of user interfaces utilized in the processes ofFIGS. 3-5 , according to various embodiments.FIG. 8A features theUE 101, which provides theuser interface 800 with aframe window 801 andoptions 803. As illustrated, the Application XYZ has requested a consent document from thedocument database 109, for instance, by submitting a request to query the consent document objects of thedocument database 109 based on an associated document identifier and the latest version identifier as well as the identifiers for the appropriate jurisdiction and language. In addition, the user interface capabilities of the Application XYZ and theUE 101 may be determined, and application/device-specific content representing the consent document object may be produced based on the determined user interface capabilities for presentation on the application and the device. By way of example, the content of the consent document associated with the consent document object may be formatted based on the percentage of the width and height of thewindow frame 801 with respect to the resolution of the display of theUE 101. As a result, the content may be presented on theuser interface 800 without having to horizontal or vertically scroll thewindow frame 801 to view the entirety of the “Terms of Use” for Application XYZ. -
FIG. 8B features theUE 101, which provides theuser interface 830 with awindow frame window 831. In this case, the consent history of User X is presented on theuser interface 830 of theUE 101. As with the presentation of the consent document object, the user response objects may be presented based on a determination of the user interface capabilities of theUE 101 to enable full viewing of the consent history without having to horizontally or vertically scroll thewindow frame 831. As shown, the detailed list inwindow frame 831 is sorted by application names and the version of the respective consent documents as represented in the consent document objects. -
FIG. 8C features theUE 101, which provides theuser interface 850 with anotification 851 andoptions 853. As mentioned, consent behavior of individual users may be determined by processing the consent document objects and the user response objects associated with the individual users. If, for instance, an inconsistency between a user response object and the consent behavior is determined, the user associated with the consent behavior may be alerted of the inconsistent behavior. InFIG. 8C , the user is being informed that he/she has recently acceptedVersion 2 of Privacy Policies issued by the company DEF for using Service ABC, but that the notion of acceptance is inconsistent with the user's consent behavior (e.g., the user has always declined to accept the Privacy Policies of the company DEF). As such, the user is given the opportunity to indicate that he/she did not acceptVersion 2 of Privacy Policies for using Service ABC to enable theconsent platform 103 to take appropriate remedial measures. - The processes described herein for consent document management may be advantageously implemented via software, hardware, firmware or a combination of software and/or firmware and/or hardware. For example, the processes described herein, may be advantageously implemented via processor(s), Digital Signal Processing (DSP) chip, an Application Specific Integrated Circuit (ASIC), Field Programmable Gate Arrays (FPGAs), etc. Such exemplary hardware for performing the described functions is detailed below.
-
FIG. 9 illustrates acomputer system 900 upon which an embodiment of the invention may be implemented. Althoughcomputer system 900 is depicted with respect to a particular device or equipment, it is contemplated that other devices or equipment (e.g., network elements, servers, etc.) withinFIG. 9 can deploy the illustrated hardware and components ofsystem 900.Computer system 900 is programmed (e.g., via computer program code or instructions) to manage consent documents as described herein and includes a communication mechanism such as abus 910 for passing information between other internal and external components of thecomputer system 900. Information (also called data) is represented as a physical expression of a measurable phenomenon, typically electric voltages, but including, in other embodiments, such phenomena as magnetic, electromagnetic, pressure, chemical, biological, molecular, atomic, sub-atomic and quantum interactions. For example, north and south magnetic fields, or a zero and non-zero electric voltage, represent two states (0, 1) of a binary digit (bit). Other phenomena can represent digits of a higher base. A superposition of multiple simultaneous quantum states before measurement represents a quantum bit (qubit). A sequence of one or more digits constitutes digital data that is used to represent a number or code for a character. In some embodiments, information called analog data is represented by a near continuum of measurable values within a particular range.Computer system 900, or a portion thereof, constitutes a means for performing one or more steps of consent document management. - A
bus 910 includes one or more parallel conductors of information so that information is transferred quickly among devices coupled to thebus 910. One ormore processors 902 for processing information are coupled with thebus 910. - A processor (or multiple processors) 902 performs a set of operations on information as specified by computer program code related to consent document management. The computer program code is a set of instructions or statements providing instructions for the operation of the processor and/or the computer system to perform specified functions. The code, for example, may be written in a computer programming language that is compiled into a native instruction set of the processor. The code may also be written directly using the native instruction set (e.g., machine language). The set of operations include bringing information in from the
bus 910 and placing information on thebus 910. The set of operations also typically include comparing two or more units of information, shifting positions of units of information, and combining two or more units of information, such as by addition or multiplication or logical operations like OR, exclusive OR (XOR), and AND. Each operation of the set of operations that can be performed by the processor is represented to the processor by information called instructions, such as an operation code of one or more digits. A sequence of operations to be executed by theprocessor 902, such as a sequence of operation codes, constitute processor instructions, also called computer system instructions or, simply, computer instructions. Processors may be implemented as mechanical, electrical, magnetic, optical, chemical or quantum components, among others, alone or in combination. -
Computer system 900 also includes amemory 904 coupled tobus 910. Thememory 904, such as a random access memory (RAM) or any other dynamic storage device, stores information including processor instructions for consent document management. Dynamic memory allows information stored therein to be changed by thecomputer system 900. RAM allows a unit of information stored at a location called a memory address to be stored and retrieved independently of information at neighboring addresses. Thememory 904 is also used by theprocessor 902 to store temporary values during execution of processor instructions. Thecomputer system 900 also includes a read only memory (ROM) 906 or any other static storage device coupled to thebus 910 for storing static information, including instructions, that is not changed by thecomputer system 900. Some memory is composed of volatile storage that loses the information stored thereon when power is lost. Also coupled tobus 910 is a non-volatile (persistent)storage device 908, such as a magnetic disk, optical disk or flash card, for storing information, including instructions, that persists even when thecomputer system 900 is turned off or otherwise loses power. - Information, including instructions for consent document management, is provided to the
bus 910 for use by the processor from anexternal input device 912, such as a keyboard containing alphanumeric keys operated by a human user, a microphone, an Infrared (IR) remote control, a joystick, a game pad, a stylus pen, a touch screen, or a sensor. A sensor detects conditions in its vicinity and transforms those detections into physical expression compatible with the measurable phenomenon used to represent information incomputer system 900. Other external devices coupled tobus 910, used primarily for interacting with humans, include adisplay device 914, such as a cathode ray tube (CRT), a liquid crystal display (LCD), a light emitting diode (LED) display, an organic LED (OLED) display, a plasma screen, or a printer for presenting text or images, and apointing device 916, such as a mouse, a trackball, cursor direction keys, or a motion sensor, for controlling a position of a small cursor image presented on thedisplay 914 and issuing commands associated with graphical elements presented on thedisplay 914. In some embodiments, for example, in embodiments in which thecomputer system 900 performs all functions automatically without human input, one or more ofexternal input device 912,display device 914 andpointing device 916 is omitted. - In the illustrated embodiment, special purpose hardware, such as an application specific integrated circuit (ASIC) 920, is coupled to
bus 910. The special purpose hardware is configured to perform operations not performed byprocessor 902 quickly enough for special purposes. Examples of ASICs include graphics accelerator cards for generating images fordisplay 914, cryptographic boards for encrypting and decrypting messages sent over a network, speech recognition, and interfaces to special external devices, such as robotic arms and medical scanning equipment that repeatedly perform some complex sequence of operations that are more efficiently implemented in hardware. -
Computer system 900 also includes one or more instances of acommunications interface 970 coupled tobus 910.Communication interface 970 provides a one-way or two-way communication coupling to a variety of external devices that operate with their own processors, such as printers, scanners and external disks. In general the coupling is with anetwork link 978 that is connected to alocal network 980 to which a variety of external devices with their own processors are connected. For example,communication interface 970 may be a parallel port or a serial port or a universal serial bus (USB) port on a personal computer. In some embodiments,communications interface 970 is an integrated services digital network (ISDN) card or a digital subscriber line (DSL) card or a telephone modem that provides an information communication connection to a corresponding type of telephone line. In some embodiments, acommunication interface 970 is a cable modem that converts signals onbus 910 into signals for a communication connection over a coaxial cable or into optical signals for a communication connection over a fiber optic cable. As another example,communications interface 970 may be a local area network (LAN) card to provide a data communication connection to a compatible LAN, such as Ethernet. Wireless links may also be implemented. For wireless links, thecommunications interface 970 sends or receives or both sends and receives electrical, acoustic or electromagnetic signals, including infrared and optical signals, that carry information streams, such as digital data. For example, in wireless handheld devices, such as mobile telephones like cell phones, thecommunications interface 970 includes a radio band electromagnetic transmitter and receiver called a radio transceiver. In certain embodiments, thecommunications interface 970 enables connection to thecommunication network 105 for providing consent document management to theUE 101. - The term “computer-readable medium” as used herein refers to any medium that participates in providing information to
processor 902, including instructions for execution. Such a medium may take many forms, including, but not limited to computer-readable storage medium (e.g., non-volatile media, volatile media), and transmission media. Non-transitory media, such as non-volatile media, include, for example, optical or magnetic disks, such asstorage device 908. Volatile media include, for example,dynamic memory 904. Transmission media include, for example, twisted pair cables, coaxial cables, copper wire, fiber optic cables, and carrier waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves. Signals include man-made transient variations in amplitude, frequency, phase, polarization or other physical properties transmitted through the transmission media. Common forms of computer-readable media include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other magnetic medium, a CD-ROM, CDRW, DVD, any other optical medium, punch cards, paper tape, optical mark sheets, any other physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, an EEPROM, a flash memory, any other memory chip or cartridge, a carrier wave, or any other medium from which a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media. - Logic encoded in one or more tangible media includes one or both of processor instructions on a computer-readable storage media and special purpose hardware, such as
ASIC 920. - Network link 978 typically provides information communication using transmission media through one or more networks to other devices that use or process the information. For example,
network link 978 may provide a connection throughlocal network 980 to ahost computer 982 or toequipment 984 operated by an Internet Service Provider (ISP).ISP equipment 984 in turn provides data communication services through the public, world-wide packet-switching communication network of networks now commonly referred to as theInternet 990. - A computer called a
server host 992 connected to the Internet hosts a process that provides a service in response to information received over the Internet. For example,server host 992 hosts a process that provides information representing video data for presentation atdisplay 914. It is contemplated that the components ofsystem 900 can be deployed in various configurations within other computer systems, e.g., host 982 andserver 992. - At least some embodiments of the invention are related to the use of
computer system 900 for implementing some or all of the techniques described herein. According to one embodiment of the invention, those techniques are performed bycomputer system 900 in response toprocessor 902 executing one or more sequences of one or more processor instructions contained inmemory 904. Such instructions, also called computer instructions, software and program code, may be read intomemory 904 from another computer-readable medium such asstorage device 908 ornetwork link 978. Execution of the sequences of instructions contained inmemory 904 causesprocessor 902 to perform one or more of the method steps described herein. In alternative embodiments, hardware, such asASIC 920, may be used in place of or in combination with software to implement the invention. Thus, embodiments of the invention are not limited to any specific combination of hardware and software, unless otherwise explicitly stated herein. - The signals transmitted over
network link 978 and other networks throughcommunications interface 970, carry information to and fromcomputer system 900.Computer system 900 can send and receive information, including program code, through thenetworks network link 978 andcommunications interface 970. In an example using theInternet 990, aserver host 992 transmits program code for a particular application, requested by a message sent fromcomputer 900, throughInternet 990,ISP equipment 984,local network 980 andcommunications interface 970. The received code may be executed byprocessor 902 as it is received, or may be stored inmemory 904 or instorage device 908 or any other non-volatile storage for later execution, or both. In this manner,computer system 900 may obtain application program code in the form of signals on a carrier wave. - Various forms of computer readable media may be involved in carrying one or more sequence of instructions or data or both to
processor 902 for execution. For example, instructions and data may initially be carried on a magnetic disk of a remote computer such ashost 982. The remote computer loads the instructions and data into its dynamic memory and sends the instructions and data over a telephone line using a modem. A modem local to thecomputer system 900 receives the instructions and data on a telephone line and uses an infra-red transmitter to convert the instructions and data to a signal on an infra-red carrier wave serving as thenetwork link 978. An infrared detector serving as communications interface 970 receives the instructions and data carried in the infrared signal and places information representing the instructions and data ontobus 910.Bus 910 carries the information tomemory 904 from whichprocessor 902 retrieves and executes the instructions using some of the data sent with the instructions. The instructions and data received inmemory 904 may optionally be stored onstorage device 908, either before or after execution by theprocessor 902. -
FIG. 10 illustrates a chip set orchip 1000 upon which an embodiment of the invention may be implemented. Chip set 1000 is programmed to manage consent documents as described herein and includes, for instance, the processor and memory components described with respect toFIG. 9 incorporated in one or more physical packages (e.g., chips). By way of example, a physical package includes an arrangement of one or more materials, components, and/or wires on a structural assembly (e.g., a baseboard) to provide one or more characteristics such as physical strength, conservation of size, and/or limitation of electrical interaction. It is contemplated that in certain embodiments the chip set 1000 can be implemented in a single chip. It is further contemplated that in certain embodiments the chip set orchip 1000 can be implemented as a single “system on a chip.” It is further contemplated that in certain embodiments a separate ASIC would not be used, for example, and that all relevant functions as disclosed herein would be performed by a processor or processors. Chip set orchip 1000, or a portion thereof, constitutes a means for performing one or more steps of providing user interface navigation information associated with the availability of functions. Chip set orchip 1000, or a portion thereof, constitutes a means for performing one or more steps of consent document management. - In one embodiment, the chip set or
chip 1000 includes a communication mechanism such as a bus 1001 for passing information among the components of thechip set 1000. Aprocessor 1003 has connectivity to the bus 1001 to execute instructions and process information stored in, for example, amemory 1005. Theprocessor 1003 may include one or more processing cores with each core configured to perform independently. A multi-core processor enables multiprocessing within a single physical package. Examples of a multi-core processor include two, four, eight, or greater numbers of processing cores. Alternatively or in addition, theprocessor 1003 may include one or more microprocessors configured in tandem via the bus 1001 to enable independent execution of instructions, pipelining, and multithreading. Theprocessor 1003 may also be accompanied with one or more specialized components to perform certain processing functions and tasks such as one or more digital signal processors (DSP) 1007, or one or more application-specific integrated circuits (ASIC) 1009. ADSP 1007 typically is configured to process real-world signals (e.g., sound) in real time independently of theprocessor 1003. Similarly, anASIC 1009 can be configured to performed specialized functions not easily performed by a more general purpose processor. Other specialized components to aid in performing the inventive functions described herein may include one or more field programmable gate arrays (FPGA), one or more controllers, or one or more other special-purpose computer chips. - In one embodiment, the chip set or
chip 1000 includes merely one or more processors and some software and/or firmware supporting and/or relating to and/or for the one or more processors. - The
processor 1003 and accompanying components have connectivity to thememory 1005 via the bus 1001. Thememory 1005 includes both dynamic memory (e.g., RAM, magnetic disk, writable optical disk, etc.) and static memory (e.g., ROM, CD-ROM, etc.) for storing executable instructions that when executed perform the inventive steps described herein to manage consent documents. Thememory 1005 also stores the data associated with or generated by the execution of the inventive steps. -
FIG. 11 is a diagram of exemplary components of a mobile terminal (e.g., handset) for communications, which is capable of operating in the system ofFIG. 1 , according to one embodiment. In some embodiments,mobile terminal 1101, or a portion thereof, constitutes a means for performing one or more steps of consent document management. Generally, a radio receiver is often defined in terms of front-end and back-end characteristics. The front-end of the receiver encompasses all of the Radio Frequency (RF) circuitry whereas the back-end encompasses all of the base-band processing circuitry. As used in this application, the term “circuitry” refers to both: (1) hardware-only implementations (such as implementations in only analog and/or digital circuitry), and (2) to combinations of circuitry and software (and/or firmware) (such as, if applicable to the particular context, to a combination of processor(s), including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions). This definition of “circuitry” applies to all uses of this term in this application, including in any claims. As a further example, as used in this application and if applicable to the particular context, the term “circuitry” would also cover an implementation of merely a processor (or multiple processors) and its (or their) accompanying software/or firmware. The term “circuitry” would also cover if applicable to the particular context, for example, a baseband integrated circuit or applications processor integrated circuit in a mobile phone or a similar integrated circuit in a cellular network device or other network devices. - Pertinent internal components of the telephone include a Main Control Unit (MCU) 1103, a Digital Signal Processor (DSP) 1105, and a receiver/transmitter unit including a microphone gain control unit and a speaker gain control unit. A
main display unit 1107 provides a display to the user in support of various applications and mobile terminal functions that perform or support the steps of consent document management. Thedisplay 1107 includes display circuitry configured to display at least a portion of a user interface of the mobile terminal (e.g., mobile telephone). Additionally, thedisplay 1107 and display circuitry are configured to facilitate user control of at least some functions of the mobile terminal. Anaudio function circuitry 1109 includes amicrophone 1111 and microphone amplifier that amplifies the speech signal output from themicrophone 1111. The amplified speech signal output from themicrophone 1111 is fed to a coder/decoder (CODEC) 1113. - A
radio section 1115 amplifies power and converts frequency in order to communicate with a base station, which is included in a mobile communication system, viaantenna 1117. The power amplifier (PA) 1119 and the transmitter/modulation circuitry are operationally responsive to theMCU 1103, with an output from thePA 1119 coupled to theduplexer 1121 or circulator or antenna switch, as known in the art. ThePA 1119 also couples to a battery interface andpower control unit 1120. - In use, a user of mobile terminal 1101 speaks into the
microphone 1111 and his or her voice along with any detected background noise is converted into an analog voltage. The analog voltage is then converted into a digital signal through the Analog to Digital Converter (ADC) 1123. Thecontrol unit 1103 routes the digital signal into theDSP 1105 for processing therein, such as speech encoding, channel encoding, encrypting, and interleaving. In one embodiment, the processed voice signals are encoded, by units not separately shown, using a cellular transmission protocol such as enhanced data rates for global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS), etc., as well as any other suitable wireless medium, e.g., microwave access (WiMAX), Long Term Evolution (LTE) networks, code division multiple access (CDMA), wideband code division multiple access (WCDMA), wireless fidelity (WiFi), satellite, and the like, or any combination thereof - The encoded signals are then routed to an
equalizer 1125 for compensation of any frequency-dependent impairments that occur during transmission though the air such as phase and amplitude distortion. After equalizing the bit stream, themodulator 1127 combines the signal with a RF signal generated in theRF interface 1129. Themodulator 1127 generates a sine wave by way of frequency or phase modulation. In order to prepare the signal for transmission, an up-converter 1131 combines the sine wave output from themodulator 1127 with another sine wave generated by asynthesizer 1133 to achieve the desired frequency of transmission. The signal is then sent through aPA 1119 to increase the signal to an appropriate power level. In practical systems, thePA 1119 acts as a variable gain amplifier whose gain is controlled by theDSP 1105 from information received from a network base station. The signal is then filtered within theduplexer 1121 and optionally sent to anantenna coupler 1135 to match impedances to provide maximum power transfer. Finally, the signal is transmitted viaantenna 1117 to a local base station. An automatic gain control (AGC) can be supplied to control the gain of the final stages of the receiver. The signals may be forwarded from there to a remote telephone which may be another cellular telephone, any other mobile phone or a land-line connected to a Public Switched Telephone Network (PSTN), or other telephony networks. - Voice signals transmitted to the mobile terminal 1101 are received via
antenna 1117 and immediately amplified by a low noise amplifier (LNA) 1137. A down-converter 1139 lowers the carrier frequency while the demodulator 1141 strips away the RF leaving only a digital bit stream. The signal then goes through theequalizer 1125 and is processed by theDSP 1105. A Digital to Analog Converter (DAC) 1143 converts the signal and the resulting output is transmitted to the user through thespeaker 1145, all under control of a Main Control Unit (MCU) 1103 which can be implemented as a Central Processing Unit (CPU). - The
MCU 1103 receives various signals including input signals from thekeyboard 1147. Thekeyboard 1147 and/or theMCU 1103 in combination with other user input components (e.g., the microphone 1111) comprise a user interface circuitry for managing user input. TheMCU 1103 runs a user interface software to facilitate user control of at least some functions of the mobile terminal 1101 to manage consent documents. TheMCU 1103 also delivers a display command and a switch command to thedisplay 1107 and to the speech output switching controller, respectively. Further, theMCU 1103 exchanges information with theDSP 1105 and can access an optionally incorporatedSIM card 1149 and amemory 1151. In addition, theMCU 1103 executes various control functions required of the terminal. TheDSP 1105 may, depending upon the implementation, perform any of a variety of conventional digital processing functions on the voice signals. Additionally,DSP 1105 determines the background noise level of the local environment from the signals detected bymicrophone 1111 and sets the gain ofmicrophone 1111 to a level selected to compensate for the natural tendency of the user of themobile terminal 1101. - The
CODEC 1113 includes theADC 1123 and DAC 1143. Thememory 1151 stores various data including call incoming tone data and is capable of storing other data including music data received via, e.g., the global Internet. The software module could reside in RAM memory, flash memory, registers, or any other form of writable storage medium known in the art. Thememory device 1151 may be, but not limited to, a single memory, CD, DVD, ROM, RAM, EEPROM, optical storage, magnetic disk storage, flash memory storage, or any other non-volatile storage medium capable of storing digital data. - An optionally incorporated
SIM card 1149 carries, for instance, important information, such as the cellular phone number, the carrier supplying service, subscription details, and security information. TheSIM card 1149 serves primarily to identify the mobile terminal 1101 on a radio network. Thecard 1149 also contains a memory for storing a personal telephone number registry, text messages, and user specific mobile terminal settings. - While the invention has been described in connection with a number of embodiments and implementations, the invention is not so limited but covers various obvious modifications and equivalent arrangements, which fall within the purview of the appended claims. Although features of the invention are expressed in certain combinations among the claims, it is contemplated that these features can be arranged in any combination and order.
Claims (20)
1. A method comprising facilitating a processing of and/or processing (1) data and/or (2) information and/or (3) at least one signal, the (1) data and/or (2) information and/or (3) at least one signal based, at least in part, on the following:
a creation of one or more consent document objects representing one or more consent documents, metadata associated with the one or more consent documents, or a combination thereof; and
a processing of one or more responses to the one or more consent documents to cause, at least in part, a creation of one or more user response objects,
wherein the one or more user response objects record the one or more responses on a per user basis.
2. A method of claim 1 , wherein the (1) data and/or (2) information and/or (3) at least one signal are further based, at least in part, on the following:
at least one determination of one or user interface capabilities of one or more applications, one or more devices, or a combination thereof; and
a presentation of the one or more consent document objects, the one or more user response objects, or a combination thereof based, at least in part, on the one or more user interface capabilities.
3. A method of claim 1 , wherein the (1) data and/or (2) information and/or (3) at least one signal are further based, at least in part, on the following:
at least one determination to query the one or more consent document objects, the one or more user response objects, or a combination thereof for the one or more consent documents, the one or more responses, or a combination thereof based, at least in part, on one or more predetermined criteria.
4. A method of claim 3 , wherein the one or more predetermined criteria include, at least in part, a document identifier, a jurisdiction identifier, a language identifier, a version identifier, a user identifier, or a combination thereof.
5. A method of claim 1 , wherein the (1) data and/or (2) information and/or (3) at least one signal are further based, at least in part, on the following:
at least one determination of context information associated with the one or more responses upon a detection of the one or more responses,
wherein the one or more user response objects include, at least in part, the context information.
6. A method of claim 5 , wherein the (1) data and/or (2) information and/or (3) at least one signal are further based, at least in part, on the following:
at least one determination of one or more timelines associated with the one or more user response objects based, at least in part, on the context information.
7. A method of claim 1 , wherein the (1) data and/or (2) information and/or (3) at least one signal are further based, at least in part, on the following:
a processing of the one or more consent document objects, the one or more user response objects, or a combination thereof to determine consent behavior of one or more users associated with the one or more consent document objects, the one or more user response objects, or a combination thereof.
8. A method of claim 7 , wherein the (1) data and/or (2) information and/or (3) at least one signal are further based, at least in part, on the following:
at least one determination of an inconsistency between at least one of the one or more user response objects and the consent behavior; and
a notification relating to at least one of the one or more responses associated with the at least one user response object based, at least in part, the inconsistency.
9. A method of claim 1 , wherein the (1) data and/or (2) information and/or (3) at least one signal are further based, at least in part, on the following:
an association of the one or more consent document objects with one or more rules relating, at least in part, to a delivery, a presentation, an enforcement, or a combination thereof of the one or more consent document objects.
10. A method of claim 1 , wherein at least one of the one or more consent documents, at least one of the one or more responses, or a combination thereof are a supplement for at least another one of the one or more consent documents, at least another one of the one or more user response objects, or a combination thereof, and wherein the (1) data and/or (2) information and/or (3) at least one signal are further based, at least in part, on the following:
a linking of the one or more consent document objects, the one or more user response objects, or a combination thereof to represent a composite of the respective consent documents, the respective responses, or a combination thereof
11. An apparatus comprising:
at least one processor; and
at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,
cause, at least in part, a creation of one or more consent document objects representing one or more consent documents, metadata associated with the one or more consent documents, or a combination thereof; and
process and/or facilitate a processing of one or more responses to the one or more consent documents to cause, at least in part, a creation of one or more user response objects,
wherein the one or more user response objects record the one or more responses on a per user basis.
12. An apparatus of claim 11 , wherein the apparatus is further caused to:
determine one or user interface capabilities of one or more applications, one or more devices, or a combination thereof and
cause, at least in part, a presentation of the one or more consent document objects, the one or more user response objects, or a combination thereof based, at least in part, on the one or more user interface capabilities.
13. An apparatus of claim 11 , wherein the apparatus is further caused to:
determine to query the one or more consent document objects, the one or more user response objects, or a combination thereof for the one or more consent documents, the one or more responses, or a combination thereof based, at least in part, on one or more predetermined criteria.
14. An apparatus of claim 13 , wherein the one or more predetermined criteria include, at least in part, a document identifier, a jurisdiction identifier, a language identifier, a version identifier, a user identifier, or a combination thereof
15. An apparatus of claim 11 , wherein the apparatus is further caused to:
determine context information associated with the one or more responses upon a detection of the one or more responses,
wherein the one or more user response objects include, at least in part, the context information.
16. An apparatus of claim 15 , wherein the apparatus is further caused to:
determine one or more timelines associated with the one or more user response objects based, at least in part, on the context information.
17. An apparatus of claim 11 , wherein the apparatus is further caused to:
process and/or facilitate a processing of the one or more consent document objects, the one or more user response objects, or a combination thereof to determine consent behavior of one or more users associated with the one or more consent document objects, the one or more user response objects, or a combination thereof
18. An apparatus of claim 17 , wherein the apparatus is further caused to:
determine an inconsistency between at least one of the one or more user response objects and the consent behavior; and
cause, at least in part, a notification relating to at least one of the one or more responses associated with the at least one user response object based, at least in part, the inconsistency.
19. An apparatus of claim 11 , wherein the apparatus is further caused to:
cause, at least in part, an association of the one or more consent document objects with one or more rules relating, at least in part, to a delivery, a presentation, an enforcement, or a combination thereof of the one or more consent document objects.
20. An apparatus of claim 11 , wherein at least one of the one or more consent documents, at least one of the one or more responses, or a combination thereof are a supplement for at least another one of the one or more consent documents, at least another one of the one or more user response objects, or a combination thereof, and wherein the apparatus is further caused to: cause, at least in part, a linking of the one or more consent document objects, the one or more user response objects, or a combination thereof to represent a composite of the respective consent documents, the respective responses, or a combination thereof.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/720,410 US20130173642A1 (en) | 2011-12-30 | 2012-12-19 | Method and apparatus for consent document management |
US16/014,944 US11042701B2 (en) | 2011-12-30 | 2018-06-21 | Method and apparatus for consent document management |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161581903P | 2011-12-30 | 2011-12-30 | |
US13/720,410 US20130173642A1 (en) | 2011-12-30 | 2012-12-19 | Method and apparatus for consent document management |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/014,944 Continuation US11042701B2 (en) | 2011-12-30 | 2018-06-21 | Method and apparatus for consent document management |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130173642A1 true US20130173642A1 (en) | 2013-07-04 |
Family
ID=48695813
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/720,410 Abandoned US20130173642A1 (en) | 2011-12-30 | 2012-12-19 | Method and apparatus for consent document management |
US16/014,944 Active 2033-11-04 US11042701B2 (en) | 2011-12-30 | 2018-06-21 | Method and apparatus for consent document management |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/014,944 Active 2033-11-04 US11042701B2 (en) | 2011-12-30 | 2018-06-21 | Method and apparatus for consent document management |
Country Status (2)
Country | Link |
---|---|
US (2) | US20130173642A1 (en) |
WO (1) | WO2013098485A1 (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140373182A1 (en) * | 2013-06-14 | 2014-12-18 | Salesforce.Com, Inc. | Systems and methods of automated compliance with data privacy laws |
US20160269491A1 (en) * | 2015-03-09 | 2016-09-15 | Samsung Electronics Co., Ltd. | User information processing method and electronic device supporting the same |
US9467424B2 (en) | 2011-10-07 | 2016-10-11 | Salesforce.Com, Inc. | Methods and systems for proxying data |
US20200019394A1 (en) * | 2018-07-16 | 2020-01-16 | International Business Machines Corporation | Controlling computer executions based on terms and conditions and user device attributes |
US20200389317A1 (en) * | 2019-06-04 | 2020-12-10 | The Toronto-Dominion Bank | Dynamic management and implementation of consent and permissioning protocols using container-based applications |
US20220198138A1 (en) * | 2020-12-17 | 2022-06-23 | International Business Machines Corporation | Consent to content template mapping |
US20220223238A1 (en) * | 2019-02-20 | 2022-07-14 | Iqvia Inc. | Management and tracking solution for specific patient consent attributes and permissions |
US11405207B2 (en) * | 2019-07-31 | 2022-08-02 | The Toronto-Dominion Bank | Dynamic implementation and management of hash-based consent and permissioning protocols |
US20220414255A1 (en) * | 2020-01-22 | 2022-12-29 | Google Llc | User consent framework |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20220090540A (en) * | 2019-10-21 | 2022-06-29 | 유니버살 일렉트로닉스 인코퍼레이티드 | Consent management system through client operation |
US20210157949A1 (en) * | 2019-11-21 | 2021-05-27 | Hewlett-Packard Development Company, L.P. | Event data tagged with consent records |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020010784A1 (en) * | 2000-01-06 | 2002-01-24 | Clayton Gary E. | Policy notice method and system |
US20030130867A1 (en) * | 2002-01-04 | 2003-07-10 | Rohan Coelho | Consent system for accessing health information |
US20040044628A1 (en) * | 2002-08-27 | 2004-03-04 | Microsoft Corporation | Method and system for enforcing online identity consent polices |
US7076558B1 (en) * | 2002-02-27 | 2006-07-11 | Microsoft Corporation | User-centric consent management system and method |
US7590705B2 (en) * | 2004-02-23 | 2009-09-15 | Microsoft Corporation | Profile and consent accrual |
US7797726B2 (en) * | 2004-12-16 | 2010-09-14 | International Business Machines Corporation | Method and system for implementing privacy policy enforcement with a privacy proxy |
US8090960B2 (en) * | 2005-08-02 | 2012-01-03 | Ricoh Company, Ltd. | Information managing method, information managing system, server apparatus, and recording medium |
US8474012B2 (en) * | 2010-12-10 | 2013-06-25 | Microsoft Corporation | Progressive consent |
Family Cites Families (38)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5485600A (en) | 1992-11-09 | 1996-01-16 | Virtual Prototypes, Inc. | Computer modelling system and method for specifying the behavior of graphical operator interfaces |
US6782506B1 (en) * | 1998-02-12 | 2004-08-24 | Newriver, Inc. | Obtaining consent for electronic delivery of compliance information |
US20010042088A1 (en) * | 1999-04-26 | 2001-11-15 | Robert N. Hotchkiss | System implementing electronic review and approval of applications to perform nonstandard medical or veterinary procedures |
US7353246B1 (en) * | 1999-07-30 | 2008-04-01 | Miva Direct, Inc. | System and method for enabling information associations |
US8380630B2 (en) * | 2000-07-06 | 2013-02-19 | David Paul Felsher | Information record infrastructure, system and method |
US7559034B1 (en) | 2000-10-19 | 2009-07-07 | DG FastChannel, Inc. | Method and system for using a hyperlink, banner, or graphical icon to initiate the overlaying of an object on a window |
US6721578B2 (en) * | 2002-01-31 | 2004-04-13 | Qualcomm Incorporated | System and method for providing an interactive screen on a wireless device interacting with a server |
US20030229515A1 (en) * | 2002-06-11 | 2003-12-11 | Syed Rizvi | Error free medical and surgical consent |
US7454508B2 (en) * | 2002-06-28 | 2008-11-18 | Microsoft Corporation | Consent mechanism for online entities |
US7707642B1 (en) * | 2004-08-31 | 2010-04-27 | Adobe Systems Incorporated | Document access auditing |
US8077832B2 (en) * | 2004-10-20 | 2011-12-13 | Speechink, Inc. | Systems and methods for consent-based recording of voice data |
US20070112660A1 (en) * | 2005-02-04 | 2007-05-17 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Disposition of proprietary virtual rights |
US20060178913A1 (en) * | 2005-02-09 | 2006-08-10 | Anne Lara | Medical and other consent information management system |
US20070192140A1 (en) * | 2005-08-17 | 2007-08-16 | Medcommons, Inc. | Systems and methods for extending an information standard through compatible online access |
US20070067189A1 (en) * | 2005-09-16 | 2007-03-22 | Numoda Corporation | Method and apparatus for screening, enrollment and management of patients in clinical trials |
US8504537B2 (en) * | 2006-03-24 | 2013-08-06 | Mcafee, Inc. | Signature distribution in a document registration system |
US20070226504A1 (en) * | 2006-03-24 | 2007-09-27 | Reconnex Corporation | Signature match processing in a document registration system |
US20070238450A1 (en) * | 2006-04-07 | 2007-10-11 | Lena Hogberg | Software activation in a mobile terminal |
US7958227B2 (en) * | 2006-05-22 | 2011-06-07 | Mcafee, Inc. | Attributes of captured objects in a capture system |
US20100217988A1 (en) * | 2007-04-12 | 2010-08-26 | Avow Systems, Inc. | Electronic document management and delivery |
US8316141B2 (en) * | 2007-04-13 | 2012-11-20 | Research In Motion Limited | Wireless email communications system providing resource update tracking features and related methods |
US8396806B2 (en) * | 2007-10-30 | 2013-03-12 | Red Hat, Inc. | End user license agreements associated with messages |
US20090265180A1 (en) * | 2008-04-21 | 2009-10-22 | Microsoft Corporation | Machine-readable end user license agreement with automated acceptance |
US9253154B2 (en) * | 2008-08-12 | 2016-02-02 | Mcafee, Inc. | Configuration management for a capture/registration system |
US20100153707A1 (en) * | 2008-11-04 | 2010-06-17 | Lentz Ii John H | Systems and Methods for Real-Time Verification of A Personal Identification Number |
US20100169803A1 (en) | 2008-12-05 | 2010-07-01 | Elizabeth Mazzei | Method and System for Implementing User Generated Preferences in a Communication System |
US8108406B2 (en) | 2008-12-30 | 2012-01-31 | Expanse Networks, Inc. | Pangenetic web user behavior prediction system |
JP5335504B2 (en) * | 2009-03-19 | 2013-11-06 | キヤノン株式会社 | Application packaging apparatus, control method thereof, and program |
US20110119290A1 (en) | 2009-10-02 | 2011-05-19 | Rabin Chandra Kemp Dhoble | Apparatuses, methods and systems for a mobile healthcare manager-based video prescription provider |
US20110099380A1 (en) * | 2009-10-23 | 2011-04-28 | Eric Johannes Vandewater | System and Method of Controlling Access to Information Content Transmitted Over Communication Network |
US20110287748A1 (en) * | 2010-05-18 | 2011-11-24 | Albert Angel | Consent, Signature and Recording Retention in a Certified Communications System |
US9465935B2 (en) * | 2010-06-11 | 2016-10-11 | D2L Corporation | Systems, methods, and apparatus for securing user documents |
US10129211B2 (en) * | 2011-09-15 | 2018-11-13 | Stephan HEATH | Methods and/or systems for an online and/or mobile privacy and/or security encryption technologies used in cloud computing with the combination of data mining and/or encryption of user's personal data and/or location data for marketing of internet posted promotions, social messaging or offers using multiple devices, browsers, operating systems, networks, fiber optic communications, multichannel platforms |
US9800427B2 (en) * | 2012-12-19 | 2017-10-24 | Hartford Fire Insurance Company | System and method for distributing electronic and paper documents as per customer consent |
US9596207B1 (en) * | 2012-12-31 | 2017-03-14 | Google Inc. | Bootstrap social network using event-related records |
US20160012556A1 (en) * | 2014-07-14 | 2016-01-14 | Rocket Lawyer Incorporated | Method and System of Creating and Signing Electronic Documents With Increased Party-Signatory Accuracy and Execution Integrity |
US20160232534A1 (en) * | 2015-02-06 | 2016-08-11 | Trunomi Ltd. | Systems and Methods for Generating an Auditable Digital Certificate |
US9838417B1 (en) | 2014-12-30 | 2017-12-05 | Fireeye, Inc. | Intelligent context aware user interaction for malware detection |
-
2012
- 2012-12-19 US US13/720,410 patent/US20130173642A1/en not_active Abandoned
- 2012-12-27 WO PCT/FI2012/051299 patent/WO2013098485A1/en active Application Filing
-
2018
- 2018-06-21 US US16/014,944 patent/US11042701B2/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020010784A1 (en) * | 2000-01-06 | 2002-01-24 | Clayton Gary E. | Policy notice method and system |
US20030130867A1 (en) * | 2002-01-04 | 2003-07-10 | Rohan Coelho | Consent system for accessing health information |
US7076558B1 (en) * | 2002-02-27 | 2006-07-11 | Microsoft Corporation | User-centric consent management system and method |
US20040044628A1 (en) * | 2002-08-27 | 2004-03-04 | Microsoft Corporation | Method and system for enforcing online identity consent polices |
US7590705B2 (en) * | 2004-02-23 | 2009-09-15 | Microsoft Corporation | Profile and consent accrual |
US7797726B2 (en) * | 2004-12-16 | 2010-09-14 | International Business Machines Corporation | Method and system for implementing privacy policy enforcement with a privacy proxy |
US8090960B2 (en) * | 2005-08-02 | 2012-01-03 | Ricoh Company, Ltd. | Information managing method, information managing system, server apparatus, and recording medium |
US8474012B2 (en) * | 2010-12-10 | 2013-06-25 | Microsoft Corporation | Progressive consent |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9467424B2 (en) | 2011-10-07 | 2016-10-11 | Salesforce.Com, Inc. | Methods and systems for proxying data |
US9900290B2 (en) | 2011-10-07 | 2018-02-20 | Salesforce.Com, Inc. | Methods and systems for proxying data |
US10430608B2 (en) * | 2013-06-14 | 2019-10-01 | Salesforce.Com, Inc. | Systems and methods of automated compliance with data privacy laws |
US20140373182A1 (en) * | 2013-06-14 | 2014-12-18 | Salesforce.Com, Inc. | Systems and methods of automated compliance with data privacy laws |
US20160269491A1 (en) * | 2015-03-09 | 2016-09-15 | Samsung Electronics Co., Ltd. | User information processing method and electronic device supporting the same |
US10901717B2 (en) * | 2018-07-16 | 2021-01-26 | International Business Machines Corporation | Controlling computer executions based on terms and conditions and user device attributes |
US20200019394A1 (en) * | 2018-07-16 | 2020-01-16 | International Business Machines Corporation | Controlling computer executions based on terms and conditions and user device attributes |
US20220223238A1 (en) * | 2019-02-20 | 2022-07-14 | Iqvia Inc. | Management and tracking solution for specific patient consent attributes and permissions |
US20200389317A1 (en) * | 2019-06-04 | 2020-12-10 | The Toronto-Dominion Bank | Dynamic management and implementation of consent and permissioning protocols using container-based applications |
US11689370B2 (en) * | 2019-06-04 | 2023-06-27 | The Toronto-Dominion Bank | Dynamic management and implementation of consent and permissioning protocols using container-based applications |
US11405207B2 (en) * | 2019-07-31 | 2022-08-02 | The Toronto-Dominion Bank | Dynamic implementation and management of hash-based consent and permissioning protocols |
US20220414255A1 (en) * | 2020-01-22 | 2022-12-29 | Google Llc | User consent framework |
US11861040B2 (en) * | 2020-01-22 | 2024-01-02 | Google Llc | User consent framework |
US20220198138A1 (en) * | 2020-12-17 | 2022-06-23 | International Business Machines Corporation | Consent to content template mapping |
Also Published As
Publication number | Publication date |
---|---|
US20180300307A1 (en) | 2018-10-18 |
US11042701B2 (en) | 2021-06-22 |
WO2013098485A1 (en) | 2013-07-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11042701B2 (en) | Method and apparatus for consent document management | |
US20230112569A1 (en) | Method and apparatus for managing files in an online account | |
US10614365B2 (en) | Method and apparatus for managing recommendation models | |
US8996688B2 (en) | Method and apparatus for monitoring and controlling data sharing | |
US9088624B2 (en) | Method and apparatus for routing notification messages | |
US20140096261A1 (en) | Method and apparatus for providing privacy policy for data stream | |
US9055020B2 (en) | Method and apparatus for sharing user information | |
US8880663B2 (en) | Method and apparatus for sharing user information | |
US20160132370A1 (en) | Method and apparatus for providing application notifications | |
US20140006616A1 (en) | Method and apparatus for categorizing application access requests on a device | |
US20150072663A1 (en) | Method and Apparatus for Providing Zone-Based Device Interaction | |
US20120254949A1 (en) | Method and apparatus for generating unique identifier values for applications and services | |
US20120110642A1 (en) | Method and apparatus for granting rights for content on a network service | |
US10475137B2 (en) | Method and apparatus for socially aware applications and application stores | |
US9246983B2 (en) | Method and apparatus for widget compatibility and transfer | |
US20130166555A1 (en) | Method and apparatus for managing contact data by utilizing social proximity information | |
US20120246336A1 (en) | Method and apparatus for providing context-based boundaries for service management | |
US20120302270A1 (en) | Method and apparatus for providing content providers for recommendation services | |
US9661451B2 (en) | Method and apparatus for providing an interface for triggering device action | |
US20140222855A1 (en) | Method and apparatus for measuring information associated with another device | |
US9313106B2 (en) | Method and apparatus for populating ad landing spots | |
US9313539B2 (en) | Method and apparatus for providing embedding of local identifiers | |
US20140122983A1 (en) | Method and apparatus for providing attribution to the creators of the components in a compound media | |
US20130097091A1 (en) | Method and apparatus for generating auditing specifications | |
US9684773B2 (en) | Method and apparatus for providing product leak source identifications |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NOKIA CORPORATION, FINLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:OLIVER, IAN JUSTIN;REEL/FRAME:044931/0829 Effective date: 20160425 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |