Page rendering method, page data interaction system and device, equipment and medium
By detecting the floor type of metaverse page data and using the metaverse rendering engine of the smart device for rendering, the slow loading and interactive lag caused by the complex metaverse floor data is solved, and the loading efficiency of the user terminal is improved.
Patent Information
- Application Number
- CN202310780877.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-28
- Publication Date
- 2024-12-31
AI Technical Summary
The metaverse floor data is complex and the code is large, which causes the user terminal to load the metaverse floor content slowly and the interaction is stuttering.
By detecting the floor type of the metaverse page data, if it is the metaverse floor type, the metaverse rendering engine is deployed using the intelligent device in the LAN for page rendering, reducing the computing burden of the user terminal and improving loading efficiency.
It effectively alleviates the interaction lag of user terminals, improves the loading efficiency of metacosmic floor content, and avoids excessive computing resources.
Smart Images

Figure CN119228961A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present disclosure relate to the computer field, and in particular to a page rendering method, a page data interaction system, a device, a equipment, and a medium. Background Art
[0002] With the rapid development of information technology, the Metaverse has emerged. It is a virtual world that uses technology to link and create, map and interact with the real world, and a digital ecological space with a new social system. At present, the rendering of the Metaverse page is usually done by using Three.js (JavaScript 3D graphics engine library), Unity3D or webGL (Web Graphics Library).
[0003] However, the above method usually has the following technical problems: the Metaverse floor data is relatively complex, the code size is large, and direct rendering can easily cause the user terminal to load the Metaverse floor content slowly and cause interaction jams.
[0004] The above information disclosed in this Background section is only for enhancement of understanding of the background of the inventive concept and therefore it may contain information that does not form the prior art that is already known in this country to a person of ordinary skill in the art. Summary of the invention
[0005] The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.
[0006] Some embodiments of the present disclosure propose a page rendering method, a page data interaction system, an apparatus, an electronic device, a computer-readable medium, and a program product to solve the technical problems mentioned in the above background technology section.
[0007] In a first aspect, some embodiments of the present disclosure provide a page rendering method, the method comprising: in response to receiving metaverse page data corresponding to a metaverse page rendering request, determining whether the page floor type corresponding to the above-mentioned metaverse page data is a metaverse floor type; in response to determining that the above-mentioned page floor type is a metaverse floor type, determining whether there is an associated smart device in the current local area network, wherein a metaverse rendering engine is deployed in the above-mentioned smart device; in response to determining that there is an associated smart device in the current local area network, sending the above-mentioned metaverse page data to the above-mentioned smart device; in response to receiving the metaverse floor code snippet sent by the above-mentioned smart device, performing page rendering according to the above-mentioned metaverse floor code snippet.
[0008] Optionally, the method further includes: in response to determining that there is no associated smart device in the current local area network, performing page rendering according to the metaverse page data.
[0009] Optionally, before sending the Metaverse page data to the smart device, the method further includes: sending a Metaverse page configuration request to the smart device.
[0010] Optionally, before determining whether the page floor type corresponding to the Metaverse page data is a Metaverse floor type in response to receiving the Metaverse page data corresponding to the Metaverse page rendering request, the method further includes: sending a Metaverse page rendering request to an associated server.
[0011] In a second aspect, some embodiments of the present disclosure provide a page data interaction system, including: a server, a user terminal, and a smart device cluster, wherein the server is configured to: compile a metaverse rendering engine into a wide area network metaverse rendering file, and deploy the wide area network metaverse rendering file to the smart devices in the smart device cluster; the user terminal is configured to: in response to receiving the metaverse page data corresponding to the metaverse page rendering request, send the metaverse page data to the smart devices in the smart device cluster; the smart device is configured to, in response to receiving the metaverse floor code snippet sent by the smart device, perform page rendering according to the metaverse floor code snippet, and send the metaverse floor code snippet to the user terminal; the user terminal is configured to: in response to receiving the metaverse floor code snippet sent by the smart device, perform page rendering according to the metaverse floor code snippet.
[0012] Optionally, the user terminal is further configured to: determine whether the page floor type corresponding to the metaverse page data is a metaverse floor type; in response to determining that the page floor type is a metaverse floor type, determine whether there is a smart device in the smart device cluster in the current local area network; in response to determining that there is a smart device in the smart device cluster in the current local area network, send the metaverse page data to the smart device.
[0013] In a third aspect, some embodiments of the present disclosure provide a page rendering device, comprising: a first determination unit, configured to determine whether the page floor type corresponding to the metaverse page data is a metaverse floor type in response to receiving metaverse page data corresponding to a metaverse page rendering request; a second determination unit, configured to determine whether there is an associated smart device in the current local area network in response to determining that the page floor type is a metaverse floor type, wherein a metaverse rendering engine is deployed in the above-mentioned smart device; a sending unit, configured to send the above-mentioned metaverse page data to the above-mentioned smart device in response to determining that there is an associated smart device in the current local area network; and a rendering unit, configured to perform page rendering according to the above-mentioned metaverse floor code snippet in response to receiving the metaverse floor code snippet sent by the above-mentioned smart device.
[0014] Optionally, the page rendering apparatus further includes: a page rendering unit configured to perform page rendering according to the above-mentioned metaverse page data in response to determining that there is no associated smart device in the current local area network.
[0015] Optionally, before the sending unit, the page rendering apparatus further includes: a request sending unit configured to send a metaverse page configuration request to the above-mentioned smart device.
[0016] Optionally, before the first determining unit, the page rendering device further includes: a request sending unit configured to send a metaverse page rendering request to an associated server.
[0017] In a fourth aspect, some embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device on which one or more programs are stored, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any implementation manner of the above-mentioned first aspect.
[0018] In a fifth aspect, some embodiments of the present disclosure provide a computer-readable medium having a computer program stored thereon, wherein when the program is executed by a processor, the method described in any implementation manner of the above-mentioned first aspect is implemented.
[0019] In a sixth aspect, some embodiments of the present disclosure provide a computer program product, including a computer program, which implements the method described in any implementation manner of the above-mentioned first aspect when executed by a processor.
[0020] The above-mentioned various embodiments of the present disclosure have the following beneficial effects: through the page rendering method of some embodiments of the present disclosure, the efficiency of loading the metaverse floor content of the user terminal is improved, and the interaction jamming of the user terminal is alleviated. Specifically, the reason why the user terminal loads the metaverse floor content slowly and the interaction jamming is that the metaverse floor data is relatively complex, the code volume is large, and it is directly rendered. Based on this, the page rendering method of some embodiments of the present disclosure, first, in response to receiving the metaverse page data corresponding to the metaverse page rendering request, determines whether the page floor type corresponding to the above-mentioned metaverse page data is the metaverse floor type. Therefore, when it is determined that the page floor type corresponding to the metaverse page data is the metaverse floor type, the page rendering can be performed through the associated metaverse rendering engine. Then, in response to determining that the above-mentioned page floor type is the metaverse floor type, it is determined whether there is an associated smart device in the current local area network. Among them, the metaverse rendering engine is deployed in the above-mentioned smart device. Therefore, the metaverse page can be rendered using the smart device deployed with the metaverse rendering engine. Then, in response to determining that there is an associated smart device in the current local area network, the above-mentioned metaverse page data is sent to the above-mentioned smart device. Thus, the Metaverse page data can be processed by using a smart device that deploys the Metaverse rendering engine. Finally, in response to receiving the Metaverse floor code snippet sent by the smart device, the page is rendered according to the Metaverse floor code snippet. Thus, the Metaverse floor content can be loaded by using the smart device associated with the local area network, and then the loaded Metaverse floor code snippet is sent to the user terminal. Thus, it avoids occupying too many computing resources of the user terminal and alleviates the interaction jam of the user terminal. BRIEF DESCRIPTION OF THE DRAWINGS
[0021] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.
[0022] Figure 1 is an architectural diagram of an exemplary system in which some embodiments of the present disclosure may be applied;
[0023] Figure 2 is a flow chart of some embodiments of the page rendering method according to the present disclosure;
[0024] Figure 3 is a flow chart of some embodiments of the page data interaction system according to the present disclosure;
[0025] Figure 4 is a schematic diagram of the structure of some embodiments of the page rendering device according to the present disclosure;
[0026] Figure 5 It is a schematic diagram of the structure of an electronic device suitable for implementing some embodiments of the present disclosure. DETAILED DESCRIPTION
[0027] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.
[0028] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.
[0029] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0030] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".
[0031] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.
[0032] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.
[0033] Figure 1 An exemplary system architecture 100 is shown to which a page rendering method or a page rendering apparatus according to some embodiments of the present disclosure may be applied.
[0034] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, 103, a network 104 and a server 105. The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.
[0035] Users can use terminal devices 101, 102, 103 to interact with server 105 through network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, 103, such as web browser applications, logistics business applications, search applications, instant messaging tools, email clients, social platform software, metaverse rendering engines, etc.
[0036] Terminal devices 101, 102, 103 can be hardware or software. When terminal devices 101, 102, 103 are hardware, they can be various electronic devices with display screens and supporting information display, including but not limited to smart phones, tablet computers, e-book readers, laptop portable computers and desktop computers, etc. When terminal devices 101, 102, 103 are software, they can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules for providing distributed services, for example, or it can be implemented as a single software or software module. No specific limitation is made here.
[0037] The server 105 may be a server that provides various services, such as a background server that provides support for information displayed on the terminal devices 101, 102, and 103. The background server may analyze and process the received request and other data, and feed back the processing results to the terminal device.
[0038] It should be noted that the page rendering method provided in the embodiment of the present disclosure can be executed by the terminal devices 101, 102, 103, or by the server 105. Accordingly, the page rendering device can be set in the terminal devices 101, 102, 103, or in the server 105. No specific limitation is made here.
[0039] It should be noted that the server can be hardware or software. When the server is hardware, it can be implemented as a distributed server cluster consisting of multiple servers, or it can be implemented as a single server. When the server is software, it can be implemented as multiple software or software modules for providing distributed services, or it can be implemented as a single software or software module. No specific limitation is made here.
[0040] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.
[0041] Continue to refer Figure 2 , shows a process 200 of some embodiments of the page rendering method according to the present disclosure. The page rendering method comprises the following steps:
[0042] Step 201, in response to receiving the metaverse page data corresponding to the metaverse page rendering request, determining whether the page floor type corresponding to the above metaverse page data is the metaverse floor type.
[0043] In some embodiments, the execution body of the page rendering method (for example, Figure 1 The terminal device 101 in the method may determine whether the page floor type corresponding to the above-mentioned metaverse page data is a metaverse floor type in response to receiving the metaverse page data corresponding to the metaverse page rendering request. That is, the execution subject of the page rendering method may be a user terminal. The metaverse page rendering request may refer to a rendering request for an active page containing a metaverse floor sent by the above-mentioned execution subject to an associated server. The metaverse page data is stored in the server. The page floor type corresponding to the metaverse page data may refer to the type of page floor data contained in the metaverse page data. The page floor data may be the source data required for a page module in a loaded page. The page floor type may be the type of the page module when configuring the page. The metaverse floor type may refer to the floor type for building a metaverse page. The metaverse page data may refer to the data for configuring the metaverse page. For example, the metaverse page data may include: page display style, font type, picture, picture format and other data.
[0044] Optionally, in response to receiving the metaverse page data corresponding to the metaverse page rendering request, before determining whether the page floor type corresponding to the above metaverse page data is the metaverse floor type, the above method also includes: sending a metaverse page rendering request to an associated server.
[0045] In practice, first, the above-mentioned execution entity may send a Metaverse page rendering request to the associated server via a wired connection or a wireless connection. The above-mentioned wireless connection method may include but is not limited to 3G / 4G connection, WiFi connection, Bluetooth connection, WiMAX connection, Zigbee connection, UWB (ultra wideband) connection, and other wireless connection methods currently known or to be developed in the future. Then, after receiving the Metaverse page rendering request, the server queries the Metaverse page data locally. Afterwards, the queried Metaverse page data is sent to the above-mentioned execution entity.
[0046] Step 202, in response to determining that the page floor type is a metaverse floor type, determine whether there is an associated smart device in the current local area network.
[0047] In some embodiments, the execution subject may determine whether there is an associated smart device in the current local area network in response to determining that the page floor type is a metaverse floor type. A metaverse rendering engine is deployed in the smart device. That is, the execution subject may automatically join the surrounding local area network. When it is determined that the page floor type is a metaverse floor type, the first postMessage request will be sent in the local area network to determine whether there is an associated smart device in the local area network. The metaverse rendering engine may refer to the rendering engine of the metaverse floor. For example, if no postMessage response is obtained within a preset time, there is no associated smart device in the current local area network.
[0048] Step 203: In response to determining that there is an associated smart device in the current local area network, the metaverse page data is sent to the smart device.
[0049] In some embodiments, the execution subject may send the Metaverse page data to the smart device in response to determining that there is an associated smart device in the current local area network. The smart device may perform edge computing of WebAssembly through the Metaverse rendering engine and splice it into a Metaverse floor HTML code fragment.
[0050] Optionally, before sending the Metaverse page data to the smart device, the method further includes: sending a Metaverse page configuration request to the smart device.
[0051] In some embodiments, the execution subject may send a Metaverse page configuration request to the smart device. Here, the Metaverse page configuration request may be a request for requesting the smart device to perform page configuration on the Metaverse page data.
[0052] Step 204, in response to receiving the Metaverse floor code snippet sent by the above-mentioned smart device, page rendering is performed according to the above-mentioned Metaverse floor code snippet.
[0053] In some embodiments, the execution subject may perform page rendering according to the Metaverse floor code snippet in response to receiving the Metaverse floor code snippet sent by the smart device. The Metaverse floor code snippet may render a completed page code snippet. The execution subject may directly run the Metaverse floor code snippet to complete page rendering on the currently displayed page.
[0054] Optionally, in response to determining that there is no associated smart device in the current local area network, page rendering is performed according to the above-mentioned metaverse page data.
[0055] In some embodiments, the execution subject may render the page according to the metaverse page data in response to determining that there is no associated smart device in the current local area network. That is, the execution subject may render the metaverse page data through Three.js or webGL.
[0056] The above-mentioned various embodiments of the present disclosure have the following beneficial effects: through the page rendering method of some embodiments of the present disclosure, the efficiency of loading the metaverse floor content of the user terminal is improved, and the interaction jamming of the user terminal is alleviated. Specifically, the reason why the user terminal loads the metaverse floor content slowly and the interaction jamming is that the metaverse floor data is relatively complex, the code volume is large, and it is directly rendered. Based on this, the page rendering method of some embodiments of the present disclosure, first, in response to receiving the metaverse page data corresponding to the metaverse page rendering request, determines whether the page floor type corresponding to the above-mentioned metaverse page data is the metaverse floor type. Therefore, when it is determined that the page floor type corresponding to the metaverse page data is the metaverse floor type, the page rendering can be performed through the associated metaverse rendering engine. Then, in response to determining that the above-mentioned page floor type is the metaverse floor type, it is determined whether there is an associated smart device in the current local area network. Among them, the metaverse rendering engine is deployed in the above-mentioned smart device. Therefore, the metaverse page can be rendered using the smart device deployed with the metaverse rendering engine. Then, in response to determining that there is an associated smart device in the current local area network, the above-mentioned metaverse page data is sent to the above-mentioned smart device. Thus, the Metaverse page data can be processed by using a smart device that deploys the Metaverse rendering engine. Finally, in response to receiving the Metaverse floor code snippet sent by the smart device, the page is rendered according to the Metaverse floor code snippet. Thus, the Metaverse floor content can be loaded by using the smart device associated with the local area network, and then the loaded Metaverse floor code snippet is sent to the user terminal. Thus, there is no need to occupy too many computing resources of the user terminal, which alleviates the interaction jam of the user terminal.
[0057] Continue to refer Figure 3 , Figure 3 300 is a flowchart of an embodiment of a page data interaction system according to some embodiments of the present disclosure. The page data interaction system provided by the present disclosure may include: a server, a user terminal, and a smart device cluster.
[0058] Step 301, the server is configured to: compile the Metaverse rendering engine into a wide area network Metaverse rendering file, and deploy the wide area network Metaverse rendering file to the smart devices in the smart device cluster.
[0059] In some embodiments, the above-mentioned server can be configured to: compile the Metaverse rendering engine into a wide area network Metaverse rendering file, and deploy the above-mentioned wide area network Metaverse rendering file to the smart devices in the above-mentioned smart device cluster. That is, first, the above-mentioned server can use C++ to develop the rendering engine (Metaverse rendering engine) of the Metaverse floor based on the cross-platform physical rendering engine Filament. Afterwards, Emscripten can be used to compile the Metaverse rendering engine into a WebAssembly file (Wide Area Network Metaverse rendering file). Afterwards, the Wide Area Network Metaverse rendering file can be deployed to an IoT smart home device cluster with edge computing capabilities. That is, the smart device cluster may refer to an IoT smart home device cluster with edge computing capabilities.
[0060] Step 302: The user terminal is configured to: in response to receiving the metaverse page data corresponding to the metaverse page rendering request, send the metaverse page data to the smart device in the smart device cluster.
[0061] In some embodiments, the user terminal is configured to: in response to receiving the metaverse page data corresponding to the metaverse page rendering request, send the metaverse page data to the smart device in the smart device cluster.
[0062] Optionally, the user terminal is further configured to: determine whether the page floor type corresponding to the metaverse page data is a metaverse floor type; in response to determining that the page floor type is a metaverse floor type, determine whether there is a smart device in the smart device cluster in the current local area network; in response to determining that there is a smart device in the smart device cluster in the current local area network, send the metaverse page data to the smart device.
[0063] Step 303, the smart device is configured to: in response to receiving the Metaverse floor code snippet sent by the smart device, render the page according to the Metaverse floor code snippet, and send the Metaverse floor code snippet to the user terminal.
[0064] In some embodiments, the smart device is configured to, in response to receiving the Metaverse floor code snippet sent by the smart device, render a page according to the Metaverse floor code snippet, and send the Metaverse floor code snippet to the user terminal. The Metaverse rendering engine can perform edge computing of WebAssembly and splice it into the Metaverse floor HTML code snippet.
[0065] Step 304, the user terminal is configured to: in response to receiving the Metaverse floor code snippet sent by the smart device, perform page rendering according to the Metaverse floor code snippet.
[0066] In some embodiments, the user terminal is configured to: in response to receiving the metaverse floor code snippet sent by the smart device, perform page rendering according to the metaverse floor code snippet.
[0067] from Figure 3 It can be seen that Figure 3 In some corresponding embodiments, the process 300 can deploy the Metaverse rendering engine in a smart device, so that when the user terminal renders the Metaverse page, it can render through the smart device. Thereby, the efficiency of loading the content of the Metaverse floor is accelerated. In addition, when rendering the Metaverse floor, the user terminal can use the edge computing capabilities of the Internet of Things terminal device to reduce the pressure of network bandwidth overhead, reduce the burden of the user terminal browser to calculate the complex Metaverse floor, and reduce the rendering time of the Metaverse floor.
[0068] Further references Figure 4 As an implementation of the methods shown in the above figures, the present disclosure provides some embodiments of a page rendering device. These embodiments of the page rendering device are Figure 2 Corresponding to the method embodiments shown, the page rendering device can be specifically applied to various electronic devices.
[0069] like Figure 4 As shown, the page rendering device 400 of some embodiments includes: a first determination unit 401, a second determination unit 402, a sending unit 403 and a rendering unit 404. The first determination unit 401 is configured to determine whether the page floor type corresponding to the above-mentioned Metaverse page data is a Metaverse floor type in response to receiving the Metaverse page data corresponding to the Metaverse page rendering request; the second determination unit 402 is configured to determine whether there is an associated smart device in the current local area network in response to determining that the above-mentioned page floor type is a Metaverse floor type, wherein the Metaverse rendering engine is deployed in the above-mentioned smart device; the sending unit 403 is configured to send the above-mentioned Metaverse page data to the above-mentioned smart device in response to determining that there is an associated smart device in the current local area network; the rendering unit 404 is configured to perform page rendering according to the above-mentioned Metaverse floor code fragment in response to receiving the Metaverse floor code fragment sent by the above-mentioned smart device.
[0070] Optionally, the page rendering apparatus 400 further includes: a page rendering unit configured to perform page rendering according to the above-mentioned metaverse page data in response to determining that there is no associated smart device in the current local area network.
[0071] Optionally, before the sending unit 403, the page rendering apparatus 400 further includes: a request sending unit configured to send a metaverse page configuration request to the above-mentioned smart device.
[0072] Optionally, before the first determining unit 401, the page rendering device 400 further includes: a request sending unit configured to send a metaverse page rendering request to an associated server.
[0073] It is understandable that the units described in the page rendering device 400 and the reference Figure 2 Therefore, the operations, features and beneficial effects described above for the method are also applicable to the page rendering device 400 and the units included therein, and will not be described in detail here.
[0074] Reference below Figure 5 , which shows a schematic diagram of the structure of an electronic device (e.g., terminal device 101) 500 suitable for implementing some embodiments of the present disclosure. The electronic devices in some embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (e.g., vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.
[0075] like Figure 5 As shown, the electronic device 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage device 508 into a random access memory (RAM) 503. In the RAM 503, various programs and data required for the operation of the electronic device 500 are also stored. The processing device 501, the ROM 502, and the RAM 503 are connected to each other via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.
[0076] Typically, the following devices may be connected to the I / O interface 505: an input device 506 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 508 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 509. The communication device 509 may allow the electronic device 500 to communicate with other devices wirelessly or by wire to exchange data. Although Figure 5 The electronic device 500 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Figure 5Each block shown in the figure may represent one device, or may represent multiple devices as required.
[0077] In particular, according to some embodiments of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, some embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In some such embodiments, the computer program can be downloaded and installed from the network through the communication device 509, or installed from the storage device 508, or installed from the ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of some embodiments of the present disclosure are executed.
[0078] It should be noted that the computer-readable medium recorded in some embodiments of the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In some embodiments of the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In some embodiments of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.
[0079] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.
[0080] The computer-readable medium may be included in the electronic device; or it may exist independently without being installed in the electronic device. The computer-readable medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device: in response to receiving the metaverse page data corresponding to the metaverse page rendering request, determine whether the page floor type corresponding to the metaverse page data is the metaverse floor type; in response to determining that the page floor type is the metaverse floor type, determine whether there is an associated smart device in the current local area network, wherein the metaverse rendering engine is deployed in the smart device; in response to determining that there is an associated smart device in the current local area network, send the metaverse page data to the smart device; in response to receiving the metaverse floor code snippet sent by the smart device, perform page rendering according to the metaverse floor code snippet.
[0081] Computer program code for performing the operations of some embodiments of the present disclosure may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0082] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0083] The units described in some embodiments of the present disclosure may be implemented by software or by hardware. The described units may also be provided in a processor, for example, may be described as: a processor comprising: a first determination unit, a second determination unit, a sending unit, and a rendering unit. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances. For example, the first determination unit may also be described as "a unit that, in response to receiving metaverse page data corresponding to a metaverse page rendering request, determines whether the page floor type corresponding to the above metaverse page data is a metaverse floor type".
[0084] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.
[0085] Some embodiments of the present disclosure also provide a computer program product, including a computer program, which implements any of the above-mentioned page rendering methods or metaverse rendering engine deployment methods or page data processing methods when executed by a processor.
[0086] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) and the technical solutions formed.
Claims
1. A page rendering method, comprising: In response to receiving the metaverse page data corresponding to the metaverse page rendering request, determining whether the page floor type corresponding to the metaverse page data is a metaverse floor type; In response to determining that the page floor type is a metaverse floor type, determining whether there is an associated smart device in the current local area network, wherein a metaverse rendering engine is deployed in the smart device; In response to determining that there is an associated smart device in the current local area network, sending the metaverse page data to the smart device; In response to receiving the Metaverse floor code snippet sent by the smart device, page rendering is performed according to the Metaverse floor code snippet.
2. The method according to claim 1, wherein: The method further comprises: In response to determining that no associated smart device exists in the current local area network, page rendering is performed according to the metaverse page data.
3. The method according to claim 1, wherein: Before sending the Metaverse page data to the smart device, the method further includes: Send a Metaverse page configuration request to the smart device.
4. The method according to claim 1, wherein: Before determining, in response to receiving the metaverse page data corresponding to the metaverse page rendering request, whether the page floor type corresponding to the metaverse page data is a metaverse floor type, the method further includes: Send a Metaverse page rendering request to the associated server.
5. A page data interaction system, comprising: Servers, user terminals, and smart device clusters, including: The server is configured to: compile the metaverse rendering engine into a wide area network metaverse rendering file, and deploy the wide area network metaverse rendering file to the smart devices in the smart device cluster; The user terminal is configured to: in response to receiving the metaverse page data corresponding to the metaverse page rendering request, send the metaverse page data to the smart device in the smart device cluster; The smart device is configured to: in response to receiving the Metaverse floor code snippet sent by the smart device, perform page rendering according to the Metaverse floor code snippet, and send the Metaverse floor code snippet to the user terminal; The user terminal is configured to: in response to receiving the Metaverse floor code snippet sent by the smart device, perform page rendering according to the Metaverse floor code snippet.
6. The page data interaction system according to claim 5, wherein: The user terminal is also configured to: Determine whether the page floor type corresponding to the metaverse page data is a metaverse floor type; In response to determining that the page floor type is a metaverse floor type, determining whether there is a smart device in the smart device cluster in the current local area network; In response to determining that there is a smart device in the smart device cluster in the current local area network, the metaverse page data is sent to the smart device.
7. A page rendering device, comprising: A first determination unit is configured to, in response to receiving metaverse page data corresponding to a metaverse page rendering request, determine whether a page floor type corresponding to the metaverse page data is a metaverse floor type; A second determination unit is configured to determine whether there is an associated smart device in the current local area network in response to determining that the page floor type is a metaverse floor type, wherein the metaverse rendering engine is deployed in the smart device; A sending unit, configured to send the Metaverse page data to the smart device in response to determining that there is an associated smart device in the current local area network; The rendering unit is configured to, in response to receiving the metaverse floor code snippet sent by the smart device, perform page rendering according to the metaverse floor code snippet.
8. An electronic device comprising: one or more processors; a storage device having one or more programs stored thereon; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 4.
9. A computer readable medium having a computer program stored thereon, wherein: When the program is executed by a processor, the method according to any one of claims 1 to 4 is implemented.
10. A computer program product, comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 4.
