US20140267581A1 - Real time virtual reality leveraging web cams and ip cams and web cam and ip cam networks - Google Patents

Abstract

Systems and methods for enabling a visitor to access VR representations authored by different authors of locations in a virtual universe via a computer network are provided. A plurality of VR data sets may be stored. Each VR data set comprise web or IP camera VR datasets and may be independently authored by a respective author different from the other authors. One or more VR data servers may be adapted to access and transmit the VR data sets, and each VR data set may be associated with a VR data server for access to the VR data set. A domain server may be adapted to access and transmit domain data comprising the location within the universe of each VR representation and the network address of the VR data server associated with the VR representation. Further, a client host may be adapted to communicate with the domain server to receive domain data representing the network address of the VR data server associated with a selected VR representation, the client host further adapted to communicate with that VR data server to access the VR data set defining the VR representation without leaving the virtual universe.

Description

CROSS REFERENCE TO RELATED APPLICATIONS
• This patent application claims the priority benefit of U.S. Provisional Patent Application Ser. No. 61/786,572 filed Mar. 15, 2013 entitled, “Personal Digital Assistance and Virtual Reality,” the disclosures of which are incorporated herein by reference.
BACKGROUND OF THE INVENTION
• 1. Field of the Invention
• The present invention relates generally to computer-generated virtual reality representations of locations. Specifically, the present invention relates to storing, organizing, and providing access to a number of virtual reality representations whose data comes from spy cams and spy cam networks of web cams all through a computer network.
• 2. Description of the Related Art
• Virtual reality (VR) models and simulates views from a location in virtual space. The visitor perceives the view from virtual space on a computer monitor or specialized display, and experiences “movement” by changing position or orientation within the virtual space. The visitor may even be “teleported” to different points in the virtual space.
• Although recognized as having substantial potential, virtual reality has remained limited because it has yet to connect to the many cloud databases as well as many remote data gathering devices. As explained below, virtual reality representations model a single virtual space, and authoring virtual reality representations requires specialized computer programming or graphics skills. These factors have hindered broader adoption of virtual reality.
• A virtual reality representation models a single volume, area, or point within virtual space. The representation may model physical space, such as a location or region on the Earth, or may model imaginary space in a video game. The visitor can move around in the virtual space, but is limited to remaining in that virtual space.
• Authors are usually involved in creating virtual reality representations of the locations, or of related locations. These representations may exist on different websites, servers, or computers. There is a need to expand the data of virtual reality away from authors who happen to take pictures or video of a geo-location.
• A webcam is a video camera that feeds its images in real time to a computer or computer network. An IP camera uses a direct connection using ethernet or Wi-Fi whereas a webcam is generally connected by a USB cable, FireWire cable, or similar cable.
• The most popular use of these cameras is the establishment of video links, permitting computers to act as videophones or videoconference stations. The common use as a video camera for the World Wide Web gave the webcam its name. Other popular uses include security surveillance, computer vision, video broadcasting, and for recording social videos.
• Webcams are known for their low manufacturing cost and flexibility making them the lowest cost form of video telephony. They have also become a source of security and privacy issues, as some built-in webcams can be remotely activated via spyware.
• It is desirable to find a way to connect these web and IP cams to the virtual reality networks to take advantage of growing the virtual data base independent of authors.
• In particular, it would be desirable that the web and IP camera representations be connected together in a way that enables the visitor to experience these representations. For example, if the locations modeled by a web or IP camera are of a physical location virtual reality visitors select, the visitor could choose that representation to experience. This creates a “virtual universe” made of separate virtual reality web or IP camera representations that can be toured by visitors.
• There are also many websites that aggregate the collection of web cams or IP cameras for visitors to explore various geo-locations. However, these websites are not organized by virtual travel and further they are not linked to other forms of data. It would be advantageous to link these web cameras and IP cameras for improvement of visitor's experiences through virtual reality representations.
• Prior art U.S. Pat. No. 7,298,378, Issues Nov. 20, 2007, “Virtual reality universe realized as a distributed location network” describes a virtual reality network which provides access to a number of virtual reality representations, each virtual reality representation representing a location in a virtual universe and defined by VR data stored on the network. The VR data can be in a simplified data format. A database stores the network address and the location in the universe of each virtual reality representation. A database server provides access to the database. The database server generates a list of locations in response to a location query from a visitor, and provides the network address of the virtual reality representation of a selected location. A visitor connects to the database server with a client host to visit the locations in the virtual universe. This patent does not describe connections to other data sources other than that created by hum authors.
SUMMARY OF THE CLAIMED INVENTION
• The invention is a network capable of connecting web cameras and IP cameras to virtual reality representations together with other virtual reality data to form a virtual universe. The virtual reality representations can be in a simplified virtual reality format that requires no special computer programming or graphics skills to create.
• A network in accordance with the present invention includes a number of virtual reality representations, each virtual reality representation representing a location in a virtual universe and defined by VR data stored on the network at a network address. For some locations in a virtual reality universe, real time data or time-sliced data (that is video or image data taken at various times) is available to add to the static virtual reality data.
• A database stores the network address and the location in the universe of each virtual reality representation as well as stores the web camera or IP camera data as well as actual links to the web or IP cameras. A database server provides access to the database. The database server generates a list of locations in response to a location query from a visitor, and provides the network address of the virtual reality representation of a selected location.
• The visitor connects to the network using a client host adapted to communicate with the domain server. The host receives data representing the network address of the VR data server associated with a selected VR representation. The host is also adapted to communicate with the VR data server to access the VR data set defining the VR representation.
• In using the network, the visitor is preferably presented with a map displaying locations in the virtual universe. Each location is associated with a virtual reality representation accessible through the network. The visitor selects a location on the map he or she desires to visit. The domain server receives the selected location and retrieves from the database the network location of the data server providing access to the selected virtual reality representation. The domain server transmits the network address of the data server to the host, and the host communicates with the data server to receive the VR data defining the virtual reality representation. For web camera or IP camera connections, the domain server transmits the network address of the data server to the host, and the host communicates with the data server to receive the VR data from the web camera or IP camera stored or real time data defining the virtual reality representation.
• In one possible embodiment, the client host includes a monitor that displays both the map and the virtual reality presentation generated from the static VR data along with data from web or IP cameras. In other possible embodiments the virtual reality presentation can utilize specialized hardware separate from the map display.
• In preferred embodiments of the present invention, the network stores data representing paths in the virtual universe. A path is defined by at least two different locations in the universe. When the domain server receives a message from the host requesting virtual movement from a first location to a second location, the domain server communicates the network address of the data server associated with the second location to the host. The host then communicates with that data server and transitions from the first VR presentation to the VR presentation of the second location. The visitor perceives a substantially continuous movement along the path from the first location to the second location without leaving the virtual universe.
• Paths can be defined in different ways in alternative embodiments of the network. The domain server can store predefined path definitions by storing a list of the locations defining the path. Alternatively, the domain server stores a data record for each location in the universe. The data set records the adjacent locations in the universe to define a path from each location to adjacent locations. In other alternative embodiments the path is defined in response to system events and then made available to the user.
• The network preferably includes administrative software that enables new virtual reality representations of static VR data along with data from web or IP cameras to be added to the network. The virtual reality representations can be stored on existing data servers on the network, or stored on data servers that are themselves added to the network. The database is updated to reflect the new locations in the virtual universe and the network addresses of the data servers accessing the representations.
• In one advantageous embodiment of the present invention, the virtual universe is divided into public and private regions. Any author can add to the network a virtual reality static VR data along with data from web or IP cameras representation of a location in the public region of the universe. Only authorized authors can add representations in private regions of the universe.
• In another advantageous embodiment of the present invention, the network is operated as a self-regulating virtual reality universe. The network preferably provides visitor access to a number of virtual reality representations, each authored by a different author or data from web or IP cameras. The domain server receives ratings from visitors to the quality of the virtual reality representations they visited, and assesses the quality of each virtual reality representation based on the ratings provided by the visitors.
• Action is then taken regarding a virtual reality based on the assessed quality of the virtual reality representation. The quality can be rated as a running average of visitor ratings. If the rating falls below a predetermined score, visitor access to the representation can be removed or the representation can be removed from the network. Preferably the action is taken automatically and without human intervention so that the network is self-regulating.
• To simplify creation of virtual reality representations, the VR data can be stored in a simplified file format that stores digital photographs taken from a specific geographic location. An author either provides the links to the web or IP cameras, as well as can determining timing of collecting snapshots of the web or IP cameras. Also an author provides a link to a website of web or IP cameras with software able to identify a particular web or IP camera based upon the geo location requested. Also an author takes a number of photographs from the location with a digital camera. The photographs are preferably in JPG format but other “digital film” formats can be used. Each photograph preferably is taken in a different viewing direction, preferably viewing north, south, east, and west. The images are uploaded to the network along with geographical data (for example, latitude and longitude) that identifies where the photographs were taken. The domain server stores the images, the viewing direction associated with each image, and geographical data in a single data file on a data server. The domain server updates its database of either the static VR data or real time or time sliced data from web or IP cameras. associating the geographical location with a virtual location in the virtual universe. The virtual representation is now accessible to visitors, and the photographs are displayed when generating the virtual reality presentation of the virtual location.
• A virtual reality network in accordance with the present invention offers many advantages. A number of different virtual reality representations are made available to visitors through a single, centrally accessible domain server. The domain server enables visitors to experience virtual reality representations created by different authors, and to tour a virtual universe created by logically organizing and connecting the separate representations.
• Authors can easily add new virtual reality representations of either the static VR data or real time or time sliced data from web or IP cameras to the network, enabling visitors to experience a virtual reality universe that grows richer and richer with time. With the simplified VR file format, persons may share with others their travels to places around the world, or may easily create their own virtual universe for business or private use.
• Other objects and features of the present invention will become apparent as the description proceeds, especially when taken in conjunction with the accompanying eight drawing sheets illustrating an embodiment of the invention.
• It is also understood; that there are many ways that the databases can be connected to, as in this case servers are defined by holding data by geo-locations, but it can be connected in any other cloud based structure.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a schematic view of a virtual reality universe realized as a distributed location network in accordance with the present invention;
• FIG. 2 is a schematic view of a virtual reality representation record used in the network shown inFIG. 1;
• FIG. 2A is a schematic view of a web cam or IP camera virtual reality representation record used in the network shown inFIG. 1;
• FIG. 2B is a schematic view of a web cam or IP camera links virtual reality representation record used in the network shown inFIG. 1;
• FIG. 2C is a schematic view of a web cam or IP camera links and timer of the link of virtual reality representation record used in the network shown inFIG. 1;
• FIG. 3 is a schematic view of a virtual reality record used in the network shown in FIGURE.
• FIG. 3A is a schematic view of a virtual reality web cam or IP camera record used in the network shown inFIG. 1;
• FIG. 4 is a sequence diagram illustrating a visitor utilizing a client host communicating with the network shown inFIG. 1 to view a location in the virtual universe;
• FIG. 4A is a sequence diagram illustrating a visitor utilizing a client host communicating with the web or IP cameras data network shown inFIG. 1 to view a location in the virtual universe;
• FIG. 5 is a view of the client host display displaying a map of the universe and a virtual reality presentation of a location in the virtual universe;
• FIG. 5A is a view of the client host display displaying a map of the universe and a virtual reality presentation of web camera or IP camera data of a location in the virtual universe;
• FIG. 6 is a sequence diagram similar toFIG. 4 illustrating a visitor moving along a path in the virtual universe;
• FIGS. 7aand7brepresent paths in the virtual universe extending between adjacent locations in the universe;
• FIGS. 8-10 illustrate other paths in the virtual universe; and
• FIG. 11 represents photographs that define a simplified virtual reality representation of a physical location modeled in the virtual universe.
DETAILED DESCRIPTION
• Systems and methods for enabling a visitor to access VR representations authored by different authors of locations in a virtual universe via a computer network are provided. A plurality of VR data sets may be stored. Each VR data set comprise web or IP camera VR datasets and may be independently authored by a respective author different from the other authors. One or more VR data servers may be adapted to access and transmit the VR data sets, and each VR data set may be associated with a VR data server for access to the VR data set. A domain server may be adapted to access and transmit domain data comprising the location within the universe of each VR representation and the network address of the VR data server associated with the VR representation. Further, a client host may be adapted to communicate with the domain server to receive domain data representing the network address of the VR data server associated with a selected VR representation, the client host further adapted to communicate with that VR data server to access the VR data set defining the VR representation without leaving the virtual universe.
• Users or visitors may use any number of different electronic computing client devices, which can include, but is not limited to, general purpose computers, mobile phones, smartphones, personal digital assistants (PDAs), portable computing devices (e.g., laptop, netbook, tablets), desktop computing devices, handheld computing device, or any other type of computing device capable of communicating over a communication network. Such devices are preferably configured to access data from other storage media, such as, but not limited to memory cards or disk drives as may be appropriate in the case of downloaded services. Such devices preferably include standard hardware computing components such as, but not limited to network and media interfaces, non-transitory computer-readable storage (memory), and processors for executing instructions that may be stored in memory.
• FIG. 1 illustrates a distributedlocation network10 in accordance with the present invention.
• Thenetwork10 enables a visitor to visit and explore a virtual universe.FIG. 1 illustrates amap12 of the virtual universe displayed on a visitor's computer monitor by a software program or virtual reality browser (VR browser)14 running on a visitor'scomputer16 connected as a network client. The universe can model a real or tangible space, such as the surface of the Earth, with the universe representing real or tangible locations in physical space. Alternatively, the universe can model an imaginary space, such as L. Frank Baum's Oz or a stick model of a protein molecule, with the universe representing imaginary locations in nonphysical space.
• Thenetwork10 is preferably a local, proprietary network (e.g., an intranet) and/or is alternatively a part of a larger wide-area network (e.g., the cloud). Thenetwork10 can be a local area network (LAN), which is communicatively coupled to a wide area network (WAN) such as the Internet. The Internet is a broad network of interconnected computers and servers allowing for the transmission and exchange of Internet Protocol (IP) data between users connected through a network service provider. Examples of network service providers are the public switched telephone network, a cable service provider, a provider of digital subscriber line (DSL) services, or a satellite service provide.
• The visitor explores the universe by selecting and viewing virtual reality presentations of virtual locations or points18 on themap12. Eachpoint18 represents a location in the universe that has at least one virtual reality representation available for a visitor to access and experience. Apoint18 can model a point, area or volume in the virtual universe and a visitor may be capable of moving about the area or volume if the virtual reality presentation enables it.
• TheVR browser14 retrieves the data for the virtual reality representations from virtual reality data servers (VR data servers)20.VR data servers20 are connected to thebrowser14 bynetwork connections22. Thenetwork connections22 may be through a Local Area Network (LAN) or a global network such as the Internet.VR data servers20 may include any type of server or other computing device as is known in the art, including standard hardware computing components such as network and media interfaces, non-transitory computer-readable storage (memory), and processors for executing instructions or accessing information that may be stored in memory. The functionalities of multiple servers may be integrated into a single server. Any of the aforementioned servers (or an integrated server) may take on certain client-side, cache, or proxy server characteristics. These characteristics may depend on the particular network placement of the server or certain configurations of the server.
• EachVR data server20 provides access toVR data24 for a virtual reality representation of the selectedpoint18. Data can be stored in conventional virtual reality file formats such as QUICKTIME, X3D, VRML, and the like, or can be stored as separate digital image files.VR data24 can be stored on theVR data server20 or stored on additional network data servers (not shown) distributed through thenetwork10.
• Theentire network10, including thenetwork client16 and theservers20 and26, may also be hosted on a single computer if a distributed network is not required.
• Apoint18 may have a number of different virtual reality representations served by a number of differentVR data servers20. These representations may be stored in different file formats, may represent the point in different seasons of the year or in different historical eras, or may provide an alternative or augmented user interface or sensory experience. Of course, aparticular data server20 could serve a number of virtual reality representations of apoint18 ordifferent points18.
• Adomain server26 hosts auniverse database30 for displaying themap12 and thepoints18 on themap12. Thedatabase30 preferably includes graphic files, image files, and other data for generating and displaying themap12. Theuniverse database30 may also include the network addresses or network paths to the VR files associated with the virtual reality representations.
• Thedomain server26 also maintains anetwork database32 that stores information about eachpoint18 and the network addresses of the one or moreVR data servers20 that provide access to VR representations of thepoint18.
• Thenetwork database32 holds a number of virtual reality representation records (VRR records)34.
• FIG. 1. also showsconnection20A to web orIP camera server20B. Web orIP camera server20B is connected to networkdatabase24A and32A ofvirtual representation records34A (seeFIG. 2A) and 38A (seeFIG. 3A). Web orIP camera server20B is also connected (thruconnection20C) tointernet cloud29A which in turn connects to numerous web or IP cameras examples30A,30B and30C. Web orIP camera server20B is also connected (thruconnection20D) tointernet cloud29B which connects to numerous web or IP cameras website.
• FIG. 2 illustrates atypical VRR record34. TheVRR record34 is a data structure that provides information enabling theVR browser14 to locate theVR data server20 providing access to a specific VR representation. AVRR record34 includes the location of thepoint18 and the network address of theVR data server20 associated with the VR representation of thepoint18.
• TheVRR record34 preferably also includes metadata providing additional information about thepoint18, the associatedVR data server20, and the virtual reality representation of thepoint18. Metadata can include the author, VR file format, or a description of the VR representation. Other metadata can include digital rights management (DRM) information, initial orientation or direction of the default opening view of the virtual reality representation, or the like.
• EachVR data server20 maintains alocal database36 that records the location or locations of theVR data24 accessed through the VR data server20 (seeFIG. 1). Thelocal database36 holds a virtual reality record (VR record)38 for each representation accessed through theVR data server20.
• FIG. 2A illustrates atypical VRR record34A. TheVRR record34A is a data structure that provides information enabling theVR browser14 to locate theVR data server20B providing access to a specific VR representation. AVRR record34A includes the location of thepoint18 and the network address of theVR data server20B associated with the VR web or IP camera representation of thepoint18.
• TheVRR record34A preferably also includes metadata providing additional information about thepoint18, the associatedVR data server20B, and the virtual reality wen or IP camera representation of thepoint18. Metadata can include the author, VR file format, or a description of the VR representation. Other metadata can include digital rights management (DRM) information, initial orientation or direction of the default opening view of the virtual reality representation, or the like. Other metadata includes Web or IP Cam Data Location, Web or IP Cam Real Time Link (the link to the real time web or IP camera) and Web or IP Cam Time sliced Data (that is data that is collected at various times from web or IP cameras).
• EachVR data server20B maintains alocal database36A that records the location or locations of theVR data24A accessed through theVR data server20B (seeFIG. 1). Thelocal database36A holds a virtual reality record (VR record)38A for each representation accessed through theVR data server20B.
• FIG. 2B shows example VRRR record for Web or IP Cameras storing the Web or IP Cam Aggregator Link (hyper link to the web or IP cameras).
• FIG. 2C. shows example VRRR record for Web or IP Cameras storing the Web or IP Cam Aggregator Link timer collector that is the time data that tells the network when to take a snapshot data of any connected Web or IP camera. In this way, the web or IP camera data stored can be stored over time.
• FIG. 3 illustrates atypical VR record38. TheVR record38 is a data structure that includes the location of thepoint18, the location of theVR data24 for the representation of the point, and metadata containing further information about theVR data24. For example, such metadata may include the author and digital rights management (DRM) information, VR data format, or descriptive information about the VR representation.
• Theuniverse database30, thenetwork database32, or alocal database36 can be realized as a single-file relational database, object database, or hierarchal XML database. Alternatively, adatabase30,32,36 can be realized as a number of separate data files, wherein each data record is stored in a respective data file. The data file can be in structured text file format, XML format, or other conventional data format. The selection of database schema and format is based on conventional software engineering considerations, including the network architecture, the network load, and available software.
• FIG. 3A illustrates atypical VR record38A. TheVR record38A is a data structure that includes the location of thepoint18, the location of the web or IPcamera VR data24A for the representation of the point, and metadata containing further information about theVR data24A. For example, such metadata may include the author and digital rights management (DRM) information, VR data format, or descriptive information about the VR representation. Other metadata includes Web or IP Cam Data Location, Web or IP Cam Real Time Link (the link to the real time web or IP camera) and Web or IP Cam Time sliced Data (that is data that is collected at various times from web or IP cameras).
• Theuniverse database24, thenetwork database24A, or alocal database36A can be realized as a single-file relational database, object database, or hierarchal XML database. Alternatively, adatabase30,24A,36A can be realized as a number of separate data files, wherein each data record is stored in a respective data file. The data file can be in structured text file format, XML format, or other conventional data format. The selection of database schema and format is based on conventional software engineering considerations, including the network architecture, the network load, and available software.
• FIG. 4 illustrates a first user session wherein avisitor39 explores the virtual universe point-by-point. For clarity only one visitor is shown connected to thenetwork10, but it should be understood that a number of visitors can simultaneously explore the universe.
• TheVR browser14 retrieves themap data30 from thedomain server26 and begins the user session by displaying themap12 shown inFIG. 1. Themap12 displays thepoints18, and the user interface of theVR browser14 enables thevisitor39 to select whichpoint18 and the representation of the selectedpoint18 he or she would like to experience.
• It should be understood that theuniverse database30 may include or enable generation of a number of different maps representing different regions or sub-regions of the universe. TheVR browser14 may simultaneously or sequentially display different maps during a user session. For example, the visitor is initially presented with a “master map” or model of the entire universe. If the virtual universe is sufficiently extensive, the user interface of theVR browser14 enables users to “drill down” and select more detailed maps or models of sub-regions (for example, maps representing a continent, a country, a city, and then a city block) to select a desiredpoint18.
• Map12 should therefore be understood to represent all possible maps theVR browser14 may display as part of its user interface. Maps may be representations of one-dimensional, two-dimensional, three-dimensional, or n-dimensional space as is appropriate for the virtual universe such maps represent.
• Themap12 may also display additional information that assists the visitor in selecting a point or a VR representation of the point. For example, the map might indicate points of historical interest or the number and types of virtual reality representations available for each point.
• In the illustrated embodiment, the visitor selects a desiredpoint18afrom themap12 by clicking the mouse (seeFIG. 1). Thebrowser14 determines the location of the selectedpoint18aon the map and requests alist40 ofVRR records34 associated with that point from the domain server26 (seeFIG. 2).
• Thedomain server26 queries thenetwork database32 for the list of VRR records of points at or proximate to the selectedpoint18a. Thedomain server26 returns theVRR list40 to theVR browser14. TheVR browser14 generates a list of available VR representations from theVRR list40, and displays the list for the selectedpoint18a.
• The display list can include information from the metadata to assist the visitor in selecting a VR representation to experience. For example, theVR browser14 might display an icon for each representation indicating some characteristic of the representation (such as season of the year, its VR file format, or quality moderation value (discussed in further detail below)).
• The visitor selects from the display list the desired virtual reality representation to experience. If there is only one representation associated with the selected point, the steps of displaying and selecting from the list can be eliminated.
• TheVR browser14 uses theVRR record34 associated with the selected representation to look up the network address of theVR data server20 providing access to the virtual representation. TheVR browser14 requests theVR record38 for the selected representation from theVR data server20. TheVR browser14 uses the returnedVR record38 to fetch the VR data file24 and initialize a virtual reality presentation that will be perceived and experienced by thevisitor39. For example, theVR browser14 could start one helper application to display a QUICKTIME presentation and another helper application to display a VRML presentation.
• In the illustrated embodiment, theVR browser14 displays themap12 in a first window and the virtual reality presentation in a second window (discussed in greater detail later). In other embodiments, virtual reality presentations could be displayed independently of theVR browser14 through more specialized or augmented VR hardware, such as a headset.
• During the VR presentation, theVR browser14 receives input from the visitor and communicates with theVR data server20 to fetch theVR data36. The visitor can change the point of view and move about the presentation as permitted by the virtual reality representation being experienced. When the visitor ends the VR presentation, the window displaying the VR presentation closes or goes blank. Thevisitor39 can then select anew point18 or quit the application.
• In addition to exploring selectedpoints18, thenetwork10 enables thevisitor39 to explore paths through the universe. See, for example,path42 shown inFIG. 5. A path is defined as extending along a set of points or extending between start and end points in the universe. Thenetwork10 supports multiple types of paths as will be described in further detail below.
• A visitor sequentially experiences virtual reality presentations of thepoints18 on the path. TheVR browser14 automatically moves from displaying one VR presentation to the next in response to visitor input indicating movement along the path. This provides the visitor with the perception of walking through or being “immersed” in the universe. If thepoints18 are sufficiently close together, the visitor will essentially perceive continuous or seamless movement through the virtual universe.
• Path42 represents a pre-defined path. A pre-defined path is defined prior to the user session and may, for example, represent a virtual river, highway, or historical trail through the universe. Pre-defined paths are preferably defined in theuniverse database30 and represented on themap12 for selection by thevisitor39.
• FIG. 4A illustrates a first user session wherein avisitor39 explores the virtual universe point-by-point. For clarity only one visitor is shown connected to thenetwork10, but it should be understood that a number of visitors can simultaneously explore the universe.
• TheVR browser14 retrieves themap data30 from thedomain server26 and begins the user session by displaying themap12 shown inFIG. 1. Themap12 displays thepoints18, and the user interface of theVR browser14 enables thevisitor39 to select whichpoint18 and the representation of the selectedpoint18 he or she would like to experience.
• It should be understood that theuniverse database30 may include or enable generation of a number of different maps representing different regions or sub-regions of the universe. TheVR browser14 may simultaneously or sequentially display different maps during a user session. For example, the visitor is initially presented with a “master map” or model of the entire universe. If the virtual universe is sufficiently extensive, the user interface of theVR browser14 enables users to “drill down” and select more detailed maps or models of sub-regions (for example, maps representing a continent, a country, a city, and then a city block) to select a desiredpoint18.
• Map12 should therefore be understood to represent all possible maps theVR browser14 may display as part of its user interface. Maps may be representations of one-dimensional, two-dimensional, three-dimensional, or n-dimensional space as is appropriate for the virtual universe such maps represent.
• Themap12 may also display additional information that assists the visitor in selecting a point or a VR representation of the point. For example, the map might indicate points of historical interest or the number and types of virtual reality representations available for each point.
• In the illustrated embodiment, the visitor selects a desiredpoint18afrom themap12 by clicking the mouse (seeFIG. 1). Thebrowser14 determines the location of the selectedpoint18aon the map and requests alist40 of web or IPcamera VRR records34A associated with that point from the domain server26 (seeFIG. 2).
• Thedomain server26 queries thenetwork database32 for the list of VRR records of points at or proximate to the selectedpoint18a. Thedomain server26 returns theVRR list40 to theVR browser14. TheVR browser14 generates a list of available VR representations from theVRR list40, and displays the list for the selectedpoint18a.
• The display list can include information from the metadata to assist the visitor in selecting a VR representation to experience. For example, theVR browser14 might display an icon for each representation indicating some characteristic of the representation (such as season of the year, its VR file format, or quality moderation value (discussed in further detail below)).
• The visitor selects from the display list the desired virtual reality representation to experience. If there is only one representation associated with the selected point, the steps of displaying and selecting from the list can be eliminated.
• TheVR browser14 uses the web or IPcamera VRR record34A associated with the selected representation to look up the network address of the VR web or IPcamera data server20B providing access to the virtual representation. TheVR browser14 requests theVR record38 for the selected representation from theVR data server20B. TheVR browser14 uses the returned web or IPcamera VR record38A to fetch the web or IP camera VR data file24A and initialize a virtual reality presentation that will be perceived and experienced by thevisitor39. For example, theVR browser14 could start one helper application to display a QUICKTIME presentation and another helper application to display a VRML presentation.
• In the illustrated embodiment, theVR browser14 displays themap12 in a first window and the virtual reality presentation in a second window (discussed in greater detail later). In other embodiments, virtual reality presentations could be displayed independently of theVR browser14 through more specialized or augmented VR hardware, such as a headset.
• During the VR presentation, theVR browser14 receives input from the visitor and communicates with the VR data server web orIP camera20B to fetch the web or IPcamera VR data36A. The visitor can change the point of view and move about the presentation as permitted by the virtual reality representation being experienced. When the visitor ends the VR presentation, the window displaying the VR presentation closes or goes blank. Thevisitor39 can then select anew point18 or quit the application.
• In addition to exploring selectedpoints18, thenetwork10 enables thevisitor39 to explore paths through the universe. See, for example,path42 shown inFIG. 5. A path is defined as extending along a set of points or extending between start and end points in the universe. Thenetwork10 supports multiple types of paths as will be described in further detail below.
• A visitor sequentially experiences virtual reality presentations of thepoints18 on the path. TheVR browser14 automatically moves from displaying one VR presentation to the next in response to visitor input indicating movement along the path. This provides the visitor with the perception of walking through or being “immersed” in the universe. If thepoints18 are sufficiently close together, the visitor will essentially perceive continuous or seamless movement through the virtual universe.
• Path42 represents a pre-defined path. A pre-defined path is defined prior to the user session and may, for example, represent a virtual river, highway, or historical trail through the universe. Pre-defined paths are preferably defined in theuniverse database30 and represented on themap12 for selection by thevisitor39.
• FIG. 5 illustrates theVR browser14 with afirst display window46 and asecond display window50.Display window46 displays themap12, thepath42, and thepoints18 along thepath42 as shown. Thesecond window50 displays the virtual reality presentation of the active, or currently visited,point18b.
• When displaying a virtual reality presentation of apoint18, theVR browser14 preferably displays anicon48 indicating theactive point18. The illustratedicon48 is an arrow that also indicates the approximate direction of the current line of view of the virtual reality presentation shown in thesecond window50.Icon48 is shown indicating thatpoint18bis the active point and that the direction of the current line of view is west.
• Navigation widgets52 associated with thefirst window46 enable the visitor to move along thepath42 or to move to a different path (such as a second path54). Navigation widgets56 associated with thesecond window50 enable the visitor to change the line of view of the VR presentation in thesecond window50.Widgets52 and56 can be combined into a single control if desired, and alternative known interface controls (including the mouse) or other interface widgets may replace or be used with thewidgets52,56.
• 56F is a widget that when activated, will manifest web or IP camera data of the point be viewed as shown inFIG. 5A.
• FIG. 5A illustrates theVR browser14 with afirst display window46 and asecond display window50A.Display window46 displays themap12, thepath42, and thepoints18 along thepath42 as shown. Thesecond window50A displays the web or IP camera virtual reality presentation of the active, or currently visited,point18b.
• When displaying a virtual reality presentation of apoint18, theVR browser14 preferably displays anicon48 indicating theactive point18. The illustratedicon48 is an arrow that also indicates the approximate direction of the current line of view of the virtual reality presentation shown in thesecond window50A.Icon48 is shown indicating thatpoint18bis the active point and that the direction of the current line of view is west.
• Navigation widgets52 associated with thefirst window46 enable the visitor to move along thepath42 or to move to a different path (such as a second path54).
• IP or webcamera navigation data56G shows the actual longitude and latitude or the location of the image shown in50A.
• IP or webcamera navigation widgets56B associated with thesecond window50A enable the visitor to change the location of the web or IP camera, that is, some remote cameras are capable of being remotely changed. This allows the visitor to travel around the location point in real time.
• IP or webcamera navigation widgets56C associated with thesecond window50A enable the visitor to change the time that the image for the web or IP camera picture was taken. This allows the visitor to go from real time, to time sliced data, so the visitor can see the past.
• FIG. 6 illustrates a second user session in which the visitor moves along and explores the path42 (thedatabase36 andVR data24 are omitted from the drawing). TheVR browser14 retrieves the map and path data from theuniverse database30 and displays themap12 as shown inFIG. 5.
• The visitor selects the desiredpath42, and theVR browser14 obtains theVRR record list40 for thepoints18 on thepath42 from thedomain server26. For simplicity, it is assumed that eachpoint18 on thepath42 has only one virtual reality representation; so eachVRR record34 is associated with asingle point18 on thepath42.
• TheVR browser14 uses theVRR record34 associated with the path'sstarting point18cto look up the network address of the appropriateVR data server20 and retrieves theVR record38 from thatserver20. The VR record data is used to initialize and display the virtual reality presentation of the first, orstarting point18c(seeFIG. 5). Widgets56 control the line of view of the virtual reality presentation as described.
• Widgets52 move the visitor to the next, or second point on thepath42. TheVR browser14 uses theVRR record34 associated with the next point to retrieve VR data for the next point. If thepoints18 along thepath42 are sufficiently close, the transition from point to point appears to the visitor as a continuous movement along the path.
• In moving from the virtual reality representation of one point to another, theVR browser14 may also maintain (as closely as possible) the same line of view to maintain the appearance of continuous movement. For example, if the visitor is looking south and moves to the next point, the initial line of view for the next point is also viewing south. In alternative embodiments, however, theVR browser14 can initialize each virtual reality presentation with a pre-determined or default line of view.
• A second type of path preferably supported by thenetwork10 is a connection path. A connection path is a dynamic path generated from anactive point18 toadjacent points18 during the user session.FIG. 7aillustrates themap12 displayingconnection paths58 extending between anactive point18dandadjacent points18e-18i.Connection paths58 connect two adjacent or neighboringpoints18, enabling the visitor to pick and choose his or her own route through the universe.
• Theconnection paths58 typically provide multiple routes between points. For example, the visitor can move frompoint18dto point18hdirectly, or can move first to point18gand then to point18h.FIG. 7billustrates theconnection paths59 when the visitor reachespoint18h. Thepaths59 start frompoint18hand end atpoints18d,18g, and18i.
• The VRR record(s)34 for eachpoint18 preferably includes a connection data set (seeFIG. 2) that lists adjacent points18. For example, the connection data set forpoint18d(shown inFIG. 7a) includes point's18e-18iand the direction to each point. This enables theVR browser14 to display theconnection paths58 available to the visitor; theVR browser14 can also iteratively retrieve the VRR records of adjacent points to display a network of available paths on themap12. The connection data set also allows theVR browser14 to efficiently respond and display the next virtual reality presentation after receiving a visitor request to move in a given direction fromactive point18d.
• Thedomain server26 generates the connection data set when anew point18 is added to the network. The adjacent points18 are retrieved from theuniverse database30 to generate the connection data set for thenew point18.
• Thedomain server26 also modifies the connection data set ofadjacent points18 as illustrated inFIGS. 8 and 9. Themaps12 inFIGS. 8 and 9 are otherwise identical to themap12 inFIG. 7a, but include a later-added point18jor18k, respectively. InFIG. 8, point18jis inserted betweenpoints18dand18h. Point18jis now adjacent to point18dinstead ofpoint18h. The connection data set associated withpoint18dis modified to removepoint18hand to insert point18jfor theconnection path58 extending betweenpoints18dand18j. InFIG. 9, point18kis an additional point adjacent to point18d. Point18kis added to the data connection set associated withpoint18dfor theconnection path58 extending betweenpoints18dand18k.
• A visitor can also preferably edit the connection data set for apoint18 to add or subtract connection paths extending from the point. The visitor can add aremote point18 to the data set, creating a connection path to that remote point. A point can be removed from the data set, eliminating a connection path. The modified data set can be stored on the visitor'smachine16 for use only by the visitor'sbrowser14, or the modifications can be saved in thenetwork database32 to be made available to all visitors.
• A third type of path supported by thenetwork10 is the event path. An event path is a dynamic path generated by the network in response to an event or visitor query. For example, thevisitor39 may request the path from his or her current location to another location in the universe. TheVR browser14 queries theuniverse database30 and displays thepoints18 along the path on themap12.
• FIG. 10 illustrates an event path60 generated by an event. Thedomain server26 maintains a list of active visitors on thenetwork10 and the current location of each visitor in the universe. Themap12 displays the positions of all theusers39 and the path to each user. For clarity only two active visitors39a,39band one path60 between them are shown inFIG. 10. Paths60 are automatically updated as visitors move about in the universe and as visitors join and leave the network.
• A fourth type of path supported by the network is the visitor-defined path. Path54 (seeFIG. 5) represents a visitor-defined path. The visitor defines the end points and thepoints18 of thepath54. The path can be created, for example, by inputting a list of thepoints18 defining the path or by having theVR browser14 maintain and store a history of thepoints18 visited by the visitor in prior visits.
• The definition of the visitor-definedpath54 may be stored on the visitor'smachine16 for use only by thevisitor39. Alternatively, the path definition is stored in theuniverse database30 and made available to all network visitors.
• As described above, thedomain server26 provides a single point of access for theVR browser14 to initiate a user session and display a map ofavailable points18 in the universe. This enablesnew points18 to be added to the universe and new virtual reality representations of new or existingpoints18 to be made available to allVR browsers14 on thenetwork10 by updating thedomain server databases30 and32.
• An author creating a virtual reality representation for a new or existingpoint18 stores the data on his or her ownVR data server20 and then connects the VR data server to thenetwork10. The author remotely invokes an administrative program on thedomain server26 that adds the location to theuniverse database30 and adds anew VRR record34 to thenetwork database32. Thenew VRR record34 includes the location of thenew point18 and the network address of the associatedVR data server20. TheVR browser14 automatically generates an up-to-date map12 when it retrieves the map data from theuniverse database30.
• If desired, theclient machine16 cancache VR data34 as well as records from thedatabases30,32, and36 for improved performance. TheVR browser14 uses the local data cache to display the map and to retrieve VR data from thenetwork10. However, the data cache should be refreshed regularly or at the visitor's command to prevent stale data. Alternatively, the database records can include a “Time to Live” field for automatic updating of the data caches.
• To facilitate creation of VR representations ofpoints18, the universe is preferably divided into a public region and a private region. Authors are free to add virtual reality representations of any point in the public region. Only authorized authors can add virtual representations of private regions.
• To illustrate the concept of public and private regions in more concrete terms, themap12 is a virtual representation of the GettysburgNational Military Park62 and the adjacent borough of Gettysburg, Pa.64. SeeFIG. 1; the borough of Gettysburg is represented schematically as a circular area. TheMilitary Park62 is a public region of the universe and the borough ofGettysburg64 is a private region of the universe.
• Tourists or Civil War buffs can author a virtual reality representation for anew point18 in theMilitary Park62 or author an additional virtual reality representation for an existingpoint18. The author can provide visitor access to the representation through a publicly or privately availableVR data server20. The author updates thedomain server databases30,32 through the administrative software as previously described and updates thelocal database36 and stores theVR data24 on thedata server20. The new point and its representation are now available to all visitors.
• Over time, the number of points in the universe having virtual reality representations increases and the number of representations for a given point increases. This enables users to select points and view presentations that provide them with a rich and varied virtual visit to thevirtual Military Park62.
• To further encourage the creation and selection of high-quality virtual presentations, each representation of apublic point18 is preferably assigned a quality moderation value. A quality moderation value represents the quality of the representation and assists visitors in selecting which representations to view. The quality moderation value is preferably stored in the representation's VRR record34 (seeFIG. 2) and is displayed on themap12.
• For example, a representation can be assigned a quality moderation value between 0 and 10, where 0 represents a low quality representation and 10 represent a high quality representation. A visitor can rate the quality of the representation after experiencing the virtual reality presentation. A running average of visitors' ratings is stored as the representation's quality moderation value. This mechanism enables thenetwork10 to be self-moderating in that representations whose quality falls below a minimum value can be automatically removed from the network or not listed for selection.
• Virtual reality representations of points withinGettysburg borough64, however, are limited to authorized authors. Examples of such authors may include owners of commercial establishments who wish to control the content of the virtual reality representation of their store or business. A private representation may be hosted on aVR data server20 whose access is controlled by the author and may or may not be assigned a quality moderation value.
• Virtual reality representations of public points are preferably created in a simple, standardized format to encourage those without technical or computer expertise to contribute virtual reality representations to thenetwork10.
• FIG. 11 illustrates a preferred, simplified virtual reality format. Four images66 are taken with a digital camera from a point, each photograph having a line of view facing north, south, east, and west, respectively. The administrative program uploads the four image files and presents an on-line form requesting the location of the point and associated metadata. The administrative program stores the image files asVR data24 on aVR data server20, updates theuniverse database30, adds the appropriate VRR record to thenetwork database32, and adds the appropriate VR record to thelocal database36.
• Because the illustratedpublic region62 represents an area of the Earth, the latitude and longitude of the corresponding physical location of an actual point on the Earth's surface provides a convenient way of identifying the location of apoint18 on themap12. The administrative program requests the latitude and longitude of the point, which can be obtained, for example, by a GPS reading when the digital photographs are taken.
• It is understood that other kinds of metadata, data fields, data keys, or data formats can be used for or stored in thedatabases30,32, and36 and thatother VR data24 can be stored in other file formats. The data can be distributed on other servers on thenetwork10. But theVR browser14 preferably accesses thenetwork10 initially through thesingle domain server26 regardless of how the data itself is distributed throughout thenetwork10.
• It is contemplated that embodiments of thevirtual reality network10 will be customized for particular industries or visitors. For example, a real estate network would host virtual reality representations of houses available for sale. The seller's real estate agent takes photographs of each room in a house and uploads them to the real estate network, along with the floor plan and other metadata. A buyer's real estate agent selects the house to visit, and the VR browser displays the floor plan and the paths through the house. The visitor moves along the paths in the house, in effect taking a virtual reality tour through each room in the house.
• The present invention may be implemented in an application that may be operable using a variety of devices. Non-transitory computer-readable storage media refer to any medium or media that participate in providing instructions to a central processing unit (CPU) for execution. Such media can take many forms, including, but not limited to, non-volatile and volatile media such as optical or magnetic disks and dynamic memory, respectively. Common forms of non-transitory computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, any other magnetic medium, a CD-ROM disk, digital video disk (DVD), any other optical medium, RAM, PROM, EPROM, a FLASHEPROM, and any other memory chip or cartridge.
• Various forms of transmission media may be involved in carrying one or more sequences of one or more instructions to a CPU for execution. A bus carries the data to system RAM, from which a CPU retrieves and executes the instructions. The instructions received by system RAM can optionally be stored on a fixed disk either before or after execution by a CPU. Various forms of storage may likewise be implemented as well as the necessary network interfaces and network topologies to implement the same.
• While we have illustrated and described preferred embodiments of our invention, it is understood that this is capable of modification, and we therefore do not wish to be limited to the precise details set forth, but desire to avail ourselves of such changes and alterations as fall within the purview of the following claims.

Claims (12)

What is claimed is:

1. A system for enabling a visitor to access VR representations authored by different authors as well as any of a plurality of web or IP cameras of locations in a virtual universe via a computer network, the system comprising:

memory for storing a plurality of VR data sets comprising web or IP camera VR datasets, wherein each VR data set defines a VR representation of a location, each data set independently authored or defined by a respective author different from the other authors;

one or more VR data servers adapted to access and transmit the VR data sets, each VR data set associated with a VR data server for access to the VR data set;

a domain server adapted to access and transmit domain data comprising the location within the universe of each VR representation and the network address of the VR data server associated with the VR representation; and

a client host adapted to communicate with the domain server to receive the domain data representing the network address of the VR data server associated with a selected VR representation, the client host further adapted to communicate with that VR data server to access the VR data set defining the VR representation without leaving the virtual universe.

2. The system ofclaim 1, wherein the web or IP camera data is obtained in real-time.

3. The system ofclaim 1, wherein the web or IP camera data is time-sliced data.

4. The system ofclaim 1, where the web or IP camera data is changeable by remotely changing the camera location.

5. The system ofclaim 1, where the web or IP camera data is extracted from a web site that aggregates the web or IP camera data.

6. The system ofclaim 1, wherein each of the one or more data servers stores a database of the locations of the both static and web or IP camera virtual reality representations accessible through the data server and the network addresses of the VR data sets defining such virtual reality representations, whereby VR data sets can be stored remotely from the data server.

8. The system ofclaim 1, wherein at least one of the VR data sets comprise first data representing a plurality of photographs or data from a web or IP camera taken from a geographical location, each photograph or data from a web or IP camera taken in a respective viewing direction, and second data representing the viewing direction of each photograph.

9. The system ofclaim 1, wherein the client host comprises means for generating both static and web or IP camera virtual reality presentation utilizing the accessed VR data set.

10. The system ofclaim 1, wherein the domain data in the domain server is updated based on author submission of information regarding the network address of the data server and the location in the virtual reality universe associated with the VR data set as well as determining the time when an IP or web camera data is to take automatic pictures.

11. The system ofclaim 1, wherein at least one of the VR data sets comprise data representing a photograph or data from a web or IP camera taken from a geographical location.

12. A method for enabling a visitor to access VR representations authored by different authors as well as any of a plurality of web or IP cameras of locations in a virtual universe via a computer network, the method comprising:

providing a plurality of data servers and a domain server interconnected with the data servers, the data servers providing access to sets of VR data of virtual representations of locations within the universe, each set of VR data authored by a respective different author independently of the other authors, the VR data comprising comprising web or IP camera VR datasets, the domain server providing access to domain data for selecting the location to visit and the network address of the data server providing access to the VR data for the selected location;

receiving data from the visitor representing a selected location in the universe;

accessing the domain data in response to the received data and obtaining therefrom the network address of the data server that provides access to the VR data for the selected location; and

transferring the VR data for the selected location from the data server to the visitor's computer for generation of a VR presentation of the selected location without leaving the virtual universe.

13. A non-transitory computer-readable storage medium, having embodied thereon a program executable by a processor to perform a method for enabling a visitor to access VR representations authored by different authors as well as any of a plurality of web or IP cameras of locations in a virtual universe via a computer network, the method comprising:

providing a plurality of data servers and a domain server interconnected with the data servers, the data servers providing access to sets of VR data of virtual representations of locations within the universe, each set of VR data authored by a respective different author independently of the other authors, the VR data comprising comprising web or IP camera VR datasets, the domain server providing access to domain data for selecting the location to visit and the network address of the data server providing access to the VR data for the selected location;

receiving data from the visitor representing a selected location in the universe;

accessing the domain data in response to the received data and obtaining therefrom the network address of the data server that provides access to the VR data for the selected location; and

transferring the VR data for the selected location from the data server to the visitor's computer for generation of a VR presentation of the selected location without leaving the virtual universe.

Images