Short message card sharing method, electronic device and system

Abstract

Embodiments of the present application disclose a short message card sharing method, an electronic device and a system. The method is applied to a first communication system, and the first communication system comprises a first electronic device, a first server and a second electronic device. The method comprises the following steps: the second electronic device receives a first short message through a second channel; the second electronic device displays a first card when detecting an operation of viewing the first short message, and the first card displays the first short message in a first card style; the second electronic device sends card rendering data to the first electronic device through the first server and a first channel when detecting an operation of forwarding the first card to the first electronic device, and the card rendering data is obtained by the first server based on the first short message; and the first electronic device displays the first card based on the card rendering data when detecting an operation of viewing the first short message. In this way, the target device can display the message card forwarded by the source device after the source device detects the operation of forwarding the card.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a method, electronic device and system for sharing short message cards. Background Technology

[0002] With the development of technology, electronic devices have gradually become an indispensable tool in people's lives. Electronic devices can contain messaging applications (APPs). Some messaging apps can implement card-based rendering for short messages sent by businesses through carrier channels (referred to as corporate short messages) to enhance their capabilities and improve the user experience. However, as a medium for sending and sharing short messages, these apps only support forwarding the original text message when a user wants to share message cards with other users, such as family and friends. They do not support forwarding the message cards. The recipient can only view the original text message on the electronic device and cannot see the message cards. In this situation, if the recipient clicks a link in the original text message, they still need to go through intermediate steps such as opening a browser to view the target interface. The interaction chain between the user and the electronic device is long, cumbersome, and results in a poor user experience. Summary of the Invention

[0003] This application provides a method, electronic device, and system for sharing short message cards. The method can be applied to a first communication system, which includes a first electronic device, a first server, and a second electronic device. First, the second electronic device receives a first short message (of type 1) through a second channel. Upon detecting an operation to view the first short message, the second electronic device displays a first card, showing the first short message in a first card style. Next, upon detecting an operation to forward the first card to the first electronic device, the second electronic device sends the first short message to the first server through the first channel, and the first server sends card rendering data to the first electronic device through the first channel. This card rendering data is obtained by the first server based on the first short message. Then, upon detecting another operation to view the first short message, the first electronic device displays the first card based on the card rendering data. By using the method provided in this application, after the source device detects an operation to forward a card to the target device, the target device can display the message card forwarded by the source device.

[0004] In a first aspect, this application provides a method for sharing short message cards, applied to a first electronic device. The method includes: receiving a first short message sent by a second electronic device through a first channel, wherein the first short message is a first type of short message received by the second electronic device through the second channel and displayed in a first card style; detecting an operation to view the first short message; and, in response to the operation to view the first short message, displaying a first card, wherein the first card displays the first short message in a first card style; wherein the first short message is displayed through the first card when viewed on the second electronic device.

[0005] Wherein, the first electronic device can be the source device for forwarding message cards; the second electronic device can be the target device for forwarding message cards; the first channel can be a network channel; the second channel can be an operator channel; the first type of short message can be an enterprise short message, which is a short message sent by an enterprise through an operator channel; the first card style can be used to indicate the style and content of the first card; the first card can be a message card converted from the first short message.

[0006] By using the method provided in the first aspect, after the source device detects the operation of forwarding a card to the target device, the target device can display the message card forwarded by the source device.

[0007] In conjunction with the first aspect, in some embodiments, the first short message includes a first identifier, which is used to indicate card rendering data uploaded by the second electronic device to the first server. The card rendering data includes a first content of the first short message and data for rendering the style of the first card. The card rendering data is used to display the first short message in the style of the first card.

[0008] The first identifier can be an identifier used to map card rendering data, such as an identification code, short link, etc.; the first server can be one or more cloud servers, including but not limited to smart information cloud servers and message push cloud servers; the first content can be part or all of the content in the original text of the first short message, and the first content of the first short message can be understood as the key information extracted by the second electronic device from the original text of the first short message.

[0009] In conjunction with the first aspect, in some embodiments, after receiving a first short message sent by a second electronic device through a first channel, the method further includes: sending a request message to a first server, the request message including a first identifier, the request message being used to obtain card rendering data corresponding to the first identifier; receiving a response message containing card rendering data sent by the first server, and storing the card rendering data; displaying a first card, specifically including: displaying the first card based on the card rendering data.

[0010] In this way, since the server 300 sends the card rendering data of the first identifier rather than the first short message to the electronic device 100, the size of the message body transmitted by the network message push channel (the first channel, also known as the network channel) can be reduced, thus saving communication resources.

[0011] In conjunction with the first aspect, in some embodiments, the first short message includes card rendering data, which includes first content of the first short message and data for rendering the style of the first card. The card rendering data is used to display the first short message in the style of the first card. Displaying the first card specifically includes: displaying the first card based on the card rendering data.

[0012] In this way, electronic device 100 can receive card rendering data directly forwarded by electronic device 200 through server 300 via the first channel, so that electronic device 100 can subsequently display the first card based on the card rendering data.

[0013] In conjunction with the first aspect, in some embodiments, the data used to render the style of the first card includes a card ID, a template ID, and a dataset. The card ID is used to indicate the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID is used to indicate the specific content in the data structure.

[0014] It should be noted that the card ID can be used to indicate the layout style of the first card corresponding to the first short message. For example, the layout style of the first card could be, for instance,... Figure 7A The layout style shown can have a card ID of "com.hbm.native.notification.card". The dataset is the data structure corresponding to the layout style, and its format can be, for example, JSON. For example, as shown... Figure 7B As shown, the dataset for the first card can include a logo, card title, main title, main content, table area, bottom content, and button area. Template IDs can be used to indicate specific content within the data structure; for example, in... Figure 7B The dataset shown includes cards with titles like "Package Pickup Notice" and main titles like "Pickup Code," etc. It's understandable that one card layout can correspond to multiple templates, with each template using a specific card layout as its base style. For example, Figure 7A The card layout shown can serve as a base style for both express delivery pickup notification templates and credit card repayment notifications. Finally, the electronic device 200 can display the first content of the first SMS message at a specific location within the template of the first card, thus generating the first card. For example, "8888" can be displayed below the "Pickup Code" field in the template of the first card.

[0015] In conjunction with the first aspect, in some embodiments, the first channel is a network channel and the second channel is a carrier channel.

[0016] Secondly, this application provides a method for sharing short message cards, applied to a second electronic device. The method includes: receiving a first short message through a second channel, wherein the first short message is a first type of short message; detecting an operation to view the first short message, displaying a first card, wherein the first card displays the first short message in a first card style; detecting an operation to forward the first card to the first electronic device, sending card rendering data to the first electronic device through a first channel, wherein the card rendering data is used for the first electronic device to display the first card when the user views the first short message.

[0017] Wherein, the first electronic device can be the source device for forwarding message cards; the second electronic device can be the target device for forwarding message cards; the first channel can be a network channel; the second channel can be an operator channel; the first type of short message can be an enterprise short message, which is a short message sent by an enterprise through an operator channel; the first card style can be used to indicate the style and content of the first card; the first card can be a message card converted from the first short message.

[0018] By using the method provided in the second aspect, after the source device detects the operation of forwarding a card to the target device, the source device can send card rendering data to the target device through the network channel, so that the target device can display the message card forwarded by the source device based on the received card rendering data.

[0019] In conjunction with the second aspect, in some embodiments, the card rendering data includes the first content of the first short message and data for rendering the style of the first card. The data for rendering the style of the first card includes a card ID, a template ID, and a dataset. The card ID is used to indicate the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID is used to indicate the specific content in the data structure.

[0020] The first content can be part or all of the original text of the first short message. The first content of the first short message can be understood as the key information extracted by the second electronic device from the original text of the first short message.

[0021] In conjunction with the second aspect, in some embodiments, sending card rendering data to the first electronic device via the first channel specifically includes: forwarding card rendering data to the first electronic device via the first server.

[0022] The first server can be one or more cloud servers, including but not limited to intelligent information cloud servers and message push cloud servers.

[0023] In some embodiments, electronic device 200 can send card rendering data of a first short message to server 300 through a first channel, so that server 300 can directly forward card rendering data to electronic device 100 through the first channel.

[0024] In conjunction with the second aspect, in some embodiments, sending card rendering data to the first electronic device via the first channel specifically includes: sending the first content of a first short message and a context identifier of the first short message to the first server via the first channel. The context identifier is used to indicate data for rendering the style of the first card. The context identifier is used by the first server to obtain data for rendering the style of the first card. The card rendering data is sent by the first server to the first electronic device via the first channel after integrating the first content and the data for rendering the style of the first card.

[0025] In conjunction with the second aspect, in some embodiments, the first channel is a network channel and the second channel is a carrier channel.

[0026] Thirdly, this application provides a method for sharing short message cards, applied to a first server. The method includes: receiving a first short message sent by a second electronic device through a first channel, wherein the first short message is a first type of short message received by the second electronic device through the second channel and displayed in a first card style, wherein the first short message is sent to the first server by the second electronic device after detecting an operation to forward the first card to the first electronic device, and the first card displays the first short message in the first card style; and sending card rendering data to the first electronic device through the first channel, wherein the card rendering data is used by the first electronic device to display the first card, and the card rendering data is obtained by the first server based on the first short message.

[0027] Wherein, the first electronic device can be the source device for forwarding message cards; the second electronic device can be the target device for forwarding message cards; the first server can be one or more cloud servers, including but not limited to intelligent information cloud servers and message push cloud servers; the first channel can be a network channel; the second channel can be an operator channel; the first type of short message can be an enterprise short message, which is a short message sent by an enterprise through an operator channel; the first card style can be used to indicate the style and content of the first card; the first card can be a message card converted from the first short message.

[0028] By using the method provided by the third party, after the source device detects the operation of forwarding a card to the target device, the server can forward card rendering data to the target device through the network channel, so that the target device can display the message card forwarded by the source device based on the received card rendering data.

[0029] In conjunction with the third aspect, in some embodiments, the card rendering data includes the first content of the first short message and data for rendering the style of the first card. The data for rendering the style of the first card includes a card ID, a template ID, and a dataset. The card ID is used to indicate the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID is used to indicate the specific content in the data structure.

[0030] The first content can be part or all of the original text of the first short message. The first content of the first short message can be understood as the key information extracted by the second electronic device from the original text of the first short message.

[0031] In conjunction with the third aspect, in some embodiments, the first short message includes card rendering data.

[0032] In this way, server 300 can receive card rendering data sent by electronic device 200 and directly forward the card rendering data to electronic device 100.

[0033] In conjunction with the third aspect, in some embodiments, the first short message includes a first content of the first short message and a context identifier of the first short message, the context identifier being used to indicate data for rendering the style of the first card. After receiving the first short message sent by the second electronic device through the first channel, the method further includes: obtaining data for rendering the style of the first card according to the context identifier; and integrating the first content and the data for rendering the style of the first card into card rendering data.

[0034] In this way, after receiving the first short message sent by the electronic device 200 through the first channel, the server 300 can obtain the data for rendering the style of the first card according to the scenario identifier, and integrate the first content of the first short message and the data for rendering the style of the first card into card rendering data, so as to send the integrated card rendering data to the electronic device 100.

[0035] In conjunction with the third aspect, in some embodiments, sending card rendering data to the first electronic device via the first channel specifically includes: generating a first identifier based on the card rendering data, the first identifier being used to indicate the card rendering data; sending the first identifier to the first electronic device via the first channel; receiving a request message sent by the first electronic device, the request message including the first identifier, the request message being used to obtain the card rendering data corresponding to the first identifier; and responding to the request message by sending a response message containing the card rendering data to the first electronic device via the first channel.

[0036] The first identifier can be an identifier used to map card rendering data, such as an identification code, a short link, etc.

[0037] In this way, since the server 300 sends the card rendering data of the first identifier rather than the first short message to the electronic device 100, the size of the message body transmitted by the network message push channel (the first channel, also known as the network channel) can be reduced, thus saving communication resources.

[0038] In conjunction with the third aspect, in some embodiments, sending a first identifier to a first electronic device via a first channel specifically includes: sending a message containing the first identifier to the first electronic device via the first channel.

[0039] In conjunction with the third aspect, in some embodiments, the first channel is a network channel and the second channel is a carrier channel.

[0040] Fourthly, this application provides a method for sharing short message cards, applied to a first communication system. The first communication system includes a first electronic device and a second electronic device. The method includes: the second electronic device receiving a first short message through a second channel, the first short message being a first type of short message; detecting an operation to view the first short message, the second electronic device displaying a first card, the first card displaying the first short message in a first card style; the second electronic device detecting an operation to forward the first card to the first electronic device; the first electronic device receiving the first short message through the first channel; detecting an operation to view the first short message, the first electronic device displaying the first card.

[0041] The first communication system can be, for example, Figure 3 In the communication system shown, the first electronic device can be a source device for forwarding message cards; the second electronic device can be a target device for forwarding message cards; the first channel can be a network channel; the second channel can be an operator channel; the first type of short message can be an enterprise short message, which is a short message sent by an enterprise through an operator channel; the first card style can be used to indicate the style and content of the first card; the first card can be a message card converted from the first short message.

[0042] By using the method provided in the fourth aspect, after the source device detects the operation of forwarding a card to the target device, the target device can display the message card forwarded by the source device.

[0043] In conjunction with the fourth aspect, in some embodiments, the first communication system further includes a first server. After the second electronic device detects an operation to forward the first card to the first electronic device, the method further includes: the second electronic device sending a first short message to the first server through a first channel; the first server sending card rendering data to the first electronic device through the first channel, the card rendering data being used by the first electronic device to display the first card, the card rendering data being obtained by the first server based on the first short message.

[0044] The first server can be one or more cloud servers, including but not limited to intelligent information cloud servers and message push cloud servers.

[0045] In this way, after the source device detects the operation of forwarding the card to the target device, the server can forward the card rendering data to the target device through the network channel, so that the target device can display the message card forwarded by the source device based on the received card rendering data.

[0046] In conjunction with the fourth aspect, in some embodiments, the card rendering data includes the first content of the first short message and data for rendering the style of the first card. The data for rendering the style of the first card includes a card ID, a template ID, and a dataset. The card ID is used to indicate the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID is used to indicate the specific content in the data structure.

[0047] The first content can be part or all of the original text of the first short message. The first content of the first short message can be understood as the key information extracted by the second electronic device from the original text of the first short message.

[0048] In conjunction with the fourth aspect, in some embodiments, the first short message includes card rendering data.

[0049] In this way, server 300 can receive card rendering data sent by electronic device 200 and directly forward the card rendering data to electronic device 100.

[0050] In conjunction with the fourth aspect, in some embodiments, the first short message includes a first content of the first short message and a context identifier of the first short message, the context identifier being used to indicate data for rendering the style of the first card. After the second electronic device sends the first short message to the first server through the first channel, the method further includes: the first server obtaining data for rendering the style of the first card according to the context identifier; and the first server integrating the first content and the data for rendering the style of the first card into card rendering data.

[0051] In this way, after receiving the first short message sent by the electronic device 200 through the first channel, the server 300 can obtain the data for rendering the style of the first card according to the scenario identifier, and integrate the first content of the first short message and the data for rendering the style of the first card into card rendering data, so as to send the integrated card rendering data to the electronic device 100.

[0052] In conjunction with the fourth aspect, in some embodiments, the first server sends card rendering data to the first electronic device through a first channel, specifically including: the first server generating a first identifier based on the card rendering data, the first identifier being used to indicate the card rendering data; the first server sending the first identifier to the first electronic device through the first channel; the first electronic device sending a request message to the first server, the request message including the first identifier, the request message being used to obtain the card rendering data corresponding to the first identifier; and in response to the request message, the first server sending a response message containing the card rendering data to the first electronic device through the first channel.

[0053] The first identifier can be an identifier used to map card rendering data, such as an identification code, a short link, etc.

[0054] In this way, since the server 300 sends the card rendering data of the first identifier rather than the first short message to the electronic device 100, the size of the message body transmitted by the network message push channel (the first channel, also known as the network channel) can be reduced, thus saving communication resources.

[0055] In conjunction with the fourth aspect, in some embodiments, the first server sends a first identifier to the first electronic device through a first channel, specifically including: the first server sending a message containing the first identifier to the first electronic device through the first channel.

[0056] In conjunction with the fourth aspect, in some embodiments, the first channel is a network channel and the second channel is a carrier channel.

[0057] Fifthly, this application provides a communication system, which includes a first electronic device, a second electronic device, and a first server; wherein the first electronic device, the first server, and the second electronic device are connected by communication; the first electronic device is any of the electronic devices described in the first aspect, the second electronic device is any of the electronic devices described in the second aspect, and the first server is any of the electronic devices described in the third aspect.

[0058] In a sixth aspect, this application provides an electronic device, which includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program, and when the processor executes the computer program, the electronic device performs the method of any one of the first, second, or third aspects described above.

[0059] In a seventh aspect, this application provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the method described in any one of the first to fourth aspects.

[0060] Eighthly, this application provides a computer program product that, when executed by a processor, implements the method described in any one of the first to fourth aspects.

[0061] Ninthly, this application provides a chip including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to execute the computer program stored in the memory, causing the chip to perform the method described in any one of the first to fourth aspects above.

[0062] The solutions provided in aspects five to nine above are used to implement or cooperate with the methods provided in aspects one to four above, and therefore can achieve the same or corresponding beneficial effects as the methods in aspects one to four above, which will not be elaborated here. Attached Figure Description

[0063] Figures 1A-1C These are schematic diagrams of a set of interfaces for card-based rendering of enterprise SMS messages provided in the embodiments of this application;

[0064] Figures 2A-2B This is a schematic diagram of the interface of a set of message cards forwarded by the current user provided in an embodiment of this application;

[0065] Figure 3 This is a schematic diagram of a communication system provided in an embodiment of this application;

[0066] Figure 4A This is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application;

[0067] Figure 4B This is a schematic diagram of the structure of a server 300 provided in an embodiment of this application;

[0068] Figure 5A This is a schematic diagram of the software architecture of an electronic device provided in an embodiment of this application;

[0069] Figure 5B This is a schematic diagram of the software architecture of an electronic device based on a short message card sharing method provided in an embodiment of this application;

[0070] Figure 5C This is a schematic diagram of the software architecture of a server 300 based on a short message card sharing method provided in an embodiment of this application;

[0071] Figure 6A This is a flowchart illustrating a method for rendering and sharing short message cards provided in an embodiment of this application;

[0072] Figure 6B This is a flowchart illustrating another method for rendering and sharing SMS cards provided in an embodiment of this application;

[0073] Figure 7A This is a schematic diagram of the layout style of a message card provided in an embodiment of this application;

[0074] Figure 7B This is a schematic diagram of the data structure corresponding to the layout style of a message card provided in an embodiment of this application;

[0075] Figures 8A-8F This is a set of schematic diagrams showing the interface for non-enterprise users to forward message cards based on the SMS card sharing method provided in the embodiments of this application. Detailed Implementation

[0076] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be a limitation of this application.

[0077] With the development of technology, electronic devices have gradually become an indispensable tool in people's lives. Electronic devices can contain messaging applications (APPs) (referred to as messaging apps). Some messaging apps on electronic devices can implement card-based rendering of short messages sent by businesses through carrier channels (referred to as enterprise short messages), creating message cards to enhance the messaging app's capabilities and improve the user experience. These message cards, also known as card-style short messages, present short message content in card format, typically including an image, title, brief description, and action buttons. Compared to traditional plain text short messages, card-style short messages are more intuitive and interactive, often used in marketing and notification scenarios. Card-style short messages can improve user experience and conversion rates through rich visual and interactive design. The aforementioned messaging app can be called a smart messaging app. This smart messaging app is a system plugin application that runs concurrently with the messaging app. It can interact with the messaging app through defined interfaces to enhance the messaging app's experience.

[0078] Figures 1A-1C These are schematic diagrams of a set of interfaces for card-based rendering of enterprise SMS messages provided in the embodiments of this application.

[0079] For example, such as Figure 1AAs shown, the electronic device can display a user interface 110, which can be the original text interface of a short message from an information app. The user interface 110 can include the original text message 111, whose sender can be, for example, "xx Travel". The original text message 111 can be, for example, "[xx Travel] Ticket issued. Please verify: First leg: [Xiaoming] ID number xxxxxx**********xx January 28th 21:00-22:50, Airport A - Airport B T2, xx Airlines, Flight number xxxxxx, Economy Class, Ticket number xxx-xxxxxxxxxx. Total amount: 779.00 yuan. Please arrive at the airport at least 2 hours in advance to check in to avoid missing your flight! Download the xx Travel app."

[0080] (https: / / xxx.cn / xxxxxxxx), check your itinerary information anytime. If your itinerary changes, you can also reschedule through the APP for greater convenience! In case of emergency, please call xxxx-xxxxxxxx [To prevent fraud, please do not trust unknown numbers.] xx Travel, in partnership with xx Airlines, offers a variety of exclusive value-added benefits, including VIP lounges, upgrade vouchers, in-flight WiFi, and more. For details, please log in to the xx Travel APP - Coupon Center. https: / / xxx.cn / xxxxxxxx". In some examples, the original text of the above short message may not be conveyed to the user through a screen display, but through other means, such as voice broadcast. In addition, the user interface 110 may also include a "display card" control 112, which can be used to convert the original text of the short message into a message card display.

[0081] In some embodiments, the electronic device may receive an operation to convert the original text of a short message into a message card for display (e.g., clicking the "Show Card" control 112), and in response to this operation, the electronic device may display, as shown below. Figure 1B The user interface 120 shown.

[0082] For example, such as Figure 1BAs shown, the electronic device can display a user interface 120, which can be a message card interface of an information app. The user interface 120 may include a message card 121, which displays key information from the aforementioned original text 111 of the short message, such as ID number, ticket number, airline, passenger name, order amount, cabin class, flight number, origin and departure location, origin and departure time, etc. The message card 121 may include one or more card buttons, which can be used to trigger specific functions. For example, card button 122 can be used to trigger the electronic device to jump to the webpage or application interface of the sender of the short message corresponding to message card 121. In addition, the user interface 120 may also include a "Show Original Text" control 123, which can be used to convert the message card into the original text of the short message for display.

[0083] As can be seen, compared with the original text of the short message, the message card can concisely and clearly display the key information of the short message, so that users can quickly grasp the key information and improve the user's experience of browsing short messages; in addition, the message card includes card buttons, so that users can click on the card buttons to realize specific functions such as direct access to web pages or applications, thereby improving the user's interactive experience with the messaging app.

[0084] It should be noted that short messages (enterprise short messages) capable of card-based rendering can be categorized into two types based on their business attributes: marketing enterprise short messages and experience-based enterprise short messages. Experience-based enterprise short messages can be event notification short messages for different industry scenarios (e.g., ...). Figure 1A The original text of the shown short message (111) belongs to the category of experience-based enterprise short messages in the travel scenario. Converting it into a message card can improve the user's experience of browsing short messages. Marketing-based enterprise short messages can be sent by merchants for product and event marketing. Converting marketing-based enterprise short messages into message cards can increase the probability of users entering the online store by clicking the card button, which is beneficial for merchants to promote products and events. For example, Figure 1C The user interface 130 shown may include message cards converted from marketing enterprise text messages. These message cards can be used to convey product marketing information such as "New xx bicycle products available" to users. The message card includes a "Buy Now" button, which users can click to enter the online store.

[0085] Messaging apps are applications for sending and sharing short messages, allowing users to forward received messages to other users, such as family and friends. However, when users want to share message cards with other users, such as family and friends, messaging apps can only forward the original text message, not the message card. The recipient can only view the original text message on their electronic device, not the message card. In this situation, if the recipient clicks a link in the original text message, they still need to go through intermediate steps such as opening a browser to view the target interface. This results in a long interaction chain between the user and the electronic device, cumbersome operation, and a poor user experience.

[0086] Figures 2A-2B This is a schematic diagram of the interface of a set of message cards forwarded by the current user provided in an embodiment of this application.

[0087] For example, such as Figure 2A As shown, the source device of the sending user displays a user interface 120, which is the message card interface of the messaging app. The user interface 120 may include a message card 121, which is a message card converted from a short message (enterprise short message) sent by the enterprise through the operator's channel. The sender of the enterprise short message could be, for example, xx Travel. The message card 121 displays key information from the enterprise short message, such as ID number, ticket number, airline, passenger name, order amount, cabin class, flight number, origin and departure location, origin and departure time, etc.

[0088] In some embodiments, the source device may receive an operation to forward a message card (e.g., message card 121) to the target device of the receiver. In response to this operation, the target device may display, as shown below. Figure 2B The user interface 140 shown.

[0089] For example, such as Figure 2B As shown, the target device of the recipient displays a user interface 140, which is the original text interface of the messaging app. The user interface 140 may include the original text of the short message 141, which can be... Figure 2A The user interface 120 shown represents the original text of the enterprise SMS message corresponding to message card 121. In some examples, the original text of the SMS message may not be presented to the user through a user interface, but rather through other means, such as voice broadcast. Furthermore, the user interface 140 may also include indication information for identifying the sender of the original SMS message 141. For example, indication information 142 may indicate that the sender of the original SMS message 141 is a user with the mobile phone number xxxxxxxxxxx, who is a non-enterprise user.

[0090] Currently, the sending source device and the receiving target device can communicate through an SMS center to send and receive SMS messages (also known as short messages), achieving an effect similar to MMS. For example, when editing an SMS message, the sending user can select a template from a local template library; each template has a corresponding template ID. After selecting a template, the sending user can preview it. After the user previews, the source device can send the SMS text along with a special identifier containing the template ID as the message body to the SMS center. After receiving the SMS from the SMS center, the target device can parse the message body to obtain the template ID and send a special SMS message carrying the template ID to the SMS center. The SMS center can obtain the corresponding download address from the content server based on the template ID and send the download address to the target device. After receiving the download address from the SMS center, the target device can download the template and save it to its local template library. Then, the target device can display personalized text based on the text and template, where the template serves as the background for the personalized text.

[0091] It can be seen that the above method has the following drawbacks: 1. When editing a text message, the sending user needs to select a template and preview the effect of combining the selected template with the text, which is a relatively cumbersome operation; 2. The message body sent by the source device needs to include the text message and a special identifier containing the template ID, which increases communication costs and wastes communication resources; 3. Communication between the sending source device and the receiving target device needs to go through the SMS center. The SMS center supports obtaining the corresponding download address from the content server based on the template ID and sending the download address to the target device, which involves a large number of interactions, and the user needs to pay operator costs.

[0092] To address the aforementioned issues, this application provides a method, electronic device, and system for sharing short message cards. This method can be applied to a first communication system, which includes a first electronic device, a first server, and a second electronic device. First, the second electronic device receives a first short message (of type 1) through a second channel. Upon detecting an operation to view the first short message, the second electronic device displays a first card, showing the first short message in a first card style. Next, upon detecting an operation to forward the first card to the first electronic device, the second electronic device sends the first short message to the first server through a first channel, and the first server sends card rendering data to the first electronic device through the first channel. This card rendering data is obtained by the first server based on the first short message. Then, upon detecting another operation to view the first short message, the first electronic device displays the first card based on the card rendering data. By using the method provided in this application, after the source device detects an operation to forward a card to the target device, the target device can display the message card forwarded by the source device.

[0093] It should be noted that the first channel can be a network channel, and the second channel can be a carrier channel. The first type of SMS is the aforementioned enterprise SMS, which is an SMS sent by an enterprise through a carrier channel. In some embodiments, an enterprise can register an account on a carrier server, which can be called an enterprise port number. Then, the carrier server can use the enterprise port number to send enterprise SMS to various terminal devices through the carrier channel. For example, the enterprise port number can be used by an enterprise to send enterprise SMS such as marketing-related enterprise SMS and experience-related enterprise SMS to non-enterprise users. Enterprise port numbers usually begin with "106". It is understood that, generally speaking, enterprise SMS can be converted into message cards through card rendering. The first card is the message card converted from the first SMS through card rendering. The first card can display the first content of the first SMS, which can be part or all of the content. The first content can be understood as the key information in the original text of the first short message, such as the ID number, ticket number, airline, passenger name, order amount, cabin class, flight number, origin and departure location, origin and departure time, etc. in a flight ticket issuance notification SMS, and the pickup code, pickup address, courier's mobile phone number, etc. in a package pickup notification SMS.

[0094] It should be noted that the card rendering data for the first short message may include the first content of the first short message and data used to render the style of the first card. The first content may be part or all of the content. The first content of the first short message can be understood as the key information extracted by the second electronic device from the original message text of the first short message. The data used to render the style of the first card may include a card ID, a template ID, and a dataset. The card ID can be used to indicate the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID can be used to indicate the specific content within the data structure. The meaning and examples of card rendering data will be explained in detail later and will not be elaborated here.

[0095] It should be noted that the first card style can be used to indicate the style and content of the first card. For example, if both the first electronic device and the second electronic device display the first short message using the first card style, it means that the style and content of the message cards displayed by the first electronic device and the second electronic device are the same.

[0096] First, we will introduce a communication system and related equipment provided in the embodiments of this application.

[0097] Figure 3 An exemplary embodiment of the communication system provided in this application is shown.

[0098] like Figure 3As shown, the communication system may include: electronic device 100 (target device), electronic device 200 (source device), and server 300 (one or more cloud servers).

[0099] In this embodiment, electronic device 100 refers to the aforementioned first electronic device, which can be the target device for receiving message cards. Electronic device 100 can be any type of smart terminal device capable of sending and receiving short messages and including a display screen. This application embodiment does not limit the specific type of electronic device 100. For example, electronic device 100 can be a mobile phone, or a mobile tablet, in-vehicle tablet, desktop computer, laptop computer, handheld computer, smartwatch, etc. As a human-computer interaction interface for users using an information APP (or smart information APP), users can interact with electronic device 100 through clicks, touches, buttons, gestures, etc., to use the card forwarding, card rendering, card button navigation, and other functions of the information APP (or smart information APP). In this application embodiment, electronic device 100 can be used to receive a first short message sent by electronic device 200 through a first channel. This first short message is a first type of short message received by electronic device 200 through a second channel and displayed in a first card style. After receiving the first short message, electronic device 100 can also be used to detect the operation of viewing the first short message. In response to the operation of viewing the first short message, electronic device 100 can also be used to display a first card, which can display the first short message in a first card style. In some embodiments, the first short message may include a first identifier, which can be used to indicate card rendering data uploaded by electronic device 200 to server 300. The card rendering data may include a first content of the first short message and data for rendering the style of the first card. The card rendering data can be used to display the first short message in the style of the first card. After receiving the first short message sent by electronic device 200 through the first channel, electronic device 100 can be used to send a request message to server 300. The request message may include the first identifier and can be used to obtain the card rendering data corresponding to the first identifier. Then, electronic device 100 can also be used to receive a response message containing card rendering data sent by server 300 and store the card rendering data so that electronic device 100 can subsequently display the first card based on the card rendering data. In other embodiments, the first short message may include card rendering data, which may include a first content of the first short message and data for rendering the style of the first card. The card rendering data can be used to display the first short message in the style of the first card. That is, electronic device 100 can be used to receive card rendering data directly forwarded by electronic device 200 through server 300 through the first channel so that electronic device 100 can subsequently display the first card based on the card rendering data.

[0100] In this context, electronic device 200 refers to the aforementioned second electronic device, which can be the source device for sending message cards. Electronic device 200 can be any type of smart terminal device capable of sending and receiving short messages and containing a display screen. This application embodiment does not limit the specific type of electronic device 200. For example, electronic device 200 can be a mobile phone, or a mobile tablet, in-vehicle tablet, desktop computer, laptop computer, handheld computer, smartwatch, etc. As a human-computer interaction interface for users using a messaging app (or smart messaging app), users can interact with electronic device 200 through clicks, touches, buttons, gestures, etc., to use functions such as card forwarding, card rendering, and card button navigation in the messaging app (or smart messaging app). In this embodiment, the electronic device 200 can be used to receive a first short message through a second channel, the first short message being a first type of short message; after receiving the first short message, the electronic device 200 can also be used to detect an operation of viewing the first short message; in response to the operation of viewing the first short message, the electronic device 200 can also be used to display a first card, the first card displaying the first short message in a first card style; after displaying the first card, the electronic device 200 can also be used to detect an operation of forwarding the first card to the electronic device 100; in response to the operation of forwarding the first card, the electronic device 200 can also be used to send card rendering data to the electronic device 100 through a first channel, the card rendering data being used by the electronic device 100 to display the first card when the user views the first short message. In some embodiments, the electronic device 200 sending card rendering data to the electronic device 100 through the first channel may specifically include: the electronic device 200 directly forwarding the card rendering data to the electronic device 100 through the server 300, that is, the electronic device 200 sending the card rendering data to the server 300 through the first channel, and the server 300 sending the card rendering data to the electronic device 100 through the first channel. In other embodiments, electronic device 200 sends card rendering data to electronic device 100 through a first channel. Specifically, this may include: electronic device 200 sending a first content of a first short message and a context identifier of the first short message to server 300 through the first channel. The context identifier can be used to indicate data for rendering the style of the first card. Server 300 obtains the data for rendering the style of the first card based on the received context identifier, and integrates the first content of the first short message with the data for rendering the style of the first card into card rendering data. Then, server 300 sends the card rendering data to electronic device 100 through the first channel.

[0101] Server 300 is the aforementioned first server, and it can be one or more cloud servers. In some embodiments, server 300 may include an intelligent information cloud server and a message push cloud server. The intelligent information cloud server can provide data association, device indexing, and other services to electronic devices 100 and 200 through a network request service interface; it can also interact with the message push cloud server through a network request service interface to push network messages to electronic devices 100. The message push cloud server can provide network message push and other services to electronic devices 100 and 200 through a network request service interface. In this embodiment, server 300 can be used to receive a first short message sent by electronic device 200 through a first channel. This first short message is a first type of short message received by electronic device 200 through a second channel and displayed in a first card style. This first short message is sent by electronic device 200 to server 300 after detecting an operation to forward the first card to electronic device 100. The first card is displayed in the first card style. Server 300 can also be used to send card rendering data to electronic device 100 through the first channel. This card rendering data can be used by electronic device 100 to display the first card. The card rendering data is obtained by server 300 based on the first short message. In some embodiments, the first short message includes card rendering data; that is, server 300 can receive card rendering data sent by electronic device 200 and directly forward the card rendering data to electronic device 100. In other embodiments, the first short message includes a first content and a context identifier, which can be used to indicate data used to render the style of the first card. After receiving a first short message from electronic device 200 via the first channel, server 300 can obtain data for rendering the style of a first card based on a context identifier, and integrate the first content of the first short message and the data for rendering the style of the first card into card rendering data. In some embodiments, server 300 sends card rendering data to electronic device 100 via the first channel, which may specifically include: as a smart information cloud server, server 300 can generate a first identifier based on the received card rendering data, the first identifier being used to indicate the card rendering data; then, as a message push cloud server, server 300 can send the first identifier to electronic device 100 via the first channel; as a smart information cloud server, server 300 can receive a request message from electronic device 100, the request message including the first identifier, the request message being used to obtain the card rendering data corresponding to the first identifier; as a smart information cloud server, in response to the request message, server 300 can send a response message containing card rendering data to electronic device 100 via the first channel.In some embodiments, the server 300 sends a first identifier to the electronic device 100 through a first channel. Specifically, the server 300, acting as a message push cloud server, can send a message containing the first identifier to the electronic device 100 through the first channel. This message is a network message.

[0102] Electronic device 100 and server 300 establish a communication connection, which may include, but is not limited to: wired connection (e.g., a wired connection established through a data cable connected via a Type-C interface), wireless connection such as wireless local area network (WLAN) communication connection, cellular mobile communication connection, etc. If it is a WLAN communication connection or a cellular mobile communication connection, then the communication connection between electronic device 100 and server 300 can be an indirect communication connection, that is, a communication connection established through an access point (AP), which may include, but is not limited to, base stations and routers. Furthermore, electronic device 100 and server 300 in this communication system can also connect and communicate using any combination of the above methods; this application embodiment does not impose any limitations on this. That is to say, electronic device 100 and server 300 in this communication system can form a network (i.e., network) according to a certain communication protocol and networking strategy, enabling mutual communication between electronic device 100 and server 300.

[0103] Electronic device 200 and server 300 establish a communication connection, which may include, but is not limited to, wired connections (e.g., a wired connection established via a data cable connected through a Type-C interface), wireless connections such as WLAN communication connections, cellular mobile communication connections, etc. If it is a WLAN communication connection or a cellular mobile communication connection, then the communication connection between electronic device 200 and server 300 can be an indirect communication connection, i.e., a communication connection established through an access point (AP), which may include, but is not limited to, base stations or routers. Furthermore, electronic device 200 and server 300 in this communication system can also connect and communicate using any combination of the above methods; this application embodiment does not impose any limitations on this. That is to say, electronic device 200 and server 300 in this communication system can form a network (i.e., network) according to a certain communication protocol and networking strategy, enabling mutual communication between electronic device 200 and server 300.

[0104] Figure 4A An electronic device 100 provided in an embodiment of this application is illustrated by way of example.

[0105] like Figure 4AAs shown, the electronic device 100 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, a sensor module 270, a display screen 284, and a subscriber identity module (SIM) card interface 285, etc. The sensor module 270 may include at least one of a pressure sensor 270A, a touch sensor 270K, etc.

[0106] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0107] Processor 210 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors.

[0108] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

[0109] The processor 210 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. This memory can store instructions or data that the processor 210 has just used or that are used repeatedly. If the processor 210 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 210, and thus improves the efficiency of the system.

[0110] The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 210 through the external memory interface 220 to perform data storage functions. For example, music, photos, videos, and other data can be stored on the external memory card. In this embodiment, the external memory can be used to store card rendering data.

[0111] Internal memory 221 can be used to store one or more computer programs, which include instructions. Processor 210 can execute the instructions stored in internal memory 221, thereby causing electronic device 100 to perform the SMS card sharing method provided in some embodiments of this application, as well as various functional applications and data processing. Internal memory 221 may include a program storage area and a data storage area. The program storage area may store the operating system; it may also store one or more applications (such as gallery, contacts, messages, etc.). The data storage area may store data created during the use of electronic device 100 (such as photos, contacts, etc.). Furthermore, internal memory 221 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.

[0112] USB port 230 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 230 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as augmented reality (AR) devices.

[0113] The charging management module 240 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 240 receives charging input from the wired charger via a USB interface 230. In some wireless charging embodiments, the charging management module 240 receives wireless charging input via the wireless charging coil of the electronic device 100. While charging the battery 242, the charging management module 240 can also supply power to the electronic device 100 via the power management module 241.

[0114] The power management module 241 connects the battery 242, the charging management module 240, and the processor 210. The power management module 241 receives input from the battery 242 and / or the charging management module 240, providing power to the processor 210, internal memory 221, external memory, display 284, and wireless communication module 260. The power management module 241 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 241 may also be located within the processor 210. In other embodiments, the power management module 241 and the charging management module 240 may be housed in the same device.

[0115] The wireless communication function of electronic device 100 can be implemented through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor. In this embodiment, electronic device 100 can receive a first short message through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor. If electronic device 100 is a target device, the first short message can be sent by the source device through a first channel (e.g., a network channel); if electronic device 100 is a source device, the first short message can be sent by the operator server through a second channel (e.g., an operator channel). If electronic device 100 is a source device, electronic device 100 can also send the first short message through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor. In some embodiments, the first short message includes card rendering data, that is, electronic device 100 can directly forward card rendering data to the target device through server 300. In other embodiments, the first short message includes a first content and a context identifier. This context identifier can be used to indicate data for rendering the style of the first card. The context identifier can also be used by the server 300 to obtain the data for rendering the style of the first card. This card rendering data is sent by the server 300 to the target device through a first channel after integrating the first content and the data for rendering the style of the first card. If the electronic device 100 is the target device, the electronic device 100 can also receive card rendering data through antenna 1, antenna 2, mobile communication module 250, wireless communication module 260, modem processor, and baseband processor. In some embodiments, the electronic device 100 can directly receive card rendering data forwarded by the server 300 through the first channel. In other embodiments, the electronic device 100 may first receive a first identifier sent by the server 300 through a first channel. This first identifier can be used to indicate card rendering data uploaded by the source device to the server 300. Then, the electronic device 100 may also send a request message to the server 300, which includes the first identifier and can be used to obtain the card rendering data corresponding to the first identifier. Next, the electronic device 100 may also receive a response message containing the card rendering data sent by the server 300 through the first channel. In some embodiments, the electronic device 100 receiving the first identifier sent by the server 300 through the first channel may specifically include the electronic device 100 receiving a network message containing the first identifier sent by the server 300 through the first channel.

[0116] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0117] The mobile communication module 250 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 250 may include at least one filter, switch, power amplifier, low-noise amplifier, etc. The mobile communication module 250 can receive electromagnetic waves via the antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to the modem processor for demodulation. The mobile communication module 250 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna. In some embodiments, at least some functional modules of the mobile communication module 250 may be housed in the processor 210. In some embodiments, at least some functional modules of the mobile communication module 250 and at least some modules of the processor 210 may be housed in the same device.

[0118] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor displays images or videos via the display screen 284. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 210 and may be housed within the same device as the mobile communication module 250 or other functional modules.

[0119] The wireless communication module 260 can provide solutions for wireless communication applications on the electronic device 100, including WLAN (such as Wireless Fidelity, WiFi), Bluetooth, Global Navigation Satellite System, frequency modulation, near field communication (NFC), infrared technology, ultra-wideband (UWB), and SparkLink. The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via an antenna, frequency-modulates and filters the electromagnetic wave signal, and sends the processed signal to the processor 210. The wireless communication module 260 can also receive signals to be transmitted from the processor 210, frequency-modulate and amplify them, and then convert them into electromagnetic waves for radiation via the antenna. For example, the wireless communication module 260 may include a Bluetooth module, a WiFi module, etc.

[0120] In some embodiments, a portion of the antenna of the electronic device 100 is coupled to the mobile communication module 250, and another portion of the antenna is coupled to the wireless communication module 260, enabling the electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), Millimeter Wave (mmWave), BitTorrent, Global Navigation Satellite System (GNSS), WLAN, NFC, Frequency Modulation (FM), UWB, and / or Infrared (IR) technology, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0121] Pressure sensor 270A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, pressure sensor 270A can be disposed on display screen 284. There are many types of pressure sensors 270A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 270A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 284, electronic device 100 detects the intensity of the touch operation based on pressure sensor 270A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 270A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example: when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.

[0122] Touch sensor 270K, also known as a touch panel or touch-sensitive surface, can be located on display screen 284. The touch sensor 270K and display screen 284 together form a touchscreen, also called a "touchscreen." Touch sensor 270K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 284. In other embodiments, touch sensor 270K may also be located on the surface of electronic device 100, in a different position than display screen 284.

[0123] In this embodiment, the electronic device 100 can detect operations such as viewing a first short message and forwarding a first card through a pressure sensor 270A and a touch sensor 270K.

[0124] Electronic device 100 can perform display functions, such as displaying a first card based on card-based rendering, through a GPU, display screen 284, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 284 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs, which execute instructions to generate or modify display information.

[0125] The display screen 284 is used to display images, videos, etc. The display screen 284 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N displays 284, where N is a positive integer greater than 1.

[0126] The SIM card interface 285 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 285 to make contact with and separate from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 285 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 285 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 285 is also compatible with different types of SIM cards. The SIM card interface 285 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 100 and cannot be separated from the electronic device 100.

[0127] The structure of electronic device 200 is the same as that of electronic device 100, and will not be described again here.

[0128] Figure 4B The structure of the server 300 provided in an embodiment of this application is illustrated by way of example.

[0129] like Figure 4B As shown, server 300 may include processor 310 and memory 320. Components in server 300 are connected to each other via a bus and communicate based on the bus.

[0130] Processor 310 may include one or more processing units, such as application processors, modem processors, GPUs, ISPs, controllers, video codecs, DSPs, baseband processors, and / or NPUs. These different processing units may be independent devices or integrated into one or more processors. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0131] Memory 320 is coupled to processor 310 and is used to store various software programs and / or multiple sets of instructions. Memory 320 can be used to store computer executable program code, which includes instructions. Processor 310 executes various functional applications and data processing of server 300 by running the instructions stored in memory 320. Memory may also be provided in processor 310 for storing instructions and data.

[0132] The memory 320 may include one or more random access memory (RAM) and one or more non-volatile memory (NVM). The RAM can be directly read and written by the processor 310. The RAM can be used to store executable programs (e.g., machine instructions) of the operating system or other running programs. The NVM can also store executable programs and user and application data. Executable programs, i.e., user data, stored in the NVM can be pre-loaded into the RAM for direct reading and writing by the processor 310.

[0133] It should be understood that, Figure 4B The server 300 shown is merely an example, and server 300 can have more than... Figure 4B The more or fewer components shown can be combined into two or more components, or they can have different component configurations. Figure 4B The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0134] The software architecture diagrams provided in the embodiments of this application will be described in detail below.

[0135] Figure 5A An exemplary embodiment of the software architecture of an electronic device provided in this application is illustrated.

[0136] The electronic devices (including electronic device 100 and electronic device 200) provided in this application embodiment can run an operating system (OS). The operating system can be various operating systems used in the industry, such as an operating system based on OpenHarmony, such as HarmonyOS; or other operating systems such as Android. TM An operating system can refer to the iOS mobile operating system; it can also refer to various open-source operating systems or their derivatives, such as Linux OS and other embedded operating systems; it can also refer to future new operating systems, such as artificial intelligence (AI) operating systems. An operating system is a set of interconnected system software programs that manage and control the operation of electronic devices, utilize and run hardware and software resources, and provide public services to organize user interactions. In electronic devices, the operating system connects downwards to the physical hardware layer and upwards to provide a runtime environment for application software.

[0137] An operating system typically includes a kernel layer, a middleware layer, and an application layer. The application layer includes applications, which can include system applications and third-party applications. The middleware layer includes a suite of software providing various services to application developers, or frameworks providing services such as databases, multimedia, and graphics, or capabilities such as distributed scheduling and system scaling. For example, the middleware layer may include a framework layer and / or a system service layer. The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The system service layer includes the system's core capabilities, providing services to applications through the framework layer. The kernel layer is the layer between hardware and software. The kernel layer may include hardware drivers and the operating system kernel. In addition to providing hardware drivers, the kernel layer also supports functions such as memory management and system process management.

[0138] The electronic devices we use in our daily lives come in various types and forms, and are applied in a wide range of scenarios. Therefore, based on the different forms and functions of electronic devices, different application scenarios, and different user needs, the operating systems used in these devices may also differ. The basic functions implemented by the electronic device provided in this application can be implemented using a general-purpose operating system or a dedicated operating system. To more clearly illustrate the implementation of the embodiments of this application under a specific operating system, the architecture of HarmonyOS is shown below. Those skilled in the art can deduce the implementation of the embodiments of this application under other specific operating systems, such as Android. TM Implementation under operating systems, etc.

[0139] The software architecture of electronic devices can be divided into several layers. In some embodiments, from bottom to top, these layers are: kernel layer, system service layer, framework layer, and application layer. Layers communicate with each other through software interfaces. System functions can be tailored, added, or combined at the subsystem level depending on the deployment scenario of different device forms. Each subsystem can also be tailored, added, or combined at the functional level.

[0140] Kernel layer:

[0141] The Kernel Abstraction Layer (KAL) provides basic kernel capabilities to upper layers by shielding the differences between multiple kernels, including but not limited to process / thread management, memory management, file system, network management, and peripheral device management.

[0142] Kernel Subsystem: Supports the selection of a suitable OS kernel for different resource-constrained devices, including but not limited to Linux kernel, HarmonyOS kernel, LiteOS (Lite Operating System), etc.

[0143] Driver Subsystem: The driver framework is the foundation for the open system hardware ecosystem, providing unified peripheral access capabilities and a framework for driver development and management. The driver framework includes: display drivers, camera drivers, audio drivers, Bluetooth drivers, sensor drivers, etc.

[0144] System service layer:

[0145] The system service layer comprises the core capabilities of the system, providing services to applications through the framework layer. This layer includes, but is not limited to, the following subsystems:

[0146] The system's basic capability subsystem set provides fundamental capabilities for the operation, scheduling, and migration of distributed applications across multiple devices. This set may include distributed soft bus, distributed data management, distributed task scheduling, and Ark multi-language runtime; it may also include multi-modal input subsystem, graphics subsystem, security subsystem, and AI subsystem.

[0147] Basic software service subsystem set: provides public and general software services; the basic software service subsystem set may include event notification subsystem, telephone service subsystem, multimedia subsystem, etc.

[0148] Enhanced Software Service Subsystem Set: Provides differentiated enhanced software services for different devices; the enhanced software service subsystem set may include proprietary business subsystems for smart screens, proprietary business subsystems for wearables, proprietary business subsystems for the Internet of Things (IoT), etc.

[0149] Hardware service subsystem set: Provides hardware services; the hardware service subsystem set may include location service subsystem, user IAM (Identity and Access Management) subsystem, wearable proprietary hardware service subsystem, biometric identification, IoT proprietary hardware service subsystem, etc.

[0150] Distributed task scheduling enables distributed service management (discovery, synchronization, registration, and invocation), supporting remote startup, remote invocation, remote connection, and migration of applications across devices.

[0151] Distributed data management enables data synchronization, data storage, data sharing, and data access across all scenarios and devices.

[0152] The distributed soft bus provides communication-related capabilities for seamless interconnection between multiple devices, including: WLAN service capabilities, Bluetooth service capabilities, soft bus, inter-process communication RPC (Remote Procedure Call), and StarFlash communication capabilities.

[0153] Ark Multilingual Runtime is a unified compilation runtime platform designed to support the joint compilation and execution of multiple programming languages ​​and multiple chip platforms.

[0154] Framework layer:

[0155] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. The framework layer includes: the ArkUI framework (which provides a complete infrastructure for UI development of system applications, including user interface (UI) functionalities such as components, layouts, animations, and interactive events, as well as a real-time UI preview tool), the user application framework, and the Ability framework (an Ability is a lightweight application; the Ability framework schedules and manages the operation and lifecycle of Abilities). Different devices may have different operating systems, and therefore support different APIs.

[0156] The HarmonyOS API is a series of open capabilities provided to support HarmonyOS application development. The HarmonyOS API can be set at the framework layer or independently of the framework layer. The HarmonyOS API includes the Audio API (audio service), Push API (push service), and Account API (account service), among others.

[0157] Application layer:

[0158] Applications can include system apps and extended / third-party apps. System apps can include the desktop, control bar, settings, contacts, phone, camera, etc., while extended / third-party apps can include social networking, travel, etc.

[0159] Figure 5B An exemplary embodiment of the software architecture of an electronic device based on a short message card sharing method provided in this application is illustrated.

[0160] like Figure 5B As shown, the application layer may include information applications (or intelligent information applications). The middleware layer may include a message receiving module, a message parsing module, a card rendering module, and a device reporting module. It should be noted that, as mentioned above, the middleware layer may include a framework layer and / or a system service layer; therefore, the message receiving module, message parsing module, card rendering module, and device reporting module may belong to either the framework layer or the system service layer.

[0161] In the card rendering stage: the application layer's information application can receive the first short message through the second channel and send the message identifier and message text of the first short message to the middleware layer's message parsing module. The first short message is a first-type short message, and the message identifier indicates the message text. The information application can also retrieve the card rendering data of the first short message from the middleware layer's message parsing module based on the message identifier after detecting an operation to view the first short message. After obtaining the card rendering data, the information application can also call the card rendering method of the middleware layer's card rendering module to display the first card. In the device reporting stage: the information application can notify the middleware layer's device reporting module to initialize during startup loading to detect events that trigger device reporting, such as receiving new messages or switching SIM cards. In the card forwarding stage: the electronic device acts as the source device (e.g., electronic device 200). After detecting an operation to forward the first card to the target device, the information application can record the target device's device information (e.g., the target device's user account hash) and send the message identifier of the first short message to the message parsing module to obtain the card rendering data of the first short message. After obtaining the card rendering data of the first short message, the messaging application can also use it to send the card rendering data of the first short message, the device information of the target device (e.g., the user account hash of the target device), and the user account of the source device (e.g., mobile phone number) to the server 300 through the first channel. If the electronic device is the target device (e.g., electronic device 100), after the message receiving module obtains the first identifier, the messaging application can also use it to obtain the card rendering data of the first short message from the server 300 based on the first identifier.

[0162] In the card forwarding phase: As the target device (e.g., electronic device 100), the middleware layer's message receiving module can receive a message sent by server 300 via a first channel, containing a first identifier and the source device's user account (e.g., mobile phone number), and retrieve the first identifier and the source device's (e.g., electronic device 200's) user account from the message. The source device's (e.g., electronic device 200's) user account can be used as the sender indication information for the first card in the target device's (e.g., electronic device 100's) information application.

[0163] In the card rendering stage: the message parsing module of the middleware layer can parse the original message of the first short message after receiving it, obtaining the context identifier and the first content of the first short message. The context identifier of the first short message indicates the context to which the original message belongs. For example, if the original message of the first short message is "[xx Express] Pick up your package at xx Express Locker No. 1, North Side of Building 1, xxx Community, using pickup code 8888. If you have any questions, please contact the courier's mobile phone number xxxxxxxxxxx", then the context of the first short message is a package pickup notification, and this package pickup notification context corresponds to the unique context identifier "C001001". The first content can be part or all of the content. The first content of the first short message can be understood as the key information extracted by the message parsing module from the original message of the first short message, such as the pickup code, pickup address, courier's mobile phone number, etc. in the package pickup notification short message. After obtaining the context identifier and first content of the first short message, the message parsing module can also be used to retrieve partial card rendering data (i.e., data used to render the style of the first card) from the server 300 based on the context identifier of the first short message. After obtaining the partial card rendering data (i.e., data used to render the style of the first card) containing the dataset, template ID, and card ID, the message parsing module can also be used to associate and store the message identifier of the first short message with the card rendering data containing the first content, dataset, template ID, and card ID of the first short message. During the card forwarding phase: When the electronic device acts as the source device (e.g., electronic device 200), the message parsing module can be used to retrieve the card rendering data of the first short message based on the message identifier of the first short message. When the electronic device acts as the target device (e.g., electronic device 100), after the information application obtains the card rendering data sent by the server 300 through the first channel, the message parsing module can also be used to associate and store the message identifier and the card rendering data. This message identifier can be the message identifier corresponding to the message sent by the server 300, which contains the first identifier and the user account of the source device (e.g., electronic device 200), received by the message receiving module.

[0164] In the card rendering stage: the card rendering module of the middleware layer can be used to update the first card in the view of the message list of the information application to achieve card-based rendering for the first short message.

[0165] In the device reporting phase: the middleware layer's device reporting module can be initialized when the messaging application starts loading to detect events that trigger device reporting, such as receiving new messages or switching SIM cards. The device reporting module can also be used for frequency control verification of events that trigger device reporting, such as frequency control verification for receiving new messages, to prevent the device reporting module from frequently reporting device information. Furthermore, after detecting an event that triggers device reporting, the device reporting module can report device information to the server (300). This device information may include, but is not limited to, the electronic device's user account hash (e.g., mobile phone number hash) and the message push token corresponding to the user account hash.

[0166] Figure 5C An exemplary embodiment of the software architecture of a server 300 based on a short message card sharing method provided in this application is illustrated.

[0167] like Figure 5C As shown, server 300 may include data association services, device indexing services, and message push services. As previously described, server 300 may include an intelligent information cloud server and a message push cloud server. In some embodiments, the data association service, device indexing service, and message push service can all belong to the intelligent information cloud server.

[0168] The data association service can be used to generate a first identifier based on the card rendering data received from electronic device 200 (source device). This first identifier can be used to indicate the card rendering data. After generating the first identifier, the data association service can also be used to integrate the scattered card rendering data into a continuous field in a specific format (e.g., JSON format) and associate the first identifier with the integrated card rendering data in the specific format (e.g., JSON format). The data association service can also be used to return the card rendering data corresponding to the first identifier received from electronic device 100 (target device) through a first channel. This card rendering data is obtained by deconstructing the integrated card rendering data in the specific format (e.g., JSON format).

[0169] The device indexing service can be used to update stored device information based on device information reported by electronic device 100. The device indexing service can also be used to index the message push token corresponding to the user account hash (e.g., mobile phone number hash) of electronic device 100 (target device). This message push token can be used to indicate the target device for message pushes.

[0170] Among them, the message push service can be used to push messages containing a first identifier and the user account (e.g., mobile phone number) of the electronic device 200 (source device) to the electronic device 100 (target device) through the first channel by interacting with the message push cloud server.

[0171] The following is a detailed flowchart illustrating the SMS card rendering and sharing method provided in the embodiments of this application.

[0172] Figure 6A The following is an exemplary illustration of the specific flow of a short message card rendering and sharing method provided in an embodiment of this application. This method can be applied to... Figure 3 The communication system shown.

[0173] like Figure 6A As shown, the method may include:

[0174] S101. Upon receiving the first short message, the electronic device 200 parses the original message of the first short message.

[0175] Specifically, the electronic device 200 can receive a first short message through a messaging app. This first short message is a first type of short message (e.g., a corporate short message) received by the electronic device 200 through a second channel (e.g., a carrier channel). In some embodiments, the electronic device 200 can identify whether the first short message is a corporate short message (i.e., a short message sent by a company through a carrier channel) by the sender's port number of the first short message. The sender's port number refers to a dedicated number assigned by the carrier for sending short messages. For example, the sender's port number of a corporate short message (which can be called a corporate port number) can be used by a company to send corporate short messages such as marketing-related corporate short messages and experience-related corporate short messages to non-company users. Corporate port numbers typically begin with "106". After determining that the first short message is a corporate short message, the electronic device 200 can send the message identifier and the original message text of the first short message to the message parsing module through the messaging app. This allows the electronic device 200 to parse the original message text of the first short message and obtain the context identifier and first content of the first short message. The message identifier of the first short message can be used to indicate the original message text of the first short message, and this message identifier is unique within the electronic device 200. For example, the message identifier "C01" uniquely corresponds to the original message "[xx Express] Please use the pickup code 8888 to pick up your package at xx Express Locker No. 1 on the north side of Building 1, xxx Community. If you have any questions, please contact the courier's mobile phone number xxxxxxxxxxx".

[0176] Specifically, after receiving the first short message, the electronic device 200 can parse the original text of the first short message through the message parsing module to obtain the context identifier and the first content of the first short message. The context identifier of the first short message indicates the context to which the original text of the first short message belongs. For example, if the original text of the first short message is "[xx Express] Pick up your package at xx Express Locker No. 1, North Side of Building 1, xxx Community, using pickup code 8888. If you have any questions, please contact the courier's mobile phone number xxxxxxxxxxx", then the context of the first short message is a package pickup notification context, and this package pickup notification context corresponds to the unique context identifier "C001001". The aforementioned first content can be part or all of the content. The first content of the first short message can be understood as the key information extracted by the electronic device 200 from the original text of the first short message through the message parsing module, such as the pickup code, pickup address, courier's mobile phone number, etc., in the package pickup notification short message.

[0177] It should be noted that before receiving the first SMS message through the messaging app, the electronic device 200 can receive the broadcast of the first SMS message through the messaging app to be aware of the event of receiving the first SMS message, and then display the message reminder of the first SMS message in the notification bar.

[0178] S102, Electronic device 200 sends a request to server 300 to obtain partial card rendering data.

[0179] S103, Server 300 returns part of the card rendering data to Electronic Device 200.

[0180] Specifically, after obtaining the context identifier and content of the first short message, the electronic device 200 can call the interface of the intelligent information cloud server (e.g., interface / getMessageData) through the message parsing module to send a request to the server 300 to obtain partial card rendering data (i.e., data used to render the style of the first card). This request may include the context identifier of the first short message to obtain the partial card rendering data (i.e., data used to render the style of the first card) corresponding to the context identifier from the server 300. The partial card rendering data (i.e., data used to render the style of the first card) may include, but is not limited to, datasets, template IDs, and card IDs.

[0181] Specifically, after receiving a request from electronic device 200 to obtain partial card rendering data (i.e., data used to render the style of the first card), server 300 can return to electronic device 200 the partial card rendering data (i.e., data used to render the style of the first card) corresponding to the context identifier of the first short message. It is understood that the intelligent information cloud server can store the correspondence between context identifiers and datasets, template IDs, card IDs, and other partial card rendering data (i.e., data used to render the style of the first card), and this correspondence is configured by server 300.

[0182] It should be noted that the card ID can be used to indicate the layout style of the first card corresponding to the first short message. For example, the layout style of the first card could be, for instance,... Figure 7A The layout style shown can have a card ID of "com.hbm.native.notification.card". The dataset is the data structure corresponding to the layout style, and its format can be, for example, JSON. For example, as shown... Figure 7B As shown, the dataset for the first card can include a logo, card title, main title, main content, table area, bottom content, and button area. Template IDs can be used to indicate specific content within the data structure; for example, in... Figure 7B The dataset shown includes cards with titles like "Package Pickup Notice" and main titles like "Pickup Code," etc. It's understandable that one card layout can correspond to multiple templates, with each template using a specific card layout as its base style. For example, Figure 7A The card layout shown can serve as a base style for both express delivery pickup notification templates and credit card repayment notifications. Finally, the electronic device 200 can display the first content of the first SMS message at a specific location within the template of the first card, thus generating the first card. For example, "8888" can be displayed below the "Pickup Code" field in the template of the first card.

[0183] S104, Electronic device 200 associates storage message identifier and card rendering data.

[0184] Specifically, after obtaining partial card rendering data (i.e., data used to render the style of the first card) containing the dataset, template ID, and card ID, the electronic device 200 can associate and store the message identifier of the first short message and the card rendering data through the message parsing module. The card rendering data of the first short message may include, but is not limited to, the first content of the first short message, the dataset, the template ID, and the card ID. The message identifier of the first short message can be used as the primary key so that when the electronic device 200 detects an operation to view the first short message, it can obtain the card rendering data corresponding to the message identifier through the message identifier of the first short message. In turn, the electronic device 200 can convert the first short message into the first card based on the obtained card rendering data.

[0185] S105, Upon detecting the operation of viewing the first short message, the electronic device 200 calls the card rendering method of the card rendering module.

[0186] S106, Electronic device 200 renders the first card based on card rendering data.

[0187] Specifically, upon detecting an operation to view the first short message, the electronic device 200 can obtain the card rendering data of the first short message from the message parsing module through the messaging app based on the message identifier of the first short message. After obtaining the card rendering data of the first short message, the electronic device 200 can display the first card by calling the card rendering method of the card rendering module through the messaging app based on the card rendering data, that is, display the first short message in the style of the first card. Then, the electronic device 200 can update the first card in the message list view of the messaging app through the card rendering module to achieve card-based rendering of the first short message.

[0188] It should be noted that viewing the first short message can include, but is not limited to: clicking the message notification for the first short message in the notification bar, or clicking the Messages app icon on the desktop to enter the conversation details page (the page where users can view the specific content of the short message) and view the first short message.

[0189] It should be noted that the interface for card-based rendering of the first short message can be referenced from the previous examples. Figures 1A-1B This will not be elaborated upon here.

[0190] As can be seen, compared with the original text of the first short message, the first card can concisely and clearly display the key information of the first short message, so that users can quickly grasp the key information and improve the user's experience of browsing the first short message; in addition, the first card includes card buttons, so that users can click on the card buttons to realize specific functions such as directly accessing web pages or applications, thereby improving the user's interactive experience with the messaging app.

[0191] S107. Upon detecting an event reported by the triggering device, the electronic device 200 reports device information to the server 300.

[0192] S108, Server 300 updates the stored device information based on the device information received from Electronic Device 200.

[0193] It should be noted that when the messaging app starts loading, the electronic device 200 can initialize through the device reporting module to detect events that trigger device reporting, such as receiving new messages or switching SIM cards. Upon detecting an event that triggers device reporting, the electronic device 200 can use the device reporting module to perform frequency control checks on the event to prevent the device reporting module from frequently reporting device information. For example, regarding the frequency control check for receiving new messages, if the time difference between the new message receiving event and the last message received is less than 24 hours, the electronic device 200 may not report device information.

[0194] Specifically, after detecting an event that triggers device reporting, electronic device 200 can call the interface of the intelligent information cloud server through the device reporting module to report device information to server 300. This device information may include, but is not limited to, the user account hash (e.g., mobile phone number hash) of electronic device 100 and the message push token corresponding to the user account hash. Among them, the message push token corresponding to the user account hash can be used to indicate the target device of the message push (i.e., the electronic device 100 corresponding to the user account hash).

[0195] It should be noted that when the event that triggers the device to report is a SIM card switch, the user account hash (such as the phone number hash) and the message push token corresponding to the user account hash in the device information will change.

[0196] Specifically, after receiving the device information reported by the electronic device 200, the server 300 can update the stored device information based on the received device information of the electronic device 200 to maintain the latest correspondence between the user account hash (e.g., mobile phone number hash) of the electronic device and the message push token corresponding to the user account hash. In the subsequent card forwarding stage, the server 300 can obtain the corresponding message push token through the user account hash (e.g., mobile phone number hash) of the electronic device 100 (target device) uploaded by the electronic device 200 (source device) to index the target device of the message push.

[0197] S109. An operation to forward the first card to electronic device 100 is detected, and electronic device 200 sends card rendering data to server 300.

[0198] Specifically, upon detecting an operation to forward the first card to electronic device 100, electronic device 200 can record the device information of electronic device 100 (target device) (e.g., the user account hash of electronic device 100) through an information APP. In some embodiments, after recording the device information of electronic device 100 (target device) (e.g., the user account hash of electronic device 100), electronic device 200 can send the message identifier of the first short message to the message parsing module through the information APP to obtain the card rendering data of the first short message. Then, electronic device 200 can obtain the card rendering data of the first short message based on the message identifier of the first short message through the message parsing module. After obtaining the card rendering data, electronic device 200 can upload the card rendering data of the first short message, the device information of electronic device 100 (e.g., the user account hash of electronic device 100), and the user account (e.g., mobile phone number) of electronic device 200 to server 300 through a first channel (e.g., a network channel) by calling the interface of the intelligent information cloud server (e.g., interface / reportMessage). In other embodiments, after recording the device information of electronic device 100 (target device) (e.g., the user account hash of electronic device 100), electronic device 200 can also upload the first content of the first short message, the context identifier of the first short message, the device information of electronic device 100 (e.g., the user account hash of electronic device 100), and the user account (e.g., mobile phone number) of electronic device 200 to server 300 through the first channel by calling the interface of the intelligent information cloud server (e.g., interface / reportMessage). The context identifier can be used by server 300 to obtain data for rendering the style of the first card and integrate the first content and the data for rendering the style of the first card into card rendering data. Sending the first content of the first short message and the context identifier of the first short message to server 300 instead of the card rendering data of the first short message can reduce the message body size transmitted through the network message push channel and save communication resources.

[0199] S110, server 300 forwards card rendering data to electronic device 100.

[0200] In some embodiments, after receiving card rendering data of a first short message from electronic device 200, device information of electronic device 100, and user account of electronic device 200, server 300 can proactively push the card rendering data of the first short message to electronic device 100 through a first channel. Optionally, the card rendering data of the first short message can be included in a network message sent by server 300 to electronic device 100. In other embodiments, after receiving the first content and context identifier of the first short message from electronic device 200, device information of electronic device 100 (e.g., user account hash of electronic device 100), and user account of electronic device 200 (e.g., mobile phone number), server 300 can obtain data for rendering the style of the first card based on the received context identifier; then, server 300 can integrate the first content of the first short message and the data for rendering the style of the first card into card rendering data. After obtaining the card rendering data of the first short message, server 300 can proactively push the card rendering data of the first short message to electronic device 100 through a first channel. Optionally, the card rendering data of the first short message can be included in a network message sent by server 300 to electronic device 100.

[0201] S111, Electronic device 100 associates and stores message identifiers and card rendering data through the message parsing module.

[0202] S112. Upon detecting the operation of viewing the first short message, the electronic device 100 calls the card rendering method of the card rendering module.

[0203] S113, Electronic device 100 renders the first card based on card rendering data.

[0204] In some embodiments, after obtaining card rendering data from server 300 via a messaging app, electronic device 100 can associate and store message identifiers and card rendering data through a message parsing module. The message identifier can be the message identifier corresponding to a message sent by server 300 to electronic device 100 via message receiving module, containing a first identifier and the user account (e.g., mobile phone number) of electronic device 200. The message identifier can serve as a primary key, allowing electronic device 100 to retrieve the corresponding card rendering data when it detects an operation to view the first short message, thereby enabling electronic device 100 to display the first card based on the obtained card rendering data. After obtaining card rendering data from server 300 via a messaging app, electronic device 100 can also display a message notification for the first short message in the notification bar via the messaging app.

[0205] Specifically, upon detecting an operation to view the first short message, the electronic device 100 can obtain the corresponding card rendering data from the message parsing module via the messaging app based on the message identifier. After obtaining the card rendering data, the electronic device 100 can display the first card by calling the card rendering method of the card rendering module based on the card rendering data, that is, display the first short message in the style of the first card. Then, the electronic device 100 can update the first card in the message list view of the messaging app through the card rendering module to achieve card-based rendering of the first short message forwarded by non-enterprise users. It should be noted that short messages forwarded by non-enterprise users can be identified by the sender's port number, which is not the enterprise port number.

[0206] It should be noted that the sender indication information of the first card can be the user account (e.g., mobile phone number) of the electronic device 200 (source device) received by the electronic device 100 from the server 300.

[0207] It should be noted that viewing the first short message can include, but is not limited to: clicking the message notification for the first short message in the notification bar, or clicking the Messages app icon on the desktop to enter the conversation details page (the page where users can view the specific content of the short message) and view the first short message.

[0208] It should be noted that steps S101-S106 can be collectively referred to as the card rendering stage, steps S107-S108 can be collectively referred to as the device reporting stage, and steps S109-S113 can be collectively referred to as the card forwarding stage.

[0209] Figure 6B The following is an exemplary illustration of the specific flow of another short message card rendering and sharing method provided in an embodiment of this application. This method can be applied to... Figure 3 The communication system shown.

[0210] like Figure 6B As shown, the method may include:

[0211] S201. Upon receiving the first short message, the electronic device 200 parses the original text of the first short message.

[0212] S202, Electronic device 200 sends a request to server 300 to obtain partial card rendering data.

[0213] S203, Server 300 returns part of the card rendering data to Electronic Device 200.

[0214] S204, Electronic device 200 associates storage message identifier and card rendering data.

[0215] S205. Upon detecting the operation of viewing the first short message, the electronic device 200 calls the card rendering method of the card rendering module.

[0216] S206, Electronic device 200 renders the first card based on card rendering data.

[0217] S207. Upon detecting an event reported by the triggering device, the electronic device 200 reports device information to the server 300.

[0218] S208, Server 300 updates the stored device information based on the device information received from Electronic Device 200.

[0219] S209. An operation to forward the first card to electronic device 100 is detected, and electronic device 200 sends card rendering data to server 300.

[0220] It is understandable that steps S201-S209 are the same as those mentioned above. Figure 6A Steps S101-S109 are similar to those shown. For a detailed explanation of steps S201-S209, please refer to the foregoing. Figure 6A The relevant textual descriptions in steps S101-S109 shown will not be repeated here.

[0221] S210 and server 300 generate a first identifier based on the received card rendering data and associate the first identifier with the card rendering data.

[0222] S211, Server 300 sends the first identifier to Electronic Device 100.

[0223] S212, Electronic device 100, carrying the first identifier, queries server 300 for card rendering data.

[0224] S213, Server 300 returns the card rendering data corresponding to the first identifier to Electronic device 100.

[0225] Specifically, after obtaining the card rendering data of the first short message, server 300 can generate a first identifier based on the card rendering data of the first short message through a data association service. This first identifier can be used to indicate the card rendering data of the first short message, and there is a one-to-one correspondence between the first identifier and the card rendering data of the first short message. After generating the first identifier, server 300 can also integrate the scattered card rendering data of the first short message, such as the first content field, dataset field, card ID field, and template ID field, into a continuous field in a specific format (e.g., JSON format) through the data association service, so that server 300 can associate and store the first identifier with the card rendering data of the first short message through the data association service. Then, server 300 can associate and store the first identifier with the card rendering data integrated into a specific format (e.g., JSON format) in server 300, for example, in a non-relational database of server 300. The first identifier can serve as a primary key, so that subsequent electronic device 100 can download the corresponding card rendering data based on the first identifier, thereby enabling electronic device 100 to render the first card based on the card rendering data.

[0226] In some embodiments, after the server 300 associates and stores the first identifier with the card rendering data integrated into a specific format (e.g., JSON format) through a data association service, the server 300 can index the message push token corresponding to the user account hash (e.g., mobile phone number hash) of the electronic device 100 through a device indexing service. This allows the server 300 to subsequently send the card rendering data of the first short message to the electronic device 100 through a network message push channel (the first channel, also referred to as the network channel). The message push token can be used to indicate the target device for the message push (i.e., the electronic device 100 corresponding to the user account hash). In other embodiments, after obtaining the card rendering data of the first short message, the server 300 can index the message push token corresponding to the user account hash through a device indexing service based on the user account hash (e.g., mobile phone number hash) of the electronic device 100. This allows the server 300 to subsequently send the card rendering data of the first short message to the electronic device 100 through a network message push channel (the first channel, also referred to as the network channel). The message push token can be used to indicate the target device for the message push (i.e., the electronic device 100 corresponding to the user account hash).

[0227] Specifically, after the data association service associates and stores the first identifier with the card rendering data integrated into a specific format, and the device index service indexes the message push token corresponding to the user account hash of the electronic device 100, the server 300 can obtain the first identifier through the data association service, and can also obtain the message push token of the electronic device 100 through the device index service. Then, the server 300 can call the interface of the message push cloud server (e.g., interface / pushMessage) based on the first identifier, the message push token of the electronic device 100, and the user account (e.g., mobile phone number) of the electronic device 200 through the message push service, so that the message push cloud server sends the first identifier and the user account (e.g., mobile phone number) of the electronic device 200 to the electronic device 100 through the first channel based on the message push token of the electronic device 100. Among them, the first identifier can be used by the electronic device 100 to download the card rendering data of the first short message corresponding to the first identifier from the server 300, and the user account of the electronic device 200 can be used as the sender indication information of the first card in the information APP of the electronic device 100. Then, server 300 can send a first identifier and user account (e.g., mobile phone number) of electronic device 200 to electronic device 100 through the first channel based on the message push token of electronic device 100. In some embodiments, server 300 can send a message containing the first identifier and user account (e.g., mobile phone number) of electronic device 200 to electronic device 100 through the first channel; this message is a network message. By sending the card rendering data of the first identifier instead of the first short message to electronic device 100, server 300 can reduce the message body size transmitted through the network message push channel and save communication resources.

[0228] Specifically, after obtaining the first identifier through the message receiving module, the electronic device 100 can use the information APP to call the interface of the intelligent information cloud server (e.g., interface / getRendData) to download card rendering data from the server 300, carrying the first identifier. For example, the electronic device 100 can send a request message to the server 300, which includes the first identifier and can be used to obtain the card rendering data corresponding to the first identifier. In response to the request message from the electronic device 100, the server 300 can use the data association service to query the card rendering data corresponding to the first identifier, which is integrated into a specific format (e.g., JSON format). Then, the server 300 can use the data association service to deconstruct the card rendering data integrated into the specific format (e.g., JSON format) to obtain the first content of the first short message, the dataset, the template ID, and the card ID, and return a response message containing the deconstructed card rendering data to the electronic device 100 through the first channel.

[0229] S214, Electronic device 100 associates storage message identifier and card rendering data.

[0230] S215. Upon detecting the operation of viewing the first short message, the electronic device 100 calls the card rendering method of the card rendering module.

[0231] S216, Electronic device 100 renders the first card based on card rendering data.

[0232] It is understandable that steps S214-S216 are the same as those mentioned above. Figure 6A Steps S111-S113 are similar to those shown. For a detailed explanation of steps S214-S216, please refer to the foregoing. Figure 6A The relevant textual descriptions in steps S111-S113 shown will not be repeated here.

[0233] It should be noted that steps S201-S206 can be collectively referred to as the card rendering stage, steps S207-S208 can be collectively referred to as the device reporting stage, and steps S209-S216 can be collectively referred to as the card forwarding stage.

[0234] Figures 8A-8F This is a set of schematic diagrams showing the interface for non-enterprise users to forward message cards based on the SMS card sharing method provided in the embodiments of this application.

[0235] For example, such as Figure 8A As shown, the electronic device 200 (source device) can display a user interface 810, which can be the original text interface of a short message from an messaging app. The user interface 810 can include the original short message 811, whose sender could be, for example, xx Express. The original short message 811 could be, for example, “[xx Express] Pick up your package at xx Express locker No. 1, north side of Building 1, xxx Community, using pickup code 8888. If you have any questions, please contact the courier's mobile number xxxxxxxxxxx.” In some examples, the above original short message may not be conveyed to the user through a user interface, but through other means, such as through voice broadcast. Furthermore, the user interface 810 may also include a “display card” control 812, which can be used to convert the original short message into a message card display.

[0236] In some embodiments, the electronic device 200 may receive an operation to convert the original text of a short message into a message card for display (e.g., clicking the "Show Card" control 812), and in response to this operation, the electronic device 200 may display, as shown below. Figure 8B The user interface shown is 820.

[0237] For example, such as Figure 8BAs shown, the electronic device 200 can display a user interface 820, which can be a message card interface for an messaging app. The user interface 820 may include message cards 821, which display key information from the aforementioned original SMS message 811, such as the pickup code, pickup address, courier's mobile phone number, etc. The message card 821 may include one or more card buttons 822, which can be used to trigger specific functions. For example, the "Contact Courier" card button can trigger the electronic device 200 to jump to a dialing interface displaying the courier's mobile phone number, and the "Copy Pickup Code" card button can trigger the electronic device 200 to copy the pickup code. Furthermore, the user interface 820 may also include a "Show Original Message" control 823, which can be used to convert the message card into the original SMS message for display.

[0238] In some embodiments, the electronic device 200 may receive an operation performed on a message card (e.g., a long press operation on message card 821), and in response to the operation, the electronic device 200 may display, as shown below. Figure 8C The user interface 830 is shown. It should be noted that the operation of long-pressing the message card 821 can specifically refer to touching the message card 821 for more than a preset time (e.g., 2 seconds).

[0239] For example, such as Figure 8C As shown, the electronic device 200 can display a user interface 830, which can include one or more options 831 for message cards (e.g., "copy" option, "select" option, "delete" option, "forward" option 831, "more" option). The one or more options 831 can be used to receive operations for message cards. For example, the "forward" option 831 can be used to trigger entry into the contact selection interface so that the user can select one or more objects to forward the message card.

[0240] In some embodiments, the electronic device 200 can receive operations such as forwarding message cards (e.g., clicking the "Forward" option 831), and in response to such operations, the electronic device 200 can display, as shown below. Figure 8D The user interface shown is 840.

[0241] For example, such as Figure 8D As shown, the electronic device 200 can display a user interface 840, which can be a contact selection interface for a messaging app. The user interface 840 can include one or more objects 841 (e.g., contact xx1, contact xx2) for message card forwarding, which can act as the recipient user of the message card.

[0242] In some embodiments, the electronic device 200 may receive an operation to select a forwarding object for a message card (e.g., selecting a contact xx1), and in response to this operation, the electronic device 200 may display, as shown below. Figure 8E The user interface shown is 850.

[0243] For example, such as Figure 8E As shown, the electronic device 200 can display a user interface 850, which may include a prompt box 851. The prompt box 851 may include a prompt message 852 (e.g., "Card content will be forwarded to contact xx1"). In some examples, the prompt message may not be displayed as text but conveyed to the user in other ways, such as through voice announcement. Furthermore, the prompt box 851 may also include a "Cancel" option and an "OK" option 853. The "OK" option 853 can be used to trigger the electronic device 200 to forward the message card to the target device of the message card forwarding object, where the message card can be displayed.

[0244] In some embodiments, electronic device 200 may receive an operation to confirm forwarding a message card to a target device (e.g., clicking the "OK" option 853), and in response to this operation, electronic device 100 (target device) may display as follows: Figure 8F The user interface shown is 860.

[0245] For example, such as Figure 8F As shown, the electronic device 100 can display a user interface 860, which can be a message card interface for an information app. The user interface 860 may include a message card 861, which can be connected to the aforementioned... Figure 8B The message card 821 shown is identical. The message card 861 may include one or more card buttons 862, which can be used to trigger specific functions. For example, the "Contact Courier" card button can trigger the electronic device 100 to jump to a dial interface displaying the courier's mobile phone number, and the "Copy Pickup Code" card button can trigger the electronic device 100 to copy the pickup code. Furthermore, the user interface 860 may also include indication information for the sender of the message card 861. For example, indication information 863 may indicate that the sender of the message card 861 is a user with the mobile phone number xxxxxxxxxxx, where the mobile phone number xxxxxxxxxxx does not contain an enterprise port number, and the user with the mobile phone number xxxxxxxxxxx is a non-enterprise user.

[0246] In this way, the sending user only needs to select the forwarding card and specify the card forwarding target on the source device, and the receiving user can receive the rendered message card on the target device. In addition, the message card includes a card button, so that the receiving user can also click the card button to realize specific functions such as directly accessing web pages or applications, which improves the user's interactive experience with the messaging app.

[0247] Compared to the aforementioned method where the source device and target device communicate through an SMS center to receive and send SMS messages, the SMS card sharing method provided in this application has the following advantages: 1. The sender only needs to select a forwarding card and determine the card forwarding target on the source device, and the receiver can receive the rendered message card on the target device. The sender does not need to select a template and preview the combined effect of the selected template and text when editing the SMS, simplifying user operations. 2. The forwarded message content is a first identifier (e.g., an identification code) rather than a message body containing SMS text and a special identifier carrying the template ID, reducing the message body size transmitted through the message push channel and saving communication resources. 3. The target device only needs to carry the first identifier to obtain the corresponding card rendering data from the cloud server, reducing the number of interactions between the source device, cloud server, and target device. 4. The aforementioned method where the source device and target device communicate through an SMS center to receive and send SMS messages requires the user to pay operator costs (SMS fees). In contrast, the method provided in this application allows the source device and target device to interact via network messages, eliminating the need for the user to pay operator costs. 5. Sharing cards via SMS for marketing businesses can broaden marketing channels and increase merchant revenue.

[0248] It should be noted that the cloud server provided in this application embodiment can record the number of times card rendering data is forwarded to the target device.

[0249] It should be noted that the first identifier provided in the embodiments of this application may be, for example, an identification code, or other identifiers used to map card rendering data, such as short links, etc., and the embodiments of this application do not limit this.

[0250] Based on the embodiments of this application, the sending user only needs to select a forwarding card and determine the card forwarding target on the source device, and the receiving user can then receive the rendered message card on the target device. Furthermore, the sender's indication information on the message card can include the sender's user account (e.g., mobile phone number). Additionally, it can be confirmed through decompiling the information application client and network packet capture that the message received by the receiving user's target device does not contain the original SMS text, but rather includes identifiers such as identification codes and links. Subsequently, the target device can query the card rendering data through an interface.

[0251] This application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a processor, it can implement the steps performed by the electronic device in the above method embodiments, or the steps performed by the human-computer interaction module and the computing module.

[0252] This application also provides a computer program product that, when run on a terminal device, enables the terminal device to perform the steps executed by the electronic device in the above method embodiments.

[0253] This application also provides a chip system, which includes a processor coupled to a memory. The processor executes a computer program stored in the memory to implement the steps performed by the electronic device in any of the method embodiments of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0254] The term "user interface (UI)," or simply "interface," used in the specification and accompanying drawings of this application, refers to the medium through which an application or operating system interacts and exchanges information with the user. It facilitates the conversion between the internal form of information and a form acceptable to the user. The user interface of an application is written in source code using specific computer languages ​​such as Java or Extensible Markup Language (XML). This source code is parsed and rendered on the terminal device, ultimately presenting user-recognizable content, such as images, text, and buttons. Controls, also known as widgets, are the basic elements of the user interface. Typical controls include toolbars, menu bars, text boxes, buttons, scroll bars, images, and text. The attributes and content of controls in the interface are defined using tags or nodes, such as XML tags. <textview> 、 <imgview> 、 <videoview>Nodes define the controls contained in the interface. A node corresponds to a control or property in the interface, and after parsing and rendering, the node is presented as the content visible to the user. In addition, many applications, such as hybrid applications, often contain web pages within their interfaces. A web page, also known as a page, can be understood as a special control embedded in the application interface. Web pages are source code written in a specific computer language, such as Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), JavaScript (JS), etc. Web page source code can be loaded and displayed as user-readable content by a browser or a web page display component with browser-like functionality. The specific content contained in a web page is also defined through tags or nodes in the web page source code; for example, HTML uses tags or nodes to define the content. 、 、 <video> 、 <canvas>To define the elements and attributes of a webpage.

[0255] The most common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an icon, window, control, or other interface element displayed on the screen of an electronic device. Controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

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

[0257] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0258] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if..." or "after..." or "in response to determining..." or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is detected" can be interpreted as meaning "if determining..." or "in response to determining..." or "when (the stated condition or event) is detected" or "in response to detecting (the stated condition or event)".

[0259] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0260] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.< / canvas> < / video> < / videoview> < / imgview> < / textview>

Claims

1. A method for sharing short message cards, applied to a first electronic device, characterized in that, The method includes: The first short message is received by the second electronic device through the first channel. The first short message is a first type of short message received by the second electronic device through the second channel and displayed in a first card style. An operation to view the first short message was detected; In response to the operation of viewing the first short message, a first card is displayed, and the first card displays the first short message in the style of the first card.

2. The method of claim 1, wherein, The first short message includes a first identifier, which is used to indicate card rendering data uploaded by the second electronic device to the first server. The card rendering data includes a first content of the first short message and data for rendering the style of the first card. The card rendering data is used to display the first short message in the style of the first card.

3. The method according to claim 2, characterized in that, After receiving the first short message sent by the second electronic device through the first channel, the method further includes: Send a request message to the first server, the request message including the first identifier, the request message being used to obtain the card rendering data corresponding to the first identifier; Receive a response message containing the card rendering data sent by the first server, and store the card rendering data; The display of the first card specifically includes: The data displayed based on the card is the first card.

4. The method of claim 1, wherein, The first short message includes card rendering data, which includes first content of the first short message and data for rendering the style of the first card. The card rendering data is used to display the first short message in the style of the first card. The display of the first card specifically includes: The data displayed based on the card is the first card.

5. The method according to any one of claims 2-4, characterized in that, The data used to render the style of the first card includes a card ID, a template ID, and a dataset. The card ID indicates the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID indicates the specific content in the data structure.

6. The method according to any one of claims 1 to 5, characterized in that, The first channel is the network channel, and the second channel is the carrier channel. 7.A method for sharing a short message card, applied to a second electronic device, the method comprising: The method includes: The first short message is received through the second channel, and the first short message is a first type of short message. Upon detecting an operation to view the first short message, a first card is displayed, showing the first short message in a first card style; Upon detecting an operation to forward the first card to a first electronic device, card rendering data is sent to the first electronic device via a first channel. The card rendering data is used by the first electronic device to display the first card when the user views the first short message.

8. The method of claim 7, wherein, The card rendering data includes the first content of the first short message and data for rendering the style of the first card. The data for rendering the style of the first card includes a card ID, a template ID, and a dataset. The card ID is used to indicate the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID is used to indicate the specific content in the data structure.

9. The method according to claim 7 or 8, characterized in that, The step of sending card rendering data to the first electronic device through the first channel specifically includes: The card rendering data is forwarded from the first server to the first electronic device.

10. The method of claim 8, wherein, The step of sending card rendering data to the first electronic device through the first channel specifically includes: The first content of the first short message and the context identifier of the first short message are sent to the first server through the first channel. The context identifier is used to indicate the data for rendering the style of the first card. The context identifier is used by the first server to obtain the data for rendering the style of the first card. The card rendering data is sent by the first server to the first electronic device through the first channel after integrating the first content and the data for rendering the style of the first card.

11. The method according to any one of claims 7-10, characterized in that, The first channel is the network channel, and the second channel is the carrier channel.

12. A short message card sharing method applied to a first server, characterized in that, The method includes: The first short message is received by the second electronic device through the first channel. The first short message is a first type of short message received by the second electronic device through the second channel and displayed in the style of a first card. The first short message is sent by the second electronic device to the first server after detecting the operation of forwarding the first card to the first electronic device. The first card displays the first short message in the style of the first card. Card rendering data is sent to the first electronic device through the first channel. The card rendering data is used by the first electronic device to display the first card. The card rendering data is obtained by the first server based on the first short message.

13. The method of claim 12, wherein, The card rendering data includes the first content of the first short message and data for rendering the style of the first card. The data for rendering the style of the first card includes a card ID, a template ID, and a dataset. The card ID is used to indicate the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID is used to indicate the specific content in the data structure.

14. The method according to claim 12 or 13, characterized in that, The first short message includes the card rendering data.

15. The method of claim 13, wherein, The first short message includes a first content and a context identifier, the context identifier indicating the data used to render the style of the first card. After receiving the first short message sent by the second electronic device through the first channel, the method further includes: The data used to render the style of the first card is obtained based on the scenario identifier; The first content and the data used to render the style of the first card are integrated into the card rendering data.

16. The method according to any one of claims 12-15, characterized in that, The step of sending card rendering data to the first electronic device through the first channel specifically includes: A first identifier is generated based on the card rendering data, and the first identifier is used to indicate the card rendering data; The first identifier is sent to the first electronic device through the first channel; A request message is received from the first electronic device, the request message including the first identifier, and the request message is used to obtain the card rendering data corresponding to the first identifier; In response to the request message, a response message containing the card rendering data is sent to the first electronic device through the first channel.

17. The method of claim 16, wherein, Sending the first identifier to the first electronic device through the first channel specifically includes: The message containing the first identifier is sent to the first electronic device through the first channel.

18. The method according to any one of claims 12-17, characterized in that, The first channel is the network channel, and the second channel is the carrier channel.

19. A short message card sharing method applied to a first communication system, characterized by, The first communication system includes a first electronic device and a second electronic device, and the method includes: The second electronic device receives the first short message through the second channel, and the first short message is a first type of short message; Upon detecting an operation to view the first short message, the second electronic device displays a first card, which shows the first short message in a first card style. The second electronic device detects the operation of forwarding the first card to the first electronic device; The first electronic device receives the first short message through the first channel; Upon detecting an action to view the first short message, the first electronic device displays the first card.

20. The method of claim 19, wherein, The first communication system further includes a first server, and after the second electronic device detects an operation to forward the first card to the first electronic device, the method further includes: The second electronic device sends the first short message to the first server through the first channel; The first server sends card rendering data to the first electronic device through the first channel. The card rendering data is used by the first electronic device to display the first card. The card rendering data is obtained by the first server based on the first short message.

21. The method of claim 20, wherein, The card rendering data includes the first content of the first short message and data for rendering the style of the first card. The data for rendering the style of the first card includes a card ID, a template ID, and a dataset. The card ID is used to indicate the layout style of the first card, the dataset is the data structure corresponding to the layout style, and the template ID is used to indicate the specific content in the data structure.

22. The method of claim 20 or 21, wherein, The first short message includes the card rendering data.

23. The method of claim 21, wherein, The first short message includes a first content and a context identifier, the context identifier indicating the data used to render the style of the first card. After the second electronic device sends the first short message to the first server through the first channel, the method further includes: The first server obtains the data for rendering the style of the first card based on the scenario identifier; The first server integrates the first content and the data used to render the style of the first card into the card rendering data.

24. The method of any one of claims 20-23, wherein, The first server sends card rendering data to the first electronic device through the first channel, specifically including: The first server generates a first identifier based on the card rendering data, and the first identifier is used to indicate the card rendering data; The first server sends the first identifier to the first electronic device through the first channel; The first electronic device sends a request message to the first server. The request message includes the first identifier and is used to obtain the card rendering data corresponding to the first identifier. In response to the request message, the first server sends a response message containing the card rendering data to the first electronic device through the first channel.

25. The method according to claim 24, characterized in that, The first server sends the first identifier to the first electronic device through the first channel, specifically including: The first server sends a message containing the first identifier to the first electronic device through the first channel.

26. The method of any one of claims 19-25, wherein, The first channel is the network channel, and the second channel is the carrier channel.

27. A communication system, characterized by It includes a first electronic device, a second electronic device, and a first server; wherein, there is a communication connection between the first electronic device, the first server, and the second electronic device; the first electronic device is the electronic device according to any one of claims 1-6, the second electronic device is the electronic device according to any one of claims 7-11, and the first server is the electronic device according to any one of claims 12-18.

28. An electronic device, comprising: The electronic device includes a processor and a memory; wherein the memory is coupled to the processor and is used to store a computer program that, when executed by the processor, causes the electronic device to perform the method as described in any one of claims 1-6, 7-11, or 12-18.

29. A computer storage medium, comprising, The computer storage medium stores a computer program that, when executed by a processor, causes the electronic device to perform the method as described in any one of claims 1-26.

30. A computer program product comprising a computer program, characterised in that, When the computer program is executed by a processor, it causes the electronic device to perform the method as described in any one of claims 1-26.

Images