A method, apparatus, device, and medium for rendering hypertext emails.

Abstract

This invention discloses a method, apparatus, device, and medium for rendering hypertext emails. The method includes: a server sending a hypertext email to a client, the hypertext email including page identification information and a page display structure; the server receiving a page rendering request from the client, the page rendering request carrying local page rendering parameters of the client and the page identification information; the server obtaining page content data corresponding to the page identification information; the server determining a page rendering result matching the client's display environment based on the page rendering parameters and the page content data; and the server sending the page rendering result to the client so that the client displays the page rendering result according to the target page display structure. This method improves user-friendliness through responsive layout and avoids client-side rendering problems by using server-side rendering, thus improving rendering quality.

Description

Technical Field

[0001] This invention relates to the field of hypertext mail, and more particularly to a hypertext mail rendering method, apparatus, device, and medium. Background Technology

[0002] Hypertext emails are a type of email that resembles a webpage, containing hypertext links that, when clicked, lead to other pages and may include images, audio, etc. Currently, when opening hypertext emails, mobile and desktop devices use the same page rendering result, making responsive layout impossible. Furthermore, the content displayed in a hypertext email is fixed when it is sent to the user's inbox, and the email cannot be updated in real time based on data.

[0003] In existing technologies, both mobile and desktop email systems suffer from hypertext email rendering issues. Mobile devices use inconsistent hypertext parsing engines, making it impossible to guarantee correct rendering of hypertext emails across all mobile email systems. On desktop, due to version updates, hypertext parsing behavior can be inconsistent, requiring extensive compatibility code to ensure correct rendering of hypertext emails when opened on specific desktop email clients. Therefore, it is necessary to resolve both the mobile parsing problem and the desktop compatibility issue. Summary of the Invention

[0004] This invention provides a method, apparatus, device, and medium for rendering hypertext emails, enabling different clients to use different rendering methods and display different page rendering results to achieve a responsive layout and improve user-friendliness. Furthermore, server-side rendering avoids parsing errors and compatibility issues encountered during client-side rendering, thus improving rendering quality.

[0005] On one hand, the present invention provides a method for rendering hypertext emails, the method comprising:

[0006] In response to the opening command of a hypertext email, a target page display structure matching the client's display environment is determined based on the client's display environment and the page display structure.

[0007] Receive a page rendering request sent by the client, the page rendering request carrying the client's local page drawing parameters and the page identification information;

[0008] Obtain the page content data corresponding to the page identifier information;

[0009] Based on the page rendering parameters and the page content data, determine the page rendering result that matches the display environment of the client;

[0010] The page rendering result is sent to the client so that the client can display the page rendering result according to the target page display structure.

[0011] On the other hand, a hypertext email rendering device is provided, the device comprising: a target page display structure determination module, a rendering request receiving module, a page content acquisition module, a rendering result acquisition module, and a rendering result sending module;

[0012] The target page display structure determination module is used to respond to the opening command of the hypertext email and determine the target page display structure that matches the display environment of the client based on the client's display environment and the page display structure of the hypertext email.

[0013] The rendering request receiving module is used to receive the page rendering request sent by the client. The page rendering request carries the page drawing parameters local to the client and the page identification information.

[0014] The page content acquisition module is used to acquire page content data corresponding to the page identification information;

[0015] The rendering result acquisition module is used to determine a page rendering result that matches the display environment of the client based on the page drawing parameters and the page content data.

[0016] The rendering result sending module is used to send the page rendering result to the client, so that the client can display the page rendering result according to the target page display structure.

[0017] On the other hand, an electronic terminal device is provided, the device including a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the hypertext email rendering method described above.

[0018] On the other hand, a computer-readable storage medium is provided, the storage medium including a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement a hypertext email rendering method as described above.

[0019] This invention provides a method, apparatus, device, and medium for rendering hypertext emails. The method includes: when a client opens a hypertext email sent by a server, it sends a page rendering request to the server; the server obtains page content data based on identification information in the page rendering request, and determines a rendering method based on page drawing parameters in the page rendering request; the server obtains a page rendering result based on the page content data and the rendering method; the server sends the page rendering result to the client, so that the client can display the page rendering result through the target page display structure. This method allows the server to use different rendering methods for different clients, improving user-friendliness. The method uses server-side rendering, which avoids the problem of insufficient rendering capabilities caused by client fragmentation and improves the quality of page rendering. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a schematic diagram illustrating an application scenario of a hypertext email rendering method provided in an embodiment of the present invention;

[0022] Figure 2 This is a flowchart of a hypertext email rendering method on the server side, provided by an embodiment of the present invention.

[0023] Figure 3 A flowchart illustrating a method for determining the display structure of a target page in a hypertext email rendering method provided in this embodiment of the invention;

[0024] Figure 4 This is a schematic diagram of the page display structure in a hypertext email rendering method provided in an embodiment of the present invention;

[0025] Figure 5 This is a schematic diagram illustrating the encoding of the page display structure in a hypertext email rendering method provided in an embodiment of the present invention;

[0026] Figure 6 This is a flowchart of a method for updating cached data in a hypertext email rendering method provided in an embodiment of the present invention;

[0027] Figure 7 This is a flowchart illustrating a method for rendering a page on a server in a hypertext email rendering method provided in an embodiment of the present invention.

[0028] Figure 8This is a flowchart illustrating a hypertext email rendering method that selects different rendering methods based on different clients, as provided in an embodiment of the present invention.

[0029] Figure 9 This is a schematic diagram illustrating the implementation of a responsive layout in a hypertext email rendering method provided in an embodiment of the present invention.

[0030] Figure 10 This is a schematic diagram of the computer-side rendering result in a hypertext email rendering method provided in an embodiment of the present invention;

[0031] Figure 11 This is a schematic diagram of the mobile rendering result in a hypertext email rendering method provided in an embodiment of the present invention;

[0032] Figure 12 This is a flowchart illustrating a hypertext email rendering method applied to a public opinion monitoring scenario, as provided in an embodiment of the present invention.

[0033] Figure 13 This is a flowchart illustrating the interaction between the server and client during rendering in a hypertext email rendering method provided in an embodiment of the present invention.

[0034] Figure 14 This is a schematic diagram of the email display process in a hypertext email rendering method provided in an embodiment of the present invention;

[0035] Figure 15 This is a logical diagram illustrating the various service modules of the server and client when executing a hypertext email rendering method according to an embodiment of the present invention.

[0036] Figure 16 This is a schematic diagram of the structure of a hypertext email rendering device provided in an embodiment of the present invention;

[0037] Figure 17 This is a schematic diagram of the hardware structure of a device for implementing the method provided in the embodiments of the present invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of this invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0039] In the description of this invention, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. Furthermore, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in sequences other than those illustrated or described herein.

[0040] Please see Figure 1 This diagram illustrates an application scenario of a hypertext email rendering method provided by an embodiment of the present invention. The application scenario includes a client 110 and a server 120. After receiving a hypertext email from the server 120, the client 110 sends a page rendering request to the server 120 when the user opens the hypertext email. The server 120 renders the email according to the page drawing parameters in the page rendering request and then sends the page rendering result back to the client 110. The client 110 selects a matching target page display structure from the page display structure in the hypertext email and displays the page rendering result.

[0041] In this embodiment of the invention, the client 110 may include physical devices such as smartphones, desktop computers, tablets, laptops, digital assistants, and smart wearable devices, and may also include software running on the physical device, such as testing programs. The operating system running on the user terminal 110 in this embodiment may include, but is not limited to, Android, iOS, Linux, Windows, and Mac systems.

[0042] In this embodiment of the invention, the server 110 may include a standalone server, a distributed server, or a server cluster consisting of multiple servers. The server 110 may include a network communication unit, a processor, and a memory, etc.

[0043] Please see Figure 2 It demonstrates a hypertext email rendering method applicable to the server side, the method comprising:

[0044] S210. In response to the opening command of the hypertext email, determine a target page display structure that matches the display environment of the client based on the client's display environment and the page display structure of the hypertext email;

[0045] Further, please see Figure 3The page display structure includes an image container for a preset display environment and an image container for a non-preset display environment. The image container for the non-preset display environment includes a first image container and a second image container. The step of determining a target page display structure that matches the client's display environment in response to the opening instruction of the hypertext email includes, based on the client's display environment and the page display structure.

[0046] S310. If the opening command of the hypertext email is triggered through a preset email address, the image container of the preset display environment is used as the target page display structure;

[0047] S320. If the opening command for an hypertext email is triggered via a non-preset email address, determine the client type of the client.

[0048] S330. If the client type of the client matches the first image container, the first image container is used as the target page display structure;

[0049] S340. If the client type information matches the second image container, determine the screen precision of the client;

[0050] S350. Based on the screen resolution of the client, a second image container that matches the screen resolution of the client is used as the target page display structure.

[0051] Specifically, the client invokes the page display structure within the hypertext email to display the page rendering result sent by the server. See also... Figure 4 ,like Figure 4 The diagram illustrates the page display structure. The default email address is an Outlook email address. The page display structure in a hypertext email uses two types of image containers: an Outlook email image container and a non-Outlook email image container. These can be created using MSO code and CSS hacks. The CSS hacks involve adding special symbols to CSS styles so that different browsers recognize different symbols. The MSO code is code that only the Outlook email client's Wordrending Engine (Word-HTML) can recognize.

[0052] For details on the specific code execution process, please refer to [link / reference]. Figure 5 ,like Figure 5This diagram illustrates the execution of encoding within the page display structure. The content `<!--[if mso]>` and `<!--[endif]—>` are encoded content written in MSO code, recognizable only by Outlook. When this encoding is executed, if the email open command is triggered by an Outlook mailbox, the encoding that hides the image container of the non-Outlook mailbox is executed. Clients with Outlook mailboxes will treat the encoding of the non-Outlook mailbox image container as a comment and will not execute it. If the email open command is triggered by a non-Outlook mailbox, since the MSO code can only be recognized by Outlook, other clients will not recognize the MSO code, thus hiding the encoding of the Outlook mailbox image container.

[0053] The image container for non-Outlook email accounts includes both desktop and mobile image containers. A media query is used to determine the local client's screen width, thus distinguishing between desktop and mobile devices. For example, if the screen width is less than 640 pixels, the local client is identified as mobile. If the local client is determined to be desktop, the desktop image container is displayed, the mobile image container is hidden, and the page rendering result is displayed using the desktop image container.

[0054] If the local client is determined to be a mobile device, the mobile image container distinguishes between different precision image rendering results based on the local client's screen device pixel ratio (devicePixelRatio). The mobile image container corresponding to the precision is selected and displayed. For example, mobile image containers include double-precision image display, triple-precision image display, and quadruple-precision image display. If the local client's screen device pixel ratio matches a triple-precision image, then the triple-precision image is displayed using the mobile image container.

[0055] If the local client's screen resolution does not match any of the preset mobile image containers with different resolutions, a default screen resolution value can be set. The mobile image container will then display the image based on this default resolution. For example, setting double-resolution image display as the default will result in the mobile image container displaying the image at double resolution when no match is found.

[0056] By editing the image containers of the preset display environment and those of non-preset display environments, other page display structures can be hidden when the target page display structure is determined. This avoids the problem of writing a lot of compatibility code when compatibility with specific desktop email clients, reduces the amount of code, and improves development efficiency.

[0057] S220. Receive a page rendering request sent by the client, the page rendering request carrying the client's local page drawing parameters and the page identification information;

[0058] Further, please see Figure 6 After receiving the page rendering request sent by the client, the method further includes:

[0059] S610. Obtain the page content update data corresponding to the page identification information;

[0060] S620. Locate the page rendering cache result that matches the page identification information and the page drawing parameters;

[0061] S630. Update the page rendering cache result according to the page content update data;

[0062] S640. The updated page rendering cache result is sent to the client so that the client displays the updated page rendering cache result according to the target page display structure.

[0063] Specifically, if the server already stores the rendered page cache result, and then obtains the page content update data corresponding to the same page identifier information, the page rendering cache result can be updated directly based on the page content update data. The server retrieves the updated page rendering cache result and sends it to the client, which can then display the updated result, allowing users to see real-time updated data when opening emails.

[0064] For example, if the server collects 10 data entries and sends them to the client before the user opens the email, but then updates the data by 5 entries when the user opens the email, the server will receive a rendering request and, based on the page identifier information, obtain the updated 5 data entries, presenting 15 data entries in the page rendering result.

[0065] By updating cached images, dynamically updated page rendering results can be obtained, allowing users to see real-time content when they open emails, thus improving the user experience.

[0066] S230. Obtain the page content data corresponding to the page identification information;

[0067] S240. Based on the page rendering parameters and the page content data, determine the page rendering result that matches the display environment of the client;

[0068] Further, please see Figure 7The page rendering parameters include client type information and region size information. Based on the page rendering parameters and the page content data, the page rendering result that matches the client's display environment is determined as follows:

[0069] S710. Determine the image rendering method corresponding to the client based on the client type information;

[0070] S720. Determine each rendering area in the webpage to be rendered based on the area size information;

[0071] S730. Based on the image rendering method, render each rendering area in the webpage to be rendered to obtain the page rendering result.

[0072] Specifically, client type information can include desktop and mobile devices, requiring different rendering methods for each. Region size information refers to the maximum area for images displayed in a hypertext email. For example, in Outlook, the height of a single image cannot exceed 1728 pixels. Therefore, based on the region size information, it's necessary to determine whether the page to be rendered exceeds the preset maximum height. If it does, the page needs to be rendered in chunks.

[0073] When a server accesses a corresponding URL using page identifier information to retrieve page content data, it obtains Hyper Text Markup Language (HTML) code with responsive layout. A headless browser then renders each rendered area of ​​the webpage in segments to obtain the final rendering result. This rendering result can be stitched together on the client side and displayed as an image. The headless browser can be Puppeteer or PhantomJS, among others.

[0074] Server-side rendering avoids the problem of insufficient rendering capabilities caused by client-side fragmentation, ensuring that parsing issues on mobile devices and compatibility issues on desktop devices do not affect webpage rendering, thereby improving the quality of page rendering.

[0075] Further, please see Figure 8 The image rendering method includes a first rendering method and a second rendering method. The rendering of each rendering area in the webpage to be rendered based on the image rendering method to obtain the page rendering result includes:

[0076] S810. If the image rendering method is the first rendering method, obtain a preset screen precision value that matches the first rendering method;

[0077] S820. Based on the first rendering method and the preset screen precision value, render each rendering area in the webpage to be rendered to obtain the page rendering result;

[0078] S830. If the image rendering method is the second rendering method, the page drawing parameters in the received page rendering request also include screen precision information;

[0079] S840. Based on the second rendering method and the screen precision information, render each rendering area in the webpage to be rendered to obtain the page rendering result corresponding to the screen precision information.

[0080] Specifically, when the client type information determines that the client is a desktop computer, the corresponding rendering method is the first rendering method, and the headless browser renders using the desktop kernel. The desktop rendering method uses a preset screen precision value for unified rendering, so the default screen precision value, such as double precision, is directly obtained to render each rendering area in the webpage to obtain the page rendering result.

[0081] When the client is determined to be a mobile device based on the client type information, the corresponding rendering method is the second rendering method. The headless browser renders using mobile kernels with multiple screen precisions. Among them, the mobile kernels with multiple screen precisions can have three screen precisions, including a mobile kernel with double precision, a mobile kernel with triple precision, and a mobile kernel with quadruple precision.

[0082] Multiple screen resolution mobile kernels are designed to match mobile devices with different resolutions. Therefore, when the server receives a page rendering request from the client, if the client is a mobile device, the client will send the mobile device's screen resolution information to the server. The server will then select the mobile kernel with the corresponding resolution based on this screen resolution information to render the page and obtain the page rendering result corresponding to the screen resolution information.

[0083] In one specific embodiment, during rendering, responsive layouts can be achieved using the capabilities provided by HyperText Markup Language 5.0 (HTML5) and Cascading Style Sheets level 3 (CSS3). These capabilities include, but are not limited to, media query layouts, flexbox layouts, rem layouts, and grid layouts. Media queries define style sheet rules based on different media types and conditions, allowing CSS to more precisely apply to different media types and different conditions within the same media. See also... Figure 9 ,like Figure 9The diagram illustrates how responsive layouts are implemented. Both desktop and mobile devices execute basic CSS code during rendering. However, different mobile devices also execute CSS code with different settings, overriding the previously executed basic CSS code to achieve the responsive layout effect. This adapts the layout to the display environment of different mobile devices. Rendering is performed using a headless browser, thus eliminating the need to consider compatibility issues between desktop and mobile devices. The final display on the client side will look like this... Figure 10 The computer-side rendering results shown, and as follows Figure 11 The mobile rendering results shown demonstrate that the page rendering can match the screen interface, presenting different page layouts on different clients.

[0084] Adapting to mobile and desktop devices with varying screen resolutions, the responsive layout allows for different rendering methods on different clients, improving user-friendliness. Furthermore, the email display webpage, built with HTML5 and CSS3, allows for richer user interfaces using scripts, further enhancing the user experience.

[0085] S250. The page rendering result is sent to the client so that the client displays the page rendering result according to the target page display structure.

[0086] Specifically, the client does not perform image rendering locally; instead, the server handles the image rendering. Based on its local display environment, the client selects the corresponding target page display structure from the page display structure. When receiving the page rendering result from the server, the client hides other page display structures within the current page display structure and displays the page rendering result through the target page display structure.

[0087] The client can also generate page rendering parameters locally and send them to the server. This allows the server to obtain a page rendering result that matches the client's local display environment based on the page rendering parameters corresponding to the client. If the client is a computer, the page rendering parameters include client type information and region size information. If the client is a mobile device, the page rendering parameters include client type information, region size information, and screen resolution information.

[0088] The client can also stitch together the page rendering results of the segmented rendering returned by the server and display them to the user in the form of a report.

[0089] Further, please see Figure 12 The hypertext email rendering method can be applied in public opinion monitoring scenarios, and the method includes:

[0090] S1210. Obtain user settings information;

[0091] S1220. Obtain alarm data for public opinion monitoring based on the alarm trigger conditions in the user settings information;

[0092] S1230. Generate page identification information based on the alarm data;

[0093] S1240. Generate a hypertext email based on the page identification information and the preset page display structure;

[0094] S1250. Retrieve an email address that matches the user settings information;

[0095] S1260. Send the hypertext email to the email address.

[0096] Specifically, users can configure alarm thresholds, media channels to be monitored, and keywords to monitor, such as crashes and cheating, on the product's web interface. When data from any media channel exceeds the threshold, the backend service will trigger an alarm, generating a report which will be sent to designated personnel via email. The email recipient can then identify and address related issues based on the report's content.

[0097] Users preset alarm trigger conditions for public opinion monitoring, such as preset keywords. An alarm is triggered every time the keyword appears. The server generates a webpage link based on these trigger conditions. This webpage link serves as the page identifier and is used to display the alarm report content. The webpage link and the preset page display structure are then used to generate a hypertext email. The page display structure consists of image containers that are displayed on different clients. The client that opens the email selects the corresponding image container to display the rendered page.

[0098] After the server generates a hypertext email, it retrieves email addresses that match the user's settings, determines the recipient of the hypertext email, and sends the hypertext email to that email address.

[0099] Please see Figure 13 It demonstrates a method for rendering hypertext emails in an interactive manner between the server and the client, the method comprising:

[0100] S1310. The server sends a hypertext email to the client, wherein the hypertext email includes page identification information and page display structure;

[0101] S1320. In response to the hypertext email open command, the server determines the target page display structure that matches the client's display environment based on the client's display environment and page display structure;

[0102] S1330. The client sends a page rendering request to the server, wherein the page rendering request carries the client's local page drawing parameters and page identification information;

[0103] S1340. The server retrieves the page content data corresponding to the page identifier information;

[0104] S1350. The server determines the page rendering result that matches the client's display environment based on the page rendering parameters and page content data;

[0105] S1360. The server sends the page rendering result to the client;

[0106] S1370. The client displays the page rendering result according to the target page display structure.

[0107] Specifically, please see Figure 14 and Figure 15 ,like Figure 14 The diagram shows the interactive flow of email display. Figure 15 This is an overall architecture diagram of the various service modules in the server and client.

[0108] When a user opens an email on their client, the server receives the instruction and first determines if it's within the default email environment, which can be Outlook. If it is Outlook, the default is desktop, and the server selects an Outlook image container to prepare the page rendering result sent by the server. If it's not Outlook, the server determines whether it's a mobile or desktop device and selects the corresponding mobile or desktop image container to prepare for display.

[0109] The client generates a page rendering request and sends it to the server's drawing service, which then renders the page. If the identifier information in the page rendering request matches the identifier information of the page rendering cache result stored in the server's image caching service, the server updates the data according to the page content corresponding to the identifier information, updates the page rendering cache result, and sends the updated page rendering cache result to the client for display.

[0110] If no cached result is found, the server-side drawing service retrieves the page content data corresponding to the identifier information, i.e., the responsive layout's HTML code, through the web service. The web service can obtain the page content data through information transmission with the backend service. The server renders the page using a headless browser based on the responsive layout's HTML code and the page rendering parameters in the page rendering request. During page rendering, the server determines the client type based on the page rendering parameters, selects the corresponding rendering method, and saves a screenshot of the final rendered page. The server sends the saved screenshot of the rendered page to the client, which then stitches the screenshots together into a report and displays it using the previously selected image container.

[0111] This invention proposes a hypertext rendering method, which includes: when a client opens a hypertext email sent by a server, it sends a page rendering request to the server; the server obtains page content data based on the identifier information in the page rendering request, and determines the rendering method based on the page drawing parameters in the page rendering request; the server obtains the page rendering result based on the page content data and the rendering method. The client obtains the target page display structure from the page display structure in the hypertext email according to its local display environment; the client receives the page rendering result sent by the server and displays the page rendering result through the target page display structure. This method is adaptable to mobile and desktop devices with different screen resolutions, enabling responsive layout and allowing different clients to use different rendering methods, thus improving user-friendliness. The method uses server-side rendering, avoiding the problem of insufficient rendering capabilities caused by client fragmentation, such as parsing issues on mobile devices and compatibility issues on desktop devices, thereby improving the quality of page rendering.

[0112] This invention also provides a server-side hypertext email rendering device; please refer to [link to relevant documentation]. Figure 16 The device includes: a target page display structure determination module 1610, a rendering request receiving module 1620, a page content acquisition module 1630, a rendering result acquisition module 1640, and a rendering result sending module 1650.

[0113] The target page display structure determination module 1610 is used to respond to the opening command of the hypertext email and determine the target page display structure that matches the display environment of the client based on the client's display environment and the page display structure of the hypertext email.

[0114] The rendering request receiving module 1620 is used to receive the page rendering request sent by the client. The page rendering request carries the page drawing parameters local to the client and the page identification information.

[0115] The page content acquisition module 1630 is used to acquire page content data corresponding to the page identification information;

[0116] The rendering result acquisition module 1640 is used to determine a page rendering result that matches the display environment of the client based on the page drawing parameters and the page content data.

[0117] The rendering result sending module 1650 is used to send the page rendering result to the client, so that the client can display the page rendering result according to the target page display structure.

[0118] The apparatus provided in the above embodiments can execute the method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method. Technical details not described in detail in the above embodiments can be found in a hypertext email rendering method provided in any embodiment of the present invention.

[0119] This embodiment also provides a device including a processor and a memory, wherein the memory stores a computer program adapted to be loaded by the processor and executed as described above in this embodiment of a hypertext email rendering method.

[0120] The device may be a computer terminal, a mobile terminal, or a server, and the device may also participate in constituting the apparatus or system provided in the embodiments of the present invention. For example... Figure 17 As shown, taking a mobile terminal as an example, the mobile terminal 17 (or computer terminal 17 or server 17) may include one or more processors 1702 (shown as 1702a, 1702b, ..., 1702n in the figure) (processor 1702 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 1704 for storing data, and a transmission device 1706 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 17 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the mobile device 17 may also include... Figure 17 More or fewer components than shown, or with Figure 17 Different configurations shown.

[0121] It should be noted that the aforementioned one or more processors 1702 and / or other data processing circuitry are generally referred to herein as "data processing circuitry". This data processing circuitry may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuitry may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the mobile device 17 (or computer terminal). As involved in the embodiments of this application, this data processing circuitry serves as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0122] The memory 1704 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the method described in the embodiments of the present invention. The processor 1702 executes various functional applications and data processing by running the software programs and modules stored in the memory 1704, thereby realizing the above-described method for generating temporal behavior capture boxes based on self-attention networks. The memory 1704 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1704 may further include memory remotely located relative to the processor 1702, and these remote memories can be connected to the mobile device 17 via a network. Examples of the above-mentioned networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0123] The transmission device 1706 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the mobile terminal 17. In one example, the transmission device 1706 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 1706 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0124] The display may be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the mobile device 17 (or computer terminal).

[0125] This specification provides the operational steps of the methods described in the embodiments or flowcharts, but more or fewer operational steps may be included based on conventional or non-inventive labor. The steps and order listed in the embodiments are merely one possible execution order among many steps and do not represent the only execution order. In actual system or interrupt product execution, the methods shown in the embodiments or drawings can be executed sequentially or in parallel (e.g., in a parallel processor or multi-threaded processing environment).

[0126] The structure shown in this embodiment is only a partial structure related to the solution of this application and does not constitute a limitation on the device to which the solution of this application is applied. Specific devices may include more or fewer components than shown, or combinations of certain components, or arrangements of different components. It should be understood that the methods, apparatuses, etc., disclosed in this embodiment can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or unit modules through some interfaces.

[0127] Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0128] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this specification can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0129] The above embodiments can be referenced to each other, and the above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for rendering hypertext emails, characterized in that, The method is used on a server, and the method includes: Receive a page rendering request sent by the client, the page rendering request carrying the client's local page drawing parameters and page identification information; Obtain the page content data corresponding to the page identifier information; Based on the page rendering parameters and the page content data, determine the page rendering result that matches the display environment of the client; The page rendering result is sent to the client so that the client can display the page rendering result according to the target page display structure. The target page display structure is selected by the client from the page display structure of the hypertext email according to the client's display environment. The target page display structure matches the client's display environment. The page display structure is composed of image containers for display on different clients.

2. The hypertext email rendering method according to claim 1, characterized in that, The page rendering parameters include client type information and region size information. Determining the page rendering result that matches the client's display environment based on the page rendering parameters and the page content data includes: Based on the client type information, determine the image rendering method corresponding to the client; Based on the area size information, determine each rendering area in the webpage to be rendered; Based on the image rendering method, each rendering area in the webpage to be rendered is rendered to obtain the page rendering result.

3. The hypertext email rendering method according to claim 2, characterized in that, The image rendering method includes a first rendering method and a second rendering method. The rendering of each rendering area in the webpage to be rendered based on the image rendering method to obtain the page rendering result includes: If the image rendering method is the first rendering method, obtain the preset screen precision value that matches the first rendering method; Based on the first rendering method and the preset screen precision value, each rendering area in the webpage to be rendered is rendered to obtain the page rendering result. If the image rendering method is the second rendering method, the page drawing parameters in the received page rendering request also include screen precision information; Based on the second rendering method and the screen precision information, each rendering area in the webpage to be rendered is rendered to obtain the page rendering result corresponding to the screen precision information.

4. The hypertext email rendering method according to claim 1, characterized in that, Before sending the hypertext email, which includes page identification information and page display structure, the following are also included: Obtain user settings information; Based on the alarm trigger conditions in the user settings, obtain alarm data for public opinion monitoring; Based on the alarm data, generate page identification information; Generate a hypertext email based on the page identification information and the preset page display structure; Retrieve email addresses that match the user's settings; Send the hypertext email to the email address.

5. The hypertext email rendering method according to claim 1, characterized in that, After receiving the page rendering request sent by the client, the process further includes: Obtain the page content update data corresponding to the page identifier information; Find the page rendering cache result that matches the page identification information and the page rendering parameters; Update the page rendering cache result based on the page content update data; The updated page rendering cache result is sent to the client so that the client can display the updated page rendering cache result according to the target page display structure.

6. The hypertext email rendering method according to claim 1, characterized in that, The page display structure includes an image container with a preset display environment and an image container with a non-preset display environment. The image container with a non-preset display environment includes a first image container and a second image container. If the opening command of the hypertext email is triggered through a preset email address, the target page display structure is the image container of the preset display environment; If an instruction to open a hypertext email is triggered via a non-preset email address, and the client type of the client matches the first image container, the target page display structure is the first image container; If an instruction to open a hypertext email is triggered via a non-preset email address, and the client type information matches the second image container, the target page display structure is the second image container that matches the screen resolution of the client.

7. A hypertext email rendering device, characterized in that, The device is used for a server and includes: a rendering request receiving module, a page content acquisition module, a rendering result acquisition module, and a rendering result sending module; The rendering request receiving module is used to receive page rendering requests sent by the client. The page rendering request carries the client's local page drawing parameters and page identification information. The page content acquisition module is used to acquire page content data corresponding to the page identification information; The rendering result acquisition module is used to determine a page rendering result that matches the display environment of the client based on the page drawing parameters and the page content data. The rendering result sending module is used to send the page rendering result to the client, so that the client can display the page rendering result according to the target page display structure. The target page display structure is selected by the client from the page display structure of the hypertext email according to the client's display environment. The target page display structure matches the client's display environment. The page display structure is composed of image containers for display on different clients.

8. The hypertext email rendering device according to claim 7, characterized in that, The client type is either a computer or a mobile terminal.

9. An electronic device, characterized in that, The device includes a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement a hypertext email rendering method as described in any one of claims 1-6.

10. A storage medium, characterized in that, The storage medium includes a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or the at least one program is loaded and executed by the processor to implement a hypertext email rendering method as described in any one of claims 1-6.

Images