Message pushing method, message pushing system, electronic equipment and storage medium

Abstract

The invention discloses a message pushing method, a message pushing system, electronic equipment and a storage medium. The method relates to the field of communication in cloud computing, and comprises the following steps: receiving a message push request, the message push request at least comprising a communication identifier of a device end initiating the request; based on the communication identifier, determining a layout style matched with the to-be-pushed message content; and based on the communication identifier, pushing the to-be-pushed message content and the layout style to the device end, the to-be-pushed message content being rendered on a screen of the device end according to the layout style. According to the invention, the technical problem of poor rendering effect of the 5G rich media message at the equipment side in the related technology is solved.

Description

Technical Field

[0001] The present application relates to the field of communications in cloud computing, and in particular to a message push method, a message push system, an electronic device, and a storage medium. Background Art

[0002] With the development of the fifth generation mobile communication system (5th Generation Mobile Communication System, referred to as 5G) technology, 5G rich media messages are increasingly used in device terminals. The existing message transmission scheme mainly obtains the screen information of the device terminal through the JavaScript (a lightweight, interpreted or just-in-time compiled programming language with function priority, referred to as JS) code of the web page, and then adjusts the size of the elements in the rich media message based on the screen size. Finally, the message can be adaptively displayed on the screen of the device terminal. However, for 5G rich media messages, when rendering the content of 5G rich media messages, JS code cannot be executed due to security requirements, which results in the inability of 5G rich media messages to adapt to the screen size of the device terminal, resulting in poor rendering effect of 5G rich media messages. In response to the above problems, no effective solution has been proposed yet. Summary of the invention

[0003] The embodiments of the present application provide a message push method, a message push system, an electronic device and a storage medium to at least solve the technical problem of poor rendering effect of 5G rich media messages on the device side in the related technology.

[0004] According to one aspect of an embodiment of the present application, a message push method is provided, which is applied to the cloud, and the method includes: receiving a message push request, wherein the message push request includes at least: a communication identifier of a device side that initiates the request; based on the communication identifier, determining a layout style that matches the message content to be pushed; based on the communication identifier, pushing the message content to be pushed and the layout style to the device side, wherein the message content to be pushed is rendered on the screen of the device side according to the layout style.

[0005] According to another aspect of an embodiment of the present application, a message push method is also provided, which is applied to a device end, and includes: responding to an input instruction of an interactive interface acting on the device end, and obtaining a communication identifier of the device end; responding to a message push instruction acting on the interactive interface, and displaying a display result of the message content to be pushed on the interactive interface, wherein the display result is a result of rendering the message content to be pushed on the screen of the device end according to a layout style matching the message content to be pushed, and the message content and layout style to be pushed are pushed to the device end by the cloud based on the communication identifier, and the layout style is determined by the cloud based on the communication identifier.

[0006] According to another aspect of an embodiment of the present application, a message push method is also provided, which includes: the device side sends a message push request to the cloud, wherein the message push request carries the communication identifier of the device side; the device side receives the message content to be pushed and the layout style matching the message content to be pushed pushed by the cloud based on the communication identifier, wherein the layout style is determined by the cloud based on the communication identifier; the device side renders the message content to be pushed on the screen of the device side based on the layout style.

[0007] According to another aspect of an embodiment of the present application, a message push method is also provided, which is applied to the cloud, including: obtaining a message push request by calling a first interface, wherein the first interface includes a first parameter, and the parameter value of the first parameter includes the message push request, and the message push request includes at least: a communication identifier of the device end that initiates the request; based on the communication identifier, determining a layout style that matches the message content to be pushed; pushing the message content and layout style to be pushed to the device end based on the communication identifier by calling a second interface, wherein the second interface includes a second parameter, and the parameter value of the second parameter includes the message content to be pushed and the layout style, and the message content to be pushed is rendered on the screen of the device end according to the layout style.

[0008] According to another aspect of an embodiment of the present application, a message push system is also provided, including: a device side, used to send a message push request, wherein the message push request includes at least: a communication identifier of the device side that initiates the request; a cloud end, connected to the device side, used to determine a layout style that matches the message content to be pushed based on the communication identifier, and push the message content and layout style to be pushed to the device side based on the communication identifier, wherein the layout style is used to represent the display result of the message content to be pushed on the screen of the device side; the device side is also used to render the message content to be pushed on the screen of the device side according to the layout style.

[0009] According to another aspect of an embodiment of the present application, a message push device is also provided, which is applied to the cloud, and the device includes: a request receiving module, which is used to receive a message push request, wherein the message push request includes at least: a communication identifier of the device end that initiates the request; a determination module, which is used to determine a layout style that matches the message content to be pushed based on the communication identifier; and a push module, which is used to push the message content and layout style to be pushed to the device end based on the communication identifier, wherein the message content to be pushed is rendered on the screen of the device end according to the layout style.

[0010] According to another aspect of an embodiment of the present application, a message push device is also provided, which is applied to a device end, and the device includes: an acquisition module, which is used to respond to input instructions of an interactive interface acting on the device end, and acquire a communication identifier of the device end; a display module, which is used to respond to message push instructions acting on the interactive interface, and display the display result of the message content to be pushed on the interactive interface, wherein the display result is the result of rendering the message content to be pushed on the screen of the device end according to a layout style matching the message content to be pushed, and the message content and layout style to be pushed are pushed to the device end by the cloud based on the communication identifier, and the layout style is determined by the cloud based on the communication identifier.

[0011] According to another aspect of an embodiment of the present application, a message push device is also provided, including: a sending module, used by a device to send a message push request to a cloud, wherein the message push request carries a communication identifier of the device; a receiving module, used by the device to receive a message content to be pushed and a layout style matching the message content to be pushed pushed by the cloud based on the communication identifier, wherein the layout style is determined by the cloud based on the communication identifier; and a display module, used by the device to render and display the message content to be pushed on a screen of the device based on the layout style.

[0012] According to another aspect of an embodiment of the present application, a message push device is also provided, which is applied to the cloud, and the device includes: an acquisition module, which is used to obtain a message push request by calling a first interface, wherein the first interface includes a first parameter, and the parameter value of the first parameter includes the message push request, and the message push request includes at least: a communication identifier of the device end that initiates the request; a determination module, which is used to determine a layout style that matches the message content to be pushed based on the communication identifier; a push module, which is used to push the message content and layout style to be pushed to the device end based on the communication identifier by calling a second interface, wherein the second interface includes a second parameter, and the parameter value of the second parameter includes the message content and layout style to be pushed, and the message content to be pushed is rendered on the screen of the device end according to the layout style.

[0013] According to another aspect of an embodiment of the present application, an electronic device is further provided, including: a memory storing an executable program; and a processor for running the program, wherein any one of the above methods is executed when the program is running.

[0014] According to another aspect of an embodiment of the present application, a computer-readable storage medium is further provided, the computer-readable storage medium including a stored executable program, wherein when the executable program is running, the device where the storage medium is located is controlled to execute any of the above methods.

[0015] In the embodiment of the present application, a message push request is received, wherein the message push request at least includes: a communication identifier of the device side that initiates the request; based on the communication identifier, determining a layout style that matches the message content to be pushed; based on the communication identifier, pushing the message content and layout style to be pushed to the device side, wherein the message content to be pushed is rendered on the screen of the device side according to the layout style. It is easy to notice that the cloud can identify the screen information of the device side through the communication identifier sent by the device side, and can determine a layout style that matches the message content to be pushed based on the screen information of the device side, and then the cloud can send the layout style to the device side at the same time as sending the message content to be pushed, so that the display result rendered on the device side matches the screen information of the device side, and the purpose of automatically adapting the 5G rich media message to the screen information of the device side is achieved, thereby achieving the technical effect of improving the rendering effect of the 5G rich media message on the device side, and then solving the technical problem of poor rendering effect of the 5G rich media message on the device side in the related technology.

[0016] It is easy to notice that the above general description and the following detailed description are only for the purpose of exemplifying and explaining the present application, and do not constitute a limitation of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 It is a hardware structure block diagram of a computer terminal (or mobile device) for implementing a message push method according to an embodiment of the present application;

[0019] Figure 2 is a structural block diagram of a computing environment according to an embodiment of the present application;

[0020] Figure 3 is a structural block diagram of a service grid according to an embodiment of the present application;

[0021] Figure 4 is a flowchart of a message push method according to Embodiment 1 of the present application;

[0022] Figure 5 is a schematic diagram of an optional method of establishing a screen database according to Embodiment 1 of the present application;

[0023] Figure 6 is a schematic diagram of multiple optional layout styles according to Embodiment 1 of the present application;

[0024] Figure 7It is a flowchart of an alternative method for a device to obtain push messages according to Embodiment 1 of the present application;

[0025] Figure 8 It is a flowchart of another alternative method for a device to obtain push messages according to Embodiment 1 of the present application;

[0026] Figure 9 It is a flowchart of a message push method according to Embodiment 2 of the present application;

[0027] Figure 10 It is a schematic diagram of an alternative interaction interface according to Embodiment 2 of the present application;

[0028] Figure 11 It is a flowchart of a message push method according to Embodiment 3 of the present application;

[0029] Figure 12 It is a flowchart of a message push method according to Embodiment 4 of the present application;

[0030] Figure 13 It is a schematic diagram of a message push device according to Embodiment 5 of the present application;

[0031] Figure 14 It is a schematic diagram of a message push device according to Embodiment 6 of the present application;

[0032] Figure 15 It is a schematic diagram of a message push device according to Embodiment 7 of the present application;

[0033] Figure 16 It is a schematic diagram of a message push device according to Embodiment 8 of the present application;

[0034] Figure 17 It is a schematic diagram of a message push system according to Embodiment 9 of the present application;

[0035] Figure 18 It is a block diagram of a computer terminal according to an embodiment of the present application. Detailed implementation manners

[0036] In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the scope of protection of the present application.

[0037] It should be noted that the terms "first", "second", etc. in the description, claims and above-mentioned drawings of this application are used to distinguish similar objects, and do not necessarily describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of this application described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0038] First, some nouns or terms that appear during the description of the embodiments of this application are applicable to the following explanations:

[0039] 5G Rich Media Message: It is an upgrade of the SMS function and a basic telecommunications service of the operator. Based on IP technology, it realizes a leap in the usage experience and supports more media formats such as voice, video, pictures, text, etc. combined, with a richer form of expression.

[0040] HTML: Hyper Text Markup Language, which is a hypertext markup language including a series of tags. Through these tags, the formats of documents on the network can be unified, and the scattered Internet resources can be connected into a logical whole. HTML text is descriptive text composed of HTML commands, and HTML commands can describe text, graphics, animations, sounds, tables, links, etc.

[0041] JavaSript: It is a lightweight, interpreted or just-in-time compiled programming language with function priority and can be used as a script for developing web pages.

[0042] Clustering: An unsupervised learning method used to divide samples of unknown categories, dividing them into several clusters according to certain rules, clustering similar samples in the same cluster, and dividing dissimilar samples into different clusters, so as to reveal the internal properties of the samples and the connection rules between them.

[0043] Embodiment 1

[0044] According to one aspect of the embodiments of this application, a message push method is provided. As an alternative implementation, the above message push method can be but is not limited to being applied to, for example Figure 1 the application scenarios shown. Figure 1 It is a schematic diagram of the application scenario of a message push method according to the embodiments of this application, as Figure 1As shown, in the application scenario, the terminal device 12 can communicate with the server 16 through the network 14, but is not limited to, and the server 16 can perform operations on the database 18, such as writing data operations or reading data operations. The terminal device 12 can include, but is not limited to, a human-computer interaction screen, a processor, and a memory. The human-computer interaction screen can be used to display, but is not limited to, deploying a virtual machine 110 on the terminal device 12. The processor can include, but is not limited to, responding to the human-computer interaction operation, executing a corresponding operation, or generating a corresponding instruction, and sending the generated instruction to the server 16. The memory is used to store relevant processing data, such as device status data.

[0045] As an optional method, the following steps in the data processing method of the virtual machine can be executed on the server 16: Step S102, receiving a message push request; Step S102, determining a layout style that matches the message content to be pushed based on the communication identifier; Step S106, pushing the message content and layout style to be pushed to the device end based on the communication identifier.

[0046] In the above manner, the communication identifier of the device side that initiates the request is determined; based on the communication identifier, the layout style that matches the message content to be pushed is determined; based on the communication identifier, the message content to be pushed and the layout style are pushed to the device side, wherein the message content to be pushed is rendered on the screen of the device side according to the layout style, thereby achieving the purpose of automatically adapting the 5G rich media message to the screen information of the device side, thereby achieving the technical effect of improving the rendering effect of the 5G rich media message on the device side, and further solving the technical problem of poor rendering effect of the 5G rich media message on the device side in the related technology.

[0047] In an optional embodiment, Figure 2 The block diagram shows the use of the above Figure 1 The server 16 (or mobile device) is shown as an embodiment of a computing node in the computing environment 201. Figure 2 is a structural block diagram of a computing environment according to an embodiment of the present application, such as Figure 2 As shown, computing environment 201 includes multiple computing nodes (such as servers) running on a distributed network (shown as 210-1, 210-2, ..., in the figure). The computing nodes all contain local processing and memory resources, and end users 202 can remotely run applications or store data in computing environment 201. Applications can be provided as multiple services 220-1, 220-2, 220-3 and 220-4 in computing environment 201, representing services "A", "D", "E" and "H" respectively.

[0048] The end user 202 can provide and access services through a web browser or other software applications on the client. In some embodiments, the provision and / or request of the end user 202 can be provided to the ingress gateway 230. The ingress gateway 230 can include a corresponding proxy to handle the provision and / or request for services (one or more services provided in the computing environment 201).

[0049] Services are provided or deployed according to various virtualization technologies supported by the computing environment 201. In some embodiments, services can be provided based on virtual machine (VM)-based virtualization, container-based virtualization, and / or similar means. VM-based virtualization can be achieved by initializing a virtual machine to simulate a real computer and executing programs and applications without directly accessing any actual hardware resources. While virtualizing the machine with a virtual machine, according to container-based virtualization, containers can be launched to virtualize the entire operating system (OS) so that multiple workloads can run on a single operating system instance.

[0050] In one embodiment of container-based virtualization, several containers of a service can be assembled into a Pod (e.g., a Kubernetes Pod). For example, as Figure 2 shown, service 220-2 can be equipped with one or more Pods 240-1, 240-2,..., 240-N (collectively referred to as Pods). A Pod can include a proxy 245 and one or more containers 242-1, 242-2,..., 242-M (collectively referred to as containers). One or more containers in the Pod handle requests related to one or more corresponding functions of the service, and the proxy 245 generally controls network functions related to the service, such as routing, load balancing, etc. Other services can also be equipped with similar Pods.

[0051] During operation, executing a user request from the end user 202 may require invoking one or more services in the computing environment 201, and executing one or more functions of a service may require invoking one or more functions of another service. As Figure 2 shown, service "A" 220-1 receives a user request from the end user 202 from the ingress gateway 230. Service "A" 220-1 can invoke service "D" 220-2, and service "D" 220-2 can request service "E" 220-3 to execute one or more functions.

[0052] The above computing environment can be a cloud computing environment, where the allocation of resources is managed by a cloud service provider, allowing the development of functions without considering the implementation, adjustment, or expansion of servers. This computing environment allows developers to execute code in response to events without building or maintaining complex infrastructure. Services can be split into a set of functions that can be automatically scaled independently, rather than scaling a single hardware device to handle potential loads.

[0053] In another alternative embodiment, Figure 3 A block diagram shows an embodiment of using the above Figure 1 shown computer terminal 10 (or mobile device) as a service mesh. Figure 3 It is a structural block diagram of a service mesh according to an embodiment of the present application. As Figure 3 shown, the service mesh 300 is mainly used to facilitate secure and reliable communication between multiple microservices. Microservices refer to decomposing an application into multiple smaller services or instances and running them on different clusters / machines.

[0054] As Figure 3 shown, the microservices can include application service instance A and application service instance B. Application service instance A and application service instance B form the functional application layer of the service mesh 300. In one implementation, application service instance A runs in the form of a container / process 308 in the machine / workload container group 314 (Pod), and application service instance B runs in the form of a container / process 310 in the machine / workload container group 316 (Pod).

[0055] In one implementation, application service instance A can be a product query service, and application service instance B can be a product order placement service.

[0056] As Figure 3 shown, application service instance A and mesh proxy (sidecar) 303 coexist in the machine workload container group 314, and application service instance B and mesh proxy 305 coexist in the machine workload container 316. Mesh proxy 303 and mesh proxy 305 form the data plane layer (dataplane) of the service mesh 300. Among them, mesh proxy 303 and mesh proxy 305 run in the form of container / process 304 and container / process 306 respectively, can receive requests 312 for product query services, and there can be two-way communication between mesh proxy 303 and application service instance A, and between mesh proxy 305 and application service instance B. In addition, there can also be two-way communication between mesh proxy 303 and mesh proxy 305.

[0057] In one embodiment, the traffic of application service instance A is routed to appropriate destinations through mesh proxy 303, and the network traffic of application service instance B is routed to appropriate destinations through mesh proxy 305. It should be noted that the network traffic mentioned herein includes, but is not limited to, forms such as Hyper Text Transfer Protocol (abbreviated as HTTP), Representational State Transfer (abbreviated as REST), google Remote Procedure Call (gRPC), an open-source in-memory data structure storage system (Redis), etc.

[0058] In one embodiment, the function of the extended data plane layer can be implemented by writing custom filters for the Envoy proxy in service mesh 300. The service mesh proxy configuration can be used to correctly proxy service traffic in the service mesh and achieve service interconnection and service governance. Mesh proxy 303 and mesh proxy 305 can be configured to perform at least one of the following functions: service discovery, health checking, routing, load balancing, authentication and authorization, and observability.

[0059] As Figure 3 shown, the service mesh 300 further includes a control plane layer. Among them, the control plane layer can be a set of services running in a dedicated namespace, and these services are hosted by the managed control plane component 301 in the machine / Workload Pod 302. As Figure 3 shown, the managed control plane component 301 communicates bidirectionally with mesh proxy 303 and mesh proxy 305. The managed control plane component 301 is configured to perform some control and management functions. For example, the managed control plane component 301 receives the telemetry data transmitted by mesh proxy 303 and mesh proxy 305 and can further aggregate this telemetry data. For these services, the managed control plane component 301 can also provide user-facing Application Programming Interfaces (APIs) to more easily manipulate network behavior and provide configuration data to mesh proxy 303 and mesh proxy 305.

[0060] Under the above operating environment, the present application provides as Figure 4The message push method shown is applied to the cloud. Figure 4 is a flow chart of a message push method according to Example 1 of the present application, such as Figure 4 As shown, the method comprises the following steps:

[0061] Step S402: receiving a message push request, wherein the message push request includes at least: a communication identifier of a device that initiates the request.

[0062] The above-mentioned message push request may be initiated by a device connected to the cloud, and is used to obtain the message to be pushed. Among them, the above-mentioned device may be a mobile terminal capable of displaying the message to be pushed, for example, it may include but is not limited to: a mobile phone, a tablet computer; the message to be pushed may be a 5G rich media message, but is not limited to this. The message push request may at least include: the communication identifier of the device initiating the request, and may also include: the message content and type of the message to be pushed. Among them, the communication identifier may be an identifier for the device initiating the request to communicate with the cloud, wherein the communication identifier may include but is not limited to: the communication number of the device initiating the request, the Internet Protocol (IP) address, the Media Access Control (MAC) address and the certificate, wherein the communication number may be the mobile phone number of the device.

[0063] In an optional embodiment, when a user wants to view the content of a message to be pushed, the user can send a message push request to the cloud through the device, and the cloud can receive the message push request sent by the device. It should be noted that the message push request at least includes: the communication identifier of the device that initiates the request. For example, when a user wants to view the content of a message to be pushed, the user can send a message push request to the cloud through a mobile phone, and the cloud can receive the message push request sent by the mobile phone. At this time, the communication identifier of the device can be a mobile phone number.

[0064] Step S404: Determine a layout style that matches the content of the message to be pushed based on the communication identifier.

[0065] The above layout style can be the display size and display position of the message content to be pushed on the screen of the device end, for example, it can be the left margin, top margin, length and width of the message content to be pushed relative to the screen, but not limited to this. The above message content to be pushed can be the message content that the message pusher wants to push to the pushed party to view in advance, or it can be the message content that the pushed party actively wants to view, which can include but is not limited to: text, pictures, audio, video, tables, links.

[0066] In an optional embodiment, after the cloud obtains the communication identifier, it can determine the layout style that matches the content of the message to be pushed based on a pre-built correspondence table between the communication identifier and the layout style.

[0067] In another optional embodiment, after the cloud obtains the communication identifier of the device end, it can first determine the device end corresponding to the communication identifier based on a preset mapping relationship, and secondly, based on a pre-built screen database, the screen database stores the matching relationship between different device ends and different screen information, and query the screen information corresponding to the device end from the screen database, and can also obtain the message content corresponding to the message push request as the message content to be pushed. Then, in order to ensure that the cloud can determine the layout style, the cloud can pre-build a database for storing the matching relationship between different screen information, different message content and different layout styles, that is, obtain a preset template library, so that when the cloud recognizes the screen information of the device end, it can query the layout style that matches both the screen information and the message content to be pushed from the preset template library.

[0068] In another optional embodiment, the number of communication identifiers of the device end is usually large, and the screen information of the device end of the same type is the same. Therefore, in order to simplify the construction cost of the database in the above embodiment, the cloud can pre-build a screen database for storing the matching relationship between different device types and different screen information, so that when the cloud obtains the communication identifier of the device end that initiates the request, it can first obtain the device end corresponding to the communication identifier from the external system (such as a communication operator), and then the cloud can query the screen information corresponding to the device end from the screen database, and can also obtain the message content corresponding to the message push request as the message content to be pushed. Among them, the device type can be a device model used to identify the device end.

[0069] In another optional embodiment, since the amount of screen information on different device ends is large, while the number of screen ratios (i.e., the aspect ratio of the screen) on the device ends is small, for example, 16:9, 18:9, 21:9, etc., therefore, in order to simplify the construction cost of the preset template library in the above embodiment, the cloud can pre-build a database for storing the matching relationship between different screen ratios and different layout styles, so that when the cloud recognizes the screen information on the device end, it can first calculate the ratio of the screen length to the screen width in the screen information to obtain the screen ratio, and can query the layout style that matches both the screen ratio and the message content to be pushed from the database.

[0070] For example, taking the message content to be pushed as two pictures as an example, when the screen ratio is 4:1, or the screen ratio is 3:1, or the screen ratio is 3:2, the layout styles matching different screen ratios can be determined, that is, the left margin, top margin, length, and width of the message content to be pushed relative to the screen can be determined. At this time, the cloud can determine the layout style that can display the message content to be pushed with a better display effect based on the screen information of the device side. For example, the left margin, top margin, length, and width of the message content to be pushed relative to the screen can be determined.

[0071] In another optional embodiment, after the cloud identifies the screen information of the device side, it can also dynamically adjust the pre-set layout style (i.e., the preset layout style) in real time based on the identified screen information, and then a layout style that can display the message content to be pushed with a better display effect on the screen can be obtained. For example, the cloud can adjust the preset layout style proportionally in real time based on the identified screen size, so a layout style that can display the message content to be pushed with a better display effect on the screen can be obtained, but it is not limited to this.

[0072] Step S406: Push the message content to be pushed and the layout style to the device side based on the communication identifier, where the message content to be pushed is rendered on the screen of the device side according to the layout style.

[0073] In an optional embodiment, after the cloud determines the message content to be pushed and the layout style, it can push the message content to be pushed and the layout style to the device side based on the communication identifier. After receiving the message content to be pushed and the layout style, the device side can render the message content to be pushed based on the layout style and display it on the screen of the device side. For example, after the cloud determines the message content to be pushed and the layout style, it can generate the layout style into an HTML template, and then send the HTML template and the message content to be pushed to the device side. The device side can render the message content to be pushed on the screen based on the HTML template.

[0074] For example, take the case where the message content to be pushed is a dual picture as an example. When the user wants to view the message content of the dual picture, first, the user can send a message push request to the cloud through the mobile phone, wherein the message push request at least includes the mobile phone number of the user's mobile phone. Secondly, after receiving the message push request, the cloud can determine the screen information corresponding to the mobile phone number from the screen database through the mobile phone number in the message push request, and can also obtain the dual picture corresponding to the message push request as the message content to be pushed. Then the cloud can determine the layout style that matches the screen size and the dual picture message from the preset template library. For example, the left margin, top margin, length and width (i.e., layout style) of the dual picture message relative to the screen can be determined. Finally, after the cloud determines the message content and layout style of the dual picture, the message content and layout style of the dual picture can be pushed to the mobile phone based on the communication identifier. After the mobile phone receives the message content and layout style to be pushed, it can render the dual picture based on the layout style and display it on the mobile phone screen.

[0075] In the embodiment of the present application, a message push request is received, wherein the message push request at least includes: a communication identifier of the device side that initiates the request; based on the communication identifier, determining a layout style that matches the message content to be pushed; based on the communication identifier, pushing the message content and layout style to be pushed to the device side, wherein the message content to be pushed is rendered on the screen of the device side according to the layout style. It is easy to notice that the cloud can identify the screen information of the device side through the communication identifier sent by the device side, and can determine a layout style that matches the message content to be pushed based on the screen information of the device side, and then the cloud can send the layout style to the device side at the same time as sending the message content to be pushed, so that the display result rendered on the device side matches the screen information of the device side, and the purpose of automatically adapting the 5G rich media message to the screen information of the device side is achieved, thereby achieving the technical effect of improving the rendering effect of the 5G rich media message on the device side, and then solving the technical problem of poor rendering effect of the 5G rich media message on the device side in the related technology.

[0076] In the above embodiment of the present application, based on the communication identifier, determining the layout style that matches the message content to be pushed includes: querying based on the communication identifier to determine the device information that matches the communication identifier; based on the device information, determining the screen information that matches the device end from the screen database, wherein the screen database is used to record the matching relationship between the device end of different device information and the screen information; based on the screen information, determining the layout style that matches the message content to be pushed.

[0077] The above-mentioned screen database can be a database set in advance in the cloud, which stores the matching relationships between different device terminals with device information and different screen information. The above-mentioned screen information can include, but is not limited to: screen size and resolution. Figure 5 It is a schematic diagram of an optional method for establishing a screen database according to Embodiment 1 of the present application. As Figure 5 shown, first, a device model screen library (i.e., the above-mentioned screen database) can be created. Secondly, the mainstream device models on the market and their corresponding screen sizes can be obtained. Then, the screen sizes can be classified, and the types with the same screen size can be divided into one category, and N different types of screen sizes can be obtained. N represents the number of different types of screen sizes, and the specific number is not limited in this embodiment and can be set according to actual needs. As Figure 5 shown, it can be known that the first type of screen size is the A-type screen size, the second screen size type is the B-type screen size, and the Nth screen size type is the N-type screen size. Among them, the aspect ratio of the A-type screen size can be 4:1, the aspect ratio of the B-type screen size can be 3:1, and the aspect ratio of the N-type screen size can be 3:2, but not limited thereto. Finally, multiple different types of screen sizes can be summarized, that is, the screen database can be obtained. It should be noted that by classifying according to the screen size, clustering can be achieved according to the aspect ratio, and only the layout customization needs to be performed on the aspect ratio.

[0078] In an optional embodiment, after the cloud receives the communication identifier of the device terminal that sends the request, first, the communication identifier can be queried through the mapping relationship between the communication identifier and the device information established in advance in the cloud to obtain the device information corresponding to the communication identifier. Secondly, based on the device information, the screen information matching the device terminal can be determined from the screen database. Finally, the layout style matching the message content to be pushed can be determined based on the screen information. For example, after determining that the screen information is the screen size type of 3:2, the layout style matching the message content to be pushed can be determined based on this screen information.

[0079] In the above embodiments of the present application, determining the layout style matching the message content to be pushed based on the screen information includes at least one of the following: obtaining multiple layout styles matching the screen information and determining the layout style matching the message content to be pushed from the multiple layout styles, where different message contents need to match different layout styles; obtaining the preset layout style matching the message content to be pushed and dynamically adjusting the preset layout style based on the proportional relationship between the screen information and the preset screen information corresponding to different preset layout styles to obtain the layout style matching the message content to be pushed.

[0080] The above-mentioned preset layout style can be a layout style set in advance in the cloud, which can enable different messages to be pushed to be displayed on different screens according to the preset layout style. The above-mentioned preset screen information can be the screen information corresponding to the preset layout style. For example, still taking the double-picture message as an example for illustration, Figure 6 is a schematic diagram of an optional multiple layout styles according to Embodiment 1 of the present application. As Figure 6 shown, among the three different types of screen information, the screen length of the A-type screen is the longest, the screen length of the B-type screen is the shortest, and the screen length of the C-type screen is in the middle. Among them, the horizontal line segment represents the length of the screen, and the vertical line segment represents the width of the screen. In addition, from Figure 6 it can be seen that the layout style matching the A-type screen size can be to display two pictures of the same size side by side, that is, Picture 1 and Picture 2 are displayed side by side horizontally on the screen. The layout style matching the B-type screen size can be to display two pictures of the same size vertically, that is, Picture 1 and Picture 2 are displayed side by side vertically on the screen. The layout style matching the C-type screen size can be to display pictures of different sizes side by side, that is, Picture 1 and Picture 2 are displayed horizontally on the screen. It should be noted that the present application takes the Figure 6 layout style of double pictures shown as an example for illustration, but it is not limited to this.

[0081] In an optional embodiment, after obtaining the screen information, the cloud can first establish multiple layout styles matching the screen information, such as multiple layout styles matching the screen size, or it can obtain the established multiple layout styles. Secondly, it can determine the layout style matching the content of the message to be pushed from the multiple layout styles. For example, when the cloud determines that the screen information is the A-type screen size, it can first determine the multiple layout styles corresponding to the A-type screen size. For example, it can first determine the display size and display position of multiple different messages to be pushed on the screen of the device. Secondly, based on the content of the message to be pushed, it can determine the layout style matching the content of the message to be pushed from the multiple layout styles. For example, when the content of the message to be pushed is multiple pictures, it can determine, based on the multiple pictures, the layout style from the multiple layout styles that can enable the multiple pictures to be displayed on the screen with a better display effect, such as the left margin, top margin, length, and width of the multiple pictures relative to the screen. Among them, the layout styles matching different message contents are different.

[0082] In another optional embodiment, after obtaining the screen information, the cloud can also obtain at least one layout style matching the content of the message to be pushed, and then can dynamically adjust the preset layout style based on the proportional relationship between the screen information and the preset screen information corresponding to different preset layout styles, that is, it can obtain the layout style that can enable the content of the message to be pushed to be displayed on the screen with a better display effect.

[0083] In the above embodiments of the present application, obtaining multiple layout styles that match the screen information includes: obtaining the screen type corresponding to the screen information; determining the layout styles in the layout style set that match the screen type corresponding to the screen information as the multiple layout styles, where different layout styles included in the layout style set need to match different screen types.

[0084] The above layout style set can be set in advance in the cloud, which is a set of layout styles corresponding to different screen types. Among them, the same screen type can correspond to multiple different layout styles, and multiple different layout styles can correspond to multiple different types of message contents.

[0085] In an alternative embodiment, as Figure 5 shown, first, the obtained screen information can be classified to obtain different screen types corresponding to different screen information, such as type A, type B, and type N. Secondly, the layout styles that match the screen type can be determined from the layout style set to obtain multiple layout styles. It should be noted that the number of layout styles set for the screen type is less than the number of layout styles set for the screen information, so the cost can be reduced.

[0086] It should be noted that because different layout styles are determined based on different message contents, and the left margin, top margin, length, and width of different layout styles relative to the screen are all different. In order to enable the message content to be pushed to be displayed on the screen with a better display effect, different screen types can match different layout styles, and different layout styles also match different message contents.

[0087] In the above embodiments of the present application, the method further includes: obtaining the screen information and multiple message contents of multiple device terminals; clustering the screen information of multiple device terminals to obtain multiple screen types; generating a layout style set that matches the multiple screen types and multiple message contents.

[0088] In an alternative embodiment, the cloud can obtain the screen information and multiple message contents of multiple device terminals in advance. The multiple device terminals here can be device terminals that communicate with the cloud or device terminals registered in the cloud. Secondly, the screen information of multiple device terminals can be clustered according to the aspect ratio (but not limited to this) to obtain multiple screen types, and then a matching layout style can be generated for different screen types and different message contents respectively, so as to obtain the above layout style set.

[0089] In the above embodiments of the present application, the screen information at least includes: the screen length and the screen width, and the preset screen information at least includes: the preset screen length and the preset screen width. Among them, based on the proportional relationship between the screen information and the preset screen information corresponding to the preset layout style, dynamically adjusting the preset layout style to obtain a layout style matching the message content to be pushed includes: obtaining the ratio of the screen length to the preset screen length to obtain a first ratio, and obtaining the ratio of the screen width to the preset screen width to obtain a second ratio; dynamically adjusting the preset layout style based on the first ratio and the second ratio to obtain a layout style.

[0090] In an alternative embodiment, first, the ratio of the screen length to the preset screen length can be obtained to obtain a first ratio, and at the same time, the ratio of the screen width to the preset screen width can be obtained to obtain a second ratio. Second, the length and width of the preset layout style can be dynamically adjusted based on the first ratio and the second ratio. That is, the top margin and length in the preset layout style are dynamically adjusted based on the first ratio. For example, directly obtaining the product of the first ratio and the top margin to obtain the top margin in this layout style, and obtaining the product of the first ratio and the length to obtain the length in this layout style; the left margin and width in the preset layout style are dynamically adjusted based on the second ratio. For example, directly obtaining the product of the second ratio and the left margin to obtain the left margin in this layout style, and obtaining the product of the second ratio and the width to obtain the width in this layout style. By scaling the screen length and the screen width respectively, it can be ensured that the layout style obtained in the above manner makes full use of the screen space of the device side. However, due to the separate scaling, the ratio of the length and width in the obtained layout style is different from the ratio of the length and width in the preset layout style, resulting in an over-stretching situation.

[0091] In the above embodiments of the present application, the screen information at least includes: the screen length and the screen width, and the preset screen information includes: the preset screen length and the preset screen width. Among them, based on the proportional relationship between the screen information and the preset screen information corresponding to the preset layout style, dynamically adjusting the preset layout style to obtain a layout style matching the message content to be pushed includes: obtaining the ratio of the screen width to the preset screen width to obtain a second ratio, and obtaining the ratio of the screen length to the screen width to obtain a third ratio; dynamically adjusting the preset layout style based on the second ratio and the third ratio to obtain a layout style matching the message content to be pushed.

[0092] In an alternative embodiment, first, the ratio of the screen width to the preset screen width can be obtained to get a second ratio, and at the same time, the ratio of the screen length to the screen width can be obtained to get a third ratio. Second, the screen length and screen width of the preset layout style can be dynamically adjusted based on the second ratio and the third ratio. That is, the left margin and width in the preset layout style are dynamically adjusted based on the second ratio. For example, the product of the second ratio and the left margin is directly obtained to get the left margin in this layout style, and the product of the second ratio and the width is obtained to get the width in this layout style. Then, based on the third ratio, the left margin and width in this layout style, the top margin and length in this layout style are obtained. For example, the product of the third ratio and the left margin is directly obtained to get the top margin in this layout style, and the product of the third ratio and the width is obtained to get the length in this layout style. By fixing the screen ratio, it can be ensured that the aspect ratio and the top-left margin ratio in the layout style obtained in the above manner are fixed, avoiding the situation of excessive stretching. However, when scaling according to the width under the condition of locking the aspect ratio, it may cause waste of space in the screen length.

[0093] In the above embodiments of the present application, based on the communication identifier, the message content and layout style to be pushed are pushed to the device side, including: generating a layout template of HyperText Markup Language based on the layout style; sending the HyperText Markup Language information and the message content to be pushed to the device side by means of a short message based on the communication identifier, wherein the message content to be pushed is filled into the HyperText Markup Language information by the device side and then rendered on the screen of the device side.

[0094] In an alternative embodiment, when the cloud obtains the message content and layout style to be pushed, first, the layout style can be generated into a layout template of HTML (i.e., HyperText Markup Language). Second, based on the communication identifier, the layout template of HTML and the message content to be pushed are sent to the device side by means of a short message. After receiving the layout template of HTML and the message content to be pushed, the device side can fill the message content to be pushed into the layout template based on the layout template of HTML and then render it on the display screen of the device side, so that the message content to be pushed can be displayed on the screen with a better display effect, and further the purpose that the message content to be pushed can adapt to the screen size can be achieved.

[0095] The message pushing method provided by the embodiments of the present application mainly includes the following content:

[0096] First, maintain a database that maps device models (such as mobile phone models) and screen sizes in the cloud system, and classify these screen sizes according to the aspect ratio to obtain N types of screen ratio types, as Figure 5 shown.

[0097] Design a 5G message content template, and there is a specific implementation for the styles of different screen size template types (i.e., there is a verified and optimal implementation). If the goal of the device side is to display two pictures, then when designing, the display layout and size on different types of screen sizes are different. For example, Figure 6 As shown, for type A, it is two tiled pictures, for type B, it is vertical, and for type C, one picture is large and the other is small. For convenience, this two-picture SMS template can be called the "dual-picture template", and the following introduction will use the "dual-picture template" instead. The elements inside, such as pictures, videos, and texts, can be called views. For different types of device screens (such as mobile phone screens), the layout is determined, and the left margin, top margin, length, and width of each view relative to the screen will also be determined, and these are all described by ratios. It should be noted that the specific content of the 5G message is fixed and cannot be changed by users.

[0098] The device side applies for the "dual-picture template" from the cloud and specifies the specific picture information of the pictures.

[0099] In the cloud, different communication identifiers (such as mobile phone numbers) and the device information corresponding to different communication identifiers (such as mobile phone model information) can be maintained.

[0100] Figure 7 It is a flowchart of an optional method for the device side to obtain push messages according to Embodiment 1 of the present application. As Figure 7 shown, the method includes the following steps:

[0101] Step S71, the device side initiates a sending request for the message to be pushed;

[0102] Step S72, after the cloud receives the sending request, it obtains the device information based on the request;

[0103] Step S73, the cloud determines the screen size type corresponding to the device information based on the device information;

[0104] Step S74, the cloud can obtain the layout description of the message content to be pushed under this screen size;

[0105] Step S75, the cloud combines the actual size of the screen to obtain the HTML information of the layout description on this device side;

[0106] Step S76, the cloud sends the HTML information and the message content to be pushed to the device side, where the layout styles of each device side are different;

[0107] Step S77, after the device side receives the HTML information and the message content to be pushed, it renders the message content to be pushed based on the HTML information and displays it on the screen.

[0108] Figure 8 It is a flowchart of another alternative method for the device side to obtain push messages according to Embodiment 1 of the present application. As Figure 8 shown, the method includes the following steps:

[0109] Step S81, the device side initiates a sending request for the message to be pushed;

[0110] Step S82, after the cloud receives the sending request, it obtains device information based on the request;

[0111] Step S83, the cloud determines the screen size of the device side based on the device information;

[0112] Step S84, in combination with the screen size, the cloud calculates in real time the layout style of the message content to be pushed according to the pre-defined rules, and generates the layout style into HTML information;

[0113] Step S85, the cloud sends the HTML information and the message content to be pushed to the device side, where the layout styles of each device side are different;

[0114] Step S86, after the device side receives the HTML information and the message content to be pushed, it renders the message content to be pushed based on the HTML information and displays it on the screen.

[0115] The message push method proposed in the embodiment of the present application maintains the relationship between the mobile phone model and the screen size, and classifies according to the aspect ratio of the screen size; the cloud provides type templates, and in different screen size types, the current type template has a unique layout method, and the left margin, top margin, height, and width of the view in the layout are expressed in a proportional manner; when sending, based on the target communication identifier (such as a mobile phone number), the device information of the device side (such as mobile phone model information) is obtained through an external system; the screen size and the "screen size aspect ratio classification" to which it belongs are obtained by querying the relationship between the mobile phone model and the screen size through the mobile phone model information; when the user sends, the layout method and the left margin, top margin, height, and width ratio of the template are obtained based on the "screen size aspect ratio classification" to which it belongs; based on the screen size of the mobile phone screen targeted for sending a short message, the layout and size information of the short message content to be sent are calculated to form a 5G message expressed in HTML; the HTML 5G message is sent to the device side (such as a mobile phone). Because the screens of different device sides have been designed with better layouts before, the layout and size received by each mobile phone are different and have been optimized, so the effect that meets the conditions can be achieved on different mobile phones; this solution also includes adjusting the layout and size of the view in proportion based on the size of the device side in real time when sending rich media messages.

[0116] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Moreover, the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entrances are provided for users to choose to authorize or reject.

[0117] It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that this application is not limited by the described action sequence, because according to this application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0118] Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disc), and includes several instructions for causing a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of this application.

[0119] Embodiment 2

[0120] According to an embodiment of this application, a message push method applied to the device side is also provided. Figure 9 is a flowchart of a message push method according to Embodiment 2 of this application, as Figure 9 shown, and the method includes the following steps:

[0121] Step S902, in response to an input instruction acting on the interaction interface of the device side, obtain the communication identifier of the device side;

[0122] Step S904, in response to a message push instruction acting on the interaction interface, display the display result of the message content to be pushed on the interaction interface, where the display result is the result obtained by rendering the message content to be pushed on the screen of the device side according to the layout style matching the message content to be pushed, and the message content to be pushed and the layout style are pushed by the cloud to the device side based on the communication identifier, and the layout style is determined by the cloud based on the communication identifier.

[0123] Figure 10It is a schematic diagram of an optional interaction interface according to Embodiment 2 of the present application, as Figure 10 shown. The interaction interface includes: a display area, an input button, and a push button. Among them, when a user hopes to view the content of the message to be pushed, the user can perform an operation on the input button on the interaction interface in the device terminal. For example, when the user can perform an operation on the input button on the interaction interface of a mobile phone, a corresponding input instruction can be generated based on the user's operation. The interaction interface obtains the communication identifier of the device terminal in response to the generated input instruction, and can display the communication identifier of the device terminal in the display area. Secondly, the user can perform an operation on the push button in the interaction interface, and a corresponding message push instruction can be generated based on the user's operation. The interaction interface can display the display result of the content of the message to be pushed in the display area in response to the generated message push instruction. Among them, the display result is the result obtained by rendering the content of the message to be pushed on the screen of the device terminal according to the layout style matching the content of the message to be pushed. The content of the message to be pushed and the layout style are pushed to the device terminal by the cloud, and the layout style is determined by the cloud based on the communication identifier.

[0124] Embodiment 3

[0125] According to an embodiment of the present application, a message push method is also provided. Figure 11 It is a flowchart of a message push method according to Embodiment 3 of the present application, as Figure 11 shown. The method includes the following steps:

[0126] Step S1102, the device terminal sends a message push request to the cloud, where the message push request carries the communication identifier of the device terminal;

[0127] Step S1104, the device terminal receives the content of the message to be pushed and the layout style matching the content of the message to be pushed pushed by the cloud based on the communication identifier, where the layout style is determined by the cloud based on the communication identifier;

[0128] Step S1106, the device terminal renders and displays the content of the message to be pushed on the screen of the device terminal based on the layout style.

[0129] In an optional embodiment, when a user hopes to view the content of the message to be pushed, the user can first send a message push request to the cloud through the device terminal. After receiving the message push request, the cloud can first determine the layout style matching the content of the message to be pushed based on the communication identifier in the message push request, and finally the cloud can push the content of the message to be pushed and the layout style matching the content of the message to be pushed to the device terminal. After receiving the pushed content of the message to be pushed and the layout style matching the content of the message to be pushed, the device terminal can render the content of the message to be pushed based on the layout style and display it on the display screen.

[0130] Example 4

[0131] According to an embodiment of the present application, a message push method is also provided, which is applied in the cloud. Figure 12 is a flowchart of a message push method according to Example 4 of the present application, such as Figure 12 As shown, the method comprises the following steps:

[0132] Step S1202, obtaining a message push request by calling a first interface, wherein the first interface includes a first parameter, a parameter value of the first parameter includes a message push request, and the message push request includes at least: a communication identifier of a device end initiating the request;

[0133] Step S1204, determining a layout style that matches the content of the message to be pushed based on the communication identifier, wherein the layout style is used to represent the display result of the content of the message to be pushed on the screen of the device end;

[0134] Step S1206, by calling the second interface based on the communication identifier, push the message content and layout style to be pushed to the device end, wherein the second interface includes a second parameter, the parameter value of the second parameter includes the message content and layout style to be pushed, and the message content to be pushed is rendered on the screen of the device end according to the layout style.

[0135] The first interface is used to obtain a message push request from the device side. The second interface is used to output the message content and layout style to be pushed to the device side.

[0136] In an optional embodiment, when a user wants to view the content of a message to be pushed, the user can first send a message push request to the cloud through the device. After the cloud obtains the message push request by calling the first interface, it can determine the layout style that matches the content of the message to be pushed based on the communication identifier in the message push request. Then, the cloud can call the second interface to push the content and layout style of the message to be pushed to the device based on the communication identifier.

[0137] It should be noted that the first interface includes a first parameter, the parameter value of the first parameter includes a message push request, and the message push request includes at least: a communication identifier of the device that initiates the request. The layout style is used to characterize the display result of the message content to be pushed on the screen of the device. The second interface includes a second parameter, the parameter value of the second parameter includes the message content to be pushed and the layout style, and the message content to be pushed is rendered on the screen of the device according to the layout style.

[0138] Example 5

[0139] According to an embodiment of the present application, a message pushing device for implementing the above-mentioned message pushing method is also provided.Figure 13 Schematic diagram of a message push device according to Embodiment 5 of the present application, which is applied to the cloud. Figure 13 As shown, the device includes: a request receiving module 1302 , a determining module 1304 and a pushing module 1306 .

[0140] Among them, the request receiving module is used to receive a message push request, wherein the message push request includes at least: a communication identifier of the device side that initiates the request; based on the communication identifier, determining a layout style that matches the message content to be pushed; based on the communication identifier, pushing the message content and layout style to be pushed to the device side, wherein the message content to be pushed is rendered on the screen of the device side according to the layout style.

[0141] In the above embodiment of the present application, the determination module includes: a first determination unit, a second determination unit and a third determination unit.

[0142] Among them, the first determination unit is used to query based on the communication identifier to determine the device information that matches the communication identifier; the second determination unit is used to determine the screen information that matches the device end from the screen database based on the device information, wherein the screen database is used to record the matching relationship between the device end and the screen information of different device information; the third determination unit is used to determine the layout style that matches the message content to be pushed based on the screen information.

[0143] In the above embodiment of the present application, the third determining unit includes at least one of the following: a first obtaining subunit and a second obtaining subunit.

[0144] Among them, the first acquisition subunit is used to acquire multiple layout styles matching the screen information, and determine the layout style matching the message content to be pushed from the multiple layout styles, wherein different message contents need to match different layout styles; the second acquisition subunit is used to acquire a preset layout style matching the message content to be pushed, and based on the proportional relationship between the screen information and the preset screen information corresponding to different preset layout styles, dynamically adjust the preset layout style to obtain a layout style matching the message content to be pushed.

[0145] In the above embodiment of the present application, the first acquisition subunit is also used to: obtain the screen type corresponding to the screen information; determine the layout style in the layout style set that matches the screen type corresponding to the screen information, which is multiple layout styles, wherein different layout styles contained in the layout style set need to match different screen types.

[0146] In the above embodiment of the present application, the first acquisition subunit is also used to: obtain screen information of multiple device ends and multiple message contents; cluster the screen information of multiple device ends to obtain multiple screen types; and generate a layout style set matching the multiple screen types and multiple message contents.

[0147] In the above embodiments of the present application, the screen information at least includes: screen length and screen width, and the preset screen information at least includes: preset screen length and preset screen width. Among them, the second acquisition subunit is further configured to: acquire the ratio of the screen length to the preset screen length to obtain a first ratio, and acquire the ratio of the screen width to the preset screen width to obtain a second ratio; dynamically adjust the preset layout style based on the first ratio and the second ratio to obtain a layout style.

[0148] In the above embodiments of the present application, the screen information at least includes: screen length and screen width, and the preset screen information includes: preset screen length and preset screen width. Among them, the second acquisition subunit is further configured to: acquire the ratio of the screen width to the preset screen width to obtain a second ratio, and acquire the ratio of the screen length to the screen width to obtain a third ratio; dynamically adjust the preset layout style based on the second ratio and the third ratio to obtain a layout style that matches the message content to be pushed.

[0149] In the above embodiments of the present application, the push module includes: a generation unit and a sending unit.

[0150] Among them, the generation unit is configured to generate hypertext markup language information based on the layout style; the sending unit is configured to send the hypertext markup language information and the message content to be pushed to the device side by means of a short message based on the communication identifier, wherein the message content to be pushed is rendered on the screen of the device side according to the hypertext markup language information.

[0151] It should be noted here that the above receiving module 1302, recognition module 1304, determination module 1306, and push module 1308 correspond to steps S402 to S408 in Embodiment 1. The instances and application scenarios implemented by the four modules and the corresponding steps are the same, but are not limited to the content disclosed in the above Embodiment 1. It should be noted that the above modules or units may be hardware components or software components stored in a memory and processed by one or more processors, and the above modules may also be part of a device and may run in the server 16 provided in Embodiment 1.

[0152] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0153] Embodiment 6

[0154] According to an embodiment of the present application, there is also provided a message push device for implementing the above message push method. Figure 14 It is a schematic diagram of a message push device according to Embodiment 6 of the present application and is applied to the device side. As Figure 4As shown in the figure, the device includes: an acquisition module 1402 and a display module 1404.

[0155] Among them, the acquisition module is used to respond to an input instruction acting on the interaction interface of the device side and acquire the communication identifier of the device side; the display module is used to respond to a message push instruction acting on the interaction interface and display the display result of the message content to be pushed on the interaction interface, where the display result is obtained by rendering the message content to be pushed on the screen of the device side according to the layout style matching the message content to be pushed, and the message content to be pushed and the layout style are pushed to the device side by the cloud, and the layout style is determined by the cloud based on the communication identifier.

[0156] It should be noted here that the above acquisition module 1402 and display module 1404 correspond to steps S902 to S904 in Embodiment 2. The instances and application scenarios implemented by the two modules and the corresponding steps are the same, but are not limited to the content disclosed in the above Embodiment 1. It should be noted that the above modules or units can be hardware components or software components stored in the memory and processed by one or more processors, and the above modules can also be part of the device and can run in the server 16 provided in Embodiment 1.

[0157] It should be noted that the preferred implementation schemes involved in the above embodiments of the present application are the same as the schemes, application scenarios, and implementation processes provided in Embodiment 1, but are not limited to the schemes provided in Embodiment 1.

[0158] Embodiment 7

[0159] According to an embodiment of the present application, there is also provided a message push device for implementing the above message push method. Figure 15 It is a schematic diagram of a message push device according to Embodiment 7 of the present application. As Figure 15 shown in the figure, the device includes: a sending module 1502, a receiving module 1504, and a display module 1506.

[0160] Among them, the sending module is used to send a message push request from the device side to the cloud, where the message push request carries the communication identifier of the device side; the receiving module is used to receive, by the device side, the message content to be pushed and the layout style matching the message content to be pushed pushed by the cloud, where the layout style is determined by the cloud based on the communication identifier; the display module is used to render and display the message content to be pushed on the screen of the device side by the device side based on the layout style.

[0161] It should be noted that the sending module 1502, the receiving module 1504 and the display module 1506 correspond to steps S1102 to S1106 in Example 3, and the three modules and the corresponding steps implement the same examples and application scenarios, but are not limited to the contents disclosed in the above-mentioned Example 1. It should be noted that the above-mentioned modules or units may be hardware components or software components stored in a memory and processed by one or more processors, and the above-mentioned modules may also be part of the device and run in the server 16 provided in Example 1.

[0162] It should be noted that the preferred implementation scheme involved in the above embodiments of the present application is the same as the scheme provided in Example 1, as well as the application scenario and implementation process, but is not limited to the scheme provided in Example 1.

[0163] Example 8

[0164] According to an embodiment of the present application, a message pushing device for implementing the above-mentioned message pushing method is also provided. Figure 16 Schematic diagram of a message push device according to Embodiment 8 of the present application, which is applied to the cloud. Figure 16 As shown, the device includes: an acquisition module 1602 , a determination module 1604 and a push module 1606 .

[0165] Among them, the acquisition module is used to obtain a message push request by calling a first interface, wherein the first interface includes a first parameter, the parameter value of the first parameter includes the message push request, and the message push request at least includes: the communication identifier of the device end that initiates the request; the determination module is used to determine the layout style that matches the message content to be pushed based on the communication identifier; the push module is used to push the message content and layout style to be pushed to the device end based on the communication identifier by calling a second interface, wherein the second interface includes a second parameter, the parameter value of the second parameter includes the message content and layout style to be pushed, and the message content to be pushed is rendered on the screen of the device end according to the layout style.

[0166] It should be noted that the acquisition module 1602, the determination module 1604 and the push module 1606 correspond to steps S1202 to S1206 in Embodiment 4, and the three modules and the corresponding steps implement the same examples and application scenarios, but are not limited to the contents disclosed in Embodiment 1. It should be noted that the modules or units may be hardware components or software components stored in a memory and processed by one or more processors, and the modules may also be part of a device and run in the server 16 provided in Embodiment 1.

[0167] It should be noted that the preferred implementation scheme involved in the above embodiments of the present application is the same as the scheme provided in Example 1, as well as the application scenario and implementation process, but is not limited to the scheme provided in Example 1.

[0168] Example 9

[0169] According to another aspect of the embodiments of the present application, a message push system is also provided. Figure 17 is a schematic diagram of a message push system according to Example 9 of the present application, such as Figure 17 As shown, the system includes: a device end 1702 and a server 1704.

[0170] Among them, the device side is used to send a message push request, wherein the message push request includes at least: the communication identifier of the device side that initiates the request; the cloud is connected to the device side, and is used to determine the layout style that matches the message content to be pushed based on the communication identifier, and push the message content and layout style to be pushed to the device side based on the communication identifier, wherein the layout style is used to represent the display result of the message content to be pushed on the screen of the device side; the device side is also used to render the message content to be pushed on the screen of the device side according to the layout style.

[0171] Example 10

[0172] The embodiment of the present application may provide a computer terminal, which may be any computer terminal device in a computer terminal group. Optionally, in this embodiment, the computer terminal may also be replaced by a terminal device such as a mobile terminal.

[0173] Optionally, in this embodiment, the computer terminal may be located in at least one network device among a plurality of network devices of the computer network.

[0174] In this embodiment, the above-mentioned computer terminal can execute the program code of the following steps in the message push method: receiving a message push request, wherein the message push request includes at least: the communication identifier of the device end that initiates the request; based on the communication identifier, determining a layout style that matches the message content to be pushed; based on the communication identifier, pushing the message content and layout style to be pushed to the device end, wherein the message content to be pushed is rendered on the screen of the device end according to the layout style.

[0175] Optionally, Figure 18 is a structural block diagram of a computer terminal according to an embodiment of the present application. Figure 18 As shown, the computer terminal A may include: one or more (only one is shown in the figure) processors 1802, a memory 1804, a storage controller, and a peripheral interface, wherein the peripheral interface is connected to a radio frequency module, an audio module, and a display.

[0176] Among them, the memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the message push method and device in the embodiment of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, realizing the above-mentioned message push method. The memory may include a high-speed random access memory, and may also include a 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 may further include a memory remotely arranged relative to the processor, and these remote memories may be connected to the terminal A via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0177] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: receive a message push request, wherein the message push request includes at least: a communication identifier of the device side that initiates the request; based on the communication identifier, determine a layout style that matches the message content to be pushed; based on the communication identifier, push the message content and layout style to be pushed to the device side, wherein the message content to be pushed is rendered on the screen of the device side according to the layout style.

[0178] Optionally, the processor may also execute the program code of the following steps: query based on the communication identifier to determine the device information that matches the communication identifier; based on the device information, determine the screen information that matches the device end from the screen database, wherein the screen database is used to record the matching relationship between the device end and the screen information of different device information; based on the screen information, determine the layout style that matches the content of the message to be pushed.

[0179] Optionally, the processor may also execute program code for at least one of the following steps: obtaining multiple layout styles that match the screen information, and determining a layout style that matches the message content to be pushed from the multiple layout styles, wherein different message contents need to match different layout styles; obtaining a preset layout style that matches the message content to be pushed, and dynamically adjusting the preset layout style based on a proportional relationship between the screen information and the preset screen information corresponding to different preset layout styles, to obtain a layout style that matches the message content to be pushed.

[0180] Optionally, the processor may also execute program code of the following steps: obtaining the screen type corresponding to the screen information; determining a layout style in a layout style set that matches the screen type corresponding to the screen information, which is a plurality of layout styles, wherein different layout styles contained in the layout style set need to match different screen types.

[0181] Optionally, the processor may also execute program code for the following steps: obtaining screen information of multiple device ends and multiple message contents; clustering the screen information of multiple device ends to obtain multiple screen types; and generating a layout style set matching the multiple screen types and multiple message contents.

[0182] Optionally, the processor may also execute the following program code: obtaining the ratio of the screen length to the preset screen length to obtain a first ratio, and obtaining the ratio of the screen width to the preset screen width to obtain a second ratio; dynamically adjusting the preset layout style based on the first ratio and the second ratio to obtain a layout style.

[0183] Optionally, the processor may also execute the following program code: obtaining the ratio of the screen width to the preset screen width to obtain a second ratio, and obtaining the ratio of the screen length to the screen width to obtain a third ratio; dynamically adjusting the preset layout style based on the second ratio and the third ratio to obtain a layout style that matches the content of the message to be pushed.

[0184] Optionally, the processor may also execute the following program code steps: based on the layout style, generate a hypertext markup language layout template; based on the communication identifier, send hypertext markup language information and the message content to be pushed to the device via SMS, wherein the message content to be pushed is filled into the hypertext markup language information by the device and then rendered on the screen of the device.

[0185] In an embodiment of the present application, a message push request is received, wherein the message push request includes at least: a communication identifier of a device that initiates the request; based on the communication identifier, identifying the screen information of the device, and obtaining the message content to be pushed; based on the identified screen information, determining a layout style that matches the message content to be pushed, wherein the layout style is used to characterize the display result of the message content to be pushed on the screen of the device; based on the communication identifier, pushing the message content to be pushed and the layout style to the device, wherein the message content to be pushed is rendered on the screen of the device according to the layout style. It is easy to notice that the cloud can identify the screen information of the device through the communication identifier sent by the device, and can determine the layout style that matches the message content to be pushed based on the screen information of the device. Then, when the cloud sends the message content to be pushed, it can send the layout style to the device at the same time, so that the display result rendered on the device matches the screen information of the device, thereby achieving the purpose of automatically adapting the 5G rich media message to the screen information of the device, thereby realizing the technical effect of improving the rendering effect of the 5G rich media message on the device, and then solving the technical problem of poor rendering effect of the 5G rich media message on the device in the related technology.

[0186] Those skilled in the art will appreciate that the structure shown in the figure is for illustration only, and the computer terminal may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (MID), a PAD, or other terminal devices. Figure 18 It does not limit the structure of the above electronic device. For example, the computer terminal A may also include Figure 18 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 18 Different configurations shown.

[0187] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0188] Embodiment 11

[0189] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the message push method provided in the first embodiment.

[0190] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0191] Optionally, in this embodiment, the storage medium is configured to store program code for performing the following steps: receiving a message push request, wherein the message push request includes at least: a communication identifier of the device side that initiates the request; based on the communication identifier, determining a layout style that matches the message content to be pushed; based on the communication identifier, pushing the message content and layout style to be pushed to the device side, wherein the message content to be pushed is rendered on the screen of the device side according to the layout style.

[0192] Optionally, in this embodiment, the storage medium is also configured to store program codes for executing the following steps: querying based on the communication identifier to determine device information that matches the communication identifier; based on the device information, determining screen information that matches the device end from a screen database, wherein the screen database is used to record the matching relationship between device ends of different device information and screen information; based on the screen information, determining a layout style that matches the content of the message to be pushed.

[0193] Optionally, in this embodiment, the storage medium is further configured to store program code for performing one of the following steps: obtaining a plurality of layout styles that match the screen information, and determining, from the plurality of layout styles, a layout style that matches the message content to be pushed, where different message contents need to match different layout styles; obtaining a preset layout style that matches the message content to be pushed, and dynamically adjusting the preset layout style based on the proportional relationship between the screen information and the preset screen information corresponding to different preset layout styles, to obtain a layout style that matches the message content to be pushed.

[0194] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: obtaining the screen type corresponding to the screen information; determining, from the layout style set, the layout styles that match the screen type corresponding to the screen information, as a plurality of layout styles, where different layout styles included in the layout style set need to match different screen types.

[0195] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: obtaining the screen information of multiple device terminals and multiple message contents; clustering the screen information of multiple device terminals to obtain multiple screen types; generating a layout style set that matches the multiple screen types and multiple message contents.

[0196] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: obtaining the ratio of the screen length to the preset screen length to obtain a first ratio, and obtaining the ratio of the screen width to the preset screen width to obtain a second ratio; dynamically adjusting the preset layout style based on the first ratio and the second ratio to obtain a layout style.

[0197] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: obtaining the ratio of the screen width to the preset screen width to obtain a second ratio, and obtaining the ratio of the screen length to the screen width to obtain a third ratio; dynamically adjusting the preset layout style based on the second ratio and the third ratio to obtain a layout style that matches the message content to be pushed.

[0198] Optionally, in this embodiment, the storage medium is further configured to store program code for performing the following steps: generating a layout template in HyperText Markup Language based on the layout style; sending the HyperText Markup Language information and the message content to be pushed to the device terminal by means of a short message based on the communication identifier, where the message content to be pushed is filled into the HyperText Markup Language information by the device terminal and then rendered on the screen of the device terminal.

[0199] The serial numbers of the embodiments of the present application above are only for description and do not represent the advantages or disadvantages of the embodiments.

[0200] In the above embodiments of the present application, the descriptions of the respective embodiments have their own focuses. For the parts not detailed in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

[0201] In the several embodiments provided by the present application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of units or modules can be in an electrical or other form.

[0202] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0203] In addition, the functional units in the various embodiments of the present application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.

[0204] If the above-mentioned integrated units are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of this 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 for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: USB flash drives, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), mobile hard disks, magnetic disks or optical disks and other various media that can store program codes.

[0205] The above are only the preferred embodiments of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A message pushing method, characterized in that, Applied to the cloud, the method includes: Receiving a message push request, where the message push request at least includes: the communication identifier of the device end that initiates the request; Based on the communication identifier, determining a layout style that matches the message content to be pushed; Based on the communication identifier, pushing the message content to be pushed and the layout style to the device end, where the message content to be pushed is rendered on the screen of the device end according to the layout style.

2. The method according to claim 1, characterized in that, Based on the communication identifier, determining a layout style that matches the message content to be pushed includes: Querying based on the communication identifier to determine device information that matches the communication identifier; Based on the device information, determining screen information that matches the device end from a screen database, where the screen database is used to record the matching relationship between the device ends with different device information and the screen information; Based on the screen information, determining the layout style that matches the message content to be pushed.

3. The method according to claim 2, wherein Based on the screen information, determining the layout style that matches the message content to be pushed includes at least one of the following: Obtaining multiple layout styles that match the screen information, and determining the layout style that matches the message content to be pushed from the multiple layout styles, where different message contents need to match different layout styles; Obtaining a preset layout style that matches the message content to be pushed, and dynamically adjusting the preset layout style based on the proportional relationship between the screen information and the preset screen information corresponding to different preset layout styles to obtain the layout style that matches the message content to be pushed.

4. The method according to claim 3, wherein Obtaining multiple layout styles that match the screen information includes: Obtaining the screen type corresponding to the screen information; Determining the layout styles that match the screen type corresponding to the screen information in a layout style set as the multiple layout styles, where different layout styles included in the layout style set need to match different screen types.

5. The method according to claim 4, wherein The method further includes: Obtaining the screen information of multiple device ends and multiple message contents; Clustering the screen information of the multiple device ends to obtain multiple screen types; Generating the layout style set that matches the multiple screen types and the multiple message contents.

6. The method according to claim 3, characterized in that, The screen information at least includes: screen length and screen width, and the preset screen information at least includes: preset screen length and preset screen width, where Based on the proportional relationship between the screen information and the preset screen information corresponding to the preset layout style, dynamically adjusting the preset layout style to obtain the layout style that matches the message content to be pushed includes: Obtaining the ratio of the screen length to the preset screen length to obtain a first ratio, and obtaining the ratio of the screen width to the preset screen width to obtain a second ratio; Dynamically adjusting the preset layout style based on the first ratio and the second ratio to obtain the layout style.

7. The method according to claim 3, wherein The screen information at least includes: screen length and screen width, and the preset screen information includes: preset screen length and preset screen width, where Based on the proportional relationship between the screen information and the preset screen information corresponding to the preset layout style, dynamically adjusting the preset layout style to obtain the layout style matching the content of the message to be pushed includes: Obtaining a ratio of the screen width to the preset screen width to obtain a second ratio, and obtaining a ratio of the screen length to the screen width to obtain a third ratio; The preset layout style is dynamically adjusted based on the second ratio and the third ratio to obtain the layout style that matches the content of the message to be pushed.

8. The method according to claim 1, characterized in that Based on the communication identifier, pushing the message content to be pushed and the layout style to the device end includes: Based on the layout style, generate a layout template of Hypertext Markup Language; Based on the communication identifier, the hypertext markup language information and the message content to be pushed are sent to the device side via SMS, wherein the message content to be pushed is filled into the hypertext markup language information by the device side and then rendered on the screen of the device side.

9. A message pushing method, characterized in that, Applied to a device, the method includes: Responding to an input instruction of an interactive interface of a device, obtaining a communication identifier of the device; In response to a message push instruction acting on the interactive interface, a display result of the message content to be pushed is displayed on the interactive interface, wherein the display result is a result of rendering the message content to be pushed on the screen of the device end according to a layout style matching the message content to be pushed, the message content to be pushed and the layout style are pushed to the device end by the cloud end based on the communication identifier, and the layout style is determined by the cloud end based on the communication identifier.

10. A message pushing method, characterized in that, include: The device sends a message push request to the cloud, wherein the message push request carries the communication identifier of the device; The device receives the message content to be pushed pushed by the cloud based on the communication identifier and the layout style matching the message content to be pushed, wherein the layout style is determined by the cloud based on the communication identifier; The device renders and displays the message content to be pushed on the screen of the device based on the layout style.

11. A message push method, characterized in that, Applied to the cloud, the method includes: Obtaining a message push request by calling a first interface, wherein the first interface includes a first parameter, a parameter value of the first parameter includes the message push request, and the message push request includes at least: a communication identifier of a device end initiating the request; Based on the communication identifier, determining a layout style that matches the content of the message to be pushed; The message content to be pushed and the layout style are pushed to the device end based on the communication identifier by calling the second interface, wherein the second interface includes a second parameter, the parameter value of the second parameter includes the message content to be pushed and the layout style, and the message content to be pushed is rendered on the screen of the device end according to the layout style.

12. A message push system, characterized in that, include: The device side is used to send a message push request, wherein the message push request at least includes: a communication identifier of the device side that initiates the request; The cloud, connected to the device side, is used to determine a layout style matching the message content to be pushed based on the communication identifier, and push the message content to be pushed and the layout style to the device side based on the communication identifier, where the layout style is used to represent the display result of the message content to be pushed on the screen of the device side; The device side is further used to render the message content to be pushed on the screen of the device side according to the layout style.

13. An electronic device, characterized in that, It includes: A memory storing an executable program; A processor for running the program, where when the program runs, it executes the method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored executable program, where when the executable program runs, it controls the device where the storage medium is located to execute the method according to any one of claims 1 to 11.

Images