Data visualization method and system, electronic equipment and storage medium

By introducing a universal rendering API into the data visualization system and calling multiple rendering algorithms, the complexity problem of multiple visualizations displayed in the same system in the prior art is solved, and a higher universality and simplified configuration process is achieved.

CN119493922APending Publication Date: 2025-02-21DATANG MOBILE COMM EQUIP CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202311022616.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-08-14
Publication Date
2025-02-21

AI Technical Summary

Technical Problem

The prior art uses multiple visual display effects simultaneously in the same system, and lacks versatility.

Method used

By providing a data visualization method, using the general rendering API to call multiple different rendering algorithms to render the visual data, thereby achieving simultaneous display of multiple visual effects.

Benefits of technology

It realizes meeting multiple visualization needs at the same time in one system, improves the versatility of data visualization, lowers the threshold for getting started, and simplifies the rendering configuration process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119493922A_ABST
    Figure CN119493922A_ABST
Patent Text Reader

Abstract

The invention provides a data visualization method and system, electronic equipment and a storage medium, and relates to the technical field of data visualization, and the method comprises the steps: obtaining to-be-visualized data; rendering the to-be-visualized data based on a general rendering application program interface API; the generic rendering API is used to invoke a plurality of different rendering algorithms. According to the data visualization method and device, multiple different visualization effects can be displayed at the same time, the use requirements of multiple visualization scenes can be met at the same time, and the universality of data visualization is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of data visualization, and in particular to a data visualization method, system, electronic device and storage medium. Background Art

[0002] Data visualization is a very important display scenario, which allows users to monitor system status more intuitively. As front-end scenarios gradually become popular, visualization will also play an important role.

[0003] Existing visualization technologies have their own usage scenarios and can only play their best effects in specific scenarios. For example, Echarts focuses on lightweight charts, and Three.js is mainly used for three-dimensional (3D) display. If you need to use multiple different visualization displays in one system at the same time, it is relatively complicated in terms of integration and use.

[0004] Therefore, it is necessary to provide a general method that can meet multiple visualization needs simultaneously. Summary of the invention

[0005] In view of the problems existing in the prior art, the embodiments of the present application provide a data visualization method, system, electronic device and storage medium to solve the problem of poor versatility of visualization.

[0006] In a first aspect, an embodiment of the present application provides a data visualization method, including:

[0007] Get the data to be visualized;

[0008] The visualization data is rendered based on a general rendering application program interface (API); the general rendering API is used to call a variety of different rendering algorithms.

[0009] In some embodiments, before rendering the visualization data based on the general rendering API, the method further includes:

[0010] Format and cache visualization data based on JSON format;

[0011] According to the rendering requirement format, the cached JSON-formatted data to be visualized is formatted and adapted.

[0012] In some embodiments, after the cached data to be visualized after being formatted in JSON is adapted according to the rendering requirement format, the method further includes:

[0013] When the rendering configuration provided by the user is different from the default rendering configuration, determining the rendering configuration to be the rendering configuration provided by the user;

[0014] In the case that the user does not provide a rendering configuration, the rendering configuration is determined to be a default rendering configuration.

[0015] In some embodiments, obtaining data to be visualized includes:

[0016] Based on a request message for requesting the data to be visualized, obtaining the data to be visualized; the request message carries indication information for indicating a rendering type; or,

[0017] A network application program interface based on duplex real-time communication to obtain the data to be visualized.

[0018] In some embodiments, the data to be visualized includes: map data;

[0019] Rendering of visual data based on the general rendering API, including:

[0020] Render the map data based on the general rendering API.

[0021] In some embodiments, before rendering the visualization data based on the general rendering API, the method further includes:

[0022] Display scenes according to requirements and dispatch rendering tasks;

[0023] Determine the required rendering algorithm based on the rendering task.

[0024] In a second aspect, an embodiment of the present application provides a data visualization system, including: a back-end server and a front-end client;

[0025] The backend server is used to provide the data to be visualized to the frontend client;

[0026] The front-end client is used to render the visualization data based on the universal rendering API; the universal rendering API is used to call a variety of different rendering algorithms.

[0027] In some embodiments, the front-end client is further configured to:

[0028] Format and cache visualization data based on JSON format;

[0029] According to the format of rendering requirements, the cached data to be visualized after JSON formatting is adapted to the format.

[0030] In some embodiments, the front-end client is further configured to:

[0031] When the rendering configuration provided by the user is different from the default rendering configuration, determining the rendering configuration to be the rendering configuration provided by the user;

[0032] In the case that the user does not provide a rendering configuration, the rendering configuration is determined to be a default rendering configuration.

[0033] In some embodiments, the backend server is specifically used to:

[0034] Based on a request message from the front-end client for requesting the data to be visualized, providing the data to be visualized to the front-end client; the request message carries indication information for indicating the rendering type; or,

[0035] Based on the network application program interface of duplex real-time communication, the data to be visualized is provided to the front-end client in real time.

[0036] In some embodiments, the system further comprises: a rendering dispatcher;

[0037] The rendering dispatcher is used to dispatch rendering tasks to the front-end client according to the required display scene;

[0038] The front-end client is also used to determine the required rendering algorithm based on the rendering task.

[0039] In some embodiments, the system further comprises: a user interface;

[0040] The user interface is used to provide interactive operations related to visualization;

[0041] The user interface is also used to submit the data to be saved to the back-end server through the interactive interface between the back-end server and the back-end server.

[0042] In some embodiments, the system further comprises: a map data server;

[0043] The map data server is used to provide map data to the front-end client; the front-end client is also used to render the map data based on the general rendering API.

[0044] In a third aspect, an embodiment of the present application further provides an electronic device, comprising a memory, a transceiver and a processor: the memory is used to store a computer program; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and execute the data visualization method as described in the first aspect above.

[0045] In a fourth aspect, an embodiment of the present application further provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the data visualization method of the first aspect as described above.

[0046] In a fifth aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the data visualization method of the first aspect as described above.

[0047] In a sixth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the data visualization method of the first aspect as described above.

[0048] In a seventh aspect, an embodiment of the present application further provides a chip product, in which a computer program is stored, and the computer program is used to enable the chip product to execute the data visualization method of the first aspect as described above.

[0049] The data visualization method, system, electronic device, and storage medium provided in the embodiments of the present application obtain the data to be visualized, and render the data to be visualized by calling a variety of different rendering algorithms through a universal rendering API, so that a variety of different visualization effects can be displayed at the same time, thereby meeting the usage requirements of a variety of visualization scenarios at the same time and improving the versatility of data visualization. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0051] Figure 1 It is one of the structural schematic diagrams of the data visualization system provided in the embodiment of the present application;

[0052] Figure 2 This is the second structural diagram of the data visualization system provided in the embodiment of the present application;

[0053] Figure 3 This is the third structural diagram of the data visualization system provided in the embodiment of the present application;

[0054] Figure 4 This is the fourth structural diagram of the data visualization system provided in the embodiment of the present application;

[0055] Figure 5 is a working principle diagram of the data visualization system provided in an embodiment of the present application;

[0056] Figure 6 It is a flowchart of a data visualization method provided in an embodiment of the present application;

[0057] Figure 7 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0058] With the development of big data and artificial intelligence, more and more data needs to be displayed, and users have more and more requirements for the way data is presented. They hope to present and analyze data in an intuitive, vivid and interactive way. Especially for network management systems, front-end visualization such as large screens and monitoring has become an extremely important part, and geographic information system (GIS) map applications have gradually become a normalized requirement in network management systems.

[0059] Furthermore, with the development of World Wide Web (Web) technology and the improvement of browser performance, front-end scenario and visualization have gradually become the next development trend of Web development. With the official release of WebGPU, it marks that the Web has entered the era of Graphics Processing Unit (GPU). In the future, more complex visualizations will be presented on the front end, and the construction of front-end visualization infrastructure is imminent.

[0060] At present, if you want to use multiple visualization display effects in the same system at the same time, the current method is to use multiple visualization technologies as project dependencies, install and integrate them in sequence, and develop them separately according to needs and scenarios to achieve the purpose of switching displays.

[0061] In response to the above technical problems, the embodiments of the present application integrate multiple visualization algorithms and call multiple visualization algorithms for rendering through a general application program interface (API) to solve the problem of poor universality of existing data visualization.

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

[0063] Figure 1 is one of the structural diagrams of the data visualization system provided in the embodiment of the present application, such as Figure 1 As shown, an embodiment of the present application provides a data visualization system 100 , including: a back-end server 110 and a front-end client 120 .

[0064] The backend server 110 is used to provide the data to be visualized to the frontend client 120;

[0065] The front-end client 120 is used to render the data to be visualized based on a universal rendering API; the universal rendering API is used to call a variety of different rendering algorithms.

[0066] Specifically, the front-end client 120 encapsulates a plurality of different rendering algorithms, and the general rendering API can call a plurality of different rendering algorithms, which may be a two-dimensional rendering algorithm, a three-dimensional rendering algorithm, a polyline rendering algorithm, and a rectangular rendering algorithm.

[0067] The backend server 110 provides the data to be visualized to the frontend client 120. After obtaining the data to be visualized, the frontend client 120 calls multiple different rendering algorithms through a general rendering API, and renders the data to be visualized by the multiple different rendering algorithms called simultaneously, thereby simultaneously displaying multiple different visualization effects.

[0068] For example, the front-end client 120 calls a two-dimensional rendering algorithm and a three-dimensional rendering algorithm through a universal rendering API, and uses the called two-dimensional rendering algorithm to perform two-dimensional rendering on the visualization data, and uses the called three-dimensional rendering algorithm to perform three-dimensional rendering on the visualization data, thereby simultaneously displaying two-dimensional rendering effects and three-dimensional rendering effects.

[0069] The data visualization system 100 provided in the embodiment of the present application provides the data to be visualized to the front-end client 120 through the back-end server 110. The front-end client 120 calls a variety of different rendering algorithms through a universal rendering API to render the data to be visualized, thereby being able to simultaneously display a variety of different visualization effects and meet the use requirements of a variety of visualization scenarios, thereby improving the versatility of the data visualization system 100.

[0070] Since the underlying layer provides a common API, users do not need to pay too much attention to the rendering process of the data to be visualized, but only need to pay attention to the user view and the display friendliness of the data, which reduces the threshold for getting started. In addition, customized secondary development can also be carried out based on this to enhance the flexibility of visualization.

[0071] In some embodiments, the front-end client 120 is further used to: format and cache the data to be visualized based on the JSON format; and adapt the format of the cached data to be visualized after being formatted in JSON according to the format required for rendering.

[0072] Specifically, the existing technology only develops a set of rendering formats for a certain display style. In some scenarios, multiple display styles are required. At this time, the first problem to be solved is to unify the formats of different data to be visualized. The current method is to format the visualization data separately according to different display styles when rendering is required, which makes the formatting process cumbersome.

[0073] In response to the above problem, since the JSON format is a universal data exchange format, it is represented as a JavaScript object in the front-end client 120. Therefore, the front-end client 120 formats the data to be visualized based on the JSON format, thereby converting the format of the data to be visualized into the JSON format, which is conducive to subsequent format conversion.

[0074] The front-end client 120 caches the data to be visualized after being formatted in JSON. Caching the data to be visualized after being formatted in JSON can reduce the number of data requests and data processing performed by the front-end client 120.

[0075] The front-end client 120 then adapts the format of the cached data to be visualized after being formatted in JSON according to the format of the rendering requirement to achieve different rendering formats.

[0076] If different types of rendering are required for the same data to be visualized, the data to be visualized may be formatted in JSON, and then the data to be visualized after the JSON formatting may be converted into different formats.

[0077] For example, the format of the rendering requirement is D3.JS format, Echarts format and Three.JS format. The front-end client 120 first formats the data to be visualized in JSON, and then converts the data to be visualized in JSON format into data to be visualized in D3.JS format, data to be visualized in Echarts format and data to be visualized in Three.JS format, thereby achieving the acquisition of data to be visualized in different formats.

[0078] In some embodiments, after the front-end client 120 obtains the data to be visualized, it first filters and selects non-essential fields in the data to be visualized to save memory. The non-essential fields can be determined according to the rendering scene.

[0079] The data visualization system 100 provided in the embodiment of the present application performs unified JSON formatting on the visualization data and then adapts the format for different display effects, thereby reducing the complexity of the formatting process to a certain extent.

[0080] In some embodiments, the front-end client 120 is further used to: when the rendering configuration provided by the user is different from the default rendering configuration, determine the rendering configuration to be the rendering configuration provided by the user; when the user does not provide a rendering configuration, determine the rendering configuration to be the default rendering configuration.

[0081] Specifically, after formatting the data and before rendering, you need to specify the rendering configuration for use by the general rendering API. The rendering configuration is usually configured as a JavaScript object.

[0082] Existing technologies all require setting rendering configurations according to regulations to achieve visualization of specific data. However, these rendering configurations are often very cumbersome and complex, with deep configuration nesting levels, and are difficult to debug and locate in limited situations.

[0083] To address the problem of cumbersome and complex rendering configurations, the front-end client 120 provides some default rendering configurations according to different rendering algorithms, and also retains the function of allowing users to provide rendering configurations.

[0084] When the rendering configuration provided by the user is different from the default rendering configuration, the rendering configuration provided by the user will overwrite the default rendering configuration, and the front-end client 120 determines that the rendering configuration is the rendering configuration provided by the user, and uses the rendering configuration provided by the user for rendering.

[0085] In the case that the user does not provide a rendering configuration, in order to improve user friendliness, the front-end client 120 determines the rendering configuration as a default rendering configuration and uses the default rendering configuration for rendering.

[0086] The data visualization system 100 provided in the embodiment of the present application uses the rendering configuration provided by the user when the rendering configuration is provided by the user; when the user does not provide the rendering configuration, the default rendering configuration is used, which simplifies the rendering configuration process to a certain extent, reduces the tediousness and complexity of the rendering configuration, and improves the rendering efficiency; in addition, it also allows users to focus on the business rather than the tedious and complex rendering configuration.

[0087] In some embodiments, the backend server 110 is specifically used to:

[0088] Based on a request message from the front-end client 120 for requesting the data to be visualized, providing the data to be visualized to the front-end client 120; the request message carries indication information for indicating a rendering type; or,

[0089] Based on the network application program interface of duplex real-time communication, the data to be visualized is provided to the front-end client 120 in real time.

[0090] Specifically, in some visualization scenarios where the real-time requirements for the visualized data are not strong, the front-end client 120 sends a request message to the back-end server 110 to request the data to be visualized. The request message carries indication information for indicating the rendering type. The rendering types include two-dimensional rendering, three-dimensional rendering, line rendering, and rectangular rendering. For example, the request message can be a Hypertext Transfer Protocol (HTTP) request.

[0091] After receiving the request message, the backend server 110 responds to the request message, returns the rendering type and provides the data to be visualized to the frontend client 120. The returned rendering type is used to indicate to the frontend client 120 that the provided data to be visualized is available.

[0092] In some visualization scenarios that have strong requirements for the real-time performance of the data to be visualized, the backend server 110 provides the data to be visualized to the frontend client 120 in real time through a network application program interface of duplex real-time communication. The frontend client 120 can also obtain the data to be visualized from the backend server 110 in real time through the network application program interface of duplex real-time communication.

[0093] For example, the network application program interface for duplex real-time communication may be WebSocket. The backend server 110 may push the data to be visualized in real time through WebSocket, and the frontend client 120 may render the pushed data to be visualized in real time.

[0094] In some real-time examples, the backend server 110 processes the data to be visualized that needs to be provided to the frontend client 120 and stores it in a database for use by the frontend client 120 through HTTP requests or WebSocket push.

[0095] In the data visualization system 100 provided in the embodiment of the present application, the back-end server 110 provides the data to be visualized to the front-end client 120 through the request message of the front-end client 120 or the network application program interface of duplex real-time communication, so as to meet the visualization scenarios with different requirements on the real-time performance of the visualized data, thereby further improving the versatility of the data visualization system 100.

[0096] In some embodiments, the data visualization system 100 further includes: a rendering dispatcher 130;

[0097] The rendering dispatcher 130 is used to dispatch rendering tasks to the front-end client 120 according to the required display scene; the front-end client 120 is also used to determine the required rendering algorithm according to the rendering task.

[0098] Specifically, Figure 2This is the second structural diagram of the data visualization system provided in the embodiment of the present application. Figure 2 As shown, the data visualization system 100 includes a backend server 110, a frontend client 120, and a rendering dispatcher 130. After the data to be visualized is formatted and before being rendered, the rendering dispatcher 130 dispatches rendering tasks to the frontend client 120 according to the required display scene. Different display scenes dispatch different rendering tasks.

[0099] For example, in a three-dimensional display scene, the rendering dispatcher 130 dispatches a three-dimensional rendering task to the front-end client 120 ; for another example, in a two-dimensional display scene, the rendering dispatcher 130 dispatches a two-dimensional rendering task to the front-end client 120 .

[0100] After receiving the rendering task, the front-end client 120 determines the required rendering algorithm according to the rendering task. For example, the front-end client 120 determines the required rendering algorithm to be a 3D rendering algorithm according to the 3D rendering task; for another example, the front-end client 120 determines the required rendering algorithm to be a 2D rendering algorithm according to the 2D rendering task.

[0101] After determining the required rendering algorithm, the front-end client 120 calls the required rendering algorithm through the general rendering API, and uses the called required rendering algorithm to render the data to be visualized.

[0102] In the data visualization system 100 provided in the embodiment of the present application, the rendering dispatcher 130 dispatches rendering tasks according to the required display scene; the front-end client 120 determines the required rendering algorithm according to the rendering task, so that the required rendering algorithm is automatically called through the rendering API interface without the need for the user to operate the rendering API interface in the future, thereby further improving the versatility of the data visualization system 100.

[0103] In some embodiments, the data visualization system 100 further includes: a user interface 140;

[0104] The user interface 140 is used to provide interactive operations related to visualization;

[0105] The user interface 140 is also used to submit the data to be saved to the backend server 110 through the interactive interface between the backend server 110 .

[0106] Specifically, Figure 3 This is the third structural diagram of the data visualization system provided in the embodiment of the present application, such as Figure 3 As shown, the data visualization system 100 includes a backend server 110 , a frontend client 120 , a rendering dispatcher 130 , and a user interface 140 .

[0107] Optionally, the data visualization system 100 may include a backend server 110 , a frontend client 120 , and a user interface 140 . Optionally, the user interface 140 may exist within the frontend client 120 .

[0108] The user interface 140 provides interactive operations related to visualization, that is, the user can perform interactive operations related to visualization on the user interface 140. The interactive operations related to visualization include: visualization viewing, visualization modification, visualization addition, or visualization data retrieval.

[0109] When the user needs to save data, the user interface 140 can submit the data to be saved to the backend server 110 through the interactive interface between the user interface 140 and the backend server 110 so that the backend server 110 can save the data.

[0110] In some real-time examples, when the user interface 140 provides data to the backend server 110 through the interactive interface, it is necessary to indicate the request address and permission parameters to the backend server 110. The request address refers to the interactive interface address, which is provided by the backend server 110 to the user interface 140 before providing the data. The permission parameter is used to indicate the processing authority of the backend server 110 for the data. For example, the processing authority can be analysis authority and use authority, so that the backend server 110 can analyze and use the saved data to update the data to be visualized.

[0111] The data visualization system provided in the embodiment of the present application has a user interface 140 that provides interactive operations related to visualization, and also interacts with the back-end server 110 through an interactive interface, thereby improving the flexibility of visualization and further improving user-friendliness.

[0112] In some embodiments, the data visualization system 100 further includes: a map data server 150;

[0113] The map data server 150 is used to provide map data to the front-end client 120; the front-end client 120 is also used to render the map data based on the general rendering API.

[0114] Specifically, for usage scenarios that require maps, Figure 4 This is a fourth structural diagram of the data visualization system provided in the embodiment of the present application, such as Figure 4 As shown, the data visualization system 100 includes a backend server 110 , a frontend client 120 , a rendering dispatcher 130 , a user interface 140 , and a map data server 150 .

[0115] Optionally, the data visualization system 100 may include a backend server 110, a frontend client 120, and a map data server 150. Optionally, the data visualization system 100 may include a backend server 110, a frontend client 120, a rendering dispatcher 130, and a map data server 150. Optionally, the data visualization system 100 may include a backend server 110, a frontend client 120, a user interface 140, and a map data server 150.

[0116] The map data server 150 directly interacts with the front-end client 120 and provides map data to the front-end client 120 so that the front-end client 120 can render the map data based on the general rendering API. When the front-end client 120 renders the map data, the back-end server 110 needs to provide support for other data requirements.

[0117] In the data visualization system 100 provided in the embodiment of the present application, the map data server 150 provides map data to the front-end client 120 for rendering, which expands the usage scenarios of the data visualization system 100 and further improves the versatility of the data visualization system 100.

[0118] Figure 5 is a working principle diagram of the data visualization system 100 provided in an embodiment of the present application, such as Figure 5 As shown, the backend server 110 provides the data to be visualized to the frontend client 120, the rendering dispatcher dispatches the rendering task to the frontend client 120, the frontend client 120 formats the data to be visualized, determines the rendering configuration, renders the formatted data to be visualized according to the rendering task, and visualizes it on the user interface 140. The map data server provides the map data to the frontend client 120 so that the frontend client 120 can render the map data. The user interface 140 also provides data to the backend server 110 to update the data to be visualized in the backend server 110.

[0119] Figure 6 is a flow chart of the data visualization method provided in the embodiment of the present application, such as Figure 6 As shown, the embodiment of the present application provides a data visualization method, the execution subject of which may be a data visualization system 100, and the method includes:

[0120] Step 610, obtaining data to be visualized;

[0121] Step 620 , rendering the data to be visualized based on a universal rendering application programming interface (API); the universal rendering API is used to call a variety of different rendering algorithms.

[0122] Specifically, the data visualization system 100 encapsulates a plurality of different rendering algorithms, and the general rendering API can call a plurality of different rendering algorithms, which may be a two-dimensional rendering algorithm, a three-dimensional rendering algorithm, a polyline rendering algorithm, a histogram rendering algorithm, and the like.

[0123] The data visualization system 100 obtains the data to be visualized. After obtaining the data to be visualized, the data visualization system 100 calls a plurality of different rendering algorithms through a general rendering API, and simultaneously renders the data to be visualized using the called plurality of different rendering algorithms, thereby simultaneously displaying a plurality of different visualization effects.

[0124] For example, the data visualization system 100 calls a two-dimensional rendering algorithm and a three-dimensional rendering algorithm through a general rendering API, and uses the called two-dimensional rendering algorithm to perform two-dimensional rendering on the data to be visualized, and uses the called three-dimensional rendering algorithm to perform three-dimensional rendering on the data to be visualized, thereby simultaneously displaying two-dimensional rendering effects and three-dimensional rendering effects.

[0125] The data visualization method provided in the embodiment of the present application obtains the data to be visualized, and calls a variety of different rendering algorithms through a universal rendering API to render the data to be visualized, so that a variety of different visualization effects can be displayed at the same time, and the usage requirements of various visualization scenarios can be met, thereby improving the versatility of data visualization.

[0126] In some embodiments, the data to be visualized includes: map data;

[0127] Rendering of visual data based on the general rendering API, including:

[0128] Render the map data based on the general rendering API.

[0129] Specifically, the data to be visualized includes map data. The data visualization system 100 obtains the map data, calls a rendering algorithm required for rendering the map data based on a general rendering API, and renders the map data using the called rendering algorithm.

[0130] The data visualization method provided in the embodiment of the present application obtains map data and renders the map data based on a general rendering API, thereby expanding the usage scenarios of data visualization and further improving the versatility of data visualization.

[0131] In some embodiments, obtaining data to be visualized includes:

[0132] Based on a request message for requesting the data to be visualized, obtaining the data to be visualized; the request message carries indication information for indicating a rendering type; or,

[0133] A network application program interface based on duplex real-time communication to obtain the data to be visualized.

[0134] Specifically, in some visualization scenarios where the real-time requirements for the visualized data are not strong, the data visualization system 100 requests the visualized data based on the request message. The request message carries indication information for indicating the rendering type. The rendering types include two-dimensional rendering, three-dimensional rendering, line rendering, and bar rendering. For example, the request message can be an HTTP request.

[0135] Based on the response to the request message, the data visualization system 100 receives the rendering type and the data to be visualized. In this case, the rendering type is used to indicate that the provided data to be visualized is available.

[0136] In some visualization scenarios that have strong requirements on the real-time performance of the data to be visualized, the data visualization system 100 obtains the data to be visualized in real time through a network application program interface of duplex real-time communication.

[0137] For example, the network application program interface for duplex real-time communication may be WebSocket. The data visualization system 100 may obtain the real-time pushed data to be visualized through WebSocket, and then perform real-time rendering on the real-time pushed data to be visualized.

[0138] The data visualization method provided in the embodiment of the present application obtains the data to be visualized through a network application program interface with request messages or duplex real-time communication to meet visualization scenarios with different requirements on the real-time performance of the visualized data, thereby further improving the versatility of data visualization.

[0139] In some embodiments, before rendering the visualization data based on the general rendering API, the method further includes:

[0140] Format and cache visualization data based on JSON format;

[0141] According to the rendering requirement format, the cached JSON-formatted data to be visualized is formatted and adapted.

[0142] Specifically, the existing technology only develops a set of rendering formats for a certain display style. In some scenarios, multiple display styles are required. At this time, the first problem to be solved is to unify the formats of different data to be visualized. The current method is to format the visualization data separately according to different display styles when rendering is required, which makes the formatting process cumbersome.

[0143] In response to the above problem, since the JSON format is a universal data exchange format and is represented as a JavaScript object in the data visualization system 100, the data visualization system 100 formats the data to be visualized based on the JSON format, thereby converting the format of the data to be visualized into the JSON format, which is conducive to subsequent format conversion.

[0144] The data visualization system 100 caches the data to be visualized after being formatted in JSON. Caching the data to be visualized after being formatted in JSON can reduce the number of times the data visualization system 100 performs data requests and data processing.

[0145] The data visualization system 100 then adapts the format of the cached data to be visualized after being formatted in JSON according to the format of the rendering requirements to achieve different rendering formats.

[0146] If different types of rendering are required for the same data to be visualized, the data to be visualized may be formatted in JSON, and then the data to be visualized after the JSON formatting may be converted into different formats.

[0147] For example, the rendering requirements are in the D3.JS format, the Echarts format, and the Three.JS format. The data visualization system 100 first formats the data to be visualized in JSON, and then converts the data to be visualized in JSON format into data to be visualized in D3.JS format, data to be visualized in Echarts format, and data to be visualized in Three.JS format, thereby achieving the acquisition of data to be visualized in different formats.

[0148] In some embodiments, after the data visualization system 100 obtains the data to be visualized, it first filters and selects non-essential fields in the data to be visualized to save memory. The non-essential fields can be determined according to the rendering scene.

[0149] The data visualization method provided in the embodiment of the present application performs unified JSON formatting on the visualized data and then adapts the format for different display effects, thereby reducing the tediousness of the formatting process to a certain extent.

[0150] In some embodiments, after the cached data to be visualized after being formatted in JSON is adapted according to the rendering requirement format, the method further includes:

[0151] When the rendering configuration provided by the user is different from the default rendering configuration, determining the rendering configuration to be the rendering configuration provided by the user;

[0152] In the case that the user does not provide a rendering configuration, the rendering configuration is determined to be a default rendering configuration.

[0153] Specifically, after formatting the data and before rendering, you need to specify the rendering configuration for use by the general rendering API. The rendering configuration is usually configured as a JavaScript object.

[0154] Existing technologies all require setting rendering configurations according to regulations to achieve visualization of specific data. However, these rendering configurations are often very cumbersome and complex, with deep configuration nesting levels, and are difficult to debug and locate in limited situations.

[0155] To address the problem of cumbersome and complex rendering configurations, the data visualization system 100 provides some default rendering configurations based on different rendering algorithms, and also retains the function of allowing users to provide rendering configurations.

[0156] When the rendering configuration provided by the user is different from the default rendering configuration, the rendering configuration provided by the user will overwrite the default rendering configuration, and the data visualization system 100 determines that the rendering configuration is the rendering configuration provided by the user, and uses the rendering configuration provided by the user for rendering.

[0157] In the case that the user does not provide a rendering configuration, in order to improve user friendliness, the data visualization system 100 determines the rendering configuration as a default rendering configuration and uses the default rendering configuration for rendering.

[0158] The data visualization method provided in the embodiment of the present application uses the rendering configuration provided by the user when the rendering configuration is provided by the user; and uses the default rendering configuration when the user does not provide the rendering configuration, which simplifies the rendering configuration process to a certain extent, reduces the tediousness and complexity of the rendering configuration, and improves the rendering efficiency; in addition, it also allows users to focus on the business rather than the tedious and complex rendering configuration.

[0159] In some embodiments, before rendering the visualization data based on the general rendering API, the method further includes:

[0160] Display scenes according to requirements and dispatch rendering tasks;

[0161] Determine the required rendering algorithm based on the rendering task.

[0162] Specifically, after the data to be visualized is formatted and before it is rendered, the data visualization system 100 dispatches rendering tasks according to the required display scene. Different display scenes dispatch different rendering tasks.

[0163] For example, for a three-dimensional display scene, the data visualization system 100 dispatches a three-dimensional rendering task; for another example, for a two-dimensional display scene, the data visualization system 100 dispatches a two-dimensional rendering task.

[0164] After the data visualization system 100 determines the rendering task, it determines the required rendering algorithm according to the rendering task. For example, the data visualization system 100 determines the required rendering algorithm as a 3D rendering algorithm according to the 3D rendering task; for another example, the data visualization system 100 determines the required rendering algorithm as a 2D rendering algorithm according to the 2D rendering task.

[0165] After determining the required rendering algorithm, the data visualization system 100 calls the required rendering algorithm through the general rendering API, and uses the called required rendering algorithm to render the data to be visualized.

[0166] The data visualization method provided in the embodiment of the present application dispatches rendering tasks according to the required display scene; based on the rendering tasks, the required rendering algorithm is determined so that the required rendering algorithm is automatically called through the rendering API interface without the need for the user to operate the rendering API interface in the future, thereby further improving the versatility of data visualization.

[0167] Figure 7 is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application, such as Figure 7 As shown, the electronic device includes a memory 720, a transceiver 700 and a processor 710, wherein:

[0168] The memory 720 is used to store computer programs; the transceiver 700 is used to send and receive data under the control of the processor 710; the processor 710 is used to read the computer program in the memory 720 and perform the following operations:

[0169] Get the data to be visualized;

[0170] The visualization data is rendered based on a general rendering application program interface (API); the general rendering API is used to call a variety of different rendering algorithms.

[0171] Specifically, the transceiver 700 is used to receive and send data under the control of the processor 710.

[0172] Among them, Figure 7In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 710 and memory represented by memory 720. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 700 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include a wireless channel, a wired channel, an optical cable, and other transmission media. The processor 710 is responsible for managing the bus architecture and general processing, and the memory 720 may store data used by the processor 710 when performing operations.

[0173] The processor 710 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0174] In some embodiments, before rendering the visualization data based on the general rendering API, the method further includes:

[0175] Format and cache visualization data based on JSON format;

[0176] According to the rendering requirement format, the cached JSON-formatted data to be visualized is formatted and adapted.

[0177] In some embodiments, after the cached data to be visualized after being formatted in JSON is adapted according to the rendering requirement format, the method further includes:

[0178] When the rendering configuration provided by the user is different from the default rendering configuration, determining the rendering configuration to be the rendering configuration provided by the user;

[0179] In the case that the user does not provide a rendering configuration, the rendering configuration is determined to be a default rendering configuration.

[0180] In some embodiments, obtaining data to be visualized includes:

[0181] Based on a request message for requesting the data to be visualized, obtaining the data to be visualized; the request message carries indication information for indicating a rendering type; or,

[0182] A network application program interface based on duplex real-time communication to obtain the data to be visualized.

[0183] In some embodiments, the data to be visualized includes: map data;

[0184] Rendering of visual data based on the general rendering API, including:

[0185] Render the map data based on the general rendering API.

[0186] In some embodiments, before rendering the visualization data based on the general rendering API, the method further includes:

[0187] Display scenes according to requirements and dispatch rendering tasks;

[0188] Determine the required rendering algorithm based on the rendering task.

[0189] It should be noted here that the above-mentioned electronic device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0190] In some embodiments, a non-transitory readable storage medium is also provided, which stores a computer program, and the computer program is used to enable a processor to execute the data visualization method provided by the above-mentioned method embodiments.

[0191] Specifically, the above-mentioned non-transitory readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as the method embodiments in this embodiment will not be described in detail here.

[0192] It should be noted that the non-transitory readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drive (SSD)), etc.

[0193] In some embodiments, a processor-readable storage medium is also provided, and the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the data visualization method provided by the above-mentioned method embodiments.

[0194] Specifically, the processor-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects that are the same as those in the method embodiments will not be described in detail herein.

[0195] In some embodiments, a computer-readable storage medium is also provided, which stores a computer program, and the computer program is used to enable a computer to execute the data visualization method provided by the above-mentioned method embodiments.

[0196] Specifically, the above-mentioned computer-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0197] In some embodiments, a chip product is also provided, in which a computer program is stored, and the computer program is used to enable the chip product to execute the data visualization methods provided by the above-mentioned method embodiments.

[0198] Specifically, the above-mentioned chip product provided in the embodiment of the present application can implement all the method steps implemented by the above-mentioned method embodiments, and can achieve the same technical effects. The parts and beneficial effects of this embodiment that are the same as the method embodiment will not be described in detail here.

[0199] It should also be noted that the terms "first", "second", etc. in the embodiments of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more.

[0200] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0201] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0202] In this application, "determine B based on A" means that the factor A should be considered when determining B. It is not limited to "B can be determined based on A alone", but should also include: "determine B based on A and C", "determine B based on A, C and E", "determine C based on A, and further determine B based on C", etc. In addition, it can also include taking A as a condition for determining B, for example, "when A meets the first condition, use the first method to determine B"; for example, "when A meets the second condition, determine B", etc.; for example, "when A meets the third condition, determine B based on the first parameter", etc. Of course, it can also be a condition that takes A as a factor for determining B, for example, "when A meets the first condition, use the first method to determine C, and further determine B based on C", etc.

[0203] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system can also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0204] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0205] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0206] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0207] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0208] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application belong to the scope of the present application and its equivalent technology, the present application is also intended to include these modifications and variations.

Claims

1. A data visualization method, characterized in that: include: Get the data to be visualized; Rendering the data to be visualized based on a general rendering application programming interface (API); The general rendering API is used to call a variety of different rendering algorithms.

2. The data visualization method according to claim 1, characterized in that: Before rendering the data to be visualized based on the general rendering API, the method further includes: Formatting and caching the data to be visualized based on the JSON format; According to the rendering requirement format, the cached data to be visualized after being formatted in JSON is adapted in format.

3. The data visualization method according to claim 2, characterized in that: After adapting the format of the cached data to be visualized after being formatted in JSON according to the rendering requirement format, the method further includes: When the rendering configuration provided by the user is different from the default rendering configuration, determining the rendering configuration to be the rendering configuration provided by the user; When the user does not provide a rendering configuration, the rendering configuration is determined to be the default rendering configuration.

4. The data visualization method according to claim 1, characterized in that: The obtaining of the data to be visualized includes: Based on a request message for requesting the data to be visualized, the data to be visualized is acquired; the request message carries indication information for indicating a rendering type; or, The data to be visualized is obtained based on a network application program interface of duplex real-time communication.

5. The data visualization method according to claim 1, characterized in that: The data to be visualized include: map data; The rendering of the data to be visualized based on a general rendering application program interface API includes: The map data is rendered based on a general rendering API.

6. The data visualization method according to claim 1, characterized in that: Before rendering the data to be visualized based on the general rendering API, the method further includes: Display scenes according to needs and dispatch rendering tasks; According to the rendering task, a required rendering algorithm is determined.

7. A data visualization system, characterized in that: include: Backend server and frontend client; The back-end server is used to provide the data to be visualized to the front-end client; The front-end client is used to render the data to be visualized based on a universal rendering API; the universal rendering API is used to call a variety of different rendering algorithms.

8. The data visualization system according to claim 7, characterized in that: The front-end client is also used to: Formatting and caching the data to be visualized based on the JSON format; According to the format of the rendering requirement, the cached data to be visualized after being formatted in JSON is adapted in format.

9. The data visualization system according to claim 8, characterized in that: The front-end client is also used to: When the rendering configuration provided by the user is different from the default rendering configuration, determining the rendering configuration to be the rendering configuration provided by the user; When the user does not provide a rendering configuration, the rendering configuration is determined to be the default rendering configuration.

10. The data visualization system according to claim 7, characterized in that: The backend server is specifically used for: Based on a request message from the front-end client for requesting the data to be visualized, providing the data to be visualized to the front-end client; the request message carries indication information for indicating a rendering type; or, Based on a network application program interface of duplex real-time communication, the data to be visualized is provided to the front-end client in real time.

11. The data visualization system according to any one of claims 7 to 10, characterized in that: The system further comprises: a rendering dispatcher; The rendering dispatcher is used to dispatch rendering tasks to the front-end client according to the required display scene; The front-end client is also used to determine a required rendering algorithm according to the rendering task.

12. The data visualization system according to claim 7, characterized in that: The system further comprises: a user interface; The user interface is used to provide interactive operations related to visualization; The user interface is also used to submit the data to be saved to the back-end server through the interactive interface between the back-end server and the back-end server.

13. The data visualization system according to claim 7, characterized in that: The system further comprises: a map data server; The map data server is used to provide map data to the front-end client; the front-end client is also used to render the map data based on a general rendering API.

14. An electronic device, characterized in that: Including memory, transceiver and processor: Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor, configured to read the computer program in the memory and execute the data visualization method described in any one of claims 1 to 6.

15. A non-transitory readable storage medium, characterized in that: The non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the data visualization method according to any one of claims 1 to 6.

Citation Information

Cited By

  • Map visualization translation tool

    EP4822526A1