Embedded interface rendering and communication system based on CEF kernel and UnrealEngine

By embedding CEF kernel and UE containers on the UnrealEngine side, the problem of inefficient development of traditional interface systems is solved, efficient development of interface rendering and communication systems is achieved, and the development efficiency of the UnrealEngine side is improved.

CN114816623BActive Publication Date: 2024-11-08HANGZHOU YIZHI MICRO TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202210349937.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-04-02
Publication Date
2024-11-08
Estimated Expiration
2042-04-02

AI Technical Summary

Technical Problem

The traditional UnrealEngine engine interface system cannot meet the complex needs of the visualization industry, resulting in inefficient development.

Method used

Embed the CEF kernel on the UnrealEngine side, implement interface rendering and communication systems through UE containers and Serializer serializers, receive mouse interaction events and external information, and parse and pass them, and use GPU rendering and material systems to improve development efficiency.

Benefits of technology

It greatly improves the development efficiency of UnrealEngine's interface effect and logic, and realizes rapid writing and efficient rendering.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114816623B_ABST
    Figure CN114816623B_ABST
Patent Text Reader

Abstract

The present invention provides an embedded interface rendering and communication system based on a CEF kernel and an UnrealEngine end, comprising: an UnrealEngine end and a Web end, wherein the UnrealEngine end is embedded with the CEF kernel, a UE container is provided in the Web end, the UnrealEngine end is bound to the UE container, the CEF kernel is used to receive a mouse interaction event sent by a UE plug-in in the UnrealEngine end, and the ue.xxx.interface function is called to parse the mouse interaction event into a JS language and pass it to the Web end, the Web end is used to enable GPU rendering of the CEF kernel, and the first pixel matrix of the screen of the CEF kernel is passed into the UE plug-in of the UnrealEngine end, the UE plug-in of the UnrealEngine end is used to draw the second pixel matrix of the CEF kernel, and the second pixel matrix is ​​passed into the material system in the UnrealEngine end. Thus, by embedding the CEF kernel in the UnrealEngine end, the interface effects and logic of the UnrealEngine end can be quickly written, which greatly improves the development efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of data visualization application, and in particular to an embedded interface rendering and communication system based on a CEF kernel and an UnrealEngine end. Background Art

[0002] With the rapid development of digital transformation of governments and enterprises, computer business systems are becoming increasingly complex. The traditional UnrealEngine engine interface system can no longer meet the current needs of the visualization industry and has low development efficiency. Summary of the invention

[0003] In order to solve the above technical problems, the present invention provides an embedded interface rendering and communication system based on CEF kernel and UnrealEngine end. By embedding CEF kernel in UnrealEngine end, the interface effects and logic of UnrealEngine end can be quickly written, which greatly improves the development efficiency.

[0004] The technical solution adopted by the present invention is as follows:

[0005] An embedded interface rendering and communication system based on a CEF kernel and an UnrealEngine end, comprising: the UnrealEngine end and a Web end, wherein the UnrealEngine end is embedded with the CEF kernel, a UE container is provided in the Web end, the UnrealEngine end is bound to the UE container, the CEF kernel is used to receive a mouse interaction event sent by a UE plug-in in the UnrealEngine end, and to call a ue.xxx.interface function to parse the mouse interaction event into a JS language and pass it to the Web end, the Web end is used to start GPU rendering of the CEF kernel, and pass a first pixel matrix of the screen of the CEF kernel to the UE plug-in of the UnrealEngine end, the UE plug-in of the UnrealEngine end is used to draw a second pixel matrix of the CEF kernel, and pass the second pixel matrix to a material system in the UnrealEngine end.

[0006] The UnrealEngine end binds a communication channel with the Web end through a unique identifier, wherein the unique identifier includes a Screen ID.

[0007] The Web end is also used to receive external information and transfer the external information to the UE plug-in through the UE container; the CEF kernel is also used to call the ue.callEasyV function to receive the external information.

[0008] The external information includes: data source information, and / or third-party platform information, and / or third-party component library information.

[0009] The UnrealEngine end is provided with a Serializer, wherein the Serializer is used to parse the external information and bind the parsed external information to the event dispatcher of the EasyV Component on the UnrealEngine end.

[0010] The CEF kernel is also used to call the ue.callWeb function to send the data information of the UnrealEngine end to the Web end.

[0011] Beneficial effects of the present invention:

[0012] The present invention can quickly program the interface effects and logic of the UnrealEngine end by embedding the CEF kernel in the UnrealEngine end, thereby greatly improving the development efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 It is a structural diagram of an embedded interface rendering and communication system based on a CEF kernel and an UnrealEngine end according to an embodiment of the present invention. DETAILED DESCRIPTION

[0014] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0015] Figure 1 It is a structural schematic diagram of an embedded interface rendering and communication system based on a CEF kernel and an UnrealEngine end according to an embodiment of the present invention.

[0016] like Figure 1 As shown, the embedded interface rendering and communication system based on the CEF kernel and the UnrealEngine end according to the embodiment of the present invention may include: an UnrealEngine end 100 and a Web end 200 .

[0017] Among them, the UnrealEngine end 100 is embedded with a CEF (Chromium Embedded Framework) kernel, a UE container is set in the Web end 200, the UnrealEngine end 100 is bound to the UE container, the CEF kernel is used to receive mouse interaction events sent by the UE plug-in in the UnrealEngine end 100, and call the ue.xxx.interface function to parse the mouse interaction events into JS language and pass them to the Web end 200, the Web end 200 is used to start the GPU rendering of the CEF kernel, and pass the first pixel matrix of the CEF kernel screen to the UE plug-in of the UnrealEngine end 100, the UE plug-in of the UnrealEngine end 100 is used to draw the second pixel matrix of the CEF kernel, and pass the second pixel matrix to the material system in the UnrealEngine end 100.

[0018] According to an embodiment of the present invention, the UnrealEngine terminal 100 binds a communication channel with the Web terminal 200 via a unique identifier, wherein the unique identifier includes a Screen ID.

[0019] Specifically, the CEF kernel can be embedded in the UnrealEngine end 100, and then the communication channel between the front end of the UE container and the UnrealEngine end 100 can be bound through the unique identifier ScreenID. Among them, the unique identifier ScreenID can be bound to the UE container, and the corresponding string, JSON or dynamic API can be parsed in the UE container to achieve the binding of the communication channel. After binding the communication channel, the UnrealEngine end 100 sends the mouse interaction event to the CEF kernel through the UE plug-in. After receiving the mouse interaction event, the CEF kernel parses the mouse interaction event into JS language and passes it to the Web end 200. Further, the GPU rendering of the CEF kernel can be turned on, and the first pixel matrix of the CEF kernel screen can be passed into the UE plug-in of the UnrealEngine end 100, and the second pixel matrix of the CEF kernel can be drawn to the material system in the UnrealEngine end 100 to achieve a complete presentation of the interface.

[0020] According to an embodiment of the present invention, the Web terminal 200 is also used to receive external information and pass the external information to the UE plug-in through the UE container; the CEF kernel is also used to call the ue.callEasyV function to receive external information. The external information includes: data source information, and / or third-party platform information, and / or third-party component library information.

[0021] Specifically, when the Web terminal 200 communicates data with the UnrealEngine terminal 100, external information can be first received through the Web terminal 200. Specifically, third-party platform information (for example, third-party map services), third-party component library information (for example, Echarts), data source information (API interface data, SQL database information, CSV data source, etc.) can be integrated into the EasyV visualization platform (basic charts, maps, etc.), and the UE container of the Web terminal 200 interacts with the EasyV visualization platform to obtain external information.

[0022] Furthermore, the external information is transmitted to the UE plug-in through the UE container of the Web terminal 200, and then the CEF kernel is used to call the ue.callEasyV function to receive the external information.

[0023] According to one embodiment of the present invention, the UnrealEngine end is provided with a Serializer, wherein the Serializer is used to parse external information and bind the parsed external information to the event dispatcher of the EasyV Component on the UnrealEngine end.

[0024] Specifically, after receiving the external information, the external information can be parsed by the Serializer, and the parsed external information can be bound to the event dispatcher of the EasyV Component on the UnrealEngine side.

[0025] According to an embodiment of the present invention, the CEF kernel is also used to call the ue.callWeb function to send data information of the UnrealEngine terminal 100 to the Web terminal 200. In other words, the UnrealEngine terminal 100 and the Web terminal 200 can perform two-way interaction of data information.

[0026] In summary, according to the embedded interface rendering and communication system based on the CEF kernel and the UnrealEngine end according to an embodiment of the present invention, the UnrealEngine end embeds the CEF kernel, a UE container is provided in the Web end, the UnrealEngine end is bound to the UE container, the CEF kernel is used to receive the mouse interaction events sent by the UE plug-in in the UnrealEngine end, and the ue.xxx.interface function is called to parse the mouse interaction events into the JS language and pass them to the Web end, the Web end is used to enable the GPU rendering of the CEF kernel, and pass the first pixel matrix of the CEF kernel screen to the UE plug-in on the UnrealEngine end, the UE plug-in on the UnrealEngine end is used to draw the second pixel matrix of the CEF kernel, and pass the second pixel matrix to the material system in the UnrealEngine end. Therefore, by embedding the CEF kernel in the UnrealEngine end, the interface effects and logic of the UnrealEngine end can be quickly written, which greatly improves the development efficiency.

[0027] In the description of the present invention, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. "Multiple" means two or more, unless otherwise clearly and specifically defined.

[0028] In the present invention, unless otherwise clearly specified and limited, the terms "installed", "connected", "connected", "fixed" and the like should be understood in a broad sense, for example, it can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0029] In the present invention, unless otherwise clearly specified and limited, a first feature being "above" or "below" a second feature may mean that the first and second features are in direct contact, or the first and second features are in indirect contact through an intermediate medium. Moreover, a first feature being "above", "above" or "above" a second feature may mean that the first feature is directly above or obliquely above the second feature, or simply means that the first feature is higher in level than the second feature. A first feature being "below", "below" or "below" a second feature may mean that the first feature is directly below or obliquely below the second feature, or simply means that the first feature is lower in level than the second feature.

[0030] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner. In addition, those skilled in the art may combine and combine the different embodiments or examples described in this specification and the features of the different embodiments or examples, unless they are contradictory.

[0031] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present invention belong.

[0032] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic devices), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0033] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0034] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0035] In addition, each functional unit in each embodiment of the present invention may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0036] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present invention have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present invention. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.

Claims

1. An embedded interface rendering and communication system based on CEF kernel and UnrealEngine end, characterized in that: include: The UnrealEngine end and the Web end, the UnrealEngine end is embedded with the CEF kernel, the Web end is provided with a UE container, the UnrealEngine end is bound to the UE container, the CEF kernel is used to receive the mouse interaction event sent by the UE plug-in in the UnrealEngine end, and call the ue.xxx.interface function to parse the mouse interaction event into JS language and pass it to the Web end, the Web end is used to start the GPU rendering of the CEF kernel, and pass the first pixel matrix of the CEF kernel screen to the UE plug-in of the UnrealEngine end, the UE plug-in of the UnrealEngine end is used to draw the second pixel matrix of the CEF kernel, and pass the second pixel matrix to the material system in the UnrealEngine end.

2. The embedded interface rendering and communication system based on CEF kernel and UnrealEngine end according to claim 1, characterized in that: The UnrealEngine end binds a communication channel with the Web end through a unique identifier, wherein the unique identifier includes a Screen ID.

3. The embedded interface rendering and communication system based on CEF kernel and UnrealEngine end according to claim 1, characterized in that: The Web end is also used to receive external information and transfer the external information to the UE plug-in through the UE container; The CEF kernel is also used to call the ue.callEasyV function to receive the external information.

4. The embedded interface rendering and communication system based on CEF kernel and UnrealEngine end according to claim 3, characterized in that: The external information includes: data source information, and / or third-party platform information, and / or third-party component library information.

5. The embedded interface rendering and communication system based on CEF kernel and UnrealEngine end according to claim 4, characterized in that: The UnrealEngine end is provided with a Serializer, wherein: The Serializer is used to parse the external information and bind the parsed external information to the event distributor of the EasyV Component on the UnrealEngine side.

6. The embedded interface rendering and communication system based on CEF kernel and UnrealEngine end according to claim 5, characterized in that: The CEF kernel is also used to call the ue.callWeb function to send the data information of the UnrealEngine end to the Web end.