The systems and methods described below relate generally to the field of electronic content, and, more specifically, the systems and methods described below relate to the field of regulating access to shared electronic content.
Due in part to the proliferation of networked computing environments, electronic content in the form of documents, agreements, forms and like are increasingly transmitted between parties in electronic format. As the number of parties grows and the complexity of the interaction increases, there exists a need to manage and control the exchange of such electronic content.
In an embodiment, the present disclosure is directed, in part, to a computer-based method of sharing electronic content. The method comprises receiving, by an electronic content sharing system, electronic content, wherein the electronic content is associated with an originator and an electronic action. The method also comprises receiving, by the electronic content sharing system, one or more recipients, wherein the one or more recipients are each to individually perform the electronic action. The method also comprises providing, by the electronic content sharing system, the electronic content to the one or more recipients, wherein the provided content comprises a request to perform the electronic action. When the electronic action is performed by a first subset of one or more recipients, the electronic content is updated by the electronic content sharing system to reflect the performed electronic action, the updated electronic content is provided to the originator by the electronic content sharing system, and the updated electronic content is provided to a second subset of the one or more recipients by the electronic content sharing system.
In an embodiment, the present disclosure is directed, in part, to an electronic content sharing computing system for sharing electronic content between a plurality of users, the electronic content sharing computing system comprising one or more processors and one or more memory units. The one or more processors are configured to store a first electronic document received from a first user, wherein the first electronic document comprises first metadata identifying a first originator indicator, wherein the first originator indicator identifies the first user and a first recipient list, wherein the first recipient list identifies a second user and a third user. The one or more processors are configured to share the first electronic document with the second user as a second electronic document, wherein the second electronic document comprises second metadata identifying a second originator indicator, wherein the second originator indicator identifies the second user and a second recipient list. The second recipient list is automatically populated with the first user as identified by the first originator indicator, and the third user as identified by the first recipient list. Upon completion of an electronic action by the second user, the second electronic document is automatically shared with the first user and the third user as a third electronic document.
In an embodiment, the present disclosure is directed, in part, to a computer-based method of sharing electronic content. The method comprises hosting a user workspace, wherein the user workspaces identifies an electronic document, wherein the electronic documents is selectably sharable with a plurality of workspace members and the plurality of workspace members. Each of the plurality of workspace members have access to the electronic document, wherein the user workspace is centralized around the electronic document. When the electronic document is shared with an additional party, the number of workspace members identified by the user workspace is increased.
The systems and methods disclosed herein are described in detail by way of examples and with reference to the figures. It will be appreciated that modifications to disclosed and described examples, arrangements, configurations, components, elements, apparatuses, methods, systems, etc. can be made and may be desired for a specific application. In this disclosure, any identification of specific techniques, arrangements, etc. are either related to a specific example presented or are merely a general description of such a technique, arrangement, etc. Identifications of specific details or examples are not intended to be, and should not be, construed as mandatory or limiting unless specifically designated as such.
The systems, apparatus, and methods disclosed herein generally relate to the sharing and auto-sharing of electronic content along with regulating access of the electronic content to particular users, with selected examples disclosed and described in detail with reference made to
Throughout this disclosure, references to components or modules generally refer to items that logically can be grouped together to perform a function or group of related functions. Like reference numerals are generally intended to refer to the same or similar components. Components and modules can be implemented in software, hardware, or a combination of software and hardware. The term software is used expansively to include not only executable code, but also data structures, data stores and computing instructions in any electronic format, firmware, and embedded software. The terms information and data are used expansively and includes a wide variety of electronic information, including but not limited to machine-executable or machine-interpretable instructions; content such as text, video data, and audio data, among others; and various codes or flags. The terms information, data, and content are sometimes used interchangeably when permitted by context. It should be noted that although for clarity and to aid in understanding some examples discussed below might describe specific features or functions as part of a specific component or module, or as occurring at a specific layer of a computing device (for example, a hardware layer, operating system layer, or application layer), those features or functions can be implemented as part of a different component or module or at a different layer.
The examples discussed below are examples only and are provided to assist in the explanation of the apparatuses, devices, systems and methods described herein. None of the features or components shown in the drawings or discussed below should be taken as mandatory for any specific implementation of any of these the apparatuses, devices, systems or methods unless specifically designated as mandatory. For ease of reading and clarity, certain components, modules, or methods can be described solely in connection with a specific figure. Any failure to specifically describe a combination or sub-combination of components should not be understood as an indication that any combination or sub-combination is not possible. Also, for any methods described, regardless of whether the method is described in conjunction with a flow diagram, it should be understood that unless otherwise specified or required by context, any explicit or implicit ordering of steps performed in the execution of a method does not imply that those steps must be performed in the order presented but instead can be performed in a different order or in parallel.
The figures and accompanying detailed description generally describe an application, or “app,” that includes computer executable instructions capable of executing on a computing platform such as a desktop, laptop, tablet, mobile computing device, or other suitable hardware. The app can include software modules, processes, application programming interfaces or APIs, drivers, helper applications such as plug-ins, databases such as search and query databases, and other types of software modules or computer programming as would be understood in the art.
Reference throughout the specification to “various embodiments,” “some embodiments,” “one embodiment,” “some example embodiments,” “one example embodiment,” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in various embodiments,” “in some embodiments,” “in one embodiment,” “some example embodiments,” “one example embodiment,” or “in an embodiment” in places throughout the specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics can be combined in any suitable manner in one or more embodiments.
The presently disclosed embodiments are generally directed to the transferring of electronic content, such as virtual documents, between many different users that are virtually connected. This virtual connection can be based on, for example, a user's involvement with an online transaction, or other type of association between the users. Similar to commonly-used social networks, a first user may have a plurality of first degree connections, with each of those first degree connections having a plurality of connections. Those plurality of connections of each of the first degree connections can be considered second degree connections of the first user. It follows that the first user can be connected (directly or indirectly) to a large network of users. One of the uses of such a network is to share and collaborate, which can rely on the sharing of electronic content between various users within the network. The systems and methods described in more detail below generally relate to controlling the access to various forms of electronic content and controlling the virtual flow path of the electronic content through the network of users. In some embodiments, electronic content that is shared with a first group of users is automatically shared with a second group of users upon the satisfaction of one or more conditions.
By way of example, such systems and methods can be used during an online transaction that is facilitated by an online or virtual transaction platform. Such transaction could include negotiations and the exchanging terms sheets, contracts, or other content conveyed to various users in electronic format. As the transaction progresses the type of content being shared can change, as well as the particular users that need to interact with that content. Additionally, as the number of parties to the transaction increases, the process for regulating control and access to that content can become complex, especially if it is desired to limit access to the content.
In some example embodiments, content is shared by an originator to a number of users on a recipient list. The originator can, for example, selectively determine the users to include in the recipient list. In the case of an online transaction, the content can be a virtual document that is to be electronically signed by each user on the recipient list. In a real estate context, for example, the originator can be a realtor and the users on the recipient list can be buyers of real estate. When one of the buyers electronically signs the document, the system shares the signed document with the realtor and the other parties that originally received the document (i.e., the other buyers). Therefore, access to the updated content (i.e., a signed transactional document) can be limited to a subset of users that is determined based on the recipients of the originally shared content. It is noted that the determination of which party receives the signed document is not necessarily based on assigned roles of the parties, but instead the system can look to the original recipient list of the shared content. In fact, in some embodiments, the systems and methods described herein are agnostic to the particular roles of the particular users, and instead sharing decisions are made based purely on the share paths of the content.
Referring now to
The memory unit 114 can store executable software and data for a sharing engine 116. When the processor 112 of the electronic content sharing system 100 executes the software of the sharing engine 116, the processor 112 can be caused to perform the various operations of the electronic content sharing system 100, such as monitor the sharing of electronic content, store additional versions of electronic content, and auto share electronic content, as discussed in more detail below. Data used by the sharing engine 116 can be from various sources, such as a data store 118, which can be an electronic computer database, for example. The data stored in the data store 118 can be stored in a non-volatile computer memory, such as a hard disk drive, a read only memory (e.g., a ROM IC), or other types of non-volatile memory. Also, the data of the data store 118 can be stored on a remote electronic computer system, for example.
The electronic content sharing system 100 can be in communication with user devices 130A-N via an electronic communications network 132. The communications network 132 can include a number of computer and/or data networks, including the Internet, LANs, WANs, GPRS networks, etc., and can comprise wired and/or wireless communication links. The user devices 130A-N that communicate with the electronic content sharing system 100 can be any type of client device suitable for communication over the network 132, such as a personal computer, a laptop computer, a tablet computer, or a netbook computer, for example. In some example embodiments, a user can communicate with the network 132 via a device 130 that is a combination handheld computer and mobile telephone, sometimes referred to as a smart phone. It can be appreciated that while certain embodiments can be described with users communicating via a smart phone or laptop by way of example, the communication can be implemented using other types of user equipment or wireless computing devices such as a mobile telephone, personal digital assistant (PDA), combination mobile telephone/PDA, handheld device, mobile unit, subscriber station, game device, messaging device, media player, pager, or other suitable mobile communications devices.
The user devices 130A-N can provide a variety of applications for allowing a user to accomplish one or more specific tasks using the electronic content sharing system 100. Applications can include, without limitation, a web browser application (e.g., INTERNET EXPLORER, MOZILLA, FIREFOX, SAFARI, OPERA, NETSCAPE NAVIGATOR) telephone application (e.g., cellular, VoIP, PTT), networking application, messaging application (e.g., e-mail, IM, SMS, MMS, BLACKBERRY Messenger), contacts application, calendar application and so forth. The user device 130 can comprise various software programs such as system programs and applications to provide computing capabilities in accordance with the described embodiments. System programs can include, without limitation, an operating system (OS), device drivers, programming tools, utility programs, software libraries, application programming interfaces (APIs), and so forth. Exemplary operating systems can include, for example, a MICROSOFT OS, APPLE OS, UNIX OS, LINUX OS, and others.
In general, an application, such as a web browsing application, can provide a user interface to communicate information between the electronic content sharing system 100 and the users via the user devices 130A-N. The user devices 130A-N can include various components for interacting with the application such as a display for presenting the user interface and a keypad for inputting data and/or commands. The user devices 130A-N can include other components for use with one or more applications such as a stylus, a touch-sensitive screen, keys (e.g., input keys, preset and programmable hot keys), buttons (e.g., action buttons, a multidirectional navigation button, preset and programmable shortcut buttons), switches, a microphone, speakers, an audio headset, a camera, and so forth. Through the interface, the users can interact with the electronic content sharing system 100 (e.g., to share content, to review content, to perform actions related to the content, and so forth).
The applications can include or be implemented as executable computer program instructions stored on computer-readable storage media such as volatile or non-volatile memory capable of being retrieved and executed by a processor to provide operations for the user devices 130A-N. The memory can also store various databases and/or other types of data structures (e.g., arrays, files, tables, records) for storing data for use by the processor and/or other elements of the user devices 130A-N.
As shown in
The web server 122 can provide a graphical web user interface through which users of the system can interact with the electronic content sharing system 100. The web server 122 can accept requests, such as HTTP requests, from clients (such as web browsers on the user devices 130A-N), and serve the clients responses, such as HTTP responses, along with optional data content, such as web pages (e.g., HTML documents) and linked objects (such as images, etc.).
The application server 126 can provide a user interface for users who do not communicate with the electronic content sharing system 100 using a web browser. Such users can have special software installed on their user devices 130A-N that allows them to communicate with the application server 126 via the network 132. Such software can be downloaded, for example, from the electronic content sharing system 100, or other software application provider, over the network to such user devices 130A-N.
Although
The types or roles of Users A-N shown in
In the illustrated embodiment, User A is a lending institution which supplies shared content 212 to User B. For this example, the shared content 212 is a real estate sales contract and User B is a buyer's agent. Users C, D and E are buyers of real estate. User B shares content to Users C, D, and E, as illustrated by shared content′ 216, 224, 220, respectively. The shared content′ 216, 224, 220 in this example is the real estate sales contract that each User C, D, and E needs to electronically sign. Referring first to User C, upon signing the document (or taking any other action associated with the electronic content), the returned content′ is shared with the originator as well as the other recipients of the shared content′. Thus, returned content′ 218 is shared with User B, returned content′ 238 is shared with User D and returned content′ 232 is shared with User E, thereby informing each User B, D, and E that User C has electronically signed the real estate sales contract. User D's interaction with the system is similar to User C, since when User D completes the action associated with the shared content′ 224, the returned content′ 226, 242, 240 is shared with User B, User C, and User E, respectively.
In the illustrated embodiment User E also shares the shared content′ 220 with User F, as shown by shared content″ 228. User F can be, for example, an attorney that User E wants to review the sales contract. Once User F satisfies the requisite action associated with the shared content″ 228, the returned content″ 230 is shared with User E. It is noted that the returned content″ 230 is not shared with any other users, since User F was the only user to receive the originally shared content″ 228. With regard to action requested with the shared content′ 220, when User E completes that action, the returned content′ 222, 234, 236 is shared with User B, User C, and User D, respectively.
B1 is the first to sign the document, indicated by signature 510. At 512 a new version of the electronic content is stored that includes the signature of B1. This new version can be stored in data store 118 (
B2 is next to sign the document, indicated by signature 520. As such, the electronic document now contains the electronic signature of B1 and B2. At 522, a new version of the electronic content is stored that includes the signature of B1 and B2 and the system automatically shares the signed version of the electronic content with BA (the originator) as well as B1 and B3 (the other recipients of the originally shared content) at 524, 526, and 528, respectively.
B3 is next to sign the document, indicated by signature 530. As such, the electronic document now contains the electronic signature of B1, B2 and B3. At 532 a new version of the electronic content is stored that includes the signature of B1, B2 and B3 and the system automatically shares the signed version of the electronic content with BA (the originator) as well as B1 and B2 (the other recipients of the originally shared content) at 538, 536, and 534, respectively.
In some embodiments, the sharing of the signed documents at 514, 516, 518, 524, 526, 528, 534, 536, and 538 automatically occurs subsequent to the completion of a particular action (i.e., the providing of an electronic signature). Thus, this type of sharing is sometimes referred to as “boomeranging” or “auto sharing,” as the electronic content sharing system can automatically route the completed document to the appropriate parties without necessarily requiring further directives from the users to facilitate such sharing. It is noted that in the embodiments illustrated herein, the particular role of a user does not control how content is “boomeranged.” Instead, the systems and methods described herein monitor the historical sharing paths of the content to determine the recipients of any autoshared content.
B3 is the first to sign the document, indicated by signature 610. At 612 a new version of the electronic content is stored that includes the signature of B3 and the system automatically shares the signed version of the electronic content with BA (the originator) as well as B1 and B2 (the other recipients of the originally shared content) at 618, 616, and 614, respectively.
B1 is next to sign the document, indicated by signature 620. As such, the electronic document now contains the electronic signature of B1 and B3. At 622 a new version of the electronic content is stored that includes the signature of B1 and B3 and the system automatically shares the signed version of the electronic content with BA (the originator) as well as B2 and B3 (the other recipients of the originally shared content) at 624, 626, and 628, respectively.
B2 is next to sign the document, indicated by signature 630. As such, the electronic document now contains the electronic signature of B1, B2 and B3. At 632 a new version of the electronic content is stored that includes the signature of B1, B2 and B3 and the system automatically shares the signed version of the electronic content with BA (the originator) as well as B1 and B3 (the other recipients of the originally shared content) at 634, 636, and 638, respectively.
B1 is the first to sign the document, indicated by signature 708. At 710 a new version of the electronic content is stored that includes the signature of B1 and the system automatically shares the signed version of the electronic content with BA (the originator) as well as B2 at 712 and 714. Additionally, B1 indicates that the electronic content is to be shared with P3, as indicated by share 716.
B2 is next to sign the document, indicated by signature 718. As such, the electronic document now contains the electronic signature of B1 and B2. At 720 a new version of the electronic content is stored that includes the signature of B1 and B2 and the system automatically shares the signed version of the electronic content with BA (the originator) as well as B1 and B3 at 722, 724, and 726, respectively.
P3 is next to sign the document, indicated by signature 728. As such, the electronic document now contains the electronic signature of B1, B2 and P3. At 730 a new version of the electronic content is stored that includes the signature of B1, B2 and P3 and the system automatically shares the signed version of the electronic content with B1 (the originator) as well as BA and B2 (the other recipients of the content originally shared by B1) at 734, 734, and 732, respectively.
Computer-based electronic content sharing systems in accordance with the present disclosure, such as the computer-based electronic content sharing system 100 of
The electronic content sharing system can, for example, utilize various electronic content sharing schemes, such as the sharing scheme illustrated in
The electronic content sharing system can host a plurality of collaborative environments, which can be referred as “loops,” for users of the system. A particular loop can include a plurality of users and a variety of electronic content. For the purposes of illustration, the electronic content is largely described in the context of an electronic document, although this disclosure is not so limited. The electronic content sharing system can facilitates collaboration over a data layer of the electronic document. The data layer can be for example, negotiation terms, written content, or any other type of content that can require input, approval or inspection by a plurality of parties. In some embodiments, the electronic document remains private to a particular user until that user shares the electronic document with one or more users. Once the electronic content is shared with another user, at that point, a loop is hosted between that the users that are sharing that electronic document.
The electronic content sharing system can facilitate electronic conversations, messaging, or other forms of notifications between users. This communication may occur within an interface of the electronic content sharing system and/or it may be pushed to various electronic devices of the users, such as in the form of text messaging, multi-media messages, instant messages, and so forth. The communications and the interactions with the data layer of the electronic document may be optionally tracked as part of an audit trail associated with that particular electronic document.
In association with the shared electronic content, the electronic content sharing system can generate one or more tasks. The tasks can be supplied by a user, or may be auto-generated based on the underlying content. For example, in the context of a legal contract which requires a signature, a task can be generated associated with the required parties supplying their electronic signatures. As those parties interact with the electronic content sharing system after being invited into the appropriate loop, they can supply their signature to the electronic document.
As the various users interact with their loops, in some embodiments, logs can be generated and maintained by the electronic content sharing system. Various types of logs can be generated. For example, the log can be centric to a particular user, centric to a particular loop, centric to a particular workspace, centric to particular electronic content, centric to a particular group of users, among a variety of other types of logs.
Referring now to
The electronic content sharing systems described herein are configured to allow users to easily share electronic content and track interactions with the shared electronic content such that a virtual collaborative environment surrounding the electronic content is created. In this regard, users of the system can optionally share content to others users, as well as access content that is received from other users.
The workspace H also has an electronic content repository which is used to stored electronic content on behalf of user H. In
The above descriptions of various components and methods are intended to illustrate specific examples and describe certain ways of making and using the systems disclosed and described here. These descriptions are neither intended to be nor should be taken as an exhaustive list of the possible ways in which these systems and modules can be made and used. A number of modifications, including substitutions of systems and modules between or among examples and variations among combinations can be made. Those modifications and variations should be apparent to those of ordinary skill in this area after having read this document.
This application is a continuation of U.S. patent application Ser. No. 14/177,656 entitled “ELECTRONIC CONTENT SHARING,” filed Feb. 11, 2014, which claims priority to U.S. Provisional Patent Application No. 61/875,352 entitled “ELECTRONIC CONTENT SHARING,” filed Sep. 9, 2013, and U.S. Provisional Patent Application No. 61/763,278 entitled “ELECTRONIC CONTENT SHARING,” filed Feb. 11, 2013, the disclosures of which are both incorporated herein by reference in their entireties.
Number | Name | Date | Kind |
---|---|---|---|
4747093 | Benne et al. | May 1988 | A |
4870576 | Tornetta | Sep 1989 | A |
5032989 | Tornetta | Jul 1991 | A |
D321903 | Chepaitis | Nov 1991 | S |
5317646 | Sant et al. | May 1994 | A |
5325297 | Bird et al. | Jun 1994 | A |
5361201 | Jost | Nov 1994 | A |
5392388 | Gibson | Feb 1995 | A |
5526341 | Shiba et al. | Jun 1996 | A |
5623655 | Chisaka | Apr 1997 | A |
5680305 | Apgar | Oct 1997 | A |
5754850 | Janssen | May 1998 | A |
D396455 | Bier | Jul 1998 | S |
5848187 | Bricklin et al. | Dec 1998 | A |
5943679 | Niles | Aug 1999 | A |
5946667 | Tull | Aug 1999 | A |
6032123 | Jameson | Feb 2000 | A |
6067831 | Hoyt et al. | May 2000 | A |
6289460 | Hajmiragha | Nov 2001 | B1 |
6401070 | McManus | Jun 2002 | B1 |
6519618 | Snyder | Feb 2003 | B1 |
D474197 | Nguyen | May 2003 | S |
D477242 | Laats | Jul 2003 | S |
6594633 | Broeman | Jul 2003 | B1 |
6609109 | Bradley | Aug 2003 | B1 |
6609118 | Khedkar | Aug 2003 | B1 |
6636803 | Hartz | Oct 2003 | B1 |
6651217 | Kennedy et al. | Nov 2003 | B1 |
6684196 | Mini et al. | Jan 2004 | B1 |
6711554 | Salzamann et al. | Mar 2004 | B1 |
6810404 | Ferguson et al. | Oct 2004 | B1 |
6898317 | Struble et al. | May 2005 | B2 |
6920455 | Wescheler | Jul 2005 | B1 |
6944648 | Dochran et al. | Sep 2005 | B2 |
D521019 | Ording | May 2006 | S |
7143290 | Ginter et al. | Nov 2006 | B1 |
D536343 | Fong et al. | Feb 2007 | S |
D544495 | Evans et al. | Jun 2007 | S |
7228319 | Fuchs | Jun 2007 | B1 |
D554660 | Hoover et al. | Nov 2007 | S |
D554661 | Hoover et al. | Nov 2007 | S |
7299408 | Daconta et al. | Nov 2007 | B1 |
7334187 | Stanciu | Feb 2008 | B1 |
D566722 | Jackson | Apr 2008 | S |
7376891 | Hitchock et al. | May 2008 | B2 |
D572726 | Guimaraes et al. | Jul 2008 | S |
7475333 | Otter et al. | Jan 2009 | B2 |
D591305 | Shimoda | Apr 2009 | S |
7543228 | Kelkar et al. | Jun 2009 | B2 |
D595727 | Koes et al. | Jul 2009 | S |
D599284 | Misumi | Sep 2009 | S |
D599814 | Ogura et al. | Sep 2009 | S |
D601159 | Truelove et al. | Sep 2009 | S |
7692635 | Iwamura | Apr 2010 | B2 |
7702999 | Sperr et al. | Apr 2010 | B1 |
D615551 | Arnell | May 2010 | S |
7725359 | Katzfey et al. | May 2010 | B1 |
D619593 | Fujioka et al. | Jul 2010 | S |
7765125 | An | Jul 2010 | B1 |
D624557 | Allen et al. | Sep 2010 | S |
7818219 | Klivington et al. | Oct 2010 | B2 |
7822691 | Kuo | Oct 2010 | B1 |
7917842 | Garrison | Mar 2011 | B2 |
7945496 | Trott | May 2011 | B2 |
7970684 | Benda | Jun 2011 | B1 |
7987117 | Mozley | Jul 2011 | B2 |
D643047 | Guss et al. | Aug 2011 | S |
D644243 | Matas | Aug 2011 | S |
D644654 | Maitlen et al. | Sep 2011 | S |
D650790 | Jeans et al. | Dec 2011 | S |
D650807 | Impas et al. | Dec 2011 | S |
D652426 | Anzures | Jan 2012 | S |
D654925 | Nishizawa et al. | Feb 2012 | S |
8145909 | Agrawal | Mar 2012 | B1 |
D656954 | Arnold et al. | Apr 2012 | S |
8151209 | Law et al. | Apr 2012 | B2 |
D659711 | Guss et al. | May 2012 | S |
D660317 | Jesberger | May 2012 | S |
D664205 | Xu et al. | Jul 2012 | S |
D665161 | Leifeld et al. | Aug 2012 | S |
D665162 | Leifeld et al. | Aug 2012 | S |
D665163 | Leifeld et al. | Aug 2012 | S |
D665421 | Morrow et al. | Aug 2012 | S |
8239496 | Peterson et al. | Aug 2012 | B2 |
D667429 | Wujcik et al. | Sep 2012 | S |
D669497 | Lee et al. | Oct 2012 | S |
D669499 | Gardner et al. | Oct 2012 | S |
D671558 | Anzures et al. | Nov 2012 | S |
D676060 | Frost et al. | Feb 2013 | S |
D676457 | Frost et al. | Feb 2013 | S |
8375016 | Allison | Feb 2013 | B2 |
D677180 | Plitkins et al. | Mar 2013 | S |
D682305 | Mierau et al. | May 2013 | S |
D682882 | Cahill et al. | May 2013 | S |
D683757 | Phelan | Jun 2013 | S |
D684185 | Van Dongen et al. | Jun 2013 | S |
D684990 | Walsh | Jun 2013 | S |
D687046 | Plitkins et al. | Jul 2013 | S |
D687057 | Plitkins | Jul 2013 | S |
D687460 | Tyler et al. | Aug 2013 | S |
D687851 | Sloo et al. | Aug 2013 | S |
D689505 | Convay et al. | Sep 2013 | S |
D690717 | Thomsen et al. | Oct 2013 | S |
D690718 | Thomsen et al. | Oct 2013 | S |
D691629 | Matas et al. | Oct 2013 | S |
D692444 | Lee et al. | Oct 2013 | S |
8583562 | McDaniel | Nov 2013 | B1 |
8589191 | Menzies | Nov 2013 | B1 |
D696265 | d'Amore et al. | Dec 2013 | S |
D697076 | Oda et al. | Jan 2014 | S |
D697518 | Thomsen et al. | Jan 2014 | S |
D697519 | Thomsen et al. | Jan 2014 | S |
D697935 | Lee et al. | Jan 2014 | S |
D698363 | Asai | Jan 2014 | S |
D699248 | Pearson et al. | Feb 2014 | S |
D699250 | Fuji et al. | Feb 2014 | S |
D699741 | Wantland et al. | Feb 2014 | S |
D699750 | Pearson et al. | Feb 2014 | S |
D700207 | Pearson et al. | Feb 2014 | S |
8650067 | Moss | Feb 2014 | B1 |
8683315 | Stover | Mar 2014 | B2 |
D703683 | Skidgel | Apr 2014 | S |
D704204 | Rydenhag | May 2014 | S |
D705263 | Hartley | May 2014 | S |
D705808 | Anzures et al. | May 2014 | S |
D706814 | Phelan | Jun 2014 | S |
D707705 | Folken et al. | Jun 2014 | S |
D708203 | Johnson | Jul 2014 | S |
D708221 | Danton et al. | Jul 2014 | S |
D708226 | Takata et al. | Jul 2014 | S |
D709917 | Faulkner et al. | Jul 2014 | S |
D711421 | Bautista | Aug 2014 | S |
D715313 | Hontz, Jr. | Oct 2014 | S |
D715322 | Sakata | Oct 2014 | S |
D716325 | Brudnicki | Oct 2014 | S |
D717334 | Sakuma | Nov 2014 | S |
D717335 | Sakuma | Nov 2014 | S |
D717681 | Shail et al. | Nov 2014 | S |
D717822 | Brotman et al. | Nov 2014 | S |
D717823 | Brotman et al. | Nov 2014 | S |
D718325 | Schoger et al. | Nov 2014 | S |
D721090 | Hong et al. | Jan 2015 | S |
D721093 | Pereira | Jan 2015 | S |
9330375 | Allison | May 2016 | B2 |
9575622 | Allison et al. | Feb 2017 | B1 |
9785627 | Campanelli et al. | Oct 2017 | B2 |
9858548 | Allison | Jan 2018 | B2 |
10062110 | Tatang | Aug 2018 | B1 |
10108928 | Allison | Oct 2018 | B2 |
10552525 | Allison | Feb 2020 | B1 |
10733364 | Allison | Aug 2020 | B1 |
10976885 | Allison | Apr 2021 | B2 |
20010039506 | Robbins | Nov 2001 | A1 |
20020035520 | Weiss | Mar 2002 | A1 |
20020065739 | Florance | May 2002 | A1 |
20020069358 | Silvester | Jun 2002 | A1 |
20020082849 | Tenorio | Jun 2002 | A1 |
20020087389 | Sklarz | Jul 2002 | A1 |
20020099733 | Teruuchi et al. | Jul 2002 | A1 |
20020129656 | Conant et al. | Sep 2002 | A1 |
20020135440 | Ryhanen | Sep 2002 | A1 |
20020184485 | Dray, Jr. et al. | Dec 2002 | A1 |
20030046639 | Fai et al. | Mar 2003 | A1 |
20030056100 | Beatson | Mar 2003 | A1 |
20030101063 | Sexton | May 2003 | A1 |
20030121008 | Tischer | Jun 2003 | A1 |
20030191719 | Ginter et al. | Oct 2003 | A1 |
20030220807 | Hoffmna | Nov 2003 | A1 |
20030227482 | Bach et al. | Dec 2003 | A1 |
20030229552 | Lebaric | Dec 2003 | A1 |
20030236832 | McIntyre | Dec 2003 | A1 |
20040098284 | Petito et al. | May 2004 | A1 |
20040128215 | Florance | Jul 2004 | A1 |
20040133493 | Ford et al. | Jul 2004 | A1 |
20040181749 | Chellapilla | Sep 2004 | A1 |
20040205534 | Koelle | Oct 2004 | A1 |
20040205653 | Hadfield et al. | Oct 2004 | A1 |
20040220885 | Salzmann et al. | Nov 2004 | A1 |
20040225884 | Lorenzini et al. | Nov 2004 | A1 |
20040255114 | Lee et al. | Dec 2004 | A1 |
20050086596 | Koch et al. | Apr 2005 | A1 |
20050108025 | Cagan | May 2005 | A1 |
20050177389 | Rakowicz et al. | Aug 2005 | A1 |
20050192930 | Hightower et al. | Sep 2005 | A1 |
20050251535 | Theissen et al. | Nov 2005 | A1 |
20050273417 | Budish | Dec 2005 | A1 |
20060007189 | Gaines | Jan 2006 | A1 |
20060015435 | Nathanson | Jan 2006 | A1 |
20060026032 | Higgins | Feb 2006 | A1 |
20060026136 | Drucker et al. | Feb 2006 | A1 |
20060069599 | Hatoun | Mar 2006 | A1 |
20060085311 | Hoerle et al. | Apr 2006 | A1 |
20060116952 | Orfano | Jun 2006 | A1 |
20060149567 | Muller et al. | Jul 2006 | A1 |
20060190810 | Piersol | Aug 2006 | A1 |
20060200308 | Arutunian | Sep 2006 | A1 |
20060259440 | Daryl et al. | Nov 2006 | A1 |
20070005383 | Kasower | Jan 2007 | A1 |
20070009158 | Geva et al. | Jan 2007 | A1 |
20070022141 | Singleton | Jan 2007 | A1 |
20070038533 | Huff | Feb 2007 | A1 |
20070088958 | Qa Im-mapami | Apr 2007 | A1 |
20070118391 | Malaney | May 2007 | A1 |
20070136361 | Jae et al. | Jun 2007 | A1 |
20070136679 | Yang | Jun 2007 | A1 |
20070168382 | Tillberg | Jul 2007 | A1 |
20070179881 | Lord | Aug 2007 | A1 |
20070186157 | Walker | Aug 2007 | A1 |
20070198952 | Pittenger et al. | Aug 2007 | A1 |
20070255625 | Katzen | Nov 2007 | A1 |
20080091700 | Brotherson | Apr 2008 | A1 |
20080091954 | Morris et al. | Apr 2008 | A1 |
20080097777 | Rielo | Apr 2008 | A1 |
20080133319 | Adiga | Jun 2008 | A1 |
20080154740 | Lee et al. | Jun 2008 | A1 |
20080155391 | Sattler et al. | Jun 2008 | A1 |
20080167941 | Kagarlis | Jul 2008 | A1 |
20080209313 | Gonser | Aug 2008 | A1 |
20080260287 | Berryman et al. | Oct 2008 | A1 |
20080262833 | Kano et al. | Oct 2008 | A1 |
20080288312 | Miles | Nov 2008 | A1 |
20080301064 | Burns | Dec 2008 | A1 |
20080319890 | Urbanski | Dec 2008 | A1 |
20090003588 | Ross | Jan 2009 | A1 |
20090006241 | Zhao | Jan 2009 | A1 |
20090018975 | Geltner | Jan 2009 | A1 |
20090024912 | McCabe et al. | Jan 2009 | A1 |
20090025087 | Perison et al. | Jan 2009 | A1 |
20090043685 | Benjamin | Feb 2009 | A1 |
20090109455 | Smith et al. | Apr 2009 | A1 |
20090173552 | Elder et al. | Jul 2009 | A1 |
20090192862 | Hoggard | Jul 2009 | A1 |
20090226090 | Okita | Sep 2009 | A1 |
20090029786 | McCabe et al. | Nov 2009 | A1 |
20090320035 | Ahlgren | Dec 2009 | A1 |
20100011286 | Isoda | Jan 2010 | A1 |
20100023379 | Rappaport | Jan 2010 | A1 |
20100057538 | Hardman | Mar 2010 | A1 |
20100076903 | Klingenberg | Mar 2010 | A1 |
20100131331 | Ginsburg | May 2010 | A1 |
20100161460 | Vroom et al. | Jun 2010 | A1 |
20100161498 | Walker | Jun 2010 | A1 |
20100235727 | Ashton et al. | Sep 2010 | A1 |
20100287260 | Peterson et al. | Nov 2010 | A1 |
20110026828 | Balasubramanian et al. | Feb 2011 | A1 |
20110178905 | Kagarlis | Jul 2011 | A1 |
20110199631 | Healy | Aug 2011 | A1 |
20110258535 | Alder et al. | Oct 2011 | A1 |
20110270766 | Ramakrishnan et al. | Nov 2011 | A1 |
20110271173 | Ait-Mokhar et al. | Nov 2011 | A1 |
20110276395 | Gaton et al. | Nov 2011 | A1 |
20110276875 | McCabe et al. | Nov 2011 | A1 |
20110313945 | Callan | Dec 2011 | A1 |
20110314371 | Peterson et al. | Dec 2011 | A1 |
20120063684 | Denoue | Mar 2012 | A1 |
20120066061 | Clement | Mar 2012 | A1 |
20120096383 | Sakamoto et al. | Apr 2012 | A1 |
20120102002 | Sathyanarayana | Apr 2012 | A1 |
20120102412 | Sinclair et al. | Apr 2012 | A1 |
20120144285 | Bach et al. | Jun 2012 | A1 |
20120209875 | Hintze | Aug 2012 | A1 |
20120254045 | Orfano | Oct 2012 | A1 |
20120254156 | Rao | Oct 2012 | A1 |
20120297277 | King | Nov 2012 | A1 |
20120297301 | Mahoney | Nov 2012 | A1 |
20130024788 | Olsen et al. | Jan 2013 | A1 |
20130036347 | Eftekhari et al. | Feb 2013 | A1 |
20130086624 | Powell | Apr 2013 | A1 |
20130096819 | Tarnok | Apr 2013 | A1 |
20130185753 | Kliot | Jul 2013 | A1 |
20130211945 | Po-Ching | Aug 2013 | A1 |
20130238965 | Barrus | Sep 2013 | A1 |
20130297442 | Simons | Nov 2013 | A1 |
20130317939 | Urbanski | Nov 2013 | A1 |
20130325623 | Balduf | Dec 2013 | A1 |
20130325665 | Shaffer | Dec 2013 | A1 |
20130346151 | Bleakley | Dec 2013 | A1 |
20140033088 | Shaver | Jan 2014 | A1 |
20140164255 | Daly | Jun 2014 | A1 |
20140164260 | Spieckerman | Jun 2014 | A1 |
20140236751 | Bloomfield | Aug 2014 | A1 |
20150081497 | Patel | Mar 2015 | A1 |
20150242747 | Packes | Aug 2015 | A1 |
20150317701 | Thomas | Nov 2015 | A1 |
20150332371 | Lomas | Nov 2015 | A1 |
20160232629 | Allison | Aug 2016 | A1 |
20180225593 | Cozine | Aug 2018 | A1 |
20190034879 | Allison | Jan 2019 | A1 |
Number | Date | Country |
---|---|---|
1020020092595 | Dec 2002 | KR |
1020070059931 | Jun 2007 | KR |
96007156 | Mar 1996 | WO |
0106416 | Jan 2001 | WO |
2009012475 | Jan 2009 | WO |
201056262 | Sep 2010 | WO |
2010151630 | Dec 2010 | WO |
2011056819 | May 2011 | WO |
2011139563 | Nov 2011 | WO |
Entry |
---|
Adobe Acrobat DC, “Convert existing forms to fillable PDFs,” 2015, 12 pages. |
Adobe Acrobat XI, “Convert an existing form into a fillable PDF form with Adobe Acrobat XI,” Quick Start Guide, 2012, 1 page. |
Corrected Notice of Allowance for U.S. Appl. No. 14/620,262; dated Dec. 23, 2019; 12 pages. |
“E-Signature Custom Signature Fonts,” http:/www.e-signature.com/en/prod01_en.htm, Mar. 28, 2006, 4pages. |
FH FA, “House Price Index Frequently Asked Questions,” Federal Housing Finance Agency, Aug. 2018, available at https://www .fhfa.gov/Media/PublicAffairs/Pages/House-Price-Index-Frequently-Asked-Questions.aspx (accessed Oct. 29, 2018). (Year: 2018). |
Final Office Action for U.S. Appl. No. 14/177,656; dated Oct. 18, 2018; 30 pages. |
Final Office Action for U.S. Appl. No. 14/177,656; dated Dec. 28, 2017; 25 pages. |
Final Office Action for U.S. Appl. No. 14/620,262; dated Jun. 20, 2018; 18 pages. |
Final Office Action for U.S. Appl. No. 14/842,267; dated May 21, 2018; 25 pages. |
Final Office Action for U.S. Appl. No. 14/842,267; dated Sep. 19, 2019; 33 pages. |
Final Office Action for U.S. Appl. No. 15/131,747; dated Jun. 14, 2019; 14 pages. |
Final Office Action for U.S. Appl. No. 15/131,747; dated Jun. 25, 2021; 14 pages. |
Final Office Action for U.S. Appl. No. 15/135,398; dated Jun. 10, 2019; 99 pages. |
Final Office Action for U.S. Appl. No. 15/135,398; dated May 15, 2020; 94 pages. |
Final Office Action for U.S. Appl. No. 15/135,398; dated Aug. 19, 2021; 24 pages. |
Final Office Action for U.S. Appl. No. 15/131,747; dated Jul. 10, 2020; 43 pages. |
Final Office Action for U.S. Appl. No. 15/436,617; dated Feb. 27, 2020; 34 pages. |
Final Office Action for U.S. Appl. No. 15/436,617; dated Jul. 3, 2019; 21 pages. |
Final Office Action for U.S. Appl. No. 15/436,617; dated Sep. 21, 2020; 26 pages. |
Final Office Action for U.S. Appl. No. 16/135,282; dated Feb. 6, 2020; 15 pages. |
International Search Report dated Feb. 22, 2010 for Application No. PCT/US2009/061012. |
International Search Report, PCT/US2010/039768, dated Feb. 23, 2011, 4 pages. |
International Search Report, PCT/US2011/033194, dated Nov. 28, 2011, 4 pages. |
International Search Report, PCT/US2011/040218, dated Feb. 17, 2012, 3 pages. |
International Search Report; PCT/US2012/046386; dated Oct. 5, 2012; 2 pages. |
Kiplinger Personal Finance, “Before Submitting a Home Offer, Make Sure All Bases Are Covered,” Jan. 2015, available at https ://www.kiplinger.com/article/real-estate/T029-COOO-SOO 1-6-ways-to-stage-your-home-for-less-than-1-000 .html (access Oct. 28, 2018). |
Non-Final Office Action for U.S. Appl. No. 13/547,120; dated Nov. 1, 2017; 14 pages. |
Non-Final Office Action for U.S. Appl. No. 14/177,656; dated Apr. 19, 2019; 31 pages. |
Non-Final Office Action for U.S. Appl. No. 14/177,656; dated Apr. 4, 2018; 28 pages. |
Non-Final Office Action for U.S. Appl. No. 14/620,262; dated Dec. 31, 2018; 18 pages. |
Non-Final Office Action for U.S. Appl. No. 14/620,262; dated Dec. 7, 2017; 18 pages. |
Non-Final Office Action for U.S. Appl. No. 14/842,267; dated Jun. 17, 2019; 30 pages. |
Non-Final Office Action for U.S. Appl. No. 15/131,747; dated Feb. 5, 2018; 38 pages. |
Non-Final Office Action for U.S. Appl. No. 15/131,747; dated Jan. 9, 2020; 37 pages. |
Non-Final Office Action for U.S. Appl. No. 15/131,747; dated Sep. 7, 2018; 38 pages. |
Non-Final Office Action for U.S. Appl. No. 15/131,747; dated Nov. 25, 2020; 81 pages. |
Non-Final Office Action for U.S. Appl. No. 15/135,398; dated Nov. 7, 2018; 99 pages. |
Non-Final Office Action for U.S. Appl. No. 15/135,398; dated Dec. 26, 2019; 90 pages. |
Non-Final Office Action for U.S. Appl. No. 15/135,398; dated Apr. 19, 2021; 28 pages. |
Non-Final Office Action for U.S. Appl. No. 15/436,617; dated Oct. 23, 2019; 24 pages. |
Non-Final Office Action for U.S. Appl. No. 15/436,617; dated Jun. 15, 2020; 12 pages. |
Non-Final Office Action for U.S. Appl. No. 15/436,617; dated Nov. 28, 2018; 16 pages. |
Non-Final Office Action for U.S. Appl. No. 15/436,617; dated Mar. 13, 2019; 20 pages. |
Non-Final Office Action for U.S. Appl. No. 16/135,282; dated Aug. 22, 2019; 14 pages. |
Non-Final Office Action for U.S. Appl. No. 16/135,282; dated Nov. 30, 2020; 15 pages. |
Notice of Allowance for U.S. Appl. No. 15/436,617; dated Dec. 9, 2020; 8 pages. |
Notice of Allowance for U.S. Appl. No. 13/547,120; dated Jun. 28, 2018; 10 pages. |
Notice of Allowance for U.S. Appl. No. 14/177,656; dated Apr. 17, 2020; 9 pages. |
Notice of Allowance for U.S. Appl. No. 14/620,262; dated Sep. 23, 2019; 12 pages. |
Notice of Allowance for U.S. Appl. No. 14/842,267; dated Apr. 1, 2020; 14 pages. |
Notice of Allowance for U.S. Appl. No. 14/177,656; dated Jun. 24, 2020; 9 pages. |
Nuance, Power PDF How To: Create Fillable PDF Form, “How to get started, and get more out of your PDF's,” 4 pages. |
Written Opinion of the International Searching Authority, PCT/US2008/070566, dated Feb. 19, 2009, 4 pages. |
Written Opinion of the International Searching Authority; PCT/US2012/046386; dated Oct. 5, 2012; 7 pages. |
U.S. Appl. No. 15/135,398 for Allison, filed Apr. 21, 2016. |
U.S. Appl. No. 16/911,122 for Allison, filed Jun. 24, 2020. |
U.S. Appl. No. 17/194,651 for Allison, filed Mar. 8, 2021. |
U.S. Appl. No. 17/401,928 for Allison, filed Aug. 13, 2021. |
Number | Date | Country | |
---|---|---|---|
61875352 | Sep 2013 | US | |
61763278 | Feb 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14177656 | Feb 2014 | US |
Child | 17022644 | US |