Patent Grant
9245064
1. The Field of the Invention
The present invention relates generally to computer-aided design or drafting software.
2. Background and Relevant Art
Many industries use computer-aided design (“CAD”) software (such as AUTOCAD, REVIT, 3DS MAX, SKETCHUP) to design and create three-dimensional computer models. Increasingly, users of conventional design software utilize this software to display three-dimensional models to clients, investors, and other individuals. The conventional focus of many conventional design software programs is on designing and creating three-dimensional computer models, and not on displaying, navigating, and sharing the three-dimensional models. As such, some conventional design software programs make displaying, navigating, and sharing the three-dimensional models difficult, inefficient, or ineffective.
For example, some conventional design software may render three-dimensional models for display that do not have a realistic appearance. In particular, the version of the three-dimensional model rendered by the conventional design software may not incorporate the full details of the three-dimensional model. For example, the rendered version of the model may not include details such as shading, color, finish, and transparency. Conventional design software that is able to create a realistic appearance by rendering and displaying sufficient details of a three-dimensional model can tend to require an excessive amount of computing power and time to display and navigate.
In addition, the navigational control tools that some conventional design software programs use to view three-dimensional models may not be natural or intuitive. The absence of intuitive navigational control tools in some conventional design software can make viewing and appreciating all aspects of a three-dimensional design difficult or time consuming. One will appreciate that the lack intuitive navigational control tools can make it particularly difficult for a person unfamiliar with the software (i.e., clients, investors) to navigate a three-dimensional model quickly and effectively.
Conventional design software can also have limited ability to share three-dimensional models with individuals that are not in the same location as the designer. For example, some conventional design software requires the designer to save or export the model into a file and send file (e.g., by email) to a desired viewer. The size alone of some three-dimensional model files can make transferring and sharing of the model difficult.
Additionally, in order to open and view the three-dimensional model file, the viewer is often required to own and have installed on his or her computer the same software as the designer. Often, it is not practical for all desired viewers of a particular design to have the same design software. This is due, in part, to the fact that conventional design software can be rather expensive, the viewer may not be in the design business, or the viewer simply prefers a brand of design software that is not the same as the designer's.
Furthermore, even in the event that the desired viewer has the same design software as the designer, the designer may not want to provide others with a digital copy of the three-dimensional model. For instance, when sharing a three-dimensional model using some conventional design software, the saved or exported computer design file can contain the visual aspects of the design as well as proprietary data concerning the design. One will appreciate that sharing all of the data associated with a three-dimensional model can be undesirable because the data could easily be misappropriated by a viewer. Moreover, the viewer may also have the ability to make edits to the design data, thereby changing the design and the designer's original intent.
In order to avoid the security risks associated with conventional design software, including those identified above, many designers resort to simply capturing a limited number of selected static views of a three-dimensional model. In some cases, these views can be combined into a video file. The designers might then provide copies of the static views or the video file, either electronically or by hard copy, to the desired viewers. While sharing static images or a video of a three-dimensional model may resolve some of the complications and risks associated with conventional design software, there can be drawbacks with sharing only certain views of a three-dimensional model. For example, the viewer cannot navigate through the three-dimensional model and see all of the different angles and lines that would be possible with a three-dimensional computer model.
According, there are a number of problems in the art that can be addressed.
Implementations of the present invention overcome one or more problems in the art with systems, methods, and apparatus configured to allow easy and efficient rendering, displaying, navigation, and/or sharing of computer generated designs and models. In particular, one or more implementations of the present invention provide the ability to capture the geometry and the graphical attributes of a three-dimensional model. One or more implementations also allow for easy and intuitive navigation of the captured geometry. Additionally, one or more implementations allow a user to share the geometry and the graphical attributes of a three-dimensional model without sharing the source file or proprietary details of the source file. Furthermore, one or more implementations can allow for sharing of the geometry and graphical attributes of a three-dimensional model without requiring the viewer to have the software used to create the three-dimensional model.
For example, a computer program storage product can have computer-executable instructions stored thereon that, when executed, cause one or more processors to perform acts of identifying one or more files corresponding to a three-dimensional computer model created by a design software application and stored within a database associated with the design software application. The acts can additionally involve identifying geometry data and graphical aspect data of the three-dimensional computer model in the one or more files. Additionally, the acts can involve extracting the geometry data and graphical aspect data from the one or more files corresponding to the three-dimensional computer model. Also, the acts can involve storing the geometry data and graphical aspect data in a storage module unassociated with the design software application. Furthermore, the acts can involve providing an accurate three-dimensional view of the geometry and graphical aspects of the three-dimensional computer model at a display device using a capture and render software application unassociated with the design software application.
Additionally, a method from the perspective of a web server can involve receiving, from a first remote client computer system, geometry data and graphical aspect data extracted from a three-dimensional computer model created using a design software application. The method can also involve storing the geometry data and graphical aspect data in one or more geometric computer model files at a web server. Furthermore, the method can involve receiving one or more requests for the one or more geometric computer model files from a second remote client computer system. Also, the method can involve sending the one or more geometric computer model files and one or more viewer application files from the web server to the second remote client computer system. The one or more viewer application files can be configured to launch a temporary viewer application on the second remote client computer system. The temporary viewer application is configured to display the geometry data and graphical aspect data of the one or more geometric computer model files.
In addition to the foregoing, a method from the perspective of a client computer system can involve sending one or more requests to a web server for one or more geometric computer model files comprising geometry data and graphical aspect data extracted from a three-dimensional computer model created using a design software application. Also, the method can involve opening a temporary viewer application hosted by the web server. The method can additionally involve receiving the one or more geometric computer model files from the web server. Furthermore, the method can involve displaying an accurate three-dimensional view of the geometry and graphical aspects of the three-dimensional computer model at a display device using the temporary viewer application
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by the practice of the invention. The features and advantages of the invention may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the present invention will become more fully apparent from the following description and appended claims, or may be learned by the practice of the invention as set forth hereinafter.
In order to describe the manner in which the above-recited and other advantages and features of the invention can be obtained, a more particular description of the invention briefly described above will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. It should be noted that the figures are not drawn to scale, and that elements of similar structure or function are generally represented by like reference numerals for illustrative purposes throughout the figures. Understanding that these drawings depict only typical embodiments of the invention and are not therefore to be considered to be limiting of its scope, the invention will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Implementations of the present invention extend to systems, methods, and apparatus configured to allow easy and efficient rendering, displaying, navigation, and/or sharing of computer generated designs and models. In particular, one or more implementations of the present invention provide the ability to capture the geometry and the graphical attributes of a three-dimensional model. One or more implementations also allow for easy and intuitive navigation of the captured geometry. Additionally, one or more implementations allow a user to share the geometry and the graphical attributes of a three-dimensional model without sharing the source file or proprietary details of the source file. Furthermore, one or more implementations can allow for sharing of the geometry and graphical attributes of a three-dimensional model without requiring the viewer to have the software used to create the three-dimensional model.
For example, at least one implementation relates to capturing the geometry and the graphical attributes of a three-dimensional computer model created using a design software application, such as, for example, REVIT, AUTOCAD, SKETCHUP, 3DS MAX (“design software”). The systems, software, and methods of the present invention can store the geometry and graphical aspects of the computer model as a geometric computer model file. In one or more implementations, the geometric computer model can include only the geometry and graphical aspects of the computer model. In other words, the geometric computer model may not include dimensional information, part information, or other work product information associated with the original computer model. Thus, as used herein, the term “geometric computer model” or “geometric computer model file” refers to a computer model and/or corresponding computer file containing substantially only the geometry and graphical aspects of a three-dimensional computer model created using design software, such as those mentioned above.
Once captured, the designer (as well as another user/viewer discussed hereinafter) can use a viewer application to explore the three-dimensional geometric computer model in a dynamically rendered virtual reality environment. The rendering techniques, in addition to the viewer interface, can allow the designer (or other user) to easily and effectively display and navigate the three-dimensional design. As explained in greater detail below, both the configuration of the geometric computer model and the viewer application can allow for seamless, intuitive navigation of a geometric computer model without requiring excessive computing power.
In addition, one or more implementations of the present invention allow the designer to securely share the geometric computer model over a network (such as a LAN, WAN, intranet, or the internet, etc.). For instance, implementations of the present invention can allow a designer to automatically publish the geometric computer model in a way that it is accessible by others through the network. Furthermore, implementations of the present invention can provide a temporary viewer application to allow for the display and navigation of the geometric computer model without requiring the design software used to create the original computer model. As used herein, a “temporary viewer application” refers to a viewer application unassociated with the design software used to create the original three-dimensional model, which is automatically installed and removed from a viewer's computer to allow secure viewing of captured geometry.
Although the viewer application can display and allow a viewer to navigate and explore the rendered geometric computer model, it is important to note that, in at least one implementation, the viewer application cannot change the three-dimensional model. Moreover, in such an implementation, the viewer does not have the original design file, which can contain proprietary and work product information the designer does not want to share with the viewer. Thus, one or more implementations can protect the designer's work product and intellectual property by making the work product otherwise inaccessible to the other users/viewers to whom the designer shares the model. This, in turn, enables the designer to freely share and show other viewers the three-dimensional model without fear they will misappropriate the design.
Referring now to the Figures,
As mentioned above, implementations of the present invention can allow the designer to capture the geometry and graphical attributes of a three-dimensional computer model in a format that allows for efficient and effective display. In particular, one or more implementations provide a software plug-in configured to interact with the design software. The software plug-in can create an additional menu item or items in the design software. For example,
In one implementation, the menu item 104 created by the software plug-in can provide a drop-down selection that provides the designer with one or more options relating to the capture and rendering of the three-dimensional design. For example, the menu item 104 can include a selectable capture function that initiates the capture and/or rendering of the three-dimensional design. Additionally, the menu item can include other selectable functions such as “Link,” which can initiate a bridge between the design software and the capture and render software application. The bridge can allow the capture and render software application to capture the geometry and graphical aspects from a three-dimensional computer model created by the design software.
An end user or designer can obtain the software plug-in described above through a variety of means. For example, the designer can download and/or install the software plug-in from an online source, such as a website. Of course, the designer can also install the software plug-in can from any other traditional means, such as a CD-ROM, a portable memory device, file sharing, etc. Moreover, the software plug-in can integrate with most, if not all, design software, including, but not limited to, those mentioned above. One will appreciate that the plug-in provided can be based upon the particular type of design software. Thus, the plug-in for REVIT can be different than the plug-in for 3DS MAX, etc.
Once the designer has installed the software plug-in on the designer's computer system, the designer can then capture a three-dimensional design in a format that allows for efficient and effective display. In one implementation of the invention, for example, the designer can first open the three-dimensional computer model 102 in an interface 100 of the design software used to create the design. The designer can then select the menu item 104 from the menu bar 106 that was added upon installing the software plug-in, and select a function. For example, the designer can select the “Capture” function 108, as shown in
Upon selection of the “Capture” function 108, a capture and render software application can automatically open. The capture and render software application can then automatically capture the three-dimensional geometry and graphical aspects of the three-dimensional computer model 102 into a geometric computer model. Furthermore, the capture and render software application can render the geometric computer model into a virtual format, and display the geometric computer model in a viewer interface, as explained in greater detail below.
More specifically, in at least one implementation upon selection of the “Capture” function, the plug-in can send a request to a server (web-based or otherwise) for the capture and render software application. Upon receiving the request, the server can send the capture and render software application to the designer's computer system. For example, the server can send one or more Java application files or other executable instructions. Upon receipt of the application files, the designer's computer system can extract and launch the capture and render software application.
Thus, in at least one implementation, the capture and render software application can be hosted on a web server. In such implementations, at least the first time a designer selects the “Capture” function 108 during a session, the web server can send the capture and render software application to the designer's computer system. Upon receipt of the capture and render software application from the web server, the designer's computer system can launch the capture and render software application. One will appreciate in light of the disclosure herein that hosting the capture and render software application on a web server can ensure that the designer has the latest version of the capture and render software application each time the designer seeks to capture a three-dimensional computer model 102.
In an alternative implementation, the capture and render software application can be stored directly on the designer's computer system. In such implementations, the designer's computer system can launch the capture and render software application directly without requiring files from the web server. In yet further implementations, the capture and render software application and/or plug-in can require connection with, and instruction from, the web server in order to launch the capture and render software application, irrespective of whether the capture and render software application is stored locally on the designer's computer system or on the web server.
In any event, once the designer selects the “Capture” feature 108, the designer's computer system can launch the capture and render software application, if the designer has not already opened the capture and render software application. Once the capture and render software application has launched, the capture and render software application can capture the geometry and graphical aspects of the three-dimensional computer model 102. For example, in one implementation the capture and render software application automatically sends an export command to the design software application. The design software application then exports the file(s) comprising the three-dimensional computer model 102. The capture and render software application then imports the file(s) comprising the three-dimensional computer model 102. During, or after, the importation of the file(s) comprising the three-dimensional computer model 102, the capture and render software application can parse the file(s) and save only the data necessary to recreate the geometry and graphical aspects of the three-dimensional computer model 102. In alternative implementations, the capture and render software application can run through the database of the design software and extract and save only the data necessary to recreate the geometry and graphical aspects of the three-dimensional computer model 102. Additionally, the capture and render software application can save or extract a context tag that indicates what type of component each piece of geometry comprises.
In one or more implementations the capture and render software application can extract and/or save the only the relevant geometry and relevant graphical aspects of the three-dimensional computer model 102 (in contrast to all of the geometry and graphical aspects). Specifically, the capture and render software application can extract and/or save the only the data or files associated with the viewable surface (for example, outer surfaces) of the three-dimensional computer model 102. Thus, the capture and render software application can recognize components and/or surfaces of the three-dimensional computer model that are not viewable and exclude data associated with such components and/or surfaces from the extracted data or not save such data.
For example, the files that form a wall 110 of the three-dimensional computer model 102 can include data corresponding to the interior components of the wall 110 (i.e., beams, framing, insulation, electrical and plumbing components), part manufacturer data, part cost data, dimensional data, etc. In one or more implementations, the capture and render software application can recognize and understand the attributes of the wall and all of the components associated with the wall. The capture and render software application can parse the data pertaining to the wall 110 and save only the relevant geometry and graphical aspects (in this case outer wall geometry, the finish texture and color data). Thus, in one or more implementations, the capture and render software application will recognize the interior components of the wall as unnecessary or irrelevant with respect to reproducing the outer or viewable geometry (i.e., the outer surfaces of the wall 110) and will not save the geometry data and graphical aspect data associated with such interior components.
In one example implementation, the capture and render software application can run on default parameters. More specifically, the capture and render software application can automatically capture geometry and graphical aspects of the three-dimensional computer model 102 upon a single selection of the “Capture” function 108. Alternatively, upon selection of the “Capture” function 108, the capture and render software application can open a parameter menu box. The parameter menu box can include several selections and options that dictate what features of the three-dimensional computer model 102 will be captured. Additionally, the parameter menu box can include several additional selections and options that dictate how the captured geometry and graphical aspects of the three-dimensional computer model 102 will be rendered. For example, the capture and render software application can allow for the capture of any number of graphical attributes, including, but not limited to, colors, shading, images (such as jpegs or bitmaps), finishes, object transparency, and the like.
The capture and render software application can save the geometry, graphical aspects, and context tags as a geometric computer model file. The geometric computer model file can comprise a file type that is compatible with the capture and render software application, but not with the design software. In at least one implementation, the capture and render software application saves or stores the geometric computer model file only in the memory (i.e., volatile storage) of the designer's computer system. In such implementations, the capture and render software application does not cache or store the geometric computer model file in the non-volatile memory of the designer's computer system. In alternative implementations, the capture and render software application can store the geometric computer model file in the non-volatile memory of the designer's computer system.
Once the geometric computer model file corresponding to the three-dimensional computer model 102 is captured, the capture and render software application can render the geometry and graphical aspects of the geometric computer model accordingly. In particular, capture and render software application can render and display the three-dimensional geometry in a viewer interface. For example,
The capture and render software application can recognize the length, width, and height of objects in the three-dimensional computer model 102. Moreover, the capture and render software application can recognize graphical attributes, in addition to the dimensions, such as color, shading, finishes, transparency, images, and the like. Furthermore, capture and render software application can render the geometry and graphical aspects of the geometric computer model in a detailed and realistic-appearing view. Also, the user can navigate different visual effects of different angles for the design elements throughout the three-dimensional view without needing to wait for additional processing. Thus, the capture and render software application can provide a much richer viewing experience to the user regarding how various geometry of the geometric computer model will look in a real-world environment, in much quicker time.
In particular, because the geometric computer model file is much smaller than the design software files corresponding to the three-dimensional computer model 102, the capture and render software application can render and allow for much quicker navigation than that possible with the design software. Furthermore, because the capture and render software application processes and only renders the geometry and graphical aspects of the three-dimensional computer model 102, the computing resources used to render and navigate the geometric computer model are minimal. One will appreciate in light of the disclosure herein that in the implementations in which only the relevant geometry and relevant graphical aspects are saved, the capture and render software application can further optimize the size of the geometric computer model file and the ease of displaying the geometry.
For example,
As mentioned, the navigational configuration of the viewer interface 200 can be video-game like, such that the designer controls the view point of the viewer using a computer mouse and/or keyboard. For example, in one or more implementations the designer can virtually “navigate” around (or through) the geometric computer model 202 by clicking the left mouse button while moving the mouse in any direction. In addition, in one or more implementations the designer can maintain a position with respect to the building, and then look (i.e., as if the user is moving his head on his neck in the virtual environment) in any direction by clicking the right mouse button while moving the mouse in any direction. Furthermore, in one or more implementations the transparency of windows can allow the viewer to look through the window at a representation of what the interior of the house would look like from the perspective from outside the window. Additionally, in one or more implementations the viewer can pass through door, windows, and/or walls to allow navigation of the interior of a structure, as if the designer where actually in the structure. In yet further implementations, the designer can customize the navigational controls (i.e., assign functions to buttons) to allow for intuitive navigation according to the designer's individual preferences.
As illustrated in both
In one implementation, the capture and render software application can use context-based ambient occlusion as a method for providing shading and lighting effects on the geometric computer model 202 to provide a realistic viewing experience. In particular, the capture and render software application can use the context tags captured from the three-dimensional computer model 102 to provide more realistic rendering and displaying of the geometric computer model 202. More specifically, the capture and render software application can use the context of a three-dimensional shape to determine how to shade the shape or adjacent shapes.
For example, the capture and render software application can calculate a lighting value (value that indicates how bright or dark to make a vertex or surface) for one or more of the vertices of the geometric computer model 202 and tie the lighting value to the vertices. In determining the lighting value, the capture and render software application can determine if other features or geometry will cause the particular vertices to fall within a shadow, and provide the vertex with an appropriate lighting value. Furthermore, the capture and render software application can analyze the context of other features or geometry and determine based on their context whether to change the lighting value of a particular vertex.
For instance, in determining the lighting value of a wall section adjacent a door, the capture and render software application can determine what geometry is adjacent the wall section. Thus, the capture and render software application can recognize the geometry of a door trim adjacent, or in front of, the wall section. Once adjacent geometry has been recognized, the capture and render software application can determine the context of the adjacent geometry (i.e., what the geometry comprises (in this case door trim)). Based at least in part on the context of the adjacent geometry, the capture and render software application provide the wall section with a lighting value. For example, the capture and render software application can ignore the effect of the door trim or a transparent table or window to reduce shading errors.
Once the geometry, graphical aspects, and lighting values have been determined, the capture and render software application can send this predetermined data to a graphical processing unit (“GPU”) of a computerized system, along with any other relevant information. In general, GPU and related hardware is often more able to handle the demands that may be needed for some cases of accurate graphical rendering. The GPU then processes the data separately from other processing components in the computer system, and sends the processed data (e.g., pixel information) to a display device. Since much of the detailed rendering of the visual effects has been done previously, the GPU can produce a fairly accurate data stream from the template without requiring a significant amount of additional processing resources and processing time.
Additionally, the GPU, in conjunction with the capture and render software application, can allow a user to navigate the geometric computer model 202 (i.e., under objects, around corners, through ceilings, etc.), while still effectively providing the expected visual effects. For example, the user can use the navigational controls, which changes X/Y/Z viewing information for the design space. This input can cause the capture and render software application to provide additional data to the GPU or processing, or can simply tell the GPU to pull other previously-processed data from cache. Thus, the capture and render software application can provide real-time lighting effects to the geometric computer model 202 as it is navigated within the viewer interface 200.
In addition to the example views illustrated in
The bookmarks window 400 can provide the designer with the ability to save a series of views in a particular order and then replay those views in virtual tour format. For example, the designer can locate a desired view and then click on the “Bookmarks” feature 208. The bookmarks window 400 can then allow the designer to save the particular desired view as a bookmark. After saving one or more desired views 402, 404, 406, 408, the designer can then create a virtual tour of the geometric computer model 202. The capture and render software application can also allow the designer to re-order or delete views to modify the tour. Furthermore, the capture and render software application can allow the designer to add notations to each of the views, as well as select the order in which the views will appear during the virtual tour. Additionally, in one or more implementations, the designer can control the lapse time between any one bookmarked view and another, and how long the tour will pause at any given bookmarked view.
As previously mentioned, the capture and render software application can save the file(s) or data corresponding to the geometric computer model 202 in the memory of the designer's computer system. These files or data can also include the bookmarks and virtual tour files. The capture and render software application can provide the designer with an option of publishing the geometric computer model 202. Specifically, the designer can select the “Publish” 206 feature provided by the viewer interface 200. Upon selection of the “Publish” 206 feature, the capture and render software application can open a publish window 500, as shown by
As shown by
The capture and render software application can allow the designer to publish the geometric computer model 202 in a format that allows for viewing on mobile devices, such as the IPHONE, as shown by
When the local save option 504 is used, the capture and render software application can provide the designer the ability to use the captured geometry and graphical aspects of a three-dimensional computer model in other design software applications, without sharing the native design file. For example, a designer can design a piece of furniture or other model in a first design software application, capture and render the design of the furniture using capture and render software application. After saving the geometric computer model to a local file, the designer can then import the geometric computer model into another design using a second design software application. This allows the designer to share the general concept of the design, no matter the other designers' choice of design software, and without the designer sharing any work product or other proprietary information. In at least one implementation, the imported geometric computer model is in a read-only format.
Implementations of the present invention can also provide a shared web-based database that provides any designer the ability to browse all geometric computer models that the designer has saved or published to the web server. Additionally, the shared web-based database can allow a designer to view any geometric computer models made publicly available or shared with the designer by others. For example, the designer or user can select the “Browse Designs” option 204 in provided by the viewer interface 200. Upon selection of the Browse Designs” option 204, the capture and render software application can send a request to the web server, which can provide a list of available geometric computer models.
In any event, after publishing the geometric computer model 202, the capture and render software application can allow a designer to share the geometric computer model 202 with others. In particular, the designer can select the “Share” feature 210 feature provided by the viewer interface 200. Upon selection of the “Share” feature 210, the capture and render software application can open a sharing window 600, as shown by
The sharing window 600 can allow the designer to share a published geometric computer model 202. In particular, after selecting the specific geometric computer model 202, the designer can then enter one or more email addresses in an email field 602, with the option of including a subject line and message, as well as sender information 604. The capture and render software application can then send an email to each email address listed that provides a link to the published geometric computer model 202.
In one or more implementations, the designer can choose whether or not to provide the viewer with the capability to share the geometric computer model 202 with other users. To facilitate this choice, the sharing window 600 can allow the designer to choose between a “Quick Share” 608 or a “Secure Share” 606. When the designer selects the “Quick Share” option 608, the capture and render software application will forward a link that the viewer can in turn forward, and which allows any user or computer system with the link to gain access to the geometric computer model 202 through the web server. Alternatively, if the designer selects the “Secure Share” option 606, the email sent to the viewer is formatted such that only the viewer whose email address the designer entered can use the hyperlink in the email to view geometric computer model 202.
In any event, when the viewer receives the email and clicks on the link, the viewer can be directed to the appropriate website, which can confirm that the viewer agrees with the terms of the use agreement. Upon agreeing, the appropriate website can send a launching file to the viewer's computer system. In one or more implementations, the launching file can comprise a JAVA network launching protocol file. Upon opening the launching file, the viewer's computer system can send a request to the web server for a capture and render software temporary viewer application, which is hosted on the web server.
Upon receiving the request, the web server can send the capture and render software temporary viewer application to the viewer's computer system. For example, the web server can send one or more Java application files or other executable instructions. Upon receipt of the application files, the viewer's computer system can extract and launch the capture and render software temporary viewer application.
In at least one implementation of the present invention, the web server can also send executable instructions to the viewer's computer system, which when executed by a processor, cause the capture and render software temporary viewer application to be stored within the memory (i.e., volatile storage) of the viewer's computer system. The viewer's computer system can then launch the capture and render software temporary viewer application. Once launched, or during the launching, the capture and render software temporary viewer application can send a request to the web server for the geometric computer model 202. The web server can send the geometric computer model 202 to the client's computer system where is it is stored in the memory (i.e., volatile storage) of the viewer's computer system.
In alternative implementations, the capture and render software temporary viewer application and/or the geometric computer model 202 can be stored within the non-volatile storage of the viewer's computer system. One will appreciate in light of the disclosure herein; however, that in at least one implementation the capture and render software temporary viewer application and the geometric computer model file 202 will only be stored in the memory (i.e., volatile storage) of the viewer's computer system. In such implementations, the capture and render software temporary viewer application and the geometric computer model file 202 will automatically be removed the viewer's computer upon the closing of the capture and render software temporary viewer application.
In at least one implementation, the published and subsequently viewable geometric computer model 202 does not allow the viewer to have access to the original design file(s) used to create the three-dimensional computer model 102. Moreover, the geometric computer model 202 does not contain any dimensional or other work product information about the three-dimensional computer model 102. Therefore, the designer can confidently share the geometric computer model 202 with other users knowing that the other users will not have access to work product or other proprietary information related to the original three-dimensional computer model 102.
Moreover, implementations of the present invention allow the user to share the geometric computer model 202 with a viewer, no matter if the viewer has the same version, or any version, of design software used to create the original three-dimensional computer model 102. Indeed, one or more implementations do not require that the viewer have any type of design software or computer model viewer software prior to receiving the link from the web server. Specifically, when the viewer clicks on the provided link, the capture and render software temporary viewer application is automatically downloaded, thus allowing the viewer to view and explore the geometric computer model 202 as described above.
For example,
The capture and render software viewer 700 can further allow the viewer to view any bookmarked tours, and generally view the all aspects of the three-dimensional model. For example, the capture and render software viewer 700 can include a play-button 702 or similar graphic device can be displayed in the viewer interface 200. A viewer can select the play-button 702, at which point the capture and render software viewer 700 can automatically move from one bookmarked view to the next in a format that allows the viewer to continue to see the three-dimensional geometric computer model 202 while “moving” from one view to the next. During the virtual tour, as each bookmarked view is reached, the capture and render software viewer 700 can display the notations (if any) associated with each view. Additionally, the capture and render software viewer 700 can provide the viewer with the ability to pause, stop, rewind, or fast forward the bookmarked tour.
Thus, the designer can make a request 804a to capture the geometry and graphical aspects of a three-dimensional computer model 102 created by a design software application 810. Upon receiving the one or more requests 804a, the one or more processors 806 can send one or more requests 812a to a web server 814 for a capture and render software application 816 hosted on the web server 814. In response to the one or more requests 812a, the web server 814 can send one or one or more messages 818 (i.e., data) comprising the capture and render software application 816. For example, the one or more messages 818 can include executable instructions that cause the designer computer system 808 to receive and launch the capture and render software application 816. In at least one implementation, the capture and render software application 816 is stored within non-volatile memory of the designer computer system 808.
Once launched, the capture and render software application 816 can cause the one or more processors 806 to automatically send a request to the design software application 810 to export the file(s) corresponding to the three-dimensional computer model 102. The design software application 810 can then cause one or more processors 806 to export the file(s) corresponding to the three-dimensional computer model 102. At this point, the capture and render software application 816 can cause the one or more processors 806 to import and parse the file(s) corresponding to the three-dimensional computer model 102 such that only the geometry, graphical aspects, and one or more context tags are saved by the capture and render software application 816. Alternatively, once launched, the capture and render software application 816 can cause the one or more processors 806 to run through a database 811 associated with the design software 810 and extract and save only the data necessary to recreate the geometry and graphical aspects of the three-dimensional computer model 102. In any event, the capture and render software application 816 can cause the one or more processors 806 to save the geometry, graphical aspects, and context tags as a geometric computer model file in the volatile storage of the designer's computer system 808.
The capture and render software application 816 can cause the one or more processors 806 to render the geometry and graphical aspects of the geometric computer model 202 accordingly. In particular, the capture and render software application 816 can cause the one or more processors 806 to determine the geometry, graphical aspects, and lighting values as explained above. The capture and render software application 816 (or the one or more processors 806) can send this predetermined data to a GPU 820. The GPU 820 then processes the data separately from other processing components in the computer system 808, and sends the processed data (e.g., pixel information) to a display device 822.
The designer 802 can also send one or more requests 804b to publish the geometric computer model 202. Upon receipt of the one or more requests 804b, the capture and render software application 816 can cause the one or more processors 806 to send the file(s)/data associated with the geometric computer model 202 to the web server 814. Upon receipt of such files/data, the web server 814 can store the file(s) in one or more data bases 824.
The designer 802 can also send one or more requests 804c to share the geometric computer model 202. Upon receipt of the one or more requests 804b, the capture and render software application 816 can cause the one or more processors 806 to send one or more requests 812c to the web server 814 to share the geometric computer model 202 with a particular email address belonging to a viewer 826. The web server 814 can then prepare an email with one or more links to the web server 814. The web server 814 can then send the email to a server (not shown) associated with the email address.
The viewer 826 can use a viewer computer system 828 to open the email sent by the web server 814. Then the viewer 826 can the send one or more requests 830 to one or more processors 832 of the viewer computer system 828 (also referred to as “second remote client computer system”) to open the link. The one or more processors 832 can in turn send one or more requests 834a to the web server 814 to open the link. The web server 814 can then send data or one or more message 836a to the one or more processors 832, such as for example, a launching file. Upon opening the launching file, the one or more processors 832 can send a request 834b to the web server 814 for a capture and render software temporary viewer application 838, which is hosted on the web server 814.
In response, to the one or more requests 834b, the web server 814 can send data or one or more message 836b comprising the capture and render viewer software application 816. For example, the one or more messages 836b can include executable instructions that cause the viewer computer system 826 to receive and launch the capture and render viewer software application 838. In at least one implementation, the capture and render software temporary viewer application 838 is stored within non-volatile memory of the viewer computer system 826.
Once launched, or during the launching, the capture and render software temporary viewer application 838 can send a request 834c to the web server 814 for the geometric computer model 202. The web server 814 can send the geometric computer model 202 to the viewer computer system 828 where is it is stored in the memory (i.e., volatile storage) of the viewer computer system 828.
The capture and render software temporary viewer application 838 can cause the one or more processors 832 to render the geometry and graphical aspects of the geometric computer model 202. In particular, the capture and render software temporary viewer application 838 can cause the one or more processors 832 to determine the geometry, graphical aspects, and lighting values as explained above. The capture and render software temporary viewer application 838 (or the one or more processors 832) can send this predetermined data to a GPU 840. The GPU 840 can then process the data separately from other processing components in the viewer computer system 828, and send the processed data (e.g., pixel information) to a display device 842.
Accordingly,
For example,
Furthermore,
In addition,
As shown by
Additionally,
Additionally, act 1010 can include sending one or more requests to the design software application 810 to export the file(s) corresponding to the three-dimensional computer model 102. Act 1010 can also include exporting the file(s) corresponding to the three-dimensional computer model 102. Furthermore, act 1010 can include importing and parsing the file(s) corresponding to the three-dimensional computer model 102 for the geometry, graphical aspects, and one or more context tags. Alternatively, act 1010 can include analyzing a database 811 associated with the design software 810 and extracting the geometry, graphical aspects, and one or more context tags of the three-dimensional computer model 102. In any event, act 1010 can further include saving the geometry, graphical aspects, and one or more context tags in volatile storage of the designer computer system.
Additionally,
In addition to the foregoing,
Furthermore, a method from the perspective of designer computer system 808 can comprise an act of receiving one or more requests 804b to share the geometric computer model 202. The method can further comprise sending one or more requests 812b to the web server 814 to share the geometric computer model 202. Specifically, the method can include sending one or more email addresses associated with a viewer 826 to the web server 814.
Additionally,
Act 1070 can also include sending one or more executable instructions and one or more application files from the web server 814 to a second remote client computer system 828 (i.e., viewer computer system). The one or more executable instructions can cause one or more processors to launch a capture and render software temporary viewer application 838 or a capture and render software application 816 on the second remote client computer system 828. Furthermore, act 1070 can include sending one or more executable instructions configured to cause the second remote client computer system 828 or 808 to store the geometric computer model files and/or the one or more application files in volatile memory.
Still further act 1070 can include sending one or more executable instructions configured to cause the second remote client computer system 828 to delete the one or more geometric computer model files upon the closing of the capture and render software temporary viewer application 838 or the capture and render software application 816. Still further act 1070 can include sending a hyperlink containing the location of the one or more geometric computer model files from the web server 814 to an email address associated with an intended viewer 826.
Additionally,
In addition to the foregoing,
Accordingly,
The embodiments of the present invention may comprise a special purpose or general-purpose computer including various computer hardware components, as discussed in greater detail below. Embodiments within the scope of the present invention also include computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer.
By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above should also be included within the scope of computer-readable media.
Computer-executable instructions comprise, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. For example, the computer model 102 shown and described was the model of a house. One will appreciate that the present invention is not so limited. Indeed, the present invention can be used to capture and share not only architectural models, but any three-dimensional model. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
This application is a U.S. National Stage Application corresponding to PCT/US10/58092, filed Nov. 24, 2010, which claims the benefit of priority to U.S. Provisional Patent Application No. 61/264,219, filed Nov. 24, 2009, the entire content of which are incorporated herein by reference.
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/US2010/058092 | 11/24/2010 | WO | 00 | 5/18/2012 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2011/066452 | 6/3/2011 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 4586145 | Bracewell | Apr 1986 | A |
| 4862376 | Ferriter | Aug 1989 | A |
| 5111392 | Malin | May 1992 | A |
| 5255207 | Cornwell | Oct 1993 | A |
| 5293479 | Quintero et al. | Mar 1994 | A |
| 5339247 | Kirihara | Aug 1994 | A |
| 5414801 | Smith | May 1995 | A |
| 5514232 | Burns | May 1996 | A |
| 5555357 | Fernandes | Sep 1996 | A |
| 5572639 | Gantt | Nov 1996 | A |
| 5576965 | Akasaka | Nov 1996 | A |
| 5588098 | Chen et al. | Dec 1996 | A |
| 5625827 | Krause | Apr 1997 | A |
| 5684713 | Asada et al. | Nov 1997 | A |
| 5740341 | Oota et al. | Apr 1998 | A |
| 5764241 | Elliott et al. | Jun 1998 | A |
| 5764518 | Collins | Jun 1998 | A |
| 5870771 | Oberg | Feb 1999 | A |
| 5894310 | Arsenault et al. | Apr 1999 | A |
| 5918232 | Pouschine et al. | Jun 1999 | A |
| 5977982 | Lauzon | Nov 1999 | A |
| 5995107 | Berteig et al. | Nov 1999 | A |
| 6014503 | Nagata | Jan 2000 | A |
| 6020885 | Honda | Feb 2000 | A |
| 6037945 | Loveland | Mar 2000 | A |
| 6052669 | Smith | Apr 2000 | A |
| 6253167 | Matsuda et al. | Jun 2001 | B1 |
| 6292810 | Richards | Sep 2001 | B1 |
| 6295513 | Thackston | Sep 2001 | B1 |
| 6335732 | Shaikh | Jan 2002 | B1 |
| 6401237 | Ishikawa | Jun 2002 | B1 |
| 6459435 | Eichel | Oct 2002 | B1 |
| 6466239 | Ishikawa | Oct 2002 | B2 |
| 6483508 | Ishikawa | Nov 2002 | B1 |
| 6493679 | Rappaport | Dec 2002 | B1 |
| 6509906 | Awe et al. | Jan 2003 | B1 |
| 6570563 | Honda | May 2003 | B1 |
| 6662144 | Normann et al. | Dec 2003 | B1 |
| 6690981 | Kawachi | Feb 2004 | B1 |
| 6701288 | Normann | Mar 2004 | B1 |
| 6721684 | Saebi | Apr 2004 | B1 |
| 6772168 | Ardoin et al. | Aug 2004 | B2 |
| 6888542 | Clauss | May 2005 | B1 |
| 6922701 | Ananian et al. | Jul 2005 | B1 |
| 6944513 | Tomomitsu | Sep 2005 | B1 |
| 6971063 | Rappaport | Nov 2005 | B1 |
| 6985832 | Saebi | Jan 2006 | B2 |
| 6999102 | Felser et al. | Feb 2006 | B2 |
| 7019753 | Rappaport | Mar 2006 | B2 |
| 7042440 | Pryor et al. | May 2006 | B2 |
| 7062454 | Giannini | Jun 2006 | B1 |
| 7062532 | Sweat | Jun 2006 | B1 |
| 7062722 | Carlin et al. | Jun 2006 | B1 |
| 7065420 | Philpott | Jun 2006 | B1 |
| 7079990 | Haller | Jul 2006 | B2 |
| 7080096 | Imamura | Jul 2006 | B1 |
| 7085697 | Rappaport | Aug 2006 | B1 |
| 7096173 | Rappaport | Aug 2006 | B1 |
| 7139686 | Critz | Nov 2006 | B1 |
| 7155228 | Rappaport | Dec 2006 | B2 |
| 7171208 | Rappaport | Jan 2007 | B2 |
| 7171344 | Lind | Jan 2007 | B2 |
| 7200639 | Yoshida | Apr 2007 | B1 |
| 7216092 | Weber | May 2007 | B1 |
| 7218979 | Tsuji | May 2007 | B2 |
| 7243054 | Rappaport | Jul 2007 | B2 |
| 7246044 | Imamura et al. | Jul 2007 | B2 |
| 7246045 | Rappaport | Jul 2007 | B1 |
| 7249005 | Loberg | Jul 2007 | B2 |
| 7266768 | Ferlitsch | Sep 2007 | B2 |
| 7277572 | MacInnes et al. | Oct 2007 | B2 |
| 7277830 | Loberg | Oct 2007 | B2 |
| 7299168 | Rappaport | Nov 2007 | B2 |
| 7299416 | Jaeger | Nov 2007 | B2 |
| 7318063 | Brychell | Jan 2008 | B2 |
| 7337093 | Ramani et al. | Feb 2008 | B2 |
| 7340383 | Mayuzumi et al. | Mar 2008 | B2 |
| 7353192 | Ellis et al. | Apr 2008 | B1 |
| 7392522 | Murray | Jun 2008 | B2 |
| 7430711 | Rivers-Moore | Sep 2008 | B2 |
| 7437376 | Sikchi | Oct 2008 | B2 |
| 7444195 | Smith | Oct 2008 | B2 |
| 7479959 | Han | Jan 2009 | B2 |
| 7492934 | Mundy | Feb 2009 | B2 |
| 7516399 | Hsu | Apr 2009 | B2 |
| 7587302 | Arvin et al. | Sep 2009 | B2 |
| 7620638 | Nonclercq | Nov 2009 | B2 |
| 7629985 | McArdle | Dec 2009 | B2 |
| 7643027 | Rothstein | Jan 2010 | B2 |
| 7643966 | Adachi | Jan 2010 | B2 |
| 7661959 | Green | Feb 2010 | B2 |
| 7676348 | Okada | Mar 2010 | B2 |
| 7761266 | Mangon | Jul 2010 | B2 |
| 7788068 | Mangon | Aug 2010 | B2 |
| 7814436 | Schrag et al. | Oct 2010 | B2 |
| 7822584 | Saebi | Oct 2010 | B1 |
| 7823074 | Takemura et al. | Oct 2010 | B2 |
| 7856342 | Kfouri et al. | Dec 2010 | B1 |
| 7877237 | Saebi | Jan 2011 | B1 |
| 7996756 | Eilers et al. | Aug 2011 | B2 |
| 8065654 | Shiihara | Nov 2011 | B2 |
| 8108267 | Varon | Jan 2012 | B2 |
| 8117558 | Hoguet | Feb 2012 | B2 |
| 8132123 | Schrag et al. | Mar 2012 | B2 |
| 8134553 | Saini et al. | Mar 2012 | B2 |
| 8185219 | Gilbert et al. | May 2012 | B2 |
| 8195434 | Powell | Jun 2012 | B2 |
| 8244025 | Davis et al. | Aug 2012 | B2 |
| 8255338 | Brittan | Aug 2012 | B1 |
| 8271336 | Mikurak | Sep 2012 | B2 |
| 8276088 | Ke | Sep 2012 | B2 |
| 8285707 | Day | Oct 2012 | B2 |
| 8290849 | Eisler | Oct 2012 | B2 |
| 8301527 | Tarbox | Oct 2012 | B2 |
| 8314799 | Pelletier et al. | Nov 2012 | B2 |
| 8326926 | Sangem et al. | Dec 2012 | B2 |
| 8332401 | Hull | Dec 2012 | B2 |
| 8332827 | Edde | Dec 2012 | B2 |
| 8334867 | Davidson | Dec 2012 | B1 |
| 8335789 | Hull | Dec 2012 | B2 |
| 8352218 | Balla et al. | Jan 2013 | B2 |
| 8386918 | Do | Feb 2013 | B2 |
| RE44054 | Kim | Mar 2013 | E |
| 8402473 | Becker | Mar 2013 | B1 |
| 8423391 | Hessedenz | Apr 2013 | B2 |
| 8442850 | Schorr | May 2013 | B2 |
| 8462147 | Sugden | Jun 2013 | B2 |
| 8468175 | Obata | Jun 2013 | B2 |
| 8499250 | Wetzer et al. | Jul 2013 | B2 |
| 8508539 | Vlietinck | Aug 2013 | B2 |
| 8510382 | Purdy | Aug 2013 | B2 |
| 8510672 | Loberg | Aug 2013 | B2 |
| 8533596 | Boss et al. | Sep 2013 | B2 |
| 8572558 | Mathieu, III | Oct 2013 | B1 |
| 8583375 | Baule | Nov 2013 | B2 |
| 8600989 | Hull | Dec 2013 | B2 |
| 8626877 | Greene | Jan 2014 | B2 |
| 8645973 | Bosworth | Feb 2014 | B2 |
| 8650179 | Driesch | Feb 2014 | B2 |
| 8763009 | Degirmenci | Jun 2014 | B2 |
| 8773426 | Hamel | Jul 2014 | B1 |
| 8819072 | Croicu | Aug 2014 | B1 |
| 8914259 | Kripac | Dec 2014 | B2 |
| 8933925 | Sinha | Jan 2015 | B2 |
| 8949789 | Schlarb | Feb 2015 | B2 |
| 8954295 | Vicknair | Feb 2015 | B1 |
| 8994726 | Furukawa | Mar 2015 | B1 |
| 9075931 | Charles | Jul 2015 | B2 |
| 9106425 | Murphey | Aug 2015 | B2 |
| 9117308 | Nag | Aug 2015 | B1 |
| 20010024211 | Kudukoli et al. | Sep 2001 | A1 |
| 20010024230 | Tsukahara | Sep 2001 | A1 |
| 20010047250 | Schuller | Nov 2001 | A1 |
| 20010047251 | Kemp | Nov 2001 | A1 |
| 20020010589 | Nashida et al. | Jan 2002 | A1 |
| 20020046294 | Brodsky | Apr 2002 | A1 |
| 20020059049 | Bradbury et al. | May 2002 | A1 |
| 20020069221 | Rao | Jun 2002 | A1 |
| 20020083076 | Wucherer | Jun 2002 | A1 |
| 20020085041 | Ishikawa | Jul 2002 | A1 |
| 20020091739 | Ferlitsch | Jul 2002 | A1 |
| 20020093538 | Carlin | Jul 2002 | A1 |
| 20020095348 | Hiroshige | Jul 2002 | A1 |
| 20020109704 | Rajarajan | Aug 2002 | A1 |
| 20020144204 | Milner | Oct 2002 | A1 |
| 20020158865 | Dye et al. | Oct 2002 | A1 |
| 20020188478 | Breeland et al. | Dec 2002 | A1 |
| 20020188678 | Edecker et al. | Dec 2002 | A1 |
| 20020196285 | Sojoodi et al. | Dec 2002 | A1 |
| 20030090530 | Ramani et al. | May 2003 | A1 |
| 20030097273 | Carpenter | May 2003 | A1 |
| 20030128232 | Tsuji | Jul 2003 | A1 |
| 20040012542 | Bowsher | Jan 2004 | A1 |
| 20040027371 | Jaeger | Feb 2004 | A1 |
| 20040098691 | Teig | May 2004 | A1 |
| 20040117746 | Narain et al. | Jun 2004 | A1 |
| 20040145614 | Takagaki et al. | Jul 2004 | A1 |
| 20040153824 | Devarajan et al. | Aug 2004 | A1 |
| 20040204903 | Saebi | Oct 2004 | A1 |
| 20040205519 | Chapel et al. | Oct 2004 | A1 |
| 20040236561 | Smith | Nov 2004 | A1 |
| 20050041028 | Coutts | Feb 2005 | A1 |
| 20050065951 | Liston | Mar 2005 | A1 |
| 20050071135 | Vredenburgh et al. | Mar 2005 | A1 |
| 20050081161 | MacInnes | Apr 2005 | A1 |
| 20050203718 | Carek | Sep 2005 | A1 |
| 20050228250 | Bitter et al. | Oct 2005 | A1 |
| 20050256874 | Chiba et al. | Nov 2005 | A1 |
| 20060028695 | Knighton | Feb 2006 | A1 |
| 20060041840 | Blair et al. | Feb 2006 | A1 |
| 20060041842 | Loberg | Feb 2006 | A1 |
| 20060119601 | Finlayson et al. | Jun 2006 | A1 |
| 20060143220 | Spencer, Jr. | Jun 2006 | A1 |
| 20060174209 | Barros | Aug 2006 | A1 |
| 20060206623 | Gipps et al. | Sep 2006 | A1 |
| 20060271378 | Day | Nov 2006 | A1 |
| 20070088704 | Bourne et al. | Apr 2007 | A1 |
| 20070097121 | Loop et al. | May 2007 | A1 |
| 20070115275 | Cook et al. | May 2007 | A1 |
| 20070130020 | Paolini | Jun 2007 | A1 |
| 20070168325 | Bourne et al. | Jul 2007 | A1 |
| 20070180425 | Storms et al. | Aug 2007 | A1 |
| 20070188488 | Choi | Aug 2007 | A1 |
| 20070204241 | Glennie et al. | Aug 2007 | A1 |
| 20070219645 | Thomas | Sep 2007 | A1 |
| 20070240049 | Rogerson | Oct 2007 | A1 |
| 20070250295 | Murray | Oct 2007 | A1 |
| 20070260432 | Okada | Nov 2007 | A1 |
| 20070271870 | Mifsud et al. | Nov 2007 | A1 |
| 20070294622 | Sterner et al. | Dec 2007 | A1 |
| 20080010382 | Ratakonda et al. | Jan 2008 | A1 |
| 20080033641 | Medalia | Feb 2008 | A1 |
| 20080036769 | Coutts | Feb 2008 | A1 |
| 20080052618 | McMillan et al. | Feb 2008 | A1 |
| 20080071559 | Arrasvuori | Mar 2008 | A1 |
| 20080112610 | Israelsen et al. | May 2008 | A1 |
| 20080126021 | Hoguet | May 2008 | A1 |
| 20080140732 | Wilson et al. | Jun 2008 | A1 |
| 20080141334 | Wicker et al. | Jun 2008 | A1 |
| 20080143884 | Foster | Jun 2008 | A1 |
| 20080174598 | Risenhoover | Jul 2008 | A1 |
| 20080188969 | O'Malley | Aug 2008 | A1 |
| 20080238946 | Baughman | Oct 2008 | A1 |
| 20080249756 | Chaisuparasmikul | Oct 2008 | A1 |
| 20080252640 | Williams | Oct 2008 | A1 |
| 20080275674 | Reghetti et al. | Nov 2008 | A1 |
| 20080282166 | Fillman et al. | Nov 2008 | A1 |
| 20080303844 | Reghetti et al. | Dec 2008 | A1 |
| 20080309678 | Reghetti et al. | Dec 2008 | A1 |
| 20090069704 | MacAdam et al. | Mar 2009 | A1 |
| 20090089186 | Paolini | Apr 2009 | A1 |
| 20090110307 | Markowitz | Apr 2009 | A1 |
| 20090113349 | Zohar et al. | Apr 2009 | A1 |
| 20090119039 | Banister | May 2009 | A1 |
| 20090138826 | Barros | May 2009 | A1 |
| 20090148050 | Reghetti et al. | Jun 2009 | A1 |
| 20090187385 | Zegdoun | Jul 2009 | A1 |
| 20090198358 | Logan | Aug 2009 | A1 |
| 20090208095 | Zebedin | Aug 2009 | A1 |
| 20090210487 | Westerhoff et al. | Aug 2009 | A1 |
| 20090248184 | Steingart et al. | Oct 2009 | A1 |
| 20090254843 | Van Wie et al. | Oct 2009 | A1 |
| 20090273598 | Reghetti et al. | Nov 2009 | A1 |
| 20090313322 | Sheehan | Dec 2009 | A1 |
| 20100017733 | Barros | Jan 2010 | A1 |
| 20100042516 | Knipfer | Feb 2010 | A1 |
| 20100121614 | Reghetti et al. | May 2010 | A1 |
| 20100122196 | Wetzer et al. | May 2010 | A1 |
| 20100138762 | Reghetti et al. | Jun 2010 | A1 |
| 20100179788 | Santina | Jul 2010 | A1 |
| 20100185514 | Glazer et al. | Jul 2010 | A1 |
| 20100198563 | Plewe | Aug 2010 | A1 |
| 20100302245 | Best | Dec 2010 | A1 |
| 20110007069 | Lee | Jan 2011 | A1 |
| 20110063440 | Neustaedter et al. | Mar 2011 | A1 |
| 20110078169 | Sit | Mar 2011 | A1 |
| 20110169826 | Elsberg et al. | Jul 2011 | A1 |
| 20110258573 | Wetzer et al. | Oct 2011 | A1 |
| 20110320966 | Edecker et al. | Dec 2011 | A1 |
| 20120005353 | Edecker et al. | Jan 2012 | A1 |
| 20120069011 | Hurt et al. | Mar 2012 | A1 |
| 20120089374 | Kripac | Apr 2012 | A1 |
| 20120331061 | Lininger | Dec 2012 | A1 |
| 20120331422 | High | Dec 2012 | A1 |
| 20130125029 | Miller | May 2013 | A1 |
| 20130257850 | Chen | Oct 2013 | A1 |
| 20130283362 | Kress | Oct 2013 | A1 |
| 20140095122 | Appleman | Apr 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1098244 | Sep 2001 | EP |
| 1204046 | May 2002 | EP |
| 2364801 | Feb 2002 | GB |
| 10334127 | Dec 1998 | JP |
| 2005301630 | Oct 2005 | JP |
| 9003618 | Apr 1990 | WO |
| 9322741 | Nov 1993 | WO |
| 0219177 | Mar 2002 | WO |
| WO02075597 | Sep 2002 | WO |
| 03023559 | Mar 2003 | WO |
| 2005033985 | Apr 2005 | WO |
| 2006018744 | Feb 2006 | WO |
| 2007093060 | Aug 2007 | WO |
| 2007106873 | Sep 2007 | WO |
| 2006018740 | Feb 2009 | WO |
| 2009100538 | Aug 2009 | WO |
| Entry |
|---|
| Blythe, Rise of the Graphics Processor, IEEE, 2008. |
| U.S. Office of Personnel Management, Clear Cache IE, 2007. |
| Wang, Intellectual Property Pertection in Collaborative Design through Lean Information Modeling and Sharing, 2006. |
| Lea, Community Place Architecture and Performance, 2007. |
| Autodesk, Maya 8.5 Shading, 2007. |
| CRC, Final Report Collaoration Platform, 2009. |
| Mental Images GmbH, RealityServer Functional Overview White Paper, 2007. |
| Rozansk, Software Systems Architecture Working With Stakeholders Using Viewpoints and Perspectives, 2008. |
| Sony, Community Place Conductor 2.0 Users Manua, 1998. |
| Vasko, Collaborative Modeling of Web Applications for Various Stakeholders, 2009. |
| Wollongong, City Centre 3D Model Specifications, May 18, 2009. |
| Office Action mailed Oct. 18, 2006 (Paper No. 20060925), U.S. Appl. No. 11/204,419, filed Aug. 16, 2005. |
| Office Action mailed Oct. 19, 2006 (Paper No. 20061012), U.S. Appl. No. 11/204,420, filed Aug. 16, 2005. |
| Chan, et al.: “Design of a Walkthrough System for Indoor Environments from Floor Plans”; Proceedings of the 1998 IEEE Conference on Information Visualization, Jul. 29-31, 1998, pp. 50-57. |
| Josie Wernecke; Title: The Inventor Mentor: Programming Object Oriented 3D Graphics with Open Inventor; Release 2; Date: Jun. 19, 1997; Published on Web Site: www.cs.ualberta.cal. |
| Office Action Mailed Nov. 28, 2007, U.S. Appl. No. 11/204,421. |
| Office Action Mailed Aug. 11, 2008, U.S. Appl. No. 11/204,421. |
| Office Action Mailed Dec. 23, 2008, U.S. Appl. No. 11/204,421. |
| Office Action Mailed Mar. 31, 2009, U.S. Appl. No. 11/204,421. |
| Office Action Mailed May 15, 2009, U.S. Appl. No. 11/204,421. |
| Office Action Mailed Jul. 29, 2009, U.S. Appl. No. 11/204,421. |
| International Search Report and Opinion on PCT/CA2007/000241, mailed May 15, 2007. |
| International Search Report and Opinion on PCT/CA2009/000190, mailed Jun. 5, 2009. |
| International Search Report and Opinion on PCT/CA2009/000183, mailed Jun. 9, 2009. |
| International Search Report and Opinion on PCT/CA2009/000311, mailed Jul. 30, 2009. |
| Office Action Mailed Aug. 18, 2010, U.S. Appl. No. 11/577,302. |
| USPTO, Office Action in U.S. Appl. No. 121444,886, mailed Oct. 27, 2011, 24 pages. |
| Advisory Action Mailed Mar. 31, 2009, U.S. Appl. No. 11/204,421. |
| Advisory Action Mailed May 15, 2009, U.S. Appl. No. 11/204,421. |
| USPTO, Office Action in U.S. Appl. No. 121444,890, mailed Oct. 27, 2011, 30 pages. |
| USPTO, Office Action in U.S. Appl. No. 12/444,886, mailed Aug. 16, 2012. |
| International Search Report for PCT/CA2009000190 mailed Apr. 12, 2012. |
| USPTO, Office Action in U.S. Appl. No. 12/444,893 mailed Feb. 19, 2013. |
| Gross M D: “Why can't CAD be more like Lego? CKB, a program for building constructions kits”, Automation in Construction, Elsevier Science Publishers, Amsterdam, NL, vol. 5, No. 4, Oct. 1, 1996 pp. 285-300, XP004072247, ISSN: 0926-5805, DOI:10.1016/S0926-5805(96)00154-9. |
| European Search Report—Application No. / U.S. Pat. No. 09719352.8-1960 / 2252951 PCT/CA2009000311. |
| EPO Search Report for EP07701791 dated Aug. 21, 2012. |
| International Search Report and Witten Opinion for PCT/US2012/038582 mailed Dec. 28, 2012. |
| Gajamani, Geetha., “Automated Project Scheduling and Inventory Monitoring Using RFID”, 2007, 24th Internationial Symposium on Automation and Robiotics in Construction. Retrieved from http://www.iaarc.org/publications/proceedings—of the—24th—isarc/automated—project—schedule—and—inventory—monitoring—using—rfid.html. |
| European Search Report—Application No. 10 833 972.2 mailed Feb. 2, 2015. |
| Notice of Allowance for U.S. Appl. No. 13/579,261 mailed on Jul. 10, 2015. |
| European Search Report—Application No. 12800327.4 mailed Feb. 18, 2015. |
| Funkhouser T et al: Modeling by example, ACM Transactions on Grpahic (TOG), ACM, US, vol. 23, No. 3, Aug. 1, 2004, pp. 652-663, XP008087089, ISSN: 0730-0301, DOI: 10.1145/1015706.1015775 *abstract* *p. 652, col. 1, paragraph 2- col. 2, paragraph 2* *p. 656, col. 1, paragraph 3-5*. |
| Anonymous: “Dresden Frauenkirche—Wikipedia, the free encyclopedia”, Jun. 8, 2011, pp. 1-7, XP055168540 retrieved from the Internet: URL: https://en.wikipedia.org/w/index.php?title=Dresden—Frauenkirche&oldid=433207596 [retrieved on Feb. 9, 2015] p. 3, paragraph 7-9*. |
| Number | Date | Country | |
|---|---|---|---|
| 20120268463 A1 | Oct 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61264219 | Nov 2009 | US |
