Method and system for sharing event, electronic equipment and storage medium

Abstract

The invention discloses an event sharing method and system, electronic equipment and a storage medium. The method comprises: receiving, by a first user device, a selection of an interface element for generating an event invitation by a first user; in response to a selection of an interface element for generating an event invitation, displaying an event invitation editing interface on a user interface of the first user device; receiving, by the first user device, a selection of one of a plurality of predefined templates by the first user; receiving, by the first user device, customized content input by a first user; generating, by the first user device, an event invitation, where generating the event invitation includes: presenting the event invitation in an appearance layout corresponding to the selected predefined template; and adding the customized content to the event invitation, and sending the generated event invitation to a second user device of the second user. The method solves the technical problems of single event invitation form and low information transmission efficiency in the prior art.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more particularly to a method, system, electronic device, and storage medium for sharing events. Background Technology

[0002] In the mobile internet application ecosystem, users complete various events across multiple applications daily. There is a need to share these events as an "invitation" with others. However, current methods of sharing events have the following limitations.

[0003] Firstly, the most common method is to capture screenshots of order details or copy text links and send them via social media or instant messaging apps. Recipients cannot directly and intuitively obtain key information, nor can they interact with the original booking resources, resulting in low information utility. Furthermore, existing event sharing methods do not support custom content input and all content is presented in the same style. They also fail to provide feedback channels for recipients. The initiator may need to manually identify and track the response status of invitees, a tedious and error-prone process.

[0004] In summary, existing technologies lack a solution that can share events in a customized manner based on event type and easily obtain feedback from invitees. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a method, system, electronic device, and storage medium for sharing events.

[0006] This invention implements a method for sharing events. This method supports user-customized content and user-associated media items. It can generate event invitations with matching visual layouts based on the event type. This solves the technical problems of existing event invitations having limited formats and low information transmission efficiency.

[0007] To achieve the above objectives, according to one aspect of the present invention, a method for sharing events is provided.

[0008] An embodiment of the present invention provides a method for sharing an event, comprising: receiving, by a first user device, a selection by a first user of an interface element for generating an event invitation; in response to the selection of the interface element for generating the event invitation, displaying an event invitation editing interface on the user interface of the first user device; on the event invitation editing interface, receiving, by the first user device, a selection by the first user of one of a plurality of predefined templates, wherein each of the plurality of predefined templates corresponds to a different appearance layout; on the event invitation editing interface, receiving, by the first user device, customized content input by the first user; generating an event invitation by the first user device, wherein generating the event invitation comprises: presenting the event invitation with an appearance layout corresponding to the selected predefined template; adding the customized content to the event invitation; and sending the generated event invitation by the first user device to a second user device of a second user.

[0009] In one embodiment, the method for sharing an event further includes: receiving additional content input by the first user equipment, the additional content including one or more of the following: text, images, audio, and video; and adding the additional content to the event invitation by the first user equipment.

[0010] In yet another embodiment, the method for sharing an event further includes: presenting a notification of the event invitation on the user interface of the second user device; receiving a selection of the notification by the second user from the second user device; and, in response to the selection of the notification by the second user device, presenting the event invitation on the user interface of the second user device in an appearance layout corresponding to the selected template.

[0011] In yet another embodiment, the method for sharing an event further includes: receiving, by the second user device, a selection by the second user of an interface element for adding a schedule reminder; and, in response to the selection of the interface element for adding a schedule reminder, adding a schedule reminder for the event on the second user device.

[0012] In yet another embodiment, the method for sharing an event further includes: receiving, by the second user equipment, the second user's selection of an interface element for accepting the event; and displaying, on the user interface of the first user equipment, that the second user has accepted the event.

[0013] In yet another embodiment, the method for sharing events further includes: receiving feedback information input by the second user from the second user equipment, wherein the feedback information includes one or more of the following: user preferences, number of companions, location selection, gifts, and messages; and sending the feedback information from the second user equipment to the first user equipment for the first user to view.

[0014] To achieve the above objectives, according to another aspect of the present invention, a system for sharing events is provided.

[0015] A system for sharing events according to the present invention includes: a first device configured to: receive a first user's selection of interface elements for generating an event invitation; in response to the selection of the interface elements for generating the event invitation, display an event invitation editing interface on the user interface of the first device; on the event invitation editing interface, receive the first user's selection of one of a plurality of predefined templates, wherein each of the plurality of predefined templates corresponds to a different appearance layout; on the event invitation editing interface, receive customized content input by the first user; generate an event invitation, wherein generating the event invitation includes: presenting the event invitation with an appearance layout corresponding to the selected predefined template; adding the customized content to the event invitation; and sending the generated event invitation to a second device of a second user.

[0016] In one embodiment, the first device is further configured to: receive additional content input by the first user, the additional content including one or more of the following: text, images, audio, and video; and add the additional content to the event invitation.

[0017] In yet another embodiment, the system for sharing events further includes: a second device configured to: present a notification of the event invitation on a user interface of the second device; receive a selection of the notification by a second user; and, in response to the selection of the notification by the second user, present the event invitation on the user interface of the second device in an appearance layout corresponding to the selected template.

[0018] In yet another embodiment, the second device is further configured to: receive a selection by the second user of an interface element for adding a schedule reminder; and, in response to the selection of the interface element for adding a schedule reminder, add a schedule reminder for the event on the second device.

[0019] In yet another embodiment, the second device is further configured to: receive the second user's selection of an interface element for accepting an event; and the first device is further configured to display on the user interface of the first device that the second user has accepted the event.

[0020] In yet another embodiment, the second device is further configured to: receive feedback information input by the second user, wherein the feedback information includes one or more of the following: user preferences, number of companions, location selection, gifts, and messages; and send the feedback information to the first device for the first user to view.

[0021] To achieve the above objectives, according to another aspect of the present invention, an electronic device is provided.

[0022] An electronic device according to an embodiment of the present invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for sharing events provided in the embodiment of the present invention.

[0023] To achieve the above objectives, according to another aspect of the present invention, a computer-readable medium is provided.

[0024] An embodiment of the present invention provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method for sharing events provided in the embodiment of the present invention.

[0025] This invention also provides a computer program product, including a computer program that, when executed by a processor, implements the method for sharing events provided in this invention.

[0026] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0027] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0028] Figure 1 This is an application environment diagram of a method for sharing events according to an embodiment of the present invention;

[0029] Figure 2 This is a flowchart illustrating a method for sharing events according to an embodiment of the present invention;

[0030] Figure 3A , Figure 3B , Figure 3C , Figure 3D , Figure 3E and Figure 3F This is an example user interface for a method of sharing events according to an embodiment of the present invention;

[0031] Figure 4 This is a schematic diagram of the main units of an apparatus for sharing events according to an embodiment of the present invention;

[0032] Figure 5 This is a schematic diagram of the structure of a computer system suitable for implementing embodiments of the present invention. Detailed Implementation

[0033] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0034] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0035] This invention provides a method for sharing events, which can be used in scenarios where events are shared with other users, such as restaurant reservations, KTV reservations, movie tickets, hotel bookings, and airline tickets.

[0036] Figure 1 This is an application environment diagram of a method for sharing events according to an embodiment of the present invention. Figure 1 The system architecture 100 shown includes multiple terminal devices 101, 102, and 103, a network 105, and a server 104. Network 105 serves as the medium for providing communication links between the terminal devices 101, 102, and 103 and the server 104. Network 105 can include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0037] Users can use terminal devices 101, 102, and 103 to interact with server 104 via network 105 to receive or send messages, etc. Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers. Various client applications, such as food ordering applications, can be installed on terminal devices 101, 102, and 103.

[0038] Server 104 can be a server that provides various services, such as based on input sent by users using terminal devices 101, 102, and 103, for example, content associated with a food order event. The server can process the received input and feed back the processing results to the terminal devices, for example, sending a generated food order event invitation to the terminal devices.

[0039] It should be noted that the method for sharing events provided in the embodiments of the present invention is generally executed by server 104, and correspondingly, the device for sharing events is generally located in server 104.

[0040] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0041] This invention provides a method for sharing events, which can be provided by... Figure 1 The server 104 in the system architecture 100 shown executes, as follows: Figure 2 As shown, the method includes the following steps.

[0042] S201: The first user equipment receives the first user's selection of the interface element used to generate the event invitation.

[0043] In this scenario, the first user can be either the initiator or a participant in the event. After the first user completes the event within the app, their device can display user interface elements for sharing the event. The first user can then select these user interface elements to initiate event sharing.

[0044] S202: In response to the selection of the interface element used to generate the event invitation, the event invitation editing interface is displayed on the user interface of the first user device.

[0045] The first user can enter content related to the event in the event invitation editing interface.

[0046] Figure 3A and Figure 3B This is an example user interface for restaurant reservations according to an embodiment of the present invention. In one embodiment, reference is made to... Figure 3AAs shown, a first user can use a restaurant reservation app to make a reservation. Once the first user completes the reservation, a reservation success screen 300a will appear on the first user's device. This reservation success screen 300a includes an interface element 301 for generating an event invitation, such as a button 301. Alternatively or additionally, the first user's device may also display an order confirmation screen after ordering, and this confirmation screen may include an interface element for generating an event invitation. Furthermore, the first user can initiate a sharing process for this restaurant reservation event by selecting the interface element for generating the event invitation. Once the first user selects this user interface element, the first user's device will display... Figure 3B The event invitation editing interface 300b is shown below. The first user can enter content related to the event in the event invitation editing interface 300b.

[0047] S203: On the event invitation editing interface, the first user device receives the first user's selection of one of a plurality of predefined templates.

[0048] Each of the multiple predefined templates corresponds to a different appearance layout. The appearance layout can include the content data structure within the invitation, information expression methods, color schemes, fonts, background patterns, interactive animations, etc. Using different styles for different events enables intelligent and automated adaptation between events and event invitation styles.

[0049] In restaurant reservation scenarios, responding to the first user's choice Figure 3B Element 307, the "Casual Dinner Template," determines whether the event invitation's characteristics are switched to "Casual Dinner." The "Casual Dinner Template" can correspond to a lively, celebratory style, unlike the clean, professional style used in the original "Business Dinner Template." Furthermore, the information structure (e.g., whether a menu is displayed, the purpose of the order, etc.) in the "Casual Dinner Template" and the original "Business Dinner Template" may also differ.

[0050] S204: On the event invitation editing interface, the first user device receives customized content input by the first user.

[0051] First-time users can personalize event invitations. They can add various customizable content related to the event, including but not limited to handwritten signatures, handwritten free text, and AI-generated text. This custom content, combined with the invitation itself as a trusted identity identifier, enhances the authenticity of the invitation.

[0052] S205: An event invitation is generated by the first user equipment.

[0053] Generating the event invitation includes: presenting the event invitation with an appearance layout corresponding to the selected predefined template; and adding customized content to the event invitation.

[0054] In an example of a food ordering scenario, such as Figure 3B As shown in the event invitation editing interface 300b, the first user is presented with this interface to differentiate and personalize the event. If the first user selects a business banquet booking template in the event invitation editing interface 300b, the event invitation is presented with the corresponding layout. The event invitation editing interface 300b supports the first user inputting a handwritten signature. The first user can select the initiator editing element 302 to input the signature. In response to the first user selecting the initiator editing element 302, the following is presented to the user: Figure 3C The example user interface 300c shown is for inputting a signature. Example user interface 300c includes a handwritten signature element 303 for the first user to add a personalized handwritten signature item. After the first user saves the handwritten signature item, the initiator section of the event invitation editing interface is updated to add the same content as the user's handwritten signature item to the event invitation, such as... Figure 3D The example user interface 300b is shown in section 304 of example user interface 300d. Alternatively, the first user can also type their signature by selecting a keyboard input element, and in this case, section 304 of example user interface 300b will display the user's signature in a predefined non-handwritten font. Additionally or alternatively, although not shown, example user interface 300c may also include other user interface elements for the user to handwrite free text to supplement other content such as the invitee, purpose, or well wishes.

[0055] The first user device can receive additional content input by the first user, including one or more of the following: text, images, audio, and video. The first user device adds the additional content to the event invitation. In one embodiment, the first user can input text to supplement the event description, add helpful tips, or express personal feelings. Alternatively, the first user can input media content items to enrich the visual and emotional expression of the event; for example, they can upload images, audio, or video related to the event. This event-sharing method can integrate multiple media content such as text, images, audio, and video into a single shared event information, thereby increasing the information capacity.

[0056] In an example of a food ordering scenario, the first user can select relevant elements in the event invitation editing interface, for example, Figure 3B The receiver input element 305 is used to supplement the receiver name. The first user can append or alternatively select other elements (although not in the...). Figure 3B(As shown in the image) users can enter other text related to the order, such as purpose, dietary needs, or location directions. First-time users can also upload locally saved or captured images or videos, such as photos of the restaurant environment or reference images of the ordered dishes. Alternatively or additionally, first-time users can also upload pre-recorded audio or captured audio, allowing the event invitation to not only include order data but also comprehensively present event-related information in multiple ways.

[0057] The event invitation editing interface also provides a screen element for sharing event details. The first user selects this screen element to share event details. Then, the first user's device adds the event details to the event invitation. The event details are stored in a predefined data source related to the current event. The first user can easily add event details to the event invitation without complex searching and uploading processes.

[0058] In the example of a food ordering scenario, the event details are the menu. For example... Figure 3B As shown in the event invitation editing interface 300b, once the interface element 306 for sharing event details is selected, the latest, structured menu data will be pulled from the associated data source (e.g., a list of dishes ordered by the user or the restaurant's complete menu database) and added to the predetermined position in the event invitation. By using the interface element for sharing event details, users are no longer required to manually collect and upload information, while ensuring the accuracy of the information.

[0059] Based on the selected predefined template, the received content and context data are added to the invitation template and information architecture to generate an event invitation. For example, in a restaurant reservation scenario, such as... Figure 3E As shown in the example user interface 300e, the "Location" field of the template is filled with "Restaurant Address" data, and user-uploaded food images are embedded in the image display area. Various content is arranged in the event invitation, such as displaying food images in a card waterfall layout.

[0060] Event invitations are typically generated as cross-platform accessible URLs, ensuring that recipients can fully receive rich, interactive shared event invitations via standard web technologies, regardless of the device they use or whether they have the event app installed.

[0061] S205: The first user equipment sends the generated event invitation to the second user equipment of the second user.

[0062] The second user is an invitee or other participant in the event. In response to the first user's sending instruction, a list of contacts can be presented to the first user, allowing the first user to specify identifiers for one or more second users, such as phone numbers, social media accounts, or email addresses. Based on the second user's identifier, an event invitation is sent to a reachable address on the second user's device.

[0063] For example, in restaurant reservation scenarios, such as Figure 3E As shown in the example user interface 300e, a first user can select the "Share with Friends" element 308. In response to the first user selecting the "Share with Friends" element 308, a contact list, such as a friend list on the user's social media platform, can be presented to the first user. The user can then select one or more second users from the friend list to send event invitations to the second users.

[0064] In a further embodiment, the event invitation notification is presented on the user interface of the second user device. When sending an event invitation using an instant messaging app, the accessible link of the event invitation can be encapsulated into a card-style message or mini-program format recognizable by the instant messaging app and pushed out, possibly with automatically generated guiding text, such as: "You have received a dinner invitation. Click to view details and confirm your attendance." For SMS or email sending methods: the link can be embedded as a shortened URL, combined with a plain text summary of the core information, to ensure that basic information is still accessible in environments where rich media content cannot be rendered. For internal system sending methods, if the second user is also an event app user, the complete event invitation is sent directly via in-app push. By generating the event invitation as a cross-platform accessible link and adapting to multiple sharing channels, the breadth and convenience of event invitation reach are ensured.

[0065] The second user equipment receives the second user's selection of the notification. In response to the second user's selection of the notification, the event invitation is presented on the user interface of the second user equipment with an appearance layout corresponding to the selected template.

[0066] When a second user selects an event invitation on their device, an animation matching the event is rendered first, before the full event invitation content is loaded. This animation is not singular or fixed, but corresponds to a predefined template previously selected by the first user. When the second user's device parses the event invitation data, it first identifies and loads the animation. The animation will play in full-screen or half-screen mode in the application window or browser page, typically lasting 1-3 seconds. The animation extends the visual layout of the predefined template, reinforcing the type and style of the event. For example, if the predefined template selected by the first user is a business dinner template, the animation can be presented in a darker color, along with formal audio. If the predefined template selected by the first user is a casual party template, the animation can be presented in a lighter color, along with upbeat audio.

[0067] After the animation finishes playing, the system renders the full interactive interface of the event invitation. At this time, the second user can engage in rich multimodal interactions with the event invitation. These interactions are recorded in real time and fed back to the first user's device for presentation to the first user.

[0068] The second user can view images, play audio and video recordings related to the event uploaded by the first user to obtain information about the event. For example, in a restaurant reservation scenario, the second user can click on the address information to invoke a map application for navigation, or click on the video uploaded by the first user to view its details.

[0069] In an additional embodiment, the second user device receives a selection from the second user of an interface element for adding a schedule reminder. In response to the selection of the interface element, a schedule reminder for the event is added on the second user device. The event invitation may include the interface element for adding a schedule reminder. In response to the second user's triggering of the interface element for adding a schedule reminder, key parameters are extracted from the event invitation's data object, including but not limited to: event title, start time, end time, and location. Based on these parameters, a schedule data object is generated and pre-populated into a default or user-specified schedule application to generate a schedule to-do item and set a reminder. Transforming events into personal schedules reduces the time cost and error probability of the second user manually entering information and effectively avoids absences due to forgetfulness, thereby improving the overall efficiency of event organization.

[0070] In another embodiment, the second user equipment receives the second user's selection of interface elements for accepting the event. The user interface of the first user equipment displays that the second user has accepted the event. The user interface of the second user equipment may present participation intention interface elements, such as "Participate," "Decline," and "Pending" buttons. The second user can input their participation intention by selecting a participation intention interface element. The second user's participation intention is recorded and fed back to the first user. On the first user equipment, the user interface updates the second user's participation intention. Upon receiving an update regarding the second user's acceptance status, the second user's participation intention can be dynamically and visually presented on the user interface of the first user equipment. For example, in an embodiment of a restaurant reservation scenario, such as... Figure 3F As shown in the example user interface 300f, the participation intention of the second user can be displayed in real time. This constructs a data loop from "sharing" to "feedback," presenting it to the first user in a visual manner, thus solving the problem of requiring the first user to manually collect participation statistics.

[0071] In an additional embodiment, the second user equipment receives feedback information input by the second user, wherein the feedback information includes one or more of the following: user preferences, number of companions, location selection, gifts, and messages. The second user equipment then sends the feedback information to the first user equipment for the first user to view.

[0072] A set of UI elements for feedback can be presented on the user interface of the second user device. This set of UI elements can be presented in the form of a conditionally triggered form. The set of UI elements can include one or more of the following: user preference elements, location selection elements, companion elements, gift elements, and message elements.

[0073] In one embodiment, after the second user selects a user preference element, a preference input interface can be presented to the second user so that the second user can input their preferences. For example, in an embodiment of a food ordering event, user preferences may include taste, dishes, food allergies, etc. In an embodiment of a movie ticket ordering event, user preferences may include preferred movies, etc. In an embodiment of an entertainment event such as an escape room / KTV, user preferences may include theme or difficulty preferences, role preferences, etc. In an embodiment of a travel event, user preferences may include transportation preferences, accommodation preferences, etc.

[0074] In another embodiment, after the second user selects the companion element, a companion input interface can be presented to the second user so that the second user can input the number of companions and / or specific names.

[0075] In another embodiment, after the second user selects a location selection element, a location input interface can be presented to the second user so that the second user can input their location selection. For example, in embodiments involving ordering food or movie tickets, a seating chart can be presented to the second user so that the second user can select a seat. In embodiments involving travel, a transportation seating chart or hotel room chart can be presented to the second user so that the second user can select a seat or room. The first user can have location management permissions and can predefine locations and lock seats. Alternatively, a smart assignment method can be used to assign locations to the second user without requiring the second user to select a location.

[0076] In another embodiment, after the second user selects a gift element, a gift list can be presented to the second user. Gifts can be virtual objects, such as e-red envelopes, platform vouchers, event-related digital emoticons, or souvenirs. Gifts can also be physical objects. The second user can be presented with a list of recommended physical objects, and can select an object within the event invitation and pay for it as a gift to the first user. Logistics delivery can be completed based on the first user's anonymized address or the address entered by the first user. Gifts can also be services, such as ordering desserts or drinks for the first user, or sharing part of the event costs.

[0077] In another embodiment, after the second user selects a message element, a message interface can be presented to the second user. The second user enters content in the message interface, including but not limited to: predefined greetings, entered text, and digital greeting cards. The second user can publish messages in the form of text, images, audio, and video. After review, messages can be compiled into a "blessing wall" and / or an electronic commemorative album, allowing user interactions to be retained long-term.

[0078] In the second user device, conditionally triggered forms can be used to guide the second user to input this feedback information. This unstructured feedback information can then be transformed into tagged, visualized data and sent to the first user device in real time. The first user device can receive and aggregate the feedback information from the second user and present it on its user interface for the first user to view and manage. This method establishes a two-way data flow channel, enabling the collection and visualization of the recipient's participation feedback, thereby solving the problems of scattered feedback information and inconvenient statistical analysis.

[0079] Therefore, this invention provides a scenario-based, multimedia-rich, and bidirectional method for sharing events to solve the technical problems of existing methods for sharing events being monotonous in form, having low information transmission efficiency, and being inconvenient for feedback information statistics.

[0080] It should be understood that the above-described embodiment using restaurant reservation as an example is only for clearly demonstrating the technical solution of the present invention, and is not intended to limit the scope of protection of the present invention. The method for sharing events proposed in this invention has a high degree of universality and configurability in its core architecture and method. In practical applications, this method, through its internally configurable data access and mapping unit, can flexibly adapt to a variety of different event scenarios. For example, in a ticketing scenario, one can purchase movie tickets, concert tickets, theater tickets, sports event tickets, etc., in a ticketing app and share them with other users. In a travel scenario, one can book airline tickets in a travel app, book accommodation in a hotel app, and book vehicles in a car rental platform, and share the travel event. In a daily consumption scenario, one can book personal training sessions in a fitness app, book a spa in a beauty app, and book housekeeping services in a repair platform, and share them with family or friends. This invention can also be applied to office scenarios; for example, one can book online / offline meetings in an office app and generate meeting invitations. Therefore, any event sharing technical solution based on the core idea of ​​this invention, regardless of its specific business field, should be considered to fall within the scope of protection sought by this invention. After reading the above embodiments, those skilled in the art will be able to apply the present invention to other similar business scenarios without any creative effort.

[0081] like Figure 4As shown. This embodiment of the invention provides a system 400 for sharing events, the system 400 comprising:

[0082] A first device 401 is configured to: receive a first user's selection of an interface element for generating an event invitation; in response to the selection of the interface element for generating the event invitation, display an event invitation editing interface on the user interface of the first device 401; on the event invitation editing interface, receive the first user's selection of one of a plurality of predefined templates, wherein each of the plurality of predefined templates corresponds to a different appearance layout; on the event invitation editing interface, receive customized content input by the first user; generate an event invitation, wherein generating the event invitation includes: presenting the event invitation with an appearance layout corresponding to the selected predefined template; adding the customized content to the event invitation; and sending the generated event invitation to a second device 402 of a second user.

[0083] In one embodiment, the first device 401 is further configured to: receive additional content input by the first user, the additional content including one or more of the following: text, images, audio, and video; and add the additional content to the event invitation.

[0084] In yet another embodiment, the system for sharing events further includes: a second device 402 configured to: present a notification of the event invitation on a user interface of the second device 402; receive a selection of the notification by a second user; and, in response to the selection of the notification by the second user, present the event invitation on the user interface of the second device 402 in an appearance layout corresponding to the selected template.

[0085] In yet another embodiment, the second device 402 is further configured to: receive selections from the second user for an interface element used to add a schedule reminder; and, in response to the selection of the interface element for adding a schedule reminder, add a schedule reminder for the event on the second device 402.

[0086] In yet another embodiment, the second device 402 is further configured to: receive the second user's selection of an interface element for accepting an event; and the first device 401 is further configured to display on the user interface of the first device 401 that the second user has accepted the event.

[0087] In yet another embodiment, the second device 402 is further configured to: receive feedback information input by the second user, wherein the feedback information includes one or more of the following: user preferences, number of companions, location selection, gifts, and messages; and send the feedback information to the first device 402 for the first user to view.

[0088] It should be understood that the manner in which embodiments of the present invention are implemented is different from the implementation method. Figure 2 The embodiments shown are the same and will not be described again here.

[0089] According to embodiments of the present invention, an electronic device is also provided.

[0090] An electronic device according to an embodiment of the present invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the method for sharing events provided in the embodiment of the present invention.

[0091] According to embodiments of the present invention, a readable storage medium is also provided.

[0092] An embodiment of the present invention provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the method for sharing events provided in the embodiment of the present invention.

[0093] The following is for reference. Figure 5 It shows a schematic diagram of the structure of a computer system 500 suitable for implementing embodiments of the present invention. Figure 5 The computer system shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.

[0094] like Figure 5 As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 502 or programs loaded from storage section 508 into random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the system 500. The CPU 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0095] The following components are connected to I / O interface 505: an input section 506 including a keyboard, mouse, etc.; an output section 507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN card, modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to I / O interface 505 as needed. A removable medium 511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 510 as needed so that computer programs read from it can be installed into storage section 508 as needed.

[0096] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 509, and / or installed from removable medium 511. When the computer program is executed by central processing unit (CPU) 501, it performs the functions defined above in the system of this invention.

[0097] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0098] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a unit, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0099] The units described in the embodiments of the present invention can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor can be described as including an acquisition unit, a processing unit, a benchmark rate table determination unit, and a premium determination unit. The names of these units do not necessarily limit the specific unit; for example, the acquisition unit can also be described as "a unit that performs the functions of the acquisition unit."

[0100] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs that, when executed by the device, cause the device to perform the method for sharing events provided by the present invention.

[0101] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for sharing an event, characterized by, comprising: receiving, by a first user device, a selection of an interface element for generating an event invitation by a first user; in response to the selection of the interface element for generating an event invitation, displaying an event invitation editing interface on a user interface of the first user device; receiving, by the first user device, a selection of one of a plurality of predefined templates on the event invitation editing interface by the first user, wherein each of the plurality of predefined templates corresponds to a different appearance layout; receiving, by the first user device, custom content input by the first user on the event invitation editing interface; generating, by the first user device, an event invitation, wherein generating the event invitation comprises rendering the event invitation in the appearance layout corresponding to the selected predefined template and adding the custom content to the event invitation, and transmitting, by the first user device, the generated event invitation to a second user device of a second user.

2. The method of claim 1, wherein, further comprising: receiving, by the first user device, additional content input by the first user, the additional content comprising one or more of: text, image, audio, and video; and adding, by the first user device, the additional content to the event invitation.

3. The method of claim 1, wherein, further comprising: presenting a notification of the event invitation on a user interface of the second user device; receiving, by the second user device, a selection of the notification by the second user; and in response to the selection of the notification by the second user, presenting the event invitation on a user interface of the second user device in the appearance layout corresponding to the selected template.

4. The method of claim 1, wherein, further comprising: receiving, by the second user device, a selection of an interface element for adding a calendar reminder by the second user; and in response to the selection of the interface element for adding a calendar reminder, adding a calendar reminder of the event on the second user device.

5. The method of claim 1, wherein, further comprising: receiving, by the second user device, a selection of an interface element for accepting the event by the second user; and displaying, on a user interface of the first user device, that the second user has accepted the event.

6. The method according to any one of claims 1-5, characterized in that, further comprising: receiving, by the second user device, feedback information input by the second user, wherein the feedback information comprises one or more of: user preferences, number of attendees, location selection, gift, and message; and transmitting, by the second user device, the feedback information to the first user device for viewing by the first user.

7. A system for sharing events, characterized by comprising: a first apparatus configured to: receive a selection of an interface element for generating an event invitation by a first user; in response to the selection of the interface element for generating an event invitation, display an event invitation editing interface on a user interface of the first apparatus; receive a selection of one of a plurality of predefined templates on the event invitation editing interface by the first user, wherein each of the plurality of predefined templates corresponds to a different appearance layout; receive custom content input by the first user on the event invitation editing interface; generate an event invitation, wherein generating the event invitation comprises: presenting the event invitation in an appearance layout corresponding to the selected predefined template; and adding the custom content to the event invitation, and sending the generated event invitation to a second device of a second user.

8. The system of claim 7, wherein, further comprising: the second device being configured to: present a notification of the event invitation on a user interface of the second device; receive a selection of the notification by the second user; and in response to the selection of the notification by the second user, present the event invitation on a user interface of the second device in the appearance layout corresponding to the selected template. comprising:

9. An electronic device, comprising: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by the one or more processors, cause the one or more processors to carry out the method according to any one of claims 1-6. the computer program which when executed by a processor carries out the method according to any one of claims 1-6.

10. A computer readable medium having stored thereon a computer program, characterized in that, ​

Images