Method and system for rendering 3D models of physical objects
A networked computing apparatus simplifies 3D model rendering by offloading 3D model generation to a separate device, reducing hardware and software requirements for catalogue devices and enabling efficient 3D model rendering on client devices.
Patent Information
- Application Number
- PCT/EP2025/073432
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2025-08-15
- Publication Date
- 2026-11-12
AI Technical Summary
Existing systems for rendering 3D models of physical objects require complex hardware, software, and expertise, making them inaccessible to small and medium-sized businesses, and the integration of AR experiences into e-commerce platforms is beyond their capabilities.
A networked computing apparatus comprising a catalogue device, a model device, and client devices, where the catalogue device stores 2D images and metadata, while the model device generates 3D models, which are then rendered on client devices, offloading repetitive computing effort and simplifying hardware and software requirements.
This approach reduces the technical burden on catalogue devices by allowing them to store only 2D images and unique identifiers, while the model device handles 3D model generation, enabling efficient rendering of 3D models on client devices with reduced resource usage.
Smart Images

Figure EP2025073432_12112026_PF_FP_ABST
Abstract
Description
[0001] P194430PC002025-08-13.DOCX
[0002] 1
[0003] Method and system for rendering 3D models of physical objects
[0004] Technical Field
[0005] The present technology relates to a method, a system, and computer programs for rendering 3D models of physical objects on a client device.
[0006] Background Art
[0007] In various applications, it is desired to render 3D models of physical objects as AR content to be viewed on client devices. Such applications, e.g., include web shops, internet catalogues, and social media.
[0008] Tools for rendering 3D models of products, e.g., include Google's ARCore (https: / / en.wikipedia.org / wiki / ARCore) or Apple's ARKit (https: / / en.wikipe-dia.org / wiki / ARKit).
[0009] The creation of 3D models and AR content is a labor-intensive process requiring complex hardware and software, significant expertise, and time. Also, a manual preparation and processing of the data is required.
[0010] Hence, such systems are typically beyond the scope of small and medium-sized businesses, and the integration of embedded AR experiences, e.g., into ecommerce product pages is well beyond the scope of most providers.
[0011] Summary
[0012] Therefore, the problem to be solved is to provide technology that simplifies the technical requirements on hardware and software for such systems and methods.
[0013] In some aspects, this problem is solved by a method for rendering 3D models of physical objects by means of a networked computing apparatus. The computing apparatus comprises at least the following elements:
[0014] - A catalogue device: The catalogue device may, e.g., be a computer (or several computers) running a web shop or an online catalogue.
[0015] - A model device: This is a device separate from the catalogue device and specialized to generate 3D models as described in more detail below.P194430PC002025-08-13.DOCX
[0016] 2
[0017] - Several client devices: These devices are separate from the catalogue device and the model device, they may, e.g., be computing devices running a web browser or a dedicated app for displaying data from the catalogue device.
[0018] The catalogue device, the model device, and the client devices are connected to each other by means of a computer network, such as the internet.
[0019] The method comprises, for each of several different types of physical objects, such as pieces of furniture or other items that are stored on the catalogue device, at least the following steps:
[0020] - Storing, on the catalogue device, a data record. The data record includes at least one 2D image of the type of object and metadata describing parameters of the type. The image may, e.g., be a photograph of the object or a computer-rendered 2D image. There may be several images per type. The metadata may, e.g., comprise data indicative of the category of the object (such as "table" or "chair" or "wardrobe") and / or size information, such as height, width, and depth, and / or material information (such as "wood", "glass", "steel") and / or color information.
[0021] - Transmitting the 2D image and the metadata of the type from the catalogue device to the model device.
[0022] - Generating, on the model device, a 3D model of the type, and storing the 3D model under a unique model identifier.
[0023] - Storing the unique model identifier in the data record on the catalogue device. Hence, the catalogue device now has the means to obtain access to the 3D model for each one of the types of physical objects.
[0024] The method further comprises at least the following:
[0025] - Receiving, via the catalogue device, a request from the one of the client devices to render a desired type of the types of physical objects. For example, a client user may operate a GUI element of a web page that the one of the client devices has retrieved from the catalogue device for a given type of object. The "one of the client devices" may be any one of the client devices. And, in subsequent executions of the method, the role of the "one of the client devices" will be taken over by different ones of the client devices.
[0026] - Retrieving, by the model device, the model attributed to the model identifier of the desired object. In other words, the model device requests transmission of the 3D model data that allows to render the desired model from various points of view.
[0027] - Sending retrieved 3D model (i.e., the model retrieved in the previous step) to the one of the client devices for being rendered on the one of the client devices.P194430PC002025-08-13.DOCX
[0028] 3
[0029] This method greatly simplifies the hardware and software requirements of the catalogue device. The catalogue device merely needs to store the 2D images, metadata, and unique identifiers for a collection of types of the physical objects, but is not concerned with generating or rendering the 3D models. The model device, on the other hand, needs only be able to generate 3D models, and it usually needs to do so only once (or a few times) for each type. The repetitive computing effort for rendering is offloaded to the client devices.
[0030] In this context, "rendering a 3D model" is to be understood as rendering a three-dimensional model on either a single screen or on a stereoscopic screen. In the former case, the user may interactively change their point-of-view to see the object from different sides. In the latter case, the user obtains a three-dimensional stereographic impression of the object and may, in addition, also change the point of view to see different sides of the object.
[0031] As mentioned, the method comprises "receiving, via catalogue device, a request from the one of the client devices to render a desired type of the types physical objects." The role of the catalogue device in this process may take various form:
[0032] - In a first variant of embodiments, the catalogue device merely sends the unique identifier of the desired type to the one of the client devices. The one of the client devices then requests the 3D model from the model device, and the model device sends the 3D model to the one of the client devices (i.e., after transmission of the unique identifier to the one of the client devices, the catalogue device has no further role in the data exchange). This simplifies the structure and workload of the catalogue device.
[0033] - In a second variant of embodiments, the catalogue device sends the unique identifier of the desired type to the model device, whereupon the model device sends the 3D model (directly or via the catalogue device) to the one of the client devices.
[0034] In the first variant of embodiments, the method may include:
[0035] - Receiving, from the one of the client devices by the catalogue device, a request for information about the desired type of the physical object. For example, the user may navigate web pages provided by a web server on the catalogue device to go to a page dedicated to the desired type.
[0036] - Sending, from the catalogue device to the one of the client devices, the information about the desired type. This information includes the unique model identifier. Hence, the one of the client devices now has the unique model identifier.P194430PC002025-08-13.DOCX
[0037] 4
[0038] - Receiving, from the one of the client devices by the model device, the unique model identifier. In other words, the one of the client devices sends the unique model identifier to the model device.
[0039] - Sending, from the model device to the one of the client devices, the 3D model of the desired physical object. Hence, the model device retrieves the 3D model attributed to the desired type using its unique model identifier and transmits it to the one of the client devices.
[0040] This method may further comprise
[0041] - Sending, from the catalogue device to the one of the client devices, an address of the model device. This address may, e.g., be a URL or IP address that the one of the client devices can use to contact the model device. This provides a technical means for direct communication between the client devices and the model device.
[0042] To reduce the resources used for generating 3D models, the method may comprise
[0043] - Receiving, through a 3D administration console of the catalogue device, a command to enable 3D rendering for a selected type of the physical object. This allows the administrator of the catalogue device to select the specific types of physical objects for which 3D rendering is to be enabled.
[0044] - In response to said command, the 2D image(s) and the metadata of the selected type is transmitted, as described above, from the catalogue device to the model device for generating the 3D model on the catalogue device.
[0045] The unique model identifier may be generated by the model device, e.g., when generating the 3D model, thereby ensuring that there is a single unique model identifier for all models stored on the model device. In this case, the unique model identifier is sent from the model device to the catalogue device, e.g., in response to the transmission of the 2D image and the metadata from the catalogue device to the model device. The catalogue device can the store the unique model identifier in the data record of the type of physical object.
[0046] Alternatively, though, the unique model identifier may be generated, at least in part, by the catalogue device, i.e., by combining a first identifier unique to the catalogue device and a second identifier unique to the type of object on the catalogue device. In this case, the unique model identifier may be sent from the catalogue device to the model device for storage with the model.
[0047] In many embodiments, the computing apparatus will comprise several catalog devices. In this case, the method comprises, storing, on the catalogue devices, data records for different types of physical objects, i.e., the types and dataP194430PC002025-08-13.DOCX
[0048] 5
[0049] records stored on two different catalog devices will be, at least in part, different. Yet all the catalogue devices will share the same model device, which reduces the technical effort to set up and maintain the computing apparatus.
[0050] In a further aspect, a data processing system is provided that comprises a catalogue device and a model device with means for carrying out the method.
[0051] In a further aspect, a set of computer programs is provided that comprise instructions which, when set of computer programs is executed by computers of the catalogue device and of the model device, cause the catalogue device and the model device to carry out the method. The set of computer programs comprises at least first software to be run on the catalogue device and second software to be run on the model device.
[0052] Brief Description of the Drawings
[0053] The technology will be better understood and objects other than those set forth above will become apparent when consideration is given to the following detailed description thereof. Such description makes reference to the annexed drawings, wherein:
[0054] Fig. l is a block diagram of an embodiment of a computing apparatus with several catalog devices, a model device, and several client devices,
[0055] Fig. 2 is a block diagram of an example of the catalogue device, Fig. 3 is a block diagram of an example of the model device, Fig. 4 a process for building a 3D model,
[0056] Fig. 5 is a schematic representation of a product page for a given type of physical object,
[0057] Fig. 6 shows example html and JavaScript code for generating a web-based 3D viewer,
[0058] Fig. 7 is an illustration of some possible steps for generating 3D models,
[0059] Fig. 8 is an illustration of some possible steps for rendering a desired physical object
[0060] Some EmbodimentsP194430PC002025-08-13.DOCX
[0061] 6
[0062] Computing Apparatus
[0063] Fig. 1 illustrates an example of a networked computing apparatus having a catalogue device 2, a model device 4, and a client device 6. As shown, typically, there are several catalogue devices 2 and several client devices 6. The devices 2, 4, 6 are connected to each other by means of a computer network 8, such as the internet.
[0064] Typically, but not necessarily, each client device 6 is a single computing device, such as a desktop computer, a tablet, or a smartphone, equipped with product viewing software 10, such as a web browser and / or a dedicated app.
[0065] Each catalogue device 2 may be implemented as a single server computer or several server computers. In the shown embodiment, it implements a server software 12 and a database 14.
[0066] Server software 12 is adapted to communicate with product viewing software 10 on the client devices 6. It may include a web server, e.g., as part of a web shop software.
[0067] Database 14 is a storage software adapted to store data records for each of a plurality of types of physical objects, such as for at least some of the articles that are offered for sale or viewing by server software 12.
[0068] Model device 4 may again be implemented as a single computer or several computers. Typically, there is one model device 4 for several catalogue devices 2, thereby reducing the implementation effort for setting up and running the computing apparatus.
[0069] Model device 4 may comprise a model store 16 and a model builder 18.
[0070] Model store 16 stores a plurality of 3D models. Each 3D model may be stored in a suitable 3D model format, such as a radiance field, 3D Gaussians, or a 3D mesh structure with texture information. In some embodiments, for compatibility with known Tenderers, the 3D model may, at least in part, be stored in .obj, .gib, and / or .usdz format. In addition, for each 3D model, model store 16 stores a model identifier, by means of which the 3D model may be retrieved.
[0071] Model builder 18 comprises one or more software packages adapted to generate, given at least one 2D image and metadata for a type of the physical object, a 3D model for storing it in model store 16.
[0072] More specific examples of these various components of the networked computing apparatus are described in the following sections.P194430PC002025-08-13.DOCX
[0073] 7
[0074] Catalogue Device
[0075] Fig. 2 illustrates an example of embodiments of catalogue device 2. As mentioned, it comprises sever software 12 and a database 14.
[0076] Server software 12 may be a web shop software, such as shopify or shopware, and it comprises (or cooperates with) a web server for, e.g., generating a user-facing web interface 22 and an administrator web interface 24. Web interface 22 provides browsing experience for the third-party users that operate the client devices 6. Admin interface 24 provides a GUI for the operator of catalogue device 2.
[0077] Server software 12 is adapted to provide, via web interface 22, client information for a plurality of types of physical objects. On web interface 22, clients may be able to search, browse, and view the various types of objects that catalog device 2 offers.
[0078] In this context, the word "type" identifies a specific embodiment (model) of the physical object, such as, e.g., a specific type of table from a certain manufacturer with specific size, material, and color.
[0079] In the following example, which does not limit the scope of the technology but illustrates an example where the technology is particularly useful, it is assumed that the physical objects are pieces of furniture that are on sale on catalogue device 2.
[0080] In this case, server software 12 offers clients a web interface to select and view the types of furniture. The user may navigate to a desired type of furniture, i.e., to a specific piece of furniture they are interested in, such as a certain type of a chair or a of a table.
[0081] Database 14 holds, for each type of furniture, a data record comprising, e.g., at least some of the following information:
[0082] - At least one 2D image of the furniture. This may be, as mentioned, a photograph or an artificially generated rendering. The 2D image may be processed to contain only the physical object itself without background or in front of a uniform background. If the 2D image has a background, background removal techniques may be used as described in the section "Model Device".
[0083] - The category of the furniture, such as "chair", "table", "sofa", etc. - The size of the furniture, such as its width, depth, and height. - The material of the furniture, such as such as "wood", "glass", or steel".
[0084] - The color of the furniture, such as an RGB value or a textual color designation.P194430PC002025-08-13.DOCX
[0085] 8
[0086] - A description of the furniture, e.g., describing advantages, applications, or qualities.
[0087] - The catalogue operator's unique identifier of the furniture, such as an SKU number.
[0088] - Pricing information, availability information, shipping information, etc.
[0089] - The unique model identifier (if there has been a 3D model generated for the type) as described below.
[0090] Server software 12 further comprises a 3D administration console 26, which may form part of, or may cooperate with, administrator web interface 24. It may, e.g., be implemented as a plug-in of sever software 12.
[0091] 3D administration console 26 provides, for each or at least some of the types of products, input means, such as GUI control elements, that allow the operator of catalogue device 2 to enable 3D rendering for selected types of furniture. When the operator selects a type of furniture in this way, i.e., if they enable 3D rendering, 3D administration console 26 causes part of the data record, or data derived therefrom, to be sent to model device 4 as a request for generating a 3D model. The data sent in this way includes at least one 2D image of the furniture as well as "metadata". The metadata may, e.g., include at least some of the following:
[0092] - The category of the furniture.
[0093] - The material of the furniture.
[0094] - The color of the furniture.
[0095] - The (textual) description of the furniture.
[0096] In response to a request for generating a 3D model, model device 4 will generate a model as described below and send back a unique model identifier. Administration console 26 receives the unique model identifier from catalogue device 4 and stores it in the data record of the selected type of furniture.
[0097] This model identifier will be used, as described below, when a client device requests information about the selected type of furniture.
[0098] Model Device
[0099] Fig. 3 illustrates an example of some embodiments of catalogue device 4. As mentioned, it comprises a model store 16 and a model builder 18.
[0100] It further comprises a control unit 28, which has a network-facing interface for sending and receiving data. This interface may, e.g., include an API 30, such as a REST-API.P194430PC002025-08-13.DOCX
[0101] 9
[0102] When control unit 28 receives, from a given catalogue device 2, a request to generate a 3D model, together with 2D image and the metadata, it feeds the image and the metadata to model builder 18.
[0103] Model builder 18 may, e.g., comprise a model generator 32, a texture generator 34, and a post-processor 36, and it may, e.g., be adapted to perform a process as shown in Fig. 4.
[0104] Model generator 32 is adapted to generate a 3D geometry of the type of physical object, using the 2D image(s) as well as the metadata as an input.
[0105] Model generator 32 may preprocess the incoming 2D image(s), Step S400 in Fig. 4. For example, if the image shows the product before a background, background removal techniques may be used, e.g., Rembg (see https: / / github.com / danielgatis / rembg) or U2-Net (see Qin et al., "U2-Net: Going Deeper with Nested U-Structure for Salient Object Detection", arXiv:2005.09007v3).
[0106] Textual information in the metadata, such as the description of the object, may be subject to semantic text parsing, e.g., using SpaCy (https: / / spacy.io and https: / / en.wikipedia.org / wiki / SpaCy), see Step S402. As a result of this, the metadata may be converted, at least in part, into structured data describing predefined attributes of the object, such as its material, color, dimensions (width, height, depth), and / or design clues. Design clues may, e.g., include the art style of the object (such as "art nouveau", "art deco", "Bauhaus", or "baroque") if such information is included in the textual metadata.
[0107] In a next Step S404, in particular if only a single image or a small number of images is / are provided, a larger number of synthetic 2D images from different points of view may be generated, e.g., using a multi-view diffusion model. An example for such a model is Trellis by Microsoft, see https: / / github.com / mi-crosoft / TRELLIS as well as Xiang et al., "Structured 3D Latents for Scalable and Versatile 3D Generation", https: / / doi.org / 10.48550 / arXiv.2412.01506.
[0108] For example, the multi -view diffusion model is provided with one or a few 2D images as well as with the, optionally semantically parsed, text of the metadata, whereupon it is made to generate N synthetic views of the object from different directions. N is larger than 1, in particular larger than 10, e.g., N = 16.
[0109] In a next Step S406, the three-dimensional surface geometry of the object is generated. The result of this step is a data structure describing the surface of the object, e.g., as a mesh. This step may, e.g., be carried out by means of Trellis as mentioned above.P194430PC002025-08-13.DOCX
[0110] io
[0111] In other embodiments, steps S404 and S406 may be combined in a single step, e.g., again using TRELLIS, which is able to directly generate the three-dimensional surface geometry starting from a single or only a few 2D images.
[0112] If desired, the surface geometry may be post-processed, Step S408, e.g., for encoding it into a desired format, such as glTF (https: / / gltf-transform.dev / ) and / or for reducing the number of meshes (e.g., using one of the compression extensions at https: / / gltf-transform.dev / ), thereby compressing the data and / or accelerating the rendering process.
[0113] In Step S410, UV maps may be generated for the surface geometry. As known to the skilled person, such UV maps provide a coordinate system for mapping the texture (see below) onto the surface geometry. For example, UV mapping may be generated using TRELLIS as mentioned above.
[0114] In Step S412, at least one texture is selected. Where necessary, several textures are selected and attributed to different parts of the object. This may, e.g., be performed by the Materialistic software package (https: / / github.com / prafull7 / mate-rialistic, https: / / arxiv.org / pdf / 2305.13291), which uses the 2D image of the type of object as an input. It segments the image to identify parts of the object having similar or identical surface texture. Further, suitable physics-based rendering (PBR) materials may be obtained using a tool such as PBR_Boost_3DGen (https: / / github.com / snow-flakewang / PBR_Boost_3DGen, https: / / arxiv.org / pdf / 2411.16080).
[0115] Typical 3D model frameworks are also capable to generate textures on the geometries. However, it has been found that more realistic textures may be generated by a separate pipeline texture generator 34, which processes the 2D image and metadata for generating textures. Hence, in Step S414, the texture may be refined, e.g., by upscaling it for high-resolution display. A suitable tool may, e.g., be provided by NVIDIA Texture Tools Exporter.
[0116] In Step S416, the model may be resized to its real size, e.g., using the structured data as obtained in Step S402. This, e.g., allows to display the object with other objects in its correct size, and / or it allows to render the object together with its dimensions, e.g., in the form of textual data and lines as illustrated in Fig. 5.
[0117] In Step S418, using post processor 36, the model, including its texture, may be stored in a format suited for rendering, e.g., in .gib and / or .usdz, for later rendering.
[0118] Other tools that may be used, instead of Trellis, include
[0119] - Meshy (https: / / www.meshy.ai), Instant Mesh (https: / / github.com / TencentARC / InstantMesh, see also Xu et al., "InstantMesh:P194430PC002025-08-13.DOCX
[0120] 11
[0121] Efficient 3D Mesh Generation from a Single Image with Sparse-view Large Reconstruction Models", arXiv: 2404.07191
[0122] - Tripo SR (https: / / github.com / VAST-AI-Research / TripoSR, see also Tochilkin et al., "TripoSR: Fast 3D Object Reconstruction from a Single Image", arXiv:2403.02151vl)
[0123] - Rodin (https: / / hyper3d.ai / ).
[0124] Other methods using multiple 2D images for generating a 3D model, i.e., generating "Multi-View Stereo (MVS)" reconstructions, may use algorithmic methods (see, e.g., https: / / en.wikipedia.org / wiki / 3D_reconstruction_from_multi-ple_images) or deep learning (see, e.g., Yao et al., "MVSNet: Depth Inference for Unstructured Multi -view Stereo", arXiv: 1804.02505v2). Similarly, techniques based on Signed Distance Fields (SDF) may be used.
[0125] Yet another method for generating 3D models based on one or more 2D images is described in Chen et al., "Learning to Predict 3D Objects with an Interpolation-based Differentiable Renderer", arXiv: 1908.01210v2.
[0126] Typical 3D model frameworks are also capable to generate textures on the geometries. However, as already mentioned, it has been found that more realistic textures may be generated by a separate pipeline texture generator 34, which processes the 2D image and metadata for generating textures, such as in Steps S412 and S414 above, which are then mapped onto the 3D geometry.
[0127] Once model generation is complete, the unique model identifier is generated, and the model is stored under said identifier in model store 16. Also, control unit 28 sends the model identifier back to catalogue server 2, which stores it in database 14.
[0128] The unique model identifier may, e.g., include a first unique identifier that uniquely identifies catalogue server 2 as well as a second unique identifier that uniquely identifies the type of object, among all the types on catalogue server 2. The first unique identifier may, e.g., comprise a URL of catalogue server 2, and the second unique identifier, may, e.g., comprise the SKU of the type.
[0129] Interaction with the Client Device
[0130] As mentioned, the client devices 6 may, e.g., use a web server 10 or an app for querying catalogue device 2.
[0131] In the following example, it is assumed that a web server 10 or app capable of displaying html data is used on the client devices 6 for selecting types of objects and for rendering them.P194430PC002025-08-13.DOCX
[0132] 12
[0133] For example, the client (i.e., the user of client device 6) browses the catalogue of products via the web interface generated by catalogue device 2. When they find a type of furniture of interest, they request information about the type of furniture.
[0134] In response, catalogue server 2 generates or retrieves a web page for the desired type and transmits it, e.g., using html, to client device 6.
[0135] To do so, catalogue server 2 accesses database 14 for information about the desired type, such as pricing, availability, the description, the size, and the category. In addition, it may retrieve the 2D image(s) of the desired type for displaying it on client device 6.
[0136] In addition, it checks if there is a unique model identifier stored in database 14 for the given type of furniture. In the following, it is assumed that this is the case.
[0137] The information sent from catalogue server 2 to client device 6 includes human-readable information about the product as well as the unique model identifier.
[0138] Client device 6 displays the human-readable information as, e.g., in a web page as shown in Fig. 5, with textual or graphical information 40a, 40b, 40c, which is not reproduced in detail in Fig. 5.
[0139] The web page may further comprise a 3D viewer 42, or a link, button, and / or QR code to bring up 3D viewer, where the user can view the furniture or other physical object by rotating, displacing, and scaling it as known from 3D viewers.
[0140] Fig. 6 illustrates an example of part of the underlying html and JavaScript of the web page. As can be seen, the shown example implements 3D viewer 42 primarily in JavaScript. In particular, it instructs client device 6 to download a JavaScript library from model device 4, see line L2. This provides a direct link between client device 6 and model device 4. In the present embodiment, it is assumed that model device 4 can be reached under the address "modelserver.ai".
[0141] The library "viewer.js" that client device 6 is instructed to download on line L2 implements, e.g., a class Product Vi ewer, which can be instantiated to generate a 3D viewer 42 (line L6) using suitable viewer parameters (lines L4).
[0142] The JavaScript that catalogue device 2 sends to client device 6 further comprises the unique model identifier ("xTTm354TlopwIRT52") attributed to the model of the type of furniture as stored on model server 4. The example script of Fig. 6 passes the model identifier to the instantiated model viewer (line L8), which then generates 3D viewer 42 (Fig. 5) for the type of product.P194430PC002025-08-13.DOCX
[0143] 13
[0144] The viewer obtains the 3D model from model device 4, downloads it to client device 6, and renders it locally in client device 6. For example, the viewer may use the WebGL library (see, e.g., https: / / www.khronos.org / webgl / ) to do so.
[0145] Method Examples
[0146] The method for rendering 3D models in an apparatus of the type discussed herein may have two phases, which may be executed in sequential or in at least partially overlapping manner.
[0147] A first phase is executed for generating the 3D models, and a second phase is executed for rendering a desired 3D model.
[0148] A variant of the first phase is illustrated in Fig. 7. It may comprise a sequence of steps that is executed for each one of different physical objects that are to be prepared for viewing as 3D models.
[0149] Typically, each such sequence is initiated on catalogue device 2, e.g., triggered by means of 3D administration console 26 as described above. It may comprise the following steps:
[0150] - S700: On a given catalogue device 2, the data record of the type of physical object is stored, e.g., in database as, e.g., in database 14. This is described in the section "Catalogue Device" above. This step may also be carried out before the sequence of Fig. 7 is initiated.
[0151] - S702: The 2D image and metadate for the type of object to be modeled are transferred from catalogue device 2 to model device 4, e.g., using the API 30 provided by model device 4, as described in the section "Model Device" above.
[0152] - S704: On model device 4, the 3D model is generated and stored, under the unique model identifier, again as described in the section "Model Device" above.
[0153] - S706: The unique model identifier is returned, e.g., as a return value via the API, from model device 4 to catalogue device 2. This is described in the section "Catalogue Device" above.
[0154] - S708: The unique model identifier is stored, by catalogue device 2, in the data record of the type of physical object in database 14. This is again described in the section "Catalogue Device" above.
[0155] These steps are repeated for any type of physical object for which a 3D model is to be generated. They may also be executed for updating the 3D model in case a given type of the physical object has changed or a generated 3D model is not satisfactory.P194430PC002025-08-13.DOCX
[0156] 14
[0157] The second phase is, as mentioned, executed for rendering a desired 3D model. An example of a second phase is illustrated in Fig. 8. It may, e.g., be initiated when the user of a client device 6 wants to know more about a given type of a physical object.
[0158] The example of Fig. 8 comprises the following steps:
[0159] - S800: A request is received, via catalogue device 2, from a client device 6 to render a desired type of the types of physical objects. For more details, see below.
[0160] - S802: Model device 4 retrieves the 3D model of the desired type of object. This may, e.g., occur in response to the JavaScript viewer as described in the section "Interaction with the Client device" being provided with the unique model identifier.
[0161] - S704: Model device 4 sends the retrieved 3D model to client device 6. Client device 6 then renders the 3D model locally as described in the section "Interaction with the Client device" above.
[0162] Step S700 may use various techniques for processing the request. In the example described in the section "Interaction with the Client device", the following steps were involved:
[0163] - S800a: The given catalogue device 2 receives the request for information about the desired type from the client device 6. This request may, e.g., be formed by the user of the client device 6 navigating to the specific web page of the desired type.
[0164] - S8OOb: Catalogue device 2 sends the information about the desired type to client device 6. This information includes the unique model identifier. This may, e.g., be implemented by sending data of the type shown in Fig. 6 to client device 6.
[0165] - S800c: Client device 6 sends the unique model identifier to model device 4. This may, e.g., occur by means of calling the method loadModel() of the JavaScript Tenderer of Fig. 6 with the unique model identifier as an argument.
[0166] - S8OOd: In response to S800c, model device 4 for sends the 3D model belonging to the unique model identifier to client device 6.
[0167] For improved flexibility, catalogue device 2 may be adapted to send the address of model device 4 to catalogue device 6. This enables catalogue device 6 to contact model device 4 without a-priori knowledge about the location of model device 4. In the example above, the address is transferred in line LI of Fig. 6.
[0168] Alternatively, in S800, the flow of the information may run through catalogue device 2, i.e., it is catalogue device 2 that sends the model identifier toP194430PC002025-08-13.DOCX
[0169] 15
[0170] model device 4. In response, model device 4 sends the corresponding model to client device 6, either directly or via catalogue device 2.
[0171] Notes
[0172] In the examples above, the physical objects are illustrated as pieces of furniture. The present technology is not limited to furniture, though, and may be used for rendering other types physical objects, i.e., for objects that exist, or are to be manufactured to exist, in the real world. Such physical objects may, e.g., include household items, garden items (such as shrubs, trees, outdoor furniture, or other ob-jects for outdoor placement), toys, vehicles, appliances, and / or fashion items.
[0173] While there are shown and described presently preferred embodiments, it is to be distinctly understood that the invention is not limited thereto but may be otherwise variously embodied and practiced within the scope of the following claims.
Claims
P194430PC002025-08-13.DOCX16Claims1. A method for rendering 3D models of physical objects by means of a networked computing apparatus, which computing apparatus comprises- a catalogue device (2),- a model device (4), and- several client devices (6),wherein the catalogue device (2), the model device (4), and the client devices (6) are connected to each other by means of a computer network (8), and wherein the method comprises, for each of several different types of physical objects:- storing, on the catalogue device (2), a data record with at least one 2D image and metadata describing parameters of the type,- transmitting the 2D image and the metadata from the catalogue device (2) to the model device (4),- generating, on the model device (4), a 3D model, and storing the 3D model under a unique model identifier, and- storing the unique model identifier in the data record on the catalogue device (2),wherein the method further comprises:- receiving, via the catalogue device (2), a request from the one of the client devices (6) to render a desired type of the types of physical objects,- retrieving, by the model device (4), the 3D model of the desired object,- sending the retrieved 3D model to the one of the client devices (6) for being rendered on the one of the client devices (6).
2. The method of claim 1 comprising:receiving, from the one of the client devices (6) by the catalogue device (2), a request for information about the desired type of the physical object,sending, from the catalogue device (2) to the one of the client devices (6), the information about the desired type including the unique model identifier,receiving, from the one of the client devices (6) by the model device (4), the unique model identifier,P194430PC002025-08-13.DOCX17sending, from the model device (4) to the one of the client devices (6), the 3D model of the desired physical object.
3. The method of claim 2 comprisingsending, from the catalogue device (2) to the one of the client devices (6), an address of the model device (4).
4. The method of any of the preceding claims wherein the metadata transmitted for a type of the physical object from the catalogue device (2) to the model device (4) include at least one of the group consisting ofa category of the type,a size of the type,a material of the type, and / ora color of the type.
5. The method of any of the preceding claims further comprising receiving, through a 3D administration console (26) of the catalogue device (2), a command to enable 3D rendering for a selected type of the physical object,in response to said command, transmitting the 2D image and the metadata of the selected type from the catalogue device (2) to the model device (4) for generating the 3D model on the catalogue device (2).
6. The method of any of the preceding claims comprising generating the unique model identifier by the model device (4) and, sending the unique model identifier from the model device (4) to the catalogue device (2) for storage.
7. The method of any of the preceding claims, wherein the computing apparatus comprises several catalog devices (2), wherein the method comprises, storing, on the catalogue devices (2), data records for different types of physical objects.
8. A data processing system comprising a catalogue device (2) and a model device (4) with means for carrying out the method of any of the preceding claims.P194430PC002025-08-13.DOCX189. A set of computer programs comprising instructions which, when set of computer programs is executed by computers of the catalogue device (2) and of the model device (4) of any of the preceding claims cause the catalogue device (2) and the model device (4) to carry out the method of any of the claims 1 to 7.
