Dynamic creation and management method and device for multiple rendering scenes, equipment and medium

Abstract

The embodiment of the invention provides a dynamic creation and management method and device for multiple rendering scenes, equipment and a medium, and relates to the technical field of image data processing.The method comprises the steps that a rendering scene management service is constructed, a scene provider and a rendering context supporting each scene type are constructed, and a rendering scene is created; associating the scene providers with the rendering contexts and associating the function modules with the rendering contexts one by one; when a user requests to carry out function operation on the current rendering scene, calling a function interface in the rendering context to execute the function operation; when the user requests to create a new rendering scene, creating a rendering scene instance through a scene provider, and performing rendering processing on the rendering scene instance through the rendering context; and when the user requests to switch the rendering scenes of other scene types, storing the state and the user configuration of the current rendering scene instance, and recovering the stored state and the user configuration in the new rendering scene instance. According to the scheme, the efficiency of switching and managing the rendering scene is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of image data processing, and in particular to a method, device, equipment and medium for dynamically creating and managing multiple rendering scenes. Background Art

[0002] Geographic information systems are widely used in joint combat simulations. There are many types of scenes in geographic information systems, such as three-dimensional earth scenes and two-dimensional map scenes, which may be implemented in different plug-ins. Many functions in the system are related to scene rendering, such as plotting, map layers, etc., which require adding various display elements to the scene. However, different scenes have different support for the same type of functions. For example, the three-dimensional earth can support geographic images, digital elevations, and various vector data layers, while the two-dimensional map only supports images and vector layers, and there is no concept of elevation layers.

[0003] At the same time, more and more new technologies including VR, AR and MR can be integrated into joint combat simulation, making the simulation of joint combat more effective and vivid.

[0004] The existing technology lacks a flexible mechanism to manage different types of scenarios and effectively bind scenarios to functions, which makes it difficult to expand scenarios and develop functions. It is necessary to design a structure that binds functions to specific scenarios, facilitates the development of functional logic, and keeps the usage as unified as possible, so that the development of functions is relatively independent and the usage is relatively simple. Summary of the invention

[0005] In view of this, an embodiment of the present invention provides a method for dynamically creating and managing multiple rendering scenes to solve the technical problems of complex scene switching and difficult scene expansion in the prior art. The method includes: Constructing a rendering scene management service, defining supported scene types in the rendering scene management service, constructing a scene provider and a rendering context supporting each of the scene types, and associating the scene provider with the rendering context, and the functional module with the rendering context one by one, wherein the rendering scene management service is used to manage the life cycle of the rendering scene and coordinate multiple scene providers; When a user requests to perform a functional operation on the current rendering scene, the functional module for implementing the functional operation calls a functional interface in the rendering context, and the functional operation is performed through the functional interface; When a user requests to create a new rendering scene, the scene provider is called through the rendering scene management service, a rendering scene instance is created through the scene provider, and the bound rendering context is called, and rendering processing is performed on the rendering scene instance through the rendering context; When the user requests to switch to a rendering scene of another scene type, the state and user configuration of the current rendering scene instance are saved, a new rendering scene instance is constructed through the scene provider, and after calling the bound rendering context to render the rendering scene instance, the saved state and user configuration are restored in the new rendering scene instance.

[0006] The embodiment of the present invention also provides a device for dynamically creating and managing multiple rendering scenes to solve the technical problems of complex scene switching and difficult scene expansion in the prior art. The device includes: A system construction module, used to construct a rendering scene management service, define supported scene types in the rendering scene management service, construct a scene provider and a rendering context supporting each of the scene types, and associate the scene provider with the rendering context, and the function module with the rendering context one by one, wherein the rendering scene management service is used to manage the life cycle of the rendering scene and coordinate multiple scene providers; An execution function operation module, configured to, when a user requests to perform a function operation on the current rendering scene, call a function interface in the rendering context through the function module that implements the function operation, and execute the function operation through the function interface; A new scene creation module is used for, when a user requests to create a new rendering scene, calling the scene provider through the rendering scene management service, creating a rendering scene instance through the scene provider, and calling the bound rendering context, and rendering the rendering scene instance through the rendering context; The scene switching module is used to save the state and user configuration of the current rendering scene instance when the user requests to switch to a rendering scene of another scene type, construct a new rendering scene instance through the scene provider, call the bound rendering context to render the rendering scene instance, and then restore the saved state and user configuration in the new rendering scene instance.

[0007] An embodiment of the present invention also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method for dynamically creating and managing any of the above-mentioned multiple rendering scenes is implemented to solve the technical problems in the prior art of complex scene switching and difficult scene expansion.

[0008] An embodiment of the present invention further provides a computer-readable storage medium storing a computer program for executing any of the above-mentioned methods for dynamically creating and managing multiple rendering scenes, so as to solve the technical problems of complex scene switching and difficult scene expansion in the prior art.

[0009] Compared with the prior art, the at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects: The efficiency of dynamic creation and management of rendering scenes is improved through the construction of rendering scene management services, scene providers, and rendering contexts. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0011] Figure 1 is a flow chart of a method for dynamically creating and managing multiple rendering scenes provided by an embodiment of the present invention; Figure 2 is a structural block diagram of a computer device provided by an embodiment of the present invention; Figure 3 It is a structural block diagram of a device for dynamically creating and managing multiple rendering scenes provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0012] The embodiments of the present application are described in detail below with reference to the accompanying drawings.

[0013] The following describes the implementation methods of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. The present application can also be implemented or applied through other different specific implementation methods, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that, in the absence of conflict, the following embodiments and the features in the embodiments can be combined with each other. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work belong to the scope of protection of the present application.

[0014] In an embodiment of the present invention, a method for dynamically creating and managing multiple rendering scenes is provided, such as Figure 1 As shown, the method includes: Step S101: constructing a rendering scene management service, defining supported scene types in the rendering scene management service, constructing a scene provider and a rendering context supporting each of the scene types, and associating the scene provider with the rendering context, and the functional module with the rendering context one by one, wherein the rendering scene management service is used to manage the life cycle of the rendering scene and coordinate multiple scene providers; Step S102: when a user requests to perform a functional operation on the current rendering scene, the functional module for implementing the functional operation calls a functional interface in the rendering context, and the functional operation is performed through the functional interface; Step S103: when the user requests to create a new rendering scene, the scene provider is called through the rendering scene management service, a rendering scene instance is created through the scene provider, and the bound rendering context is called, and rendering processing is performed on the rendering scene instance through the rendering context; Step S104: When the user requests to switch to a rendering scene of another scene type, the state and user configuration of the current rendering scene instance are saved, a new rendering scene instance is constructed through the scene provider, and the bound rendering context is called to render the rendering scene instance, and then the saved state and user configuration are restored in the new rendering scene instance.

[0015] Specifically, if there are two scene types, three-dimensional earth scenes and two-dimensional map scenes, they may be implemented in different plug-ins. When the plug-in is started, the plug-in will register the functional services provided by itself with the framework. The scene plug-in will register the services of the scene provider (IFxSceneProvider), and the scene management plug-in will register the scene management service (IFxSceneService) for external use. When you need to create a rendering scene of a certain scene type, first get the scene management service, and then call the interface provided by it to create the scene. Inside the scene management plug-in, all registered scene provider services will be obtained, and traversal will be queried to see if the required type of scene is provided. If found, the interface will be called to create a specific scene.

[0016] In specific implementation, the following steps are implemented to call the scene provider through the rendering scene management service, create a rendering scene instance through the scene provider, call the bound rendering context, and perform rendering processing on the rendering scene instance through the rendering context: The scene type to be created is obtained from the user request; all the scene providers are traversed in the scene management service, and the scene providers that support the scene type are screened; the rendering scene instance is constructed through the screened scene providers, and the corresponding rendering context is called; the resources required for rendering the rendering scene instance are loaded through the rendering context, and the functions supported by the rendering scene instance are bound.

[0017] In a specific implementation, the following steps are performed to save the state and user configuration of the current rendering scene instance, construct a new rendering scene instance through the scene provider, call the bound rendering context to render the rendering scene instance, and then restore the saved state and user configuration in the new rendering scene instance: After serializing the state and user configuration of the current rendering scene instance, a serialized state file is generated, wherein the state and the user configuration include the camera state, layer visibility, the state of the functional module, and the interaction state; the rendering data of the current rendering scene instance in the memory is released, all objects in the rendering scene instance are removed, and the monitoring of the interaction events related to the current rendering scene instance is canceled, wherein the rendering data includes the basic model, texture data and map tiles; according to the scene type after switching, a new rendering context is obtained, the basic model, the texture data and the map tiles used by the new rendering context are preloaded, and a new rendering scene instance is generated; through the serialized state file, the state and user configuration are restored in the new rendering scene instance.

[0018] In one embodiment of the present invention, during combat simulation, switching from a 3D tactical map to a 2D strategic map can be achieved through the following steps. First, record the longitude and latitude, altitude and currently activated "unit tracking" function of the 3D camera; destroy the current 3D rendering context, and release the 3D terrain mesh, texture and particle special effect resources. Initialize a new 2D rendering context, load the plane map tiles required for the 2D rendering model, and initialize the Canvas renderer; project the 3D longitude and latitude into 2D plane coordinates, and reactivate the "unit tracking" function (displayed as a 2D icon). Through state preservation, resource management, asynchronous loading and state recovery mechanisms, dynamic switching of rendering scenes can be achieved to ensure efficient and stable operation of the system. This solution is suitable for complex military simulation systems that require multi-perspective collaboration, taking into account both flexibility and performance.

[0019] Camera status includes camera position, rotation angle, field of view (FOV), zoom level, etc. Layer visibility includes the display / hide status of each data layer (such as terrain, unit markers, heat map), etc. Functional module status includes activated functions (such as plotting tools, path planning) and their configuration parameters, etc. Interaction status includes selected units, view focus, user-defined bookmarks, etc.

[0020] In specific implementation, the following steps are performed to restore the state and user configuration in the new rendering scene instance through the serialized state file: The state and the user configuration are read from the serialized state file, and the state and the user configuration are applied to the new rendering context; scene parameters having differences between the rendering scene instances before and after the switching are obtained, and the scene parameters based on the rendering scene instance before the switching are converted into the scene parameters based on the rendering scene after the switching; the functional module used before the switching is restarted, and the state and the user configuration are applied to the functional module.

[0021] In a specific implementation, the following steps are performed to implement calling the functional interface in the rendering context through the functional module that implements the functional operation, and performing the functional operation through the functional interface: The functional module for implementing the functional operation is obtained through the functional operation requested by the user, wherein the functional operation includes plotting, layer management, and signal analysis; the rendering context corresponding to the current rendering scene instance is called through the rendering scene management service; the functional module calls the functional interface through the rendering context, executes the functional operation through the functional interface, and executes the underlying rendering instructions through the rendering context.

[0022] In specific implementation, the following steps are performed to add the new scene type: When adding a new scene type, define the scene provider that supports the new scene type, and append the new scene type to the scene type of the scene management service; create the rendering context that supports the new scene type, create the rendering scene instance that supports the new scene type through the scene provider, and associate the scene provider with the rendering context; obtain dedicated resources and underlying rendering instructions that support the new scene type, and add the dedicated resources and the underlying rendering instructions to the rendering context.

[0023] In one embodiment of the present invention, after the user plans a path in the 3D tactical map, it is possible to switch to an AR scene to verify the actual situation.

[0024] By building an AR scene provider and AR rendering context that support AR specifications in the rendering scene management system, the specific implementation method is as follows: Define a scene provider that supports AR scenes, and add AR scenes to the scene types of the scene management service; create an AR rendering scene instance and a rendering context that supports the AR rendering scene instance, and bind the AR rendering scene instance to the rendering context of the AR rendering scene; Obtain the functions supported by the AR scene (such as plane detection, virtual-reality fusion) and the permissions of the AR session hardware, and load AR-specific resources (such as virtual object models, camera images, anchor configuration, virtual object overlay, etc.). Encapsulate AR underlying rendering instructions in a rendering context that supports AR rendering scenes (such as ARKit / ARCore or WebXR), and add AR scene extension-specific functions (such as plane detection, virtual-reality collision, etc.) to the rendering context; Package the scene providers that support AR scenes, the rendering contexts that support AR rendering scene instances, and the functional modules that build AR scenes into independent plug-ins; When a user creates an AR scene, the scene management service is called to create an AR rendering scene instance, and the function module of the AR rendering scene instance is called. (For example, after superimposing a virtual path indication arrow in the real environment, the deviation between the soldier's physical position and the virtual path is displayed in real time through the camera screen).

[0025] In one embodiment of the present invention, switching from a 3D tactical map to a VR command room can be achieved.

[0026] By building a VR scene provider and VR rendering context that supports VR specifications in the rendering scene management system, the specific implementation method is as follows: Define a scene provider that supports VR scenes, and add VR scenes to the scene types of the scene management service; create a VR rendering scene instance and a rendering context that supports the VR rendering scene instance, and bind the VR rendering scene instance to the rendering context of the VR rendering scene instance; Get the functions supported by the VR scene (such as controller interaction and spatial audio), load VR-specific resources (such as 3D environment, controller model, etc.). Encapsulate VR underlying rendering instructions (VR environment model, binocular stereo rendering, controller interaction, etc.) in the rendering context that supports VR rendering scene instances, and add VR scene extension-specific functions (VR teleportation function, VR gesture recognition, etc.) in the rendering context.

[0027] When a user creates a VR scene, the scene management service is called to create a VR rendering scene instance, and the function module of the VR rendering scene instance is called.

[0028] In one embodiment of the invention, real-time status data of the equipment is overlaid into the MR view.

[0029] By building an MR scene provider and MR rendering context that support the MR specification in the rendering scene management system, the specific implementation method is as follows: Define a scene provider that supports MR scenes, and add MR scenes to the scene types of the scene management service; create an MR rendering scene instance and a rendering context that supports the MR rendering scene instance, and bind the MR rendering scene instance to the rendering context of the MR rendering scene; Obtain the functions supported by the MR scene (such as spatial mapping, virtual-reality occlusion) and the hardware permissions of the MR session, and load virtual-reality fusion resources (such as virtual dashboards, physical collision models, etc.). Encapsulate MR underlying rendering instructions (such as virtual-reality fusion rendering) in the rendering context that supports MR rendering scenes, and add MR scene extension-specific functions (such as virtual-reality occlusion processing) in the rendering context; Package the scene provider that supports MR scenes, the rendering context that supports MR rendering scene instances, and the functional modules for building MR scenes into independent plug-ins; When a user creates an MR scene, the scene management service is called to create an MR rendering scene instance, and the functional module of the MR rendering scene instance is called.

[0030] In specific implementation, plug-in management is achieved through the following steps: The scene provider, the rendering context and the functional module for constructing the rendering scene supporting the same scene type are packaged into a scene management plug-in; through the scene management service, the scene management plug-in is called to realize the dynamic creation and management of multiple rendering scenes.

[0031] In the combat simulation, which is one of the application scenarios of the embodiment of the present invention, the deployment of troops, logistics routes, and division of enemy-occupied areas are displayed in the strategic map scene (2D). Interaction is realized in the strategic map scene (2D) (selecting units to issue movement instructions, right-clicking to view detailed intelligence, etc.); UAV reconnaissance images, firepower coverage, and electronic interference areas are displayed in the tactical view scene (3D). Interaction is realized in the tactical view scene (3D) (drag to adjust the camera angle, click on the unit to view the real-time status, etc.). Multi-source sensor data such as radar, infrared, and sonar are superimposed in the sensor monitoring scene (hybrid view). Interaction is realized in the sensor monitoring scene (hybrid view) (sliding the timeline to play back historical data, filtering specific sensor types, etc.). The dynamic creation and management method of the embodiment of the present invention is used to realize switching between the strategic map scene, the tactical view scene, and the sensor monitoring scene, or to add scenes such as VR and AR to the strategic map scene or the tactical view scene.

[0032] Dynamically register scene providers (IFxSceneProvider) and management services (IFxSceneService) through the plug-in mechanism to achieve flexible expansion of scene types and functions. Functional services (such as plotting, layers) are associated with the scene rendering context through a unified interface, and different scenes can customize function implementation (such as 3D earth supports elevation layers, 2D maps only image layers). Combine asynchronous loading and reference counting strategies to dynamically manage the life cycle of scene resources.

[0033] In this embodiment, a computer device is provided, such as Figure 2 As shown, it includes a memory 201, a processor 202, and a computer program stored in the memory and executable on the processor, and the processor implements any of the above-mentioned data storage methods when executing the computer program.

[0034] Specifically, the computer device may be a computer terminal, a server or a similar computing device.

[0035] In this embodiment, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program for executing any of the above-mentioned methods for dynamically creating and managing multiple rendering scenes.

[0036] Specifically, computer-readable storage media include permanent and non-permanent, removable and non-removable media, and information storage can be achieved by any method or technology. Information can be computer-readable instructions, data structures, modules of programs or other data. Examples of computer-readable storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable storage media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0037] Based on the same inventive concept, an apparatus for dynamically creating and managing multiple rendering scenes is also provided in an embodiment of the present invention, as described in the following embodiments. Since the principle of solving the problem by the apparatus for dynamically creating and managing multiple rendering scenes is similar to that of dynamically creating and managing multiple rendering scenes, the implementation of the apparatus for dynamically creating and managing multiple rendering scenes can refer to the implementation of the dynamic creation and management method of multiple rendering scenes, and the repeated parts will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements predetermined functions. Although the apparatus described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0038] Figure 3 is a structural block diagram of a device for dynamically creating and managing multiple rendering scenes according to an embodiment of the present invention. Figure 3 As shown, it includes: a system construction module 301, an execution function operation module 302, a new scene creation module 303 and a scene switching module 304. The structure is described below.

[0039] The system construction module 301 is used to construct a rendering scene management service, define supported scene types in the rendering scene management service, construct a scene provider and a rendering context supporting each of the scene types, and associate the scene provider with the rendering context, and the function module with the rendering context one by one, wherein the rendering scene management service is used to manage the life cycle of the rendering scene and coordinate multiple scene providers; An executing function operation module 302 is used for, when a user requests to perform a function operation on the current rendering scene, calling a function interface in the rendering context through the function module that implements the function operation, and performing the function operation through the function interface; A new scene creation module 303 is used for, when a user requests to create a new rendering scene, calling the scene provider through the rendering scene management service, creating a rendering scene instance through the scene provider, and calling the bound rendering context to perform rendering processing on the rendering scene instance through the rendering context; The scene switching module 304 is used to save the state and user configuration of the current rendering scene instance when the user requests to switch to a rendering scene of another scene type, construct a new rendering scene instance through the scene provider, call the bound rendering context to render the rendering scene instance, and then restore the saved state and user configuration in the new rendering scene instance.

[0040] In one embodiment, the execution function operation module includes: A function module acquisition unit, used for acquiring a function module for implementing the function operation through the function operation requested by the user, wherein the function operation includes plotting, layer management, and signal analysis; A rendering context calling unit, configured to call the rendering context corresponding to the current rendering scene instance through the rendering scene management service; The function operation execution unit is used for the function module to call the function interface through the rendering context, execute the function operation through the function interface, and execute the underlying rendering instruction through the rendering context.

[0041] In one embodiment, the new scene creation module includes: A scene type acquisition unit, used for acquiring the scene type to be created from the user request; A scene provider screening unit, used for traversing all the scene providers in the scene management service, and screening the scene providers that support the scene type; Calling a rendering context unit, used to construct the rendering scene instance through the filtered scene provider, and calling the corresponding rendering context; The scene rendering unit is used to load the resources required for rendering the rendering scene instance through the rendering context and bind the functions supported by the rendering scene instance.

[0042] In one embodiment, the scene switching module includes: A state saving unit, used to generate a serialized state file after serializing the state and user configuration of the current rendering scene instance, wherein the state and the user configuration include camera state, layer visibility, state of functional modules, and interaction state; A release memory unit is used to release the rendering data of the current rendering scene instance in the memory, remove all objects in the rendering scene instance, and cancel the monitoring of the interaction events related to the current rendering scene instance, wherein the rendering data includes a basic model, texture data, and map tiles; A preloading unit, used for acquiring the new rendering context according to the scene type after switching, preloading the basic model, the texture data and the map tile used by the new rendering context, and generating a new rendering scene instance; The state restoration unit is used to restore the state and user configuration in the new rendering scene instance through the serialized state file.

[0043] In one embodiment, a state restoration unit is used to read the state and the user configuration from the serialized state file, and apply the state and the user configuration to the new rendering context; obtain scene parameters that are different in the rendering scene instance before and after the switching, and convert the scene parameters based on the rendering scene instance before the switching into the scene parameters based on the rendering scene after the switching; restart the functional module used before the switching, and apply the state and the user configuration to the functional module.

[0044] In one embodiment, the above device further includes: a new type of scene appending module.

[0045] In one embodiment, a new type of scene appending module includes: A provider definition unit is used to define the scenario provider supporting the new scenario type when a new scenario type is added, and add the new scenario type to the scenario type of the scenario management service; A rendering context creation unit, configured to create the rendering context supporting the new scene type, create the rendering scene instance supporting the new scene type through the scene provider, and associate the scene provider with the rendering context; The dedicated resource adding unit is used to obtain dedicated resources and underlying rendering instructions that support the new scene type, and add the dedicated resources and the underlying rendering instructions in the rendering context.

[0046] In one embodiment, the above device further includes: a plug-in module.

[0047] In one embodiment, the plug-in module includes: A plug-in packaging unit, used for packaging the scene provider, the rendering context and the functional module for constructing a rendering scene supporting the same scene type into a scene management plug-in; The dynamic management unit is used to call the scene management plug-in through the scene management service to realize the dynamic creation and management of multiple rendering scenes.

[0048] The embodiments of the present invention achieve the following technical effects: The rendering scene management service is used to independently manage resources and states of different rendering scenes. The scene provider and rendering context are used to bind functions to specific scenes, which facilitates the development of functional logic. The usage is kept as unified and simple as possible, which improves the efficiency of dynamic creation and management of rendering scenes. Dynamic switching of rendering scenes can seamlessly switch 2D / 3D views. Functional modules are rendered through rendering context operations to avoid direct dependence on the underlying API (underlying rendering instructions), which improves the maintainability of rendering scenes. Through plug-in scene management, modular function binding, efficient resource scheduling and data synchronization mechanism, dynamic creation, management and function switching of multiple rendering scenes can be realized in the battlefield situation display system. Taking into account flexible scalability and high-performance rendering, it is suitable for real-time decision support in complex battlefield environments, and lays a technical foundation for future expansion (such as the integration of AR / VR / MR). It can be applied to military training, industrial maintenance and other fields that require multi-modal interaction.

[0049] Obviously, those skilled in the art should understand that the modules or steps of the above-mentioned embodiments of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. In this way, the embodiments of the present invention are not limited to any specific combination of hardware and software.

[0050] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the embodiments of the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.

Claims

1. A method for dynamically creating and managing multiple rendering scenes, characterized in that: include: Constructing a rendering scene management service, defining supported scene types in the rendering scene management service, constructing a scene provider and a rendering context supporting each of the scene types, and associating the scene provider with the rendering context, and the functional module with the rendering context one by one, wherein the rendering scene management service is used to manage the life cycle of the rendering scene and coordinate multiple scene providers; When a user requests to perform a functional operation on the current rendering scene, the functional module for implementing the functional operation calls a functional interface in the rendering context, and the functional operation is performed through the functional interface; When a user requests to create a new rendering scene, the scene provider is called through the rendering scene management service, a rendering scene instance is created through the scene provider, and the bound rendering context is called, and rendering processing is performed on the rendering scene instance through the rendering context; When the user requests to switch to a rendering scene of another scene type, the state and user configuration of the current rendering scene instance are saved, a new rendering scene instance is constructed through the scene provider, and after calling the bound rendering context to render the rendering scene instance, the saved state and user configuration are restored in the new rendering scene instance.

2. The method for dynamically creating and managing multiple rendering scenes according to claim 1, characterized in that: The scene provider is called through the rendering scene management service, a rendering scene instance is created through the scene provider, and the bound rendering context is called, and rendering processing is performed on the rendering scene instance through the rendering context, including: Acquire the scene type to be created from the user request; Traversing all the scene providers in the scene management service, and screening out the scene providers that support the scene type; Constructing the rendering scene instance through the filtered scene provider, and calling the corresponding rendering context; The resources required for rendering the rendering scene instance are loaded through the rendering context, and the functions supported by the rendering scene instance are bound.

3. The method for dynamically creating and managing multiple rendering scenes according to claim 1, characterized in that: Saving the state and user configuration of the current rendering scene instance, constructing a new rendering scene instance through the scene provider, calling the bound rendering context to render the rendering scene instance, and then restoring the saved state and user configuration in the new rendering scene instance, including: After serializing the state and user configuration of the current rendering scene instance, a serialized state file is generated, wherein the state and the user configuration include camera state, layer visibility, state of functional modules, and interaction state; Release the rendering data of the current rendering scene instance in the memory, remove all objects in the rendering scene instance, and cancel the monitoring of interactive events related to the current rendering scene instance, wherein the rendering data includes a basic model, texture data, and map tiles; Acquire the new rendering context according to the scene type after switching, preload the basic model, the texture data and the map tile used by the new rendering context, and generate a new rendering scene instance; The state and user configuration are restored in the new rendering scene instance through the serialized state file.

4. The method for dynamically creating and managing multiple rendering scenes according to claim 3, characterized in that: Restoring the state and user configuration in the new rendering scene instance through the serialized state file includes: Read the state and the user configuration from the serialized state file, and apply the state and the user configuration to the new rendering context; Acquire scene parameters having differences between the rendering scene instances before and after switching, and convert the scene parameters based on the rendering scene instance before switching into the scene parameters based on the rendering scene instance after switching; The function module used before the switching is restarted, and the state and the user configuration are applied to the function module.

5. The method for dynamically creating and managing multiple rendering scenes according to claim 1, characterized in that: Calling a function interface in the rendering context through the function module that implements the function operation, and performing the function operation through the function interface, includes: Acquiring a functional module that implements the functional operation through the functional operation requested by the user, wherein the functional operation includes plotting, layer management, and signal analysis; Calling the rendering context corresponding to the current rendering scene instance through the rendering scene management service; The functional module calls the functional interface through the rendering context, performs the functional operation through the functional interface, and executes the underlying rendering instruction through the rendering context.

6. The method for dynamically creating and managing multiple rendering scenes according to any one of claims 1 to 5, characterized in that: Also includes: When a new scene type is added, the scene provider supporting the new scene type is defined, and the new scene type is added to the scene type of the scene management service; Creating the rendering context supporting the new scene type, creating the rendering scene instance supporting the new scene type through the scene provider, and associating the scene provider with the rendering context; Acquire dedicated resources and underlying rendering instructions that support the new scene type, and add the dedicated resources and the underlying rendering instructions to the rendering context.

7. The method for dynamically creating and managing multiple rendering scenes according to any one of claims 1 to 5, characterized in that: Also includes: Packing the scene provider, the rendering context and the functional module for constructing a rendering scene that support the same scene type into a scene management plug-in; Through the scene management service, the scene management plug-in is called to realize dynamic creation and management of multiple rendering scenes.

8. A device for dynamically creating and managing multiple rendering scenes, characterized in that: include: A system construction module, used to construct a rendering scene management service, define supported scene types in the rendering scene management service, construct a scene provider and a rendering context supporting each of the scene types, and associate the scene provider with the rendering context, and the function module with the rendering context one by one, wherein the rendering scene management service is used to manage the life cycle of the rendering scene and coordinate the collaboration of the scene providers; An execution function operation module, configured to, when a user requests to perform a function operation on the current rendering scene, call a function interface in the rendering context through the function module that implements the function operation, and execute the function operation through the function interface; A new scene creation module is used for, when a user requests to create a new rendering scene, calling the scene provider through the rendering scene management service, creating a rendering scene instance through the scene provider, and calling the bound rendering context, and rendering the rendering scene instance through the rendering context; The scene switching module is used to save the state and user configuration of the current rendering scene instance when the user requests to switch to a rendering scene of another scene type, construct a new rendering scene instance through the scene provider, call the bound rendering context to render the rendering scene instance, and then restore the saved state and user configuration in the new rendering scene instance.

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for dynamically creating and managing multiple rendering scenes according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method for dynamically creating and managing multiple rendering scenes according to any one of claims 1 to 7.

Images