Information sharing method, device, electronic device and storage medium

Abstract

The present application discloses an information sharing method, device, electronic device and storage medium, belonging to the technical field of electronic devices. The method is applied to a first electronic device, and the method comprises: receiving a first input from a first user; in response to the first input, when a screenshot image corresponding to the first input is associated with schedule information, sending a schedule sharing object to a second user; wherein the schedule sharing object is determined according to the schedule information.

Description

Technical Field

[0001] The present application belongs to the technical field of electronic equipment, and specifically relates to an information sharing method, device, electronic equipment and storage medium. Background Art

[0002] In daily life and work, people use calendars to record their to-do items to remind themselves and avoid forgetting important things.

[0003] When a user needs to share his / her schedule information with others and hopes that the other party will participate in his / her schedule information, the user will send his / her recorded schedule information to others in the form of screenshots. However, the information transmitted by the screenshots is limited, resulting in the problem of incomplete transmission of the schedule information. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide an information sharing method, device, electronic device and storage medium, which can fully convey schedule information.

[0005] In a first aspect, an embodiment of the present application provides an information sharing method, which is applied to a first electronic device, and includes:

[0006] receiving a first input from a first user;

[0007] In response to the first input, when the screenshot image corresponding to the first input is associated with schedule information, a schedule sharing object is sent to the second user; wherein the schedule sharing object is determined according to the schedule information.

[0008] In a second aspect, an embodiment of the present application provides an information sharing method, which is applied to a second electronic device, and the method includes:

[0009] When receiving the schedule sharing object sent by the first electronic device, receiving a fourth input from the second user;

[0010] In response to the fourth input, the schedule information associated with the schedule sharing object is added to the schedule application.

[0011] In a third aspect, an embodiment of the present application provides an information sharing device, which is applied to a first electronic device, and includes:

[0012] A receiving module, configured to receive a first input from a first user;

[0013] The sharing module is used to respond to the first input and send a schedule sharing object to the second user when the screenshot image corresponding to the first input is associated with schedule information; wherein the schedule sharing object is determined according to the schedule information.

[0014] In a fourth aspect, an embodiment of the present application provides an information sharing device, which is applied to a second electronic device, and includes:

[0015] A receiving module, configured to receive a fourth input from a second user when receiving the schedule sharing object sent by the first electronic device;

[0016] The association module is used to add the schedule information associated with the schedule sharing object to the schedule application in response to the fourth input.

[0017] In a fifth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0018] In a sixth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

[0019] In a seventh aspect, an embodiment of the present application provides a computer program product, which is stored in a storage medium and is executed by at least one processor to implement the method described in the first aspect.

[0020] In an embodiment of the present application, by responding to the first input of the first user, when the screenshot image corresponding to the first input is associated with schedule information, the schedule sharing object determined according to the schedule information is sent to the second user. In this way, when the first user shares his own schedule information, the schedule information associated with the screenshot image corresponding to the first input can be shared with the second user. In this way, the schedule information associated with the screenshot image corresponding to the first input can be completely conveyed to the second user, thereby improving the integrity of the transmission of the schedule information. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 is a schematic diagram of the structure of an information sharing system provided by some embodiments of the present application;

[0022] Figure 2 is a flowchart of an information sharing method provided by some embodiments of the present application;

[0023] Figure 3 is a schematic diagram of a screenshot of a calendar application interface provided by some embodiments of the present application;

[0024] Figure 4 is a flowchart of an information sharing method provided by some embodiments of the present application;

[0025] Figure 5is a schematic diagram of a screenshot of a calendar application interface provided by some embodiments of the present application;

[0026] Figure 6 is a schematic diagram of a screenshot of a calendar application interface provided by some embodiments of the present application;

[0027] Figure 7 is a schematic diagram of a screenshot of a calendar application interface provided by some embodiments of the present application;

[0028] Figure 8 is a schematic diagram of a screenshot of a calendar application interface provided by some embodiments of the present application;

[0029] Fig. 9 is a schematic diagram of a screenshot of a calendar application interface provided by some embodiments of the present application;

[0030] Fig.10 is a schematic diagram of a screenshot of a calendar application interface provided by some embodiments of the present application;

[0031] Fig.11 is a schematic diagram of a screenshot of a calendar application interface provided by some embodiments of the present application;

[0032] Fig.12 is a flowchart of an information sharing method provided by some embodiments of the present application;

[0033] Fig.13 is a flowchart of an information sharing method provided by some embodiments of the present application;

[0034] Fig.14 This is a schematic diagram of a schedule sharing object provided in some embodiments of the present application;

[0035] Fig.15 This is a schematic diagram of a schedule sharing object provided in some embodiments of the present application;

[0036] Fig.16 This is a schematic diagram of a schedule sharing object provided in some embodiments of the present application;

[0037] Fig.17 This is a schematic diagram of a schedule sharing object provided in some embodiments of the present application;

[0038] Fig.18 This is a schematic diagram of a schedule sharing object provided in some embodiments of the present application;

[0039] Fig.19 This is a schematic diagram of a schedule sharing object provided in some embodiments of the present application;

[0040] Fig. 20 This is a schematic diagram of a schedule sharing object provided in some embodiments of the present application;

[0041] Fig.21 This is a schematic diagram of a schedule sharing object provided in some embodiments of the present application;

[0042] Fig. 22 is a flowchart of an information sharing method provided by some embodiments of the present application;

[0043] Fig.23 is a schematic diagram of the structure of an information processing device shown in some embodiments of the present application;

[0044] Fig.24 is a schematic diagram of the structure of an information processing device shown in some embodiments of the present application;

[0045] Fig.25 is a schematic diagram of the structure of an electronic device shown in some embodiments of the present application;

[0046] Fig.26 It is a schematic diagram of the hardware structure of an electronic device shown in some embodiments of the present application. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.

[0048] The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or N. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0049] As described in the background technology section, in the prior art, when using a calendar interface screenshot or a schedule interface to convey schedule information, it may not be possible to include all of the schedule information in the screenshot, thus resulting in the problem of incomplete schedule information transmission. In order to solve the above problem, the embodiments of the present application provide an information sharing method, device, electronic device and storage medium. By responding to a first input of a first user, when a screenshot image corresponding to the first input is associated with schedule information, a schedule sharing object determined according to the schedule information is sent to a second user. In this way, when the first user shares his own schedule information, the schedule information associated with the screenshot image corresponding to the first input can be shared with the second user. In this way, the schedule information associated with the screenshot image corresponding to the first input can be completely transmitted to the second user, thereby improving the integrity of the schedule information transmission.

[0050] The technical solution of the embodiment of the present application can be applied to scenarios where calendar information is conveyed by taking screenshots of a calendar interface or a schedule interface, and the schedule information can be completely conveyed to other objects.

[0051] The information sharing method provided in the embodiment of the present application is described in detail below through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0052] The information sharing method provided in the embodiment of the present application can be applied to Figure 1 In the architecture shown, the specific Figure 1 Provide detailed explanation.

[0053] Figure 1 FIG. 1 is an architecture diagram of an information sharing system according to an exemplary embodiment. Figure 1 As shown, the information sharing system may include: a first electronic device 200 and a second electronic device 300, and the first electronic device 200 and the second electronic device 300 both establish a communication connection through a network 100 to perform data communication or interaction.

[0054] In one example, the first electronic device 200 and the second electronic device 300 may be, but are not limited to, a personal computer (PC), a smart phone, a tablet computer, a personal digital assistant (PDA), etc. The network may be a wired or wireless network. It should be noted that Figure 1 This is just an example, and the number of second electronic devices can be set according to needs and is not limited here.

[0055] The information sharing method provided in the embodiments of the present application will be described in detail below.

[0056] Figure 2It is a flow chart of an information sharing method provided in an embodiment of the present application. The executor of the information sharing method may be an information sharing system. It should be noted that the above-mentioned executor does not constitute a limitation on the present application.

[0057] like Figure 2 As shown, the information sharing method provided in the embodiment of the present application may include steps 210 to 270.

[0058] Step 210: Receive a first input from a first user.

[0059] The first user may be a user who wants to share schedule information with other users on the first electronic device.

[0060] The first input may be an input made by the first user to the calendar application interface or the schedule application interface. The first input is used to send the schedule sharing user to the second user when the screenshot image corresponding to the first input is associated with the schedule information. The first input may be a first operation. Exemplarily, the first input includes but is not limited to: the touch input of the calendar application interface or the schedule application interface by the first user through a touch device such as a finger or a stylus, or a voice command input by the first user, or a specific gesture input by the first user, or other feasible inputs, which can be determined according to actual use requirements, and the embodiment of the present invention is not limited. The specific gesture in the embodiment of the present application may be any one of a single-click gesture, a sliding gesture, a drag gesture, a pressure recognition gesture, a long press gesture, an area change gesture, a double press gesture, and a double-click gesture; the click input in the embodiment of the present application may be a single-click input, a double-click input, or any number of click inputs, etc., and may also be a long press input or a short press input. For example, the first input may be: a screenshot input of the calendar application interface or the schedule application interface by the first user.

[0061] Step 220: In response to the first input, when the screenshot image corresponding to the first input is associated with the schedule information, the schedule sharing object is sent to the second user.

[0062] The screenshot image corresponding to the first input may be a screenshot generated in response to the first input. The screenshot image here may be a screenshot of a calendar application or a screenshot of a schedule application. The screenshot images in the following embodiments are all described by taking a screenshot of a calendar application as an example. Figure 3 This is a screenshot of the calendar application interface for June 2024.

[0063] The schedule sharing object may be a sharing object containing schedule information, that is, the schedule sharing object is determined according to the schedule information, for example, it may be a document or a picture containing schedule information.

[0064] The second user may be the user with whom the first user wants to share the shared information. For example, the second user may be a friend of the first user.

[0065] It should be noted that the execution entity of the above steps 210 to 220 may be the first electronic device 200 in the information sharing system.

[0066] Step 230: When the schedule sharing object sent by the first electronic device is received, a fourth input from the second user is received.

[0067] Among them, the fourth input can be the input of the second user to the schedule sharing object, and the above fourth input is used to add the schedule information associated with the schedule sharing object to the schedule application, and the fourth input can be the fourth operation. Exemplarily, the above fourth input includes but is not limited to: the second user's touch input to the schedule sharing object through a touch device such as a finger or a stylus, or a voice command input by the second user, or a specific gesture input by the second user, or other feasible inputs, which can be determined according to actual use requirements, and the embodiment of the present invention is not limited. The specific gesture in the embodiment of the present application can be any one of a single-click gesture, a sliding gesture, a drag gesture, a pressure recognition gesture, a long press gesture, an area change gesture, a double-press gesture, and a double-click gesture; the click input in the embodiment of the present application can be a single-click input, a double-click input, or any number of click inputs, etc., and can also be a long press input or a short press input. For example, the above fourth input can be: the second user's touch input to the schedule sharing object, such as the fourth input can be the second user's click input to the schedule sharing object.

[0068] Step 240: In response to the fourth input, add the schedule information associated with the schedule sharing object to the schedule application.

[0069] It should be noted that the execution entity of the above steps 230 to 240 may be the second electronic device 300 in the information sharing system.

[0070] In an embodiment of the present application, the first electronic device responds to the first input of the first user and, when the screenshot image corresponding to the first input is associated with the schedule information, sends the schedule sharing object determined according to the schedule information to the second user. In this way, when the first user shares his own schedule information, he can share the schedule information associated with the screenshot image corresponding to the first input with the second user. In this way, the schedule information associated with the screenshot image corresponding to the first input can be completely conveyed to the second user, thereby improving the integrity of the transmission of the schedule information.

[0071] When the second electronic device receives a schedule sharing object sent by the first electronic device, it can add the schedule information associated with the schedule sharing object to the schedule application by responding to the fourth input of the second user. In this way, the second user does not need to manually associate the schedule information associated with the schedule sharing object with his own schedule application, which improves the efficiency of obtaining schedule information. Moreover, since the schedule sharing object is associated with the complete schedule information of the screenshot image corresponding to the first input of the first user, when the schedule information associated with the schedule sharing object is associated with the schedule application, the schedule information associated with the screenshot image corresponding to the first input of the first user can be completely associated with the schedule application, which improves the integrity of the transmission of schedule information.

[0072] Figure 4 It is a flow chart of an information sharing method provided in an embodiment of the present application. The execution subject of the information sharing method may be the first electronic device 200 in the information sharing system. It should be noted that the above execution subject does not constitute a limitation on the present application.

[0073] like Figure 4 As shown, the information sharing method provided in the embodiment of the present application may include steps 410 to 420.

[0074] Step 410: Receive a first input from a first user.

[0075] Step 420: In response to the first input, when the screenshot image corresponding to the first input is associated with schedule information, the schedule sharing object is sent to the second user.

[0076] In some embodiments of the present application, in order to improve the flexibility of the schedule information shared by the user, step 420 may specifically include:

[0077] In response to the first input, determining a screenshot image;

[0078] receiving a second input of the first user regarding the screenshot image;

[0079] In response to the second input, when the date corresponding to the second input is associated with schedule information, determining a schedule sharing object according to the schedule information associated with the date;

[0080] Send the schedule sharing object to the second user.

[0081] Among them, the second input can be the input of the screenshot image by the first user. The second input is used to determine the schedule sharing object according to the schedule information associated with the date when the date corresponding to the second input is associated with the schedule information, and send the schedule sharing object to the second user. The second input can be a second operation. Exemplarily, the second input includes but is not limited to: the touch input of the screenshot image by the first user through a touch device such as a finger or a stylus, or a voice command input by the first user, or a specific gesture input by the first user, or other feasible inputs, which can be determined according to actual use requirements, and the embodiment of the present invention is not limited. The specific gesture in the embodiment of the present application can be any one of a single-click gesture, a sliding gesture, a drag gesture, a pressure recognition gesture, a long press gesture, an area change gesture, a double press gesture, and a double-click gesture; the click input in the embodiment of the present application can be a single-click input, a double-click input, or any number of click inputs, etc., and can also be a long press input or a short press input. For example, the second input can be: the first user's selected input of the target date in the screenshot image, such as the second input can be the user circling the target date in the screenshot image.

[0082] The target date mentioned above may be at least one date in the screenshot image, that is, the target date here may be one date or multiple dates.

[0083] Continue to refer Figure 3 , with the number of target dates as one, and the specific target date as Figure 3 Take the date of June 21, 2024 as an example. Figure 3 As shown, the first user can circle the date of June 21, 2024 in the calendar application interface screenshot 31 , which means that the first user has performed a second input on the calendar application interface screenshot 31 .

[0084] refer to Figure 5 , taking the number of target dates as 2 as an example, the specific target dates are Figure 5 Take the two dates of June 20, 2024 and June 21, 2024 as an example. Figure 5 As shown, the first user can circle the two dates of June 20, 2024 and June 21, 2024 in the calendar interface screenshot 41, which means that the first user has performed a second input on the calendar application interface screenshot 41.

[0085] It should be noted that the above Figure 3 and Figure 5 The number of target dates is only an example. The number of target dates in the embodiment of the present application may not be limited to 1 or 2, but may be 3 or more. The specific number of target dates can be set according to user needs and is not limited in the embodiment of the present application.

[0086] In an embodiment of the present application, a screenshot image can be determined in response to a first input. When the first user's second input to the screenshot image corresponds to date associated schedule information, a schedule sharing object generated based on the schedule information can be sent to a second user. In this way, the schedule information of the date that the user wants to share can be selected according to user needs, thereby improving the flexibility of the schedule information shared by the user.

[0087] In some embodiments of the present application, in order to improve the flexibility of identifying schedule information, before determining the schedule sharing object according to the schedule information associated with the date, the above method may further include:

[0088] Display inquiry information;

[0089] receiving a fifth input of the first user regarding the inquiry information;

[0090] In response to the fifth input, if the fifth input indicates that the first user is determined to share the date-associated schedule information corresponding to the second input with the second user, the date-associated schedule information corresponding to the second input is determined.

[0091] The inquiry information may be information for inquiring the first user whether to share the date-associated schedule information corresponding to the second input with the second user.

[0092] The fifth input may be an input of the inquiry information by the first user. The fifth input is used to determine the date-associated schedule information corresponding to the second input when the fifth input indicates that the first user determines to share the date-associated schedule information corresponding to the second input with the second user. The fifth input may be a fifth operation. Exemplarily, the fifth input includes but is not limited to: the touch input of the inquiry information by the first user through a touch device such as a finger or a stylus, or a voice command input by the first user, or a specific gesture input by the first user, or other feasible inputs, which can be determined according to actual use requirements, and the embodiment of the present invention is not limited. The specific gesture in the embodiment of the present application may be any one of a single-click gesture, a sliding gesture, a drag gesture, a pressure recognition gesture, a long press gesture, an area change gesture, a double press gesture, and a double-click gesture; the click input in the embodiment of the present application may be a single-click input, a double-click input, or any number of click inputs, etc., and may also be a long press input or a short press input. For example, the fifth input may be: the first user's response input to the inquiry information.

[0093] In some embodiments of the present application, when it is detected that a date in the screenshot image is selected, an inquiry message may be displayed asking the first user whether the first user wants to share the schedule information associated with the date corresponding to the second input with the second user, and then the user's fifth input may be received. When the fifth input indicates that the first user is sure to share the schedule information associated with the date corresponding to the second input with the second user, the schedule information of the date corresponding to the second input may be retrieved in the first electronic device to obtain the schedule information associated with the date corresponding to the second input.

[0094] It should be noted that the retrieval of the schedule information of the date corresponding to the second input in the first electronic device may be performed by using an information retrieval algorithm to retrieve the schedule information of the date corresponding to the second input in the first electronic device, or may be other retrieval methods, which are not specifically limited in the embodiments of the present application.

[0095] In addition, it should be noted that the inquiry information can be displayed in the form of a pop-up window, in the form of a bubble, or in the form of a control. The specific display form of the inquiry information is not limited in the embodiments of the present application.

[0096] Continue to refer Figure 3 , taking the number of target dates as 1 and the query information being displayed in the form of a control as an example, after the first user circles the date of June 21, 2024 in the screenshot 31 of the calendar application interface, the query information can be displayed as follows Figure 6 As shown, a "share with schedule" control 61 is displayed, in which the "share with schedule" control 61 is used to indicate whether the first user wants to share the schedule information corresponding to June 21, 2024. If the first user clicks the "share with schedule" control 61, it indicates that the first user is sure to share the schedule information corresponding to June 21, 2024. After the first user clicks the "share with schedule" control 61, Figure 7 As shown, the schedule information 71 for June 21, 2024 is determined and displayed.

[0097] refer to Figure 5 , taking the number of target dates as 2 as an example, and the query information being displayed in the form of a control as an example, after the first user circles the two dates of June 20, 2024 and June 21, 2024 in the calendar application interface screenshot 41, the following can be done: Figure 8 As shown, a "share with schedule" control 81 is displayed, in which the "share with schedule" control 81 is used to indicate whether the first user wants to share the schedule information corresponding to June 20, 2024 and June 21, 2024. If the first user clicks the "share with schedule" control 81, it indicates that the first user is sure to share the schedule information corresponding to June 20, 2024 and June 21, 2024. After the first user clicks the "share with schedule" control 81, Fig. 9 As shown, the schedule information 91 for June 20, 2024 and June 21, 2024 is determined and displayed.

[0098] In another example, when the fifth input indicates that the first user determines not to share the date-associated schedule information corresponding to the second input with the second user, only a screenshot of the calendar application interface may be shared with the second user, such as Figure 6 As shown, if the first user clicks the "Screenshot Share Only" control 62, it indicates that the first user is determined not to share the schedule information corresponding to June 21, 2024, but only to share the calendar application interface screenshot 31, and finally the calendar application interface screenshot 31 is shared with the second user.

[0099] In some embodiments of the present application, if the first user has not edited the schedule information associated with the date corresponding to the second input in advance, then when the fifth input indicates that the first user is sure to share the schedule information associated with the date corresponding to the second input with the second user, the first electronic device will not retrieve the corresponding schedule information when retrieving the schedule information associated with the date corresponding to the second input. The first user can then edit the schedule information associated with the date corresponding to the second input in real time. For example, if the schedule information associated with the date corresponding to the second input edited by the first user in real time is "Send an email to Customer A", then the schedule information "Send an email to Customer A" is the schedule information associated with the date corresponding to the second input.

[0100] In another embodiment, the first user has edited the schedule information of the target date in advance, "Call client B to urge payment", but when the fifth input indicates that the first user is sure to share the schedule information associated with the date corresponding to the second input with the second user, when the first electronic device retrieves the schedule information associated with the date corresponding to the second input, after the first electronic device retrieves the pre-edited schedule information of the target date, "Call client B to urge payment", the first user remembers that there is other schedule information on the date corresponding to the second input, such as the need to send an email to client A, then the first user may also edit the schedule information associated with the date corresponding to the second input, "Send an email to client A", in real time. In this way, the schedule information "Call client B to urge payment" edited in advance by the first user and the schedule information "Send an email to client A" edited in real time by the first user are both schedule information associated with the date corresponding to the second input.

[0101] That is to say, the date-associated schedule information corresponding to the second input may be pre-edited by the first user, or edited by the first user in real time, or a combination of the above two situations, which is not limited in the embodiments of the present application.

[0102] In an embodiment of the present application, when the first user determines to share the schedule information associated with the date corresponding to the second input with the second user, the schedule information associated with the date corresponding to the second input is determined. In this way, the schedule information associated with the date corresponding to the second input can be determined according to user needs, thereby improving the flexibility of determining the schedule information associated with the date corresponding to the second input.

[0103] In some embodiments of the present application, in order to improve the flexibility of the sharing method of the shared schedule information, in response to the second input, when the date corresponding to the second input is associated with the schedule information, determining the schedule sharing object according to the schedule information associated with the date may specifically include:

[0104] In response to the second input, when the date corresponding to the second input is associated with the schedule information, displaying the schedule sharing type;

[0105] receiving a third input of a first sharing type in the schedule sharing type;

[0106] In response to the third input, a schedule sharing object is determined according to the schedule information associated with the date and the first sharing type.

[0107] The schedule sharing type may be a sharing type used when sharing schedule information, such as a document format or a picture format.

[0108] The first sharing type may be any sharing type in the schedule sharing type, for example, a document type or a picture type.

[0109] The third input may be an input made by the first user to the first sharing type in the schedule sharing type. The third input is used to determine the schedule sharing object according to the schedule information associated with the date and the first sharing type. The third input may be a third operation. Exemplarily, the third input includes but is not limited to: the first user touches the first sharing type in the schedule sharing type through a touch device such as a finger or a stylus, or a voice command input by the first user, or a specific gesture input by the first user, or other feasible inputs, which may be determined according to actual use requirements, and the embodiment of the present invention is not limited thereto. The specific gesture in the embodiment of the present application may be any one of a single-click gesture, a sliding gesture, a dragging gesture, a pressure recognition gesture, a long-press gesture, an area change gesture, a double-press gesture, and a double-click gesture; the click input in the embodiment of the present application may be a single-click input, a double-click input, or any number of click inputs, etc., and may also be a long-press input or a short-press input. For example, the third input may be: the first user touches the first sharing type in the schedule sharing type, such as the third input may be the first user clicks the first sharing type in the schedule sharing type.

[0110] In some embodiments of the present application, after determining the date-associated schedule information corresponding to the second input, the schedule sharing type can be displayed. In response to the first user's third input of the first sharing type in the schedule sharing type, a schedule sharing object can be generated based on the selected first sharing type and the date-associated schedule information corresponding to the second input.

[0111] Continue to refer Figure 7 After displaying the schedule information 71 of June 21, 2024, the first user clicks the "OK" control 72, indicating that the first user has determined that the schedule information 71 is the schedule information to be shared with the second user. Fig.10 The schedule sharing type selection interface 101 is shown. The schedule sharing type selection interface 101 may include at least one schedule sharing type, such as Fig.10 In the “picture” sharing type 1011 and the “document” sharing type 1012, the first user clicks the “picture” sharing type 1011, and then clicks the “confirm sharing” control 102, then the schedule information 71 can be generated into picture type sharing content.

[0112] Continue to refer Fig. 9 After displaying the schedule information 91 of June 20, 2024 and June 21, 2024, the first user clicks the "OK" control 92, indicating that the first user has determined that the schedule information 91 is the schedule information to be shared with the second user. Fig.11 The schedule sharing type selection interface 111 is shown. The schedule sharing type selection interface 111 may include at least one schedule sharing type, such as Fig.11 In the “picture” sharing type 1111 and the “document” sharing type 1112, the first user clicks the “picture” sharing type 1111, and then clicks the “confirm sharing” control 112, then the schedule information 91 can be generated into picture type sharing content.

[0113] It should be noted that when the schedule information is used to generate the sharing content of the first sharing type and obtain the schedule sharing object, the screenshot image corresponding to the first input and the date-associated schedule information corresponding to the second input may be sent to the second electronic device together, that is, the screenshot image corresponding to the first input is displayed on the second electronic device, and the screenshot image has the date-associated schedule information corresponding to the second input and the date corresponding to the circled second input, as described in the following embodiments. Fig.14 and Fig.16 shown.

[0114] In an embodiment of the present application, by responding to the first user's third input of the first sharing type in the schedule sharing type, a schedule sharing object containing schedule information can be generated based on the selected first sharing type and the date associated schedule information corresponding to the second input. In this way, a schedule sharing object of the sharing type required by the first user can be generated according to the needs of the first user, thereby improving the flexibility of the sharing method of shared schedule information.

[0115] In some embodiments of the present application, in order to facilitate a better understanding of the solution of the embodiments of the present application, the screenshot image is a screenshot image of the calendar application interface as an example to specifically illustrate the above Figure 3 The information sharing method shown.

[0116] like Fig.12 As shown, the information sharing method provided in the embodiment of the present application may include steps 1210 to 1250.

[0117] Step 1210: In response to a first input of a first user to the calendar application interface, a screenshot image of the calendar application interface is obtained.

[0118] Step 1220: In response to the first user's second input of the screenshot of the calendar application interface, a query message is displayed asking the first user whether to share the date-associated schedule information corresponding to the second input with the second user.

[0119] Step 1230: If the first user determines to share the date-associated schedule information corresponding to the second input with the second user, the date-associated schedule information corresponding to the second input is determined.

[0120] Step 1240: In response to a first sharing type among the schedule sharing types selected by the second user, determine a schedule sharing object based on the first sharing type and the date-associated schedule information corresponding to the second input.

[0121] Step 1250: Send the schedule sharing object to the second user.

[0122] Fig.13 It is a flow chart of an information sharing method provided in an embodiment of the present application. The execution subject of the information sharing method may be the second electronic device 300 in the information sharing system. It should be noted that the above execution subject does not constitute a limitation on the present application.

[0123] like Fig.13 As shown, the information sharing method provided in the embodiment of the present application may include steps 1310 to 1320.

[0124] Step 1310: When receiving the schedule sharing object sent by the first electronic device, receive a fourth input from the second user.

[0125] Among them, the fourth input can be the input of the second user to the schedule sharing object, and the above fourth input is used to add the schedule information associated with the schedule sharing object to the schedule application, and the fourth input can be the fourth operation. Exemplarily, the above fourth input includes but is not limited to: the first user's touch input to the schedule sharing object through a touch device such as a finger or a stylus, or a voice command input by the first user, or a specific gesture input by the first user, or other feasible inputs, which can be determined according to actual use requirements, and the embodiment of the present invention is not limited. The specific gesture in the embodiment of the present application can be any one of a single-click gesture, a sliding gesture, a drag gesture, a pressure recognition gesture, a long press gesture, an area change gesture, a double-press gesture, and a double-click gesture; the click input in the embodiment of the present application can be a single-click input, a double-click input, or any number of click inputs, etc., and can also be a long press input or a short press input. For example, the above fourth input can be: the first user's touch input to the schedule sharing object, such as the fourth input can be the first user's click input to the schedule sharing object.

[0126] In some embodiments of the present application, when the second electronic device receives a schedule sharing object sent by the first electronic device, the schedule information associated with the schedule sharing object can be viewed.

[0127] In one example, reference Fig.14 , Fig.14 The above-mentioned received by the second electronic device Fig.10 In the example shown, the generated picture type schedule information 141, the second user can click the "view schedule" control 142, Fig.15 As shown, check schedule information 71.

[0128] In another example, reference Fig.16 , Fig.16 The above-mentioned received by the second electronic device Fig.11 In the example shown, the generated schedule information 161 in the form of a picture, the second user can click the "view schedule" control 162 to Fig.17 As shown, check schedule information 91.

[0129] Step 1320: In response to the fourth input, add the schedule information associated with the schedule sharing object to the schedule application.

[0130] In some embodiments of the present application, in response to the fourth input of the user, the schedule information associated with the schedule sharing object can be directly added to the schedule application.

[0131] Continue to refer Fig.15 The second user can click the "one-click import" control 151 to import the schedule information 71 into the schedule application.

[0132] Continue to refer Fig.17 The second user can click the "one-click import" control 171 to import the schedule information 91 into the schedule application.

[0133] In an embodiment of the present application, when the second electronic device receives a schedule sharing object sent by the first electronic device, it can add the schedule information associated with the schedule sharing object to the schedule application by responding to the fourth input of the second user. In this way, the second user does not need to manually associate the schedule information associated with the schedule sharing object with his own schedule application, which improves the efficiency of obtaining schedule information. Moreover, since the schedule sharing object is associated with the complete schedule information of the screenshot image corresponding to the first input of the first user, when the schedule information associated with the schedule sharing object is associated with the schedule application, the schedule information associated with the screenshot image corresponding to the first input of the first user can be completely associated with the schedule application, thereby improving the integrity of the transmission of schedule information.

[0134] In some embodiments of the present application, the schedule information associated with the schedule sharing object may include schedule information associated with at least two dates respectively; step 1310 may specifically include:

[0135] In case of receiving the schedule sharing object sent by the first electronic device, receiving a fourth input of the second user for a first date of the at least two dates;

[0136] Step 1320 may specifically include:

[0137] In response to the fourth input, the schedule information associated with the first date is added to the schedule application.

[0138] The first date may be any one of at least two dates.

[0139] In some embodiments of the present application, when the schedule information associated with the schedule sharing object includes schedule information associated with at least two dates respectively, if the second user has other information on a certain date and cannot participate in the schedule information of that date, then in response to the user's fourth input of the first date of the at least two dates, the schedule information associated with the first date can be added to the schedule application.

[0140] Continue to refer Fig.17The schedule information associated with the schedule sharing object received by the second electronic device includes the schedule information on June 20, 2024 and the schedule information on June 21, 2024, wherein the schedule information on June 20, 2024 includes Schedule 1, Schedule 2 and Schedule 3, and the schedule information on June 21, 2024 includes Schedule 4. If the second user has other things on June 21, 2024 and cannot participate in the schedule information of the first user on June 21, 2024, the second user can only associate the schedule information on June 20, 2024 with the schedule application, but not associate the schedule information on June 21, 2024 with the schedule application.

[0141] When associating the schedule information for June 20, 2024 to the schedule application, the second user can click Fig.16 The circled date of June 20, 2024, can be Fig.18 As shown, Schedule 1, Schedule 2 and Schedule 3 on June 20, 2024 are selected, and then the second user clicks the "One-click Import" control 181, and Schedule 1, Schedule 2 and Schedule 3 on June 20, 2024 can be imported into the schedule application.

[0142] It should be noted that the above Fig.17 In the example shown, after the second user clicks the "One-click Import" control 171, all the schedule information 91 is imported into the schedule application, that is, the schedule information on June 20, 2024: Schedule 1, Schedule 2 and Schedule 3, and the schedule information on June 21, 2024: Schedule 4 are all imported into the schedule application.

[0143] In an embodiment of the present application, when the schedule information associated with the schedule sharing object includes schedule information associated with at least two dates respectively, only the schedule information associated with the first date can be added to the schedule application in response to the second user's fourth input of the first date of the at least two dates according to user needs. In this way, only the schedule information associated with the date required by the user can be added to the schedule application according to user needs, thereby improving the flexibility of the schedule information added to the schedule application.

[0144] In some embodiments of the present application, the schedule information associated with the schedule sharing object may include at least two schedule information; step 1310 may specifically include:

[0145] In case of receiving the schedule sharing object sent by the first electronic device, receiving a fourth input of the second user on the first schedule information of the at least two schedule information;

[0146] Step 1320 may specifically include:

[0147] In response to the fourth input, the first schedule information is added to the schedule application.

[0148] The first schedule information may be any one of at least two schedule information.

[0149] In some embodiments of the present application, when the schedule information associated with the schedule sharing object includes at least two schedule information, if the schedule of the second user conflicts with one or several schedule information among the at least two schedule information and the second user cannot participate in the schedule information, the second user may only select the schedule information that does not conflict with his or her own schedule information. Specifically, in response to the user's fourth input to the first schedule information among the at least two schedule information, the first schedule information may be added to the schedule application.

[0150] Continue to refer Fig.15 The schedule information associated with the schedule sharing object received by the second electronic device includes the schedule information on June 20, 2024. The schedule information on June 20, 2024 includes Schedule 1, Schedule 2 and Schedule 3. If the second user has other things to do in the afternoon of June 20, 2024 and cannot participate in the first user's Schedule 2 and Schedule 3 on June 20, 2024, the second user can only associate Schedule 1 on June 20, 2024 with the schedule application, but not associate Schedule 2 and Schedule 3 on June 20, 2024 with the schedule application.

[0151] When associating Schedule 1 on June 20, 2024 to the schedule application, the second user can click Fig.15 Schedule 1 in the Fig.19 As shown, schedule 1 on June 20, 2024 is selected, and then the second user clicks the "one-click import" control 191, and schedule 1 on June 20, 2024 can be imported into the schedule application.

[0152] It should be noted that the above Fig.15 In the example shown, after the second user clicks the "one-click import" control 151, all the schedule information 71 is imported into the schedule application, that is, the schedule information on June 20, 2024: Schedule 1, Schedule 2 and Schedule are all imported into the schedule application.

[0153] In an embodiment of the present application, when the schedule information associated with the schedule sharing object includes at least two schedule information, only the first schedule information can be added to the schedule application in response to the second user's fourth input of the first schedule information among the at least two schedule information according to user needs. In this way, only the schedule information required by the user can be added to the schedule application according to user needs, thereby improving the flexibility of the schedule information added to the schedule application.

[0154] Above Fig.18 and Fig.19The example shown is that the second user determines whether the schedule information associated with the schedule sharing object conflicts with his own schedule information. The efficiency of adding schedule information in this way is relatively low, and manually adding schedule information may result in errors in the added schedule information.

[0155] In order to solve the above problem, in an embodiment of the present application, after the second electronic device receives the schedule sharing object sent by the first electronic device, the second electronic device can independently determine the schedule information associated with the schedule sharing object and the schedule information of the second user that does not conflict, and directly add the schedule information to the schedule application.

[0156] That is, in the case of receiving the schedule sharing object sent by the first electronic device, before receiving the fourth input of the second user, the above method may further include:

[0157] Determine target schedule information from schedule information associated with a schedule sharing object;

[0158] The adding the schedule information associated with the schedule sharing object to the schedule application may specifically include:

[0159] Add the target schedule information to the schedule application.

[0160] Among them, the target schedule information may include at least one of the following: schedule information in the schedule information associated with the schedule sharing object that does not conflict with the schedule information of the second user; when there are multiple schedule information on the same date in the schedule information associated with the schedule sharing object, at least one schedule information selected from the multiple schedule information.

[0161] In some embodiments of the present application, when the schedule information associated with the schedule sharing object conflicts with the schedule information of the second user, the non-conflicting schedule information may be added to the schedule application.

[0162] Continue to refer Figure 7 In the example shown, taking the schedule information 71 associated with the schedule sharing object as "Visiting Customer C" as an example, if the second user has other things to do throughout the day on June 21, 2024, the schedule information 71 associated with the schedule sharing object conflicts with the schedule information of the second user. When adding the schedule information to the schedule application, the schedule information 71 associated with the schedule sharing object may not be added to the schedule application of the second user.

[0163] Continue to refer Figure 7In the example shown, taking the schedule information 71 associated with the schedule sharing object as "Visiting Customer C" as an example, if the second user has other things on June 21, 2024, but the things do not conflict with the schedule information 71 associated with the schedule sharing object, then when adding the schedule information to the schedule application, the schedule information 71 associated with the schedule sharing object can be added to the second user's schedule application.

[0164] When there are multiple schedule information on the same date in the schedule information associated with the schedule sharing object, and the second user has limited energy and can only participate in part of the schedule information, at least one schedule information can be selected from the multiple schedule information and associated with the second user's schedule application.

[0165] In one example, taking the date corresponding to the second input as June 21, 2024, the schedule for that day includes: "Visiting Customer C" and "Holding a Parent-Teacher Meeting", that is, there are multiple schedule information on that day, and the second user currently only has the energy to participate in one schedule, then one of the schedule information can be selected and added to the second user's schedule application.

[0166] In an embodiment of the present application, by adding schedule information associated with the schedule sharing object that does not conflict with the schedule information of the second user to the schedule application of the second user, and / or, when there are multiple schedule information on the same date in the schedule information associated with the schedule sharing object, at least one schedule information can be selected from the multiple schedule information and added to the schedule application of the second user, so that according to the needs of the second user, the second electronic device can automatically select the schedule information required by the second user and add it to the schedule application, thereby improving the efficiency and accuracy of adding schedule information to the schedule application.

[0167] In some embodiments of the present application, in order to improve the flexibility of determining the target schedule information, the determining the target schedule information from the schedule information associated with the schedule sharing object may specifically include:

[0168] When it is determined that the schedule information associated with the schedule sharing object conflicts with the schedule information of the second user, and / or when the schedule information associated with the schedule sharing object contains multiple schedule information on the same date, display at least one conflicting schedule information;

[0169] receiving a sixth input from a second user regarding a first conflicting schedule information among the at least one conflicting schedule information;

[0170] In response to the sixth input, the first conflicting schedule information is used as the target schedule information.

[0171] The at least one conflicting schedule information may be schedule information in the schedule information associated with the schedule sharing object that conflicts with the schedule information of the second user, and / or multiple schedule information on the same date in the schedule information associated with the schedule sharing object.

[0172] The first conflicting schedule information may be any conflicting schedule information among the at least one conflicting schedule information.

[0173] The sixth input may be an input by the second user to the first conflicting schedule information in at least one conflicting schedule information. The sixth input is used to use the first conflicting schedule information as the target schedule information, and the sixth input may be a sixth operation. Exemplarily, the sixth input includes but is not limited to: the second user touch input to the first conflicting schedule information in at least one conflicting schedule information through a touch device such as a finger or a stylus, or a voice command input by the second user, or a specific gesture input by the second user, or other feasible inputs, which may be determined according to actual use requirements, and the embodiment of the present invention is not limited thereto. The specific gesture in the embodiment of the present application may be any one of a single-click gesture, a sliding gesture, a dragging gesture, a pressure recognition gesture, a long press gesture, an area change gesture, a double-press gesture, and a double-click gesture; the click input in the embodiment of the present application may be a single-click input, a double-click input, or any number of click inputs, etc., and may also be a long press input or a short press input. For example, the sixth input may be: the second user click input to the first conflicting schedule information in at least one conflicting schedule information.

[0174] In some embodiments of the present application, when it is determined that the schedule information associated with the schedule sharing object conflicts with the schedule information of the second user, and / or there are multiple schedule information on the same date in the schedule information associated with the schedule sharing object, at least one conflicting schedule information may be displayed, and in response to the second user's sixth input of the first conflicting schedule information in the at least one conflicting schedule information, the first conflicting schedule information may be used as the target schedule information.

[0175] Continue to refer Fig.15 After the second user clicks the "one-key import" control 151, Fig. 20 As shown, a conflicting schedule interface 201 is displayed, and the conflicting schedule interface 201 includes at least one conflicting schedule information, such as Fig. 20 Schedule 1, schedule 2 and schedule 3 are conflicting schedule information. If the second user cannot participate in schedule 1 and schedule 2, the second user can only select schedule 3 and then click the "Reserve" control 202, and schedule 3 can be added to the second user's schedule application.

[0176] In another example, the second user may also select Schedule 1 and Schedule 2, and then click the "Do Not Keep" control 203, so that Schedule 1 and Schedule 2 are not added to the second user's schedule application, and only Schedule 3 is added to the second user's schedule application.

[0177] Continue to refer Fig.17 After the second user clicks the "one-key import" control 171, Fig.21 As shown, a conflicting schedule interface 211 is displayed, and the conflicting schedule interface 211 includes at least one conflicting schedule information, such as Fig.21 Schedule 1, Schedule 2 and Schedule 3 are conflicting schedule information. If the second user cannot participate in Schedule 1 and Schedule 2, the second user can only select Schedule 3 and then click the "Reserve" control 192 to add Schedule 3 to the second user's schedule application.

[0178] In another example, the second user may also select Schedule 1 and Schedule 2, and then click the "Do Not Keep" control 213, so that Schedule 1 and Schedule 2 are not added to the second user's schedule application, and only Schedule 3 is added to the second user's schedule application.

[0179] In an embodiment of the present application, when it is determined that the schedule information associated with the schedule sharing object conflicts with the schedule information of the second user, and / or when there are multiple schedule information on the same date in the schedule information associated with the schedule sharing object, at least one conflicting schedule information is displayed, and in response to the second user's sixth input of the first conflicting schedule information in the at least one conflicting schedule information, the first conflicting schedule information can be used as the target schedule information. In this way, the target schedule information can be selected according to user needs, thereby improving the flexibility of determining the target schedule information.

[0180] In some embodiments of the present application, in order to facilitate a better understanding of the solutions of the embodiments of the present application, the following specific scenarios are used to illustrate the above Fig.13 The information sharing method shown.

[0181] like Fig. 22 As shown, the information sharing method provided in the embodiment of the present application may include steps 2210 to 2230.

[0182] Step 2210: Receive a schedule sharing object sent by the first electronic device.

[0183] Step 2220: In response to the second user's operation of importing the schedule information of the schedule sharing object into the schedule information of the second user, display at least one conflicting schedule information.

[0184] The import operation of the second user in the above step 2220 importing the schedule information of the schedule sharing object into the schedule information of the second user is the fourth input of the second user in the above step 1310 .

[0185] Step 2230: In response to the second user's selection operation on the first conflicting schedule information among the at least one conflicting schedule information, add the first conflicting schedule information to the schedule application.

[0186] The information sharing method provided in the embodiment of the present application can be executed by an information sharing device. In the embodiment of the present application, the information sharing device provided in the embodiment of the present application is described by taking the information sharing method executed by the information sharing device as an example.

[0187] Fig.23 FIG. 2 is a schematic diagram showing a structure of an information sharing device according to an exemplary embodiment. The information sharing device is applied to a first electronic device 200. Fig.23 As shown, the information sharing device 2300 may include:

[0188] The receiving module 2310 is used to receive a first input from a first user;

[0189] The sharing module 2320 is used to respond to the first input and send a schedule sharing object to the second user when the screenshot image corresponding to the first input is associated with schedule information; wherein the schedule sharing object is determined according to the schedule information.

[0190] In an embodiment of the present application, by responding to the first input of the first user, when the screenshot image corresponding to the first input is associated with schedule information, the schedule sharing object determined according to the schedule information is sent to the second user. In this way, when the first user shares his own schedule information, the schedule information associated with the screenshot image corresponding to the first input can be shared with the second user. In this way, the schedule information associated with the screenshot image corresponding to the first input can be completely conveyed to the second user, thereby improving the integrity of the transmission of the schedule information.

[0191] In some embodiments of the present application, the sharing module 2320 may include:

[0192] A first determining unit, configured to determine the screenshot image in response to the first input;

[0193] A receiving unit, configured to receive a second input of the first user on the screenshot image;

[0194] A second determining unit, configured to, in response to the second input, determine the schedule sharing object according to the schedule information associated with the date when the date corresponding to the second input is associated with the schedule information;

[0195] A sharing unit is used to send the schedule sharing object to the second user.

[0196] In some embodiments of the present application, the second determining unit is specifically configured to:

[0197] In response to the second input, if the date corresponding to the second input is associated with schedule information, displaying a schedule sharing type;

[0198] receiving a third input of a first sharing type among the schedule sharing types;

[0199] In response to the third input, the schedule sharing object is determined according to the schedule information associated with the date and the first sharing type.

[0200] Fig.24 FIG. 1 is a schematic diagram showing a structure of an information sharing device according to an exemplary embodiment, and the information sharing device is applied to the second electronic device 300. Fig.24 As shown, the information sharing device 2400 may include:

[0201] The receiving module 2410 is configured to receive a fourth input from a second user when receiving the schedule sharing object sent by the first electronic device;

[0202] The association module 2420 is configured to add the schedule information associated with the schedule sharing object to a schedule application in response to the fourth input.

[0203] In an embodiment of the present application, when a schedule sharing object sent by a first electronic device is received, the schedule information associated with the schedule sharing object can be added to the schedule application in response to the fourth input of the second user. In this way, the second user does not need to manually associate the schedule information associated with the schedule sharing object with his own schedule application, which improves the efficiency of obtaining schedule information. Moreover, since the schedule sharing object is associated with the complete schedule information of the screenshot image corresponding to the first input of the first user, when the schedule information associated with the schedule sharing object is associated with the schedule application, the schedule information associated with the screenshot image corresponding to the first input of the first user can be completely associated with the schedule application, thereby improving the integrity of the transmission of schedule information.

[0204] In some embodiments of the present application, the schedule information associated with the schedule sharing object includes schedule information associated with at least two dates respectively; the receiving module 2410 is specifically configured to: upon receiving the schedule sharing object sent by the first electronic device, receive a fourth input of the second user for a first date of the at least two dates;

[0205] The associating module 2420 is specifically configured to: in response to the fourth input, add the schedule information associated with the first date to the schedule application.

[0206] In some embodiments of the present application, the schedule information associated with the schedule sharing object includes at least two schedule information; the receiving module 2410 is specifically configured to: upon receiving the schedule sharing object sent by the first electronic device, receive a fourth input from the second user on the first schedule information of the at least two schedule information;

[0207] The associating module 2420 is specifically configured to: in response to the fourth input, add the first schedule information to the schedule application.

[0208] The information sharing device in the embodiment of the present application can be an electronic device, or a component in the electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or other devices other than a terminal. Exemplarily, the electronic device can be a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted electronic device, a mobile Internet device (Mobile Internet Device, MID), an augmented reality (augmented reality, AR) / virtual reality (virtual reality, VR) device, a robot, a wearable device, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a netbook or a personal digital assistant (personal digital assistant, PDA), etc., and can also be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0209] The information sharing device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0210] The information sharing device provided in the embodiment of the present application can achieve Figure 3 The various processes implemented by the method embodiment, and / or, Fig.13 To avoid repetition, the various processes implemented by the method embodiment are not described here.

[0211] Alternatively, if Fig.25As shown, an embodiment of the present application also provides an electronic device 2500, including a processor 2501 and a memory 2502, wherein the memory 2502 stores programs or instructions that can be executed on the processor 2501, and when the program or instructions are executed by the processor 2501, the various steps of the above-mentioned information sharing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, they are not repeated here.

[0212] It should be noted that the electronic devices in the embodiments of the present application include the mobile electronic devices and non-mobile electronic devices mentioned above.

[0213] Fig.26 A schematic diagram of the hardware structure of an electronic device to implement an embodiment of the present application.

[0214] The electronic device 2600 includes but is not limited to: a radio frequency unit 2601, a network module 2602, an audio output unit 2603, an input unit 2604, a sensor 2605, a display unit 2606, a user input unit 2607, an interface unit 2608, a memory 2609, and a processor 2610 and other components.

[0215] Those skilled in the art will appreciate that the electronic device 2600 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 2610 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.26 The electronic device structure shown in the figure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0216] When the electronic device 2600 is the first electronic device in the information sharing system:

[0217] The user input unit 2607 is used to receive a first input from a first user;

[0218] Processor 2610 is used to send a schedule sharing object to a second user in response to the first input when the screenshot image corresponding to the first input is associated with schedule information; wherein the schedule sharing object is determined according to the schedule information.

[0219] In this way, by responding to the first input of the first user, when the screenshot image corresponding to the first input is associated with schedule information, the schedule sharing object determined according to the schedule information is sent to the second user. In this way, when the first user shares his own schedule information, the schedule information associated with the screenshot image corresponding to the first input can be shared with the second user. In this way, the schedule information associated with the screenshot image corresponding to the first input can be completely conveyed to the second user, thereby improving the integrity of the transmission of schedule information.

[0220] Optionally, the processor 2610 is further configured to determine the screenshot image in response to the first input;

[0221] The user input unit 2607 is further used to receive a second input of the first user on the screenshot image;

[0222] Processor 2610 is further configured to respond to the second input, and when the date corresponding to the second input is associated with schedule information, determine the schedule sharing object according to the schedule information associated with the date; and send the schedule sharing object to the second user.

[0223] In this way, by responding to the first input, the screenshot image can be determined. When the first user's second input to the screenshot image corresponds to the date associated with the schedule information, the schedule sharing object generated based on the schedule information can be sent to the second user. In this way, the schedule information of the date that the user wants to share can be selected according to the user's needs, thereby improving the flexibility of the schedule information shared by the user.

[0224] Optionally, the display unit 2606 is configured to, in response to the second input, display a schedule sharing type when the date corresponding to the second input is associated with schedule information;

[0225] The user input unit 2607 is further used to receive a third input of the first sharing type in the schedule sharing type;

[0226] The processor 2610 is further configured to, in response to the third input, determine the schedule sharing object according to the schedule information associated with the date and the first sharing type.

[0227] In this way, by responding to the first user's third input of the first sharing type in the schedule sharing type, a schedule sharing object containing the schedule information can be generated according to the selected first sharing type and the date associated schedule information corresponding to the second input. In this way, a schedule sharing object of the sharing type required by the first user can be generated according to the needs of the first user, thereby improving the flexibility of the sharing method of the shared schedule information.

[0228] When the electronic device 2600 is the second electronic device in the above information sharing system:

[0229] The user input unit 2607 is used to receive a fourth input from the second user when receiving the schedule sharing object sent by the first electronic device;

[0230] The processor 2610 is configured to add the schedule information associated with the schedule sharing object to a schedule application in response to the fourth input.

[0231] In this way, when a schedule sharing object sent by the first electronic device is received, the schedule information associated with the schedule sharing object can be added to the schedule application by responding to the fourth input of the second user. In this way, the second user does not need to manually associate the schedule information associated with the schedule sharing object with his own schedule application, which improves the efficiency of obtaining schedule information. Moreover, since the schedule sharing object is associated with the complete schedule information of the screenshot image corresponding to the first input of the first user, when the schedule information associated with the schedule sharing object is associated with the schedule application, the schedule information associated with the screenshot image corresponding to the first input of the first user can be completely associated with the schedule application, thereby improving the integrity of the transmission of schedule information.

[0232] Optionally, the schedule information associated with the schedule sharing object includes schedule information associated with at least two dates respectively; the user input unit 2607 is further used to: when receiving the schedule sharing object sent by the first electronic device, receive a fourth input of the second user on a first date of the at least two dates;

[0233] The processor 2610 is further configured to: in response to the fourth input, add the schedule information associated with the first date to the schedule application.

[0234] In this way, when the schedule information associated with the schedule sharing object includes schedule information associated with at least two dates respectively, according to user needs, by responding to the second user's fourth input of the first date of at least two dates, only the schedule information associated with the first date can be added to the schedule application. In this way, according to user needs, only the schedule information associated with the date required by the user can be added to the schedule application, thereby improving the flexibility of the schedule information added to the schedule application.

[0235] Optionally, the schedule information associated with the schedule sharing object includes at least two schedule information;

[0236] The user input unit 2607 is further configured to: upon receiving the schedule sharing object sent by the first electronic device, receive a fourth input from the second user on the first schedule information of the at least two schedule information;

[0237] The processor 2610 is further configured to: in response to the fourth input, add the first schedule information to the schedule application.

[0238] In this way, when the schedule information associated with the schedule sharing object includes at least two schedule information, only the first schedule information can be added to the schedule application in response to the second user's fourth input of the first schedule information among the at least two schedule information according to user needs. In this way, only the schedule information required by the user can be added to the schedule application according to user needs, thereby improving the flexibility of the schedule information added to the schedule application.

[0239] It should be understood that in the embodiment of the present application, the input unit 2604 may include a graphics processor (Graphics Processing Unit, GPU) 26041 and a microphone 26042, and the graphics processor 26041 processes the image data of the static picture or video obtained by the image capture device (such as a color camera) in the video capture mode or the image capture mode. The display unit 2606 may include a display panel 26061, and the display panel 26061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 2607 includes a touch panel 26071 and at least one of other input devices 26072. The touch panel 26071 is also called a touch screen. The touch panel 26071 may include two parts: a touch detection device and a touch controller. Other input devices 26072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0240] The memory 2609 can be used to store software programs and various data. The memory 2609 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 2609 may include a volatile memory or a non-volatile memory, or the memory 2609 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory 2609 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0241] The processor 2610 may include one or more processing units; optionally, the processor 2610 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 2610.

[0242] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information sharing method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0243] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0244] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned information sharing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0245] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0246] An embodiment of the present application provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned information sharing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0247] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0248] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0249] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. An information sharing method, characterized in that: The method is applied to a first electronic device, and the method includes: receiving a first input from a first user; In response to the first input, when the screenshot image corresponding to the first input is associated with schedule information, a schedule sharing object is sent to the second user; wherein the schedule sharing object is determined according to the schedule information.

2. The method according to claim 1, characterized in that The step of sending the schedule sharing object to the second user in response to the first input when the screenshot image corresponding to the first input is associated with schedule information includes: In response to the first input, determining the screenshot image; receiving a second input of the first user regarding the screenshot image; In response to the second input, when the date corresponding to the second input is associated with schedule information, determining the schedule sharing object according to the schedule information associated with the date; The schedule sharing object is sent to the second user.

3. The method according to claim 2, characterized in that The step of responding to the second input and determining the schedule sharing object according to the schedule information associated with the date in response to the second input includes: In response to the second input, if the date corresponding to the second input is associated with schedule information, displaying a schedule sharing type; receiving a third input of a first sharing type among the schedule sharing types; In response to the third input, the schedule sharing object is determined according to the schedule information associated with the date and the first sharing type.

4. An information sharing method, characterized in that: The method is applied to a second electronic device, and the method includes: When receiving the schedule sharing object sent by the first electronic device, receiving a fourth input from the second user; In response to the fourth input, the schedule information associated with the schedule sharing object is added to the schedule application.

5. The method according to claim 4, characterized in that The schedule information associated with the schedule sharing object includes schedule information associated with at least two dates respectively; The step of receiving a fourth input from a second user upon receiving the schedule sharing object sent by the first electronic device includes: In case of receiving the schedule sharing object sent by the first electronic device, receiving a fourth input of the second user for a first date among the at least two dates; In response to the fourth input, adding the schedule information associated with the schedule sharing object to the schedule application includes: In response to the fourth input, the schedule information associated with the first date is added to the schedule application.

6. The method according to claim 4, characterized in that The schedule information associated with the schedule sharing object includes at least two schedule information; The step of receiving a fourth input from a second user upon receiving the schedule sharing object sent by the first electronic device includes: In case of receiving the schedule sharing object sent by the first electronic device, receiving a fourth input of the second user on the first schedule information among the at least two schedule information; In response to the fourth input, adding the schedule information associated with the schedule sharing object to the schedule application includes: In response to the fourth input, the first schedule information is added to the schedule application.

7. An information sharing device, characterized in that: The device is applied to a first electronic device, and includes: A receiving module, configured to receive a first input from a first user; The sharing module is used to respond to the first input and send a schedule sharing object to the second user when the screenshot image corresponding to the first input is associated with schedule information; wherein the schedule sharing object is determined according to the schedule information.

8. An information sharing device, characterized in that: The device is applied to a second electronic device, and includes: A receiving module, configured to receive a fourth input from a second user when receiving the schedule sharing object sent by the first electronic device; The association module is used to add the schedule information associated with the schedule sharing object to the schedule application in response to the fourth input.

9. An electronic device, characterized in that: It includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, it implements the steps of the information sharing method according to any one of claims 1 to 3, and / or the steps of the information sharing method according to any one of claims 4 to 6.

10. A readable storage medium, characterized in that: The readable storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, the steps of the information sharing method described in any one of claims 1-3 and / or the steps of the information sharing method described in any one of claims 4-6 are implemented.

Images