CN114024927A

CN114024927A - Information sharing method and device

Info

Publication number: CN114024927A
Application number: CN202010685956.5A
Authority: CN
Inventors: 黄铁鸣; 钟亮; 杨培艺; 李斌; 赵东
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-07-16
Filing date: 2020-07-16
Publication date: 2022-02-08
Anticipated expiration: 2040-07-16
Also published as: CN114024927B

Abstract

The embodiment of the application provides an information sharing method and device, which relate to the technical field of computers, and the method comprises the following steps: a first client of a first application responds to the operation of newly building the shared calendar and displays a shared calendar establishing interface; displaying the shared calendar editing content in the shared calendar creation interface in response to the shared calendar content editing operation triggered in the shared calendar creation interface; responding to a sharing user selection operation triggered in the shared calendar creation interface, and displaying a target group user in the shared calendar creation interface; and responding to the storage operation triggered by the shared calendar creation interface, sending the edited content data of the shared calendar and the user data of the target group users as newly-built shared calendar information data to a first application server so that the first application server can issue a newly-built shared calendar notification to the target group users, wherein the first application server is a team instant messaging application server. The safety of calendar sharing is improved.

Description

Information sharing method and device

Technical Field

The embodiment of the invention relates to the technical field of computers, in particular to an information sharing method and device.

Background

The instant messaging application becomes one of the most commonly used applications on the mobile intelligent terminal. The instant messaging application can transmit characters, pictures, even voice and videos, and share webpage links, so that the communication efficiency between people is improved. With the application of personal instant messaging technology, the demand of team instant messaging is met, and various team instant messaging applications are urged to be generated, wherein the team instant messaging applications are managed by aiming at each team member in enterprises, schools or social organizations and can also send message notifications to specific groups of non-team members.

In the team instant messaging application, a team instant messaging application user can use an electronic calendar, add schedule information to the electronic calendar according to the needs of the user, and add schedule related to work or study.

In the prior art, users of team instant messaging applications share an electronic calendar through a calendar subscription link, but the calendar subscription link has a security problem, so that users of the team instant messaging applications in the prior art cannot share the electronic calendar in a secure manner.

Disclosure of Invention

The embodiment of the application provides an information sharing method and device, which are used for sharing an electronic calendar in a safe mode.

In one aspect, an embodiment of the present application provides an information sharing method, where the method includes:

a first client of a first application responds to the operation of creating the shared calendar and displays a shared calendar creation interface, the first application is a team instant messaging application, and the first client is a client for a creation user of the newly created shared calendar to log in through a first application account of the creation user;

the first client responds to the shared calendar content editing operation triggered in the shared calendar creation interface, and displays the shared calendar editing content in the shared calendar creation interface;

the first client responds to a sharing user selection operation triggered in the shared calendar creation interface, and displays target group users in the shared calendar creation interface;

the first client responds to the storage operation triggered by the shared calendar creation interface, the shared calendar editing content data and the user data of the target group users are sent to the first application server as newly-built shared calendar information data, so that the first application server can issue a newly-built shared calendar notification to the target group users, and the first application server is a team instant messaging application server.

the method comprises the steps that a first application server receives newly-built shared calendar information data sent by a first client of a first application, the newly-built shared calendar information data are determined after the first client responds to operation of the newly-built shared calendar, the first application is a team instant messaging application, the first application server is a team instant messaging application server, and the first client and a client which is a creating user of the newly-built shared calendar and logs in through a first application account of the creating user;

the first application server determines user data of a target group user in the newly-built shared calendar information data information, and issues a newly-built shared calendar notification message to the target group user based on the user data of the target group user.

Optionally, the issuing, by the first application server, a new shared calendar notification message to the target group user includes:

receiving notification indication information sent by a first application;

and sending a newly-built shared calendar notification to a second application server based on the notification indication information, so that a second application device sends the newly-built shared calendar notification to a second application client, and the newly-built shared calendar notification is displayed in a first application notification platform in the second application client, wherein the second application is a personal instant messaging application, the second application server is a personal instant messaging application server, and the second application client is a client logged in by a target group user through a second application account.

Optionally, after issuing a new shared calendar notification message to the target group user based on the user data of the target group user, the method further includes:

the method comprises the steps that a first application server receives a calendar information acquisition request sent by a second client of a first application, wherein the calendar information acquisition request is determined after the second client responds to a viewing operation triggered by a new shared calendar notification, and the second client is a client on which a target group user of the new shared calendar logs in through a first application account of the target group user;

and the first application server sends the calendar information data stored in the first application server and the first calendar identification information corresponding to the calendar information data to the second client, so that the second client displays the newly-built shared calendar in the calendar display interface.

Optionally, after the first application server sends each calendar information data stored in the first application server and each first calendar identification information corresponding to each calendar information data to the second client, the method further includes:

the method comprises the steps that a first application server receives a schedule information acquisition request aiming at a newly-built shared calendar, which is sent by a second client of a first application, wherein the schedule information acquisition request comprises a first operation sequence value of the newly-built shared calendar stored in a local database of the second client;

the first application server determines schedule information data according to the first operation sequence value and a second operation sequence value of the newly-built shared calendar acquired from local databases of other clients, wherein the operation sequence value is used for representing the editing times of the newly-built shared calendar, the second operation sequence value is stored in the local databases of the first client or other second clients, and the first operation sequence value is not larger than the second operation sequence value;

and the first application server sends the schedule information data to the second client so that the second client displays the schedule information in the calendar display interface.

On one hand, the embodiment of the application provides an information sharing system, which comprises a first client of a first application and a first application server, wherein the first client is a client for a creating user to create a shared calendar to log in through a first application account of the creating user, and the first application server is a team instant messaging application server;

the first client of the first application is to: responding to the operation of newly building the shared calendar, displaying a shared calendar building interface, wherein the first application is a team instant messaging application, and the first client corresponds to a building user of the newly built shared calendar; displaying the shared calendar editing content in the shared calendar creation interface in response to the shared calendar content editing operation triggered in the shared calendar creation interface; responding to a sharing user selection operation triggered in the shared calendar creation interface, and displaying a target group user in the shared calendar creation interface; in response to the storage operation triggered by the shared calendar creation interface, sending the edited content data of the shared calendar and the user data of the target group users as newly-built shared calendar information data to a first application server;

the first application server is specifically configured to: and issuing a notice of newly-built shared calendar to the target group users.

Optionally, the first client is further configured to:

responding to the authority setting operation of the target group user, and displaying the selectable authority on an authority setting interface;

responding to the storage operation of the authority setting interface, and establishing a target corresponding relation between the target group user and the selected target authority;

and taking the target corresponding relation as the user data of the target group user.

Optionally, the sharing system further includes a second client of the first application, where the second client is a client on which a target group user creating a new shared calendar logs in through a first application account of the target group user;

the second client is specifically configured to:

sending a calendar information acquisition request to a first application server in response to a viewing operation triggered by the newly-built shared calendar notification;

the first application server is further configured to: determining calendar information data according to the calendar information acquisition request, and sending the calendar information data to the second client;

the second client is specifically configured to: receiving calendar information data sent by a first application server, wherein the calendar information data comprises each calendar information data stored in the first application server and each first calendar identification information corresponding to each calendar information data;

determining identification information of a newly-built shared calendar corresponding to the notification of the newly-built shared calendar and newly-built shared calendar information data according to each second calendar identification information, each first calendar identification information and the target authority of a target group user stored in a local database of a second client;

and displaying the newly-built shared calendar in a calendar display interface based on the information data of the newly-built shared calendar.

Optionally, the second client is further configured to:

sending a schedule information acquisition request aiming at the newly-built shared calendar to a first application server, wherein the schedule acquisition request comprises a first operation sequence value of the newly-built shared calendar stored in a local database of a second client;

the first application server is further configured to: determining schedule information data based on a first operation sequence value in the schedule information acquisition request and a second operation sequence value of the newly-built shared calendar, and sending the schedule information data to a second client, wherein the operation sequence value is used for representing the editing times of the newly-built shared calendar information data, the second operation sequence value is stored in a local database of the first client or other second clients, and the first operation sequence value is not larger than the second operation sequence value;

the second client is specifically configured to: receiving schedule information data sent by a first application server, and updating a first operation sequence value in a local database of a second client into a second operation sequence value;

and displaying the schedule information in the calendar display interface according to the schedule information data.

Optionally, the first client is further configured to:

responding to a new calendar schedule operation triggered by the new shared calendar, and displaying a schedule creation interface;

displaying schedule editing content in the schedule creating interface in response to a schedule content editing operation triggered in the schedule creating interface;

responding to a storage operation triggered by a schedule creation interface, sending schedule editing content data to a first application server, and updating a second operation sequence value of a newly-created shared calendar in a local database of a first client;

the first application server is further configured to: and issuing the new schedule notice to the target group user.

Optionally, the first client is specifically configured to:

acquiring reference schedule data information of a target group user, which is sent by a first application server, wherein the reference schedule data is generated after a target group user newly establishes schedules in other calendars;

and determining whether the schedule editing content data conflicts with the reference schedule data, if so, displaying a prompt interface to prompt the creation user to modify the schedule editing content data.

Optionally, the first client is specifically configured to:

in response to schedule participation user selection operation triggered by a schedule creation interface, displaying schedule participation users in a schedule participation user selection interface, wherein the schedule participation users are users in the target group users;

responding to a schedule effective time editing operation triggered by a schedule creating interface, and displaying schedule effective time editing contents on a time setting interface;

the data processing unit is specifically configured to:

sending user data of a schedule participation user and time editing content data serving as schedule editing content data to a first application server;

the first application server is specifically configured to: and prompting the schedule participation user to participate in the new schedule corresponding to the new schedule notification before the schedule effective time.

Optionally, the first client is specifically configured to:

acquiring style information of a newly-built shared calendar;

the interface display unit is specifically configured to:

and displaying the schedule information according to the style information of the newly-built shared calendar.

Optionally, the second client is further configured to:

responding to schedule information modification operation triggered by a target date in a newly-built shared calendar interface, and determining whether the operation authority of a target group user corresponding to the modification operation meets the requirement of preset operation authority;

if the requirement of the preset operation authority is met, displaying a schedule information editing interface;

responding to schedule information editing operation triggered in the schedule editing interface, and displaying schedule information editing content in the schedule editing interface;

responding to a storage operation triggered by a schedule editing interface, sending schedule information editing content data serving as schedule updating information of a target date to a first application server, and updating a first operation sequence value in a local database of a second client;

the first application server is specifically configured to: and issuing schedule updating notification of the target date to other target group users and the creating user.

Optionally, the first client is further configured to:

sending notification indication information to a first application server, wherein the notification indication information is used for indicating the first application server to send a newly-built shared calendar notification to a second application corresponding to a target group user through a second application server, the second application is a personal instant messaging application, and the second application server is a personal instant messaging application server;

the first application server is further configured to: and sending the new shared calendar notification to the second application server so that the new shared calendar notification is displayed in the first application notification platform in the second application.

Optionally, the first client is specifically configured to:

acquiring information of a group to be selected and a contact list to be selected, and displaying the group to be selected and the contact list to be selected;

responding to the selection operation of the target group user, and displaying the selected group to be selected and/or the selected contact;

taking the selected group to be selected and/or the selected contact as a new shared calendar user group, and taking the new shared calendar user group data as the user data of the target group user;

the first application server is specifically configured to: and issuing a notice of the newly-built shared calendar to a user group of the newly-built shared calendar.

Optionally, the first client is further configured to:

responding to an unsubscribe newly-built shared calendar operation triggered by the newly-built shared calendar, and sending a user data updating message aiming at a target group user of the newly-built shared calendar to the first server, wherein the user data updating message comprises user data of an unsubscribing user of the newly-built shared calendar, and the user data updating message is used for indicating the first server to issue an unsubscribe user unsubscribe newly-built shared calendar notification to the target group user and a creating user;

the first application server is further configured to: and issuing a notice of unsubscribing the newly-built shared calendar to the target group users and the creation users.

In one aspect, an embodiment of the present application provides an information sharing apparatus, applied to a first application server, including:

the system comprises a receiving unit, a first client and a second client, wherein the receiving unit is used for receiving newly-built shared calendar information data sent by the first client, the newly-built shared calendar information data is determined after the first client responds to the operation of the newly-built shared calendar, the first application is a team instant messaging application, the first application server is a team instant messaging application server, and the first client and the client which is a creating user of the newly-built shared calendar log in through a first application account of the creating user;

and the sending unit is used for determining the user data of the target group user in the new shared calendar information data information and issuing a new shared calendar notification message to the target group user based on the user data of the target group user.

Optionally, the receiving unit is specifically configured to:

receiving notification indication information sent by a first client;

the sending unit is specifically configured to:

and sending a newly-built shared calendar notification to a second application server based on the notification indication information, so that the second application device sends the newly-built shared calendar notification to a second application, and the newly-built shared calendar notification is displayed in a first application notification platform in the second application, wherein the second application is a personal instant messaging application, and the second application server is a personal instant messaging application server.

Optionally, the receiving unit is further configured to:

receiving a request for obtaining calendar information sent by a second client, wherein the request for obtaining the calendar information is determined after the second client responds to a viewing operation triggered by aiming at a newly-built shared calendar notification, and the second client is a client for logging in a target group user of the newly-built shared calendar through a first application account of the target group user;

the sending unit is further configured to:

and sending each calendar information data stored in the first application server and each first calendar identification information corresponding to each calendar information data to the second client so that the second client displays the newly-built shared calendar in a calendar display interface.

Optionally, the receiving unit is further configured to:

receiving a schedule information acquisition request aiming at the newly-built shared calendar, which is sent by a second client, wherein the schedule acquisition request comprises a first operation sequence value of the newly-built shared calendar stored in a local database of the second client;

determining schedule information data according to the first operation sequence value and a second operation sequence value of the newly-built shared calendar acquired from local databases of other clients, wherein the operation sequence value is used for representing the editing times of the newly-built shared calendar, the second operation sequence value is stored in the local databases of the first client or other second clients, and the first operation sequence value is not greater than the second operation sequence value;

the sending unit is further configured to:

and sending the schedule information data to the first application so that the second client displays the schedule information in the calendar display interface.

In one aspect, an embodiment of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the steps of the information sharing method when executing the computer program.

In one aspect, embodiments of the present application provide a computer-readable storage medium, which stores a computer program executable by a computer device, and when the program runs on the computer device, the computer device is caused to execute the steps of the information sharing method.

The information sharing method provided in the embodiment of the application can respond to a request of a creating user for creating a new shared calendar, determine calendar data of the new shared calendar through calendar content edited by the creating user, and use at least one target group user selected by the creating user as a sharing user of the new shared calendar, that is, the new shared calendar is shared by the creating user and at least one target group user, after the creating user is created, the first application server sends a notification of the new shared calendar to each target group user, each target group user can view the notification, and the new shared calendar can be displayed in calendar display interfaces of the creating user and at least one target group user, and the displayed content is edited according to the creating user when creating the new shared calendar.

By the information sharing method, the shared calendar is established in the team instant messaging application, a plurality of team instant messaging application users can share the calendar schedule through the shared calendar, and the information sharing method is realized through interaction between the team instant messaging application and the background server without involving a calendar sharing link, so that the safety of calendar sharing is improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.

Fig. 1 is a schematic view of an application scenario of an information sharing method according to an embodiment of the present application;

fig. 2 is a schematic view of an application scenario of an information sharing method according to an embodiment of the present application;

fig. 3 is a schematic flowchart of an information sharing method according to an embodiment of the present disclosure;

fig. 4 is a schematic diagram of a first application interface according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a method for triggering an operation of creating a new shared calendar according to an embodiment of the present application;

FIG. 6 is a schematic illustration of a calendar interface provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of a newly created shared calendar interface according to an embodiment of the present application;

FIG. 8 is a schematic diagram illustrating a method for setting a new shared calendar style according to an embodiment of the present application;

fig. 9 is a schematic diagram illustrating a method for selecting a target group of users according to an embodiment of the present disclosure;

FIG. 10 is a diagram illustrating a selection of a target group of users according to an embodiment of the present disclosure;

fig. 11 is a schematic diagram of a notification message interface according to an embodiment of the present application;

fig. 12 is a schematic diagram of a notification message interface according to an embodiment of the present application;

fig. 13 is a schematic diagram illustrating a method for setting permissions to target group users according to an embodiment of the present application;

fig. 14 is a schematic diagram illustrating a method for setting permissions to target group users according to an embodiment of the present application;

fig. 15 is a schematic view of an application scenario of an information sharing method according to an embodiment of the present application;

FIG. 16 is a schematic diagram of a new schedule interface according to an embodiment of the present application;

fig. 17 is a schematic diagram of a data interaction method according to an embodiment of the present application;

FIG. 18 is a diagram illustrating a method for selecting a calendar for display according to an embodiment of the present disclosure;

FIG. 19 is a schematic diagram of a multi-schedule display provided in an embodiment of the present application;

fig. 20 is a schematic diagram of a notification message provided in an embodiment of the present application;

fig. 21 is a schematic diagram of a notification message provided in an embodiment of the present application;

fig. 22 is a schematic diagram illustrating an interaction method of notification messages according to an embodiment of the present application;

fig. 23 is a schematic diagram illustrating a method for displaying a notification message in a personal instant application according to an embodiment of the present application;

fig. 24 is a schematic view of an application scenario of an information sharing method according to an embodiment of the present application;

fig. 25 is a schematic structural diagram of an information sharing apparatus according to an embodiment of the present disclosure;

fig. 26 is a schematic structural diagram of an information sharing apparatus according to an embodiment of the present disclosure;

fig. 27 is a schematic structural diagram of a computer device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more clearly apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

For convenience of understanding, terms referred to in the embodiments of the present application are explained below:

electronic calendar: the electronic calendar is software which is applied to a plurality of operating systems and integrates functions of a calendar, weather, an alarm clock, notes, a yellow calendar and the like, the electronic calendar comprises elements such as calendar names, colors, descriptions and the like, and each calendar event in the electronic calendar is called a schedule and consists of a plurality of elements such as calendar event questions, time, places, participators, notes and the like.

Sharing the calendar: refers to an electronic calendar shared by a plurality of users, and the shared calendar comprises a creating user and a shared user of the shared calendar besides elements in the electronic calendar.

Instant Messaging (IM for short): the instant message sending and receiving process is carried out among the mobile terminal, the tablet computer and the computer user by utilizing a network. The instant messaging can transmit characters, pictures, even voice and video, share webpage links, and improve the communication efficiency between people.

The instant messaging application: an application software developed based on an instant messaging technology is a social application capable of transmitting characters, pictures, even voice and video and sharing webpage links. The team instant messaging application and the personal instant messaging application can be divided according to the fact that a user is a platform, an organization or an individual user for distinguishing. The team instant messaging application can be understood as an instant messaging application used by enterprises, companies, specific groups and specific organizations, and can be used for managing each team person in a team and sending management information to each team person; the personal instant messaging application refers to an instant messaging application used by an individual user, and the individual user can use the personal instant messaging application to carry out information transmission with other individual users and also can carry out information transmission with members or groups in the team instant messaging application through the personal instant messaging application.

And (3) notifying the platform: the content sharing platform is a content sharing platform in team instant messaging application, a main body of sending and editing of the content sharing platform is a user in the team instant messaging application, and the user in the team instant messaging application can display push information sent by the team instant messaging application in the content sharing platform in the personal instant messaging application of the user in the team instant messaging application in a mode of registering the content sharing platform.

In a specific practical process, the inventor of the present application finds that the prior art scheme for implementing calendar sharing is implemented by a subscription link. Specifically, users sharing the calendar are used as organizers, and users shared by the calendar are used as shared persons. The organizer sends the details of the calendar and the schedule to the background, the background generates a subscription link, and the organizer sends the link to the shared person through various channels after obtaining the subscription link. The sharees can use the link to access calendar and event details and add to their own calendars, and updates to the calendars and schedules can be propagated to the sharees.

However, the method for sharing a calendar through a subscription link in the prior art has at least the following problems:

firstly, the subscription link has information leakage risk, and if the link is leaked to a third party, calendar and schedule information can be obtained by unrelated people outside a team; secondly, in the prior art, the calendar sharing process is complicated, and after an organizer acquires a subscription link, the link is distributed through communication tools such as mails and instant messaging, so that information cannot be sent to a shared person in time; finally, the organizer cannot effectively manage the shared calendar, and the organizer cannot acquire effective information aiming at the conditions that the shared person does not subscribe the calendar, the shared person removes the calendar after subscribing the calendar and the like, so that the cooperation efficiency is reduced.

Based on the above problem, the inventor of the present application first invented an information sharing method, in the present application, a shared calendar is newly created in a team instant messaging application, content data of the shared calendar is determined by calendar content edited by a creating user of the newly created shared calendar, and shared users of the shared calendar are determined by target group users selected by the creating user of the newly created shared calendar.

And further, the team instant messaging application sends the content data to a team instant messaging application server, the team instant messaging application server issues a newly-built shared calendar notification to each shared person, and each shared user can obtain the newly-built shared calendar based on the newly-built shared calendar notification.

By the method, the shared user obtains the newly-built shared calendar through the internal data communication process of the team instant messaging application, and the calendar link is not involved in the sharing process of the newly-built shared calendar, so that the safety of shared calendar data can be guaranteed, namely, only the creating user and the shared user can view the shared calendar, and other users in the team instant messaging application cannot obtain the shared calendar data.

After introducing the design concept of the embodiment of the present application, some simple descriptions are provided below for application scenarios to which the technical solution of the embodiment of the present application can be applied, and it should be noted that the application scenarios described below are only used for describing the embodiment of the present application and are not limited. In specific implementation, the technical scheme provided by the embodiment of the application can be flexibly applied according to actual needs.

To further illustrate the technical solutions provided by the embodiments of the present application, the following detailed description is made with reference to the accompanying drawings and the detailed description. Although the embodiments of the present application provide method steps as shown in the following embodiments or figures, more or fewer steps may be included in the method based on conventional or non-inventive efforts. In steps where no necessary causal relationship exists logically, the order of execution of the steps is not limited to that provided by the embodiments of the present application.

In order to solve the problems of a text classification method in the prior art, the application provides an information sharing method. Referring to fig. 1, it is a system architecture diagram applicable to the embodiment of the present application, which includes at least a creation user terminal 101, a target group user terminal 102, a team instant messaging application server 103, and a personal instant messaging application server 104.

The creating user terminal 101 runs a team instant messaging application, and the creating user terminal 101 can run the team instant messaging application through a team instant messaging application client, a team instant messaging application web page version client, or a team instant messaging application applet client.

The creating user triggers a new shared calendar operation in the team instant messaging application running in the creating user terminal 101, edits calendar content in a shared calendar creating interface, and selects a target group user, wherein the target group user is a shared user of the new shared calendar, and the target group user is also a user of the team instant messaging application.

After the creating user terminal 101 completes the operation in response to the newly created shared calendar of the creating user, the calendar information data of the newly created shared calendar is sent to the team instant messaging application server 103, the team instant messaging application server 103 sends a notification of the newly created shared calendar to the target group user terminal 102 used by the target group user, and the notification of the newly created shared calendar is displayed in the team instant messaging application operated by the target group user terminal 102.

Similarly, the target group user terminal 102 runs a team instant messaging application, and the target group user terminal 102 may run the team instant messaging application through a team instant messaging application client, a team instant messaging application web page version client, or a team instant messaging application applet client.

The creating user terminal 101 may include one or more processors 1011, memory 1012, an I/O interface 1013 interacting with the team instant messaging application server 103, and a display panel 1014, among other things. The creation user terminal 101 may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, and the like.

Likewise, the target group user terminal 102 may include one or more processors 1021, memory 1022, an I/O interface 1023 to interact with the team instant messaging application server 103, and a display panel 1024, among other things. The target group user terminal 102 may be, but is not limited to, a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, and the like.

In the embodiment of the present application, the team instant messaging application server 103 is a background server of the team instant messaging application, and provides services for each client of the team instant messaging application. The team instant messaging application server 103 can save the calendar information data of the newly created shared calendar transmitted by the creating user terminal 101 and can transmit a notification of the newly created shared calendar to each target group user terminal 102 of each target group user.

The team instant messaging application server 103 may include one or more processors 1031, memory 1032, and I/O interface 1033 to interact with the creating user terminal 101, the target group user terminal 102, and the like. Server 103 may also configure database 1034. The server 103 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like. The creating user terminal 101, the target group user terminal 102 and the team instant messaging application server 103 may be directly or indirectly connected through wired or wireless communication, and the application is not limited herein.

Further, as shown in fig. 2, in the embodiment of the present application, the creating user terminal 101 may further send a new shared calendar notification to the display of the personal instant messaging application used by the target group user through the interaction between the team instant messaging application server 103 and the personal instant messaging application server 104.

Specifically, in this embodiment of the application, the creating user terminal 101 sends notification instruction information to the team instant messaging application server 103, after receiving the notification instruction information, the team instant messaging application server 103 sends a new shared calendar notification to the personal instant messaging application server 104, the personal instant messaging application server 104 sends the new shared calendar notification to the target group user terminal 102, the personal instant messaging application is run in the target group user terminal 102, and a team instant messaging application notification platform in the personal instant messaging application displays the new shared calendar notification.

In the embodiment of the present application, the target group user terminal 102 runs a personal instant messaging application, and the target group user terminal 102 may run the personal instant messaging application through a personal instant messaging application client, a personal instant messaging application web page version client, or a personal instant messaging application applet client.

The personal instant messaging application server 104 may include one or more processors 1041, memory 1042, and I/O interface 1043 to interact with the creating user terminal 101, the target group user terminal 102, the team instant messaging application server 103, and the like. In addition, personal instant messaging application server 104 may also configure database 1044. The personal instant messaging application server 104 may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing basic cloud computing services such as a cloud service, a cloud database, cloud computing, a cloud function, cloud storage, a Network service, cloud communication, a middleware service, a domain name service, a security service, a Content Delivery Network (CDN), a big data and artificial intelligence platform, and the like. The creating user terminal 101, the target group user terminal 102, the team instant messaging application server 103 and the personal instant messaging application server 104 may be directly or indirectly connected through wired or wireless communication, and the present application is not limited herein.

Of course, the method provided in the embodiment of the present application is not limited to be used in the application scenarios shown in fig. 1 and fig. 2, and may also be used in other possible application scenarios, and the embodiment of the present application is not limited. Functions that can be implemented by each device in the application scenarios shown in fig. 1 and fig. 2 will be described together in the following method embodiments, and will not be described in detail herein.

The following describes the technical solution provided in the embodiment of the present application with reference to the application scenarios shown in fig. 1 and fig. 2.

To facilitate the introduction of the information sharing method in the embodiment of the present application, a process of creating a shared calendar is first introduced.

In the embodiment of the application, a client used by a creating user for creating the new shared calendar is a first client, a first application runs in the first client, and the first application is a team instant messaging application; the shared users of the newly-built shared calendar are target group users, the target group users are selected by the creation user, at least one target group user exists, and the client used by each target group user is a second client.

Specifically, as shown in fig. 3, in the process of creating a new shared calendar, the method includes the following steps:

step S301, the first application in the first client responds to a new shared calendar operation triggered by the creation user, and displays a shared calendar creation interface.

In the embodiment of the present application, the creating user may enter the "calendar" interface by triggering a "schedule" control in the first application interface, as shown in fig. 4 and 5 in detail.

Fig. 4 represents a first application interface, where the first application interface includes controls such as "message", "address book", "workbench", "me", and the like, and also includes controls such as "schedule" and "to-do".

The "message" control is used to display communication messages in the first application, displaying the communication messages in a message list, each message notification line corresponding to a first application user, group or other application.

The address book control is used for displaying the associated users of the creating user in the first application, and the associated users may include users belonging to the same group, or may include users belonging to a friend relationship with the creating user, but not belonging to the same group.

The 'workbench' control is used for carrying out work processing, a workbench interface is displayed after the 'workbench' control is triggered specifically, each work module is included in the workbench interface, and the specific work module can be self-defined without limitation.

The "I' M" control is used to characterize the attribute information of the creating user and to provide the creating user with an interface for personalized settings.

The schedule control is used for displaying a calendar and schedule information in the calendar and recording the contents of work plans and the like of a creation user.

The to-do control is used for displaying the to-do event of the creation user.

In the embodiment of the present application, the creating user triggers a "schedule" control to jump from the first application interface shown in fig. 4 to a calendar interface, the calendar interface is shown in fig. 5, calendar information is displayed, and for each date in the calendar information, a schedule corresponding to the date is displayed.

In an alternative embodiment, the calendar interface has calendar information in the upper portion and schedule information in the lower portion.

Of course, fig. 4 and fig. 5 are only exemplary interface descriptions, and other interface display manners are also within the scope of the embodiments of the present application, and are not limited herein.

In the embodiment of the application, after the calendar interface is displayed, a newly-built shared calendar interface can be triggered in a voice mode, a gesture mode and the like, and the newly-built shared calendar interface can also be triggered through a control.

In an alternative embodiment, the creating user displays the calendar setting interface by triggering the "calendar setting control" in fig. 5, and displays the new shared calendar interface in the "new calendar" control in the calendar setting interface. Specifically, an optional calendar setting interface is shown in fig. 6, where in fig. 6, a calendar style selection area and a calendar list area are included, the calendar style may include a color, a font, a display time system, and the like, the display time system may include display according to a day mode, display according to a three-day mode, or display according to a week mode, and of course, other display time system modes, for example, display according to a month mode, and the like, and details thereof are not repeated here.

In fig. 6, a "new calendar" control is included, and through the "new calendar" control, a new shared calendar operation can be triggered, and a shared calendar creation interface is displayed.

Specifically, the shared calendar creation interface may include a plurality of editing areas, for example, the shared calendar creation interface includes at least a calendar name editing area in which a calendar name may be input and a target group user selection area in which a target group user may be selected.

Of course, the shared calendar creation interface in the embodiment of the present application may further include other editing areas, for example, a shared calendar style editing area.

Illustratively, as shown in FIG. 7, an exemplary shared calendar creation interface is displayed in which a calendar name edit area, a calendar description edit area, a target group user selection area, and a shared calendar style edit area are included.

Step S302, the first application running in the first client responds to the shared calendar content editing operation in the calendar creation interface by the creation user, and displays the shared calendar editing content in the shared calendar creation interface.

Specifically, in the embodiment of the present application, the creating user may edit the content in the calendar creating interface and display the content in the shared calendar creating interface.

In an alternative embodiment, the creating user inputs a name of the newly created shared calendar in the calendar name editing area, a preset rule of the name can be set, and when the content input by the creating user meets the preset rule, the content input by the creating user is displayed in the calendar name editing area; if the content input by the creating user meets the preset rule, prompt information is displayed, and the prompt information can be 'please input the content meeting the naming rule'.

Illustratively, the rule is preset to allow only Chinese characters to be input, and when the creating user inputs Chinese characters, the Chinese characters input by the creating user are displayed in the calendar name editing area, and when the creating user inputs English characters, the "please input Chinese name" is displayed in the calendar name editing area.

In the embodiment of the present application, the creating user may select the shared calendar style in the shared calendar style editing area, and in an alternative embodiment, as shown in fig. 8, the creating user may select any one of a style 1, a style 2, an amniotic fluid 3, and a style 4.

Step S303, the first application running in the first client responds to the sharing user selection operation of the creation user, and displays the selected target group user.

Specifically, in the embodiment of the present application, in order to share a newly-created shared calendar, a target group user needs to be selected for sharing, and a creating user may select the target group user from team members belonging to the same work team or select the target group user from friends of the creating user.

In an alternative embodiment, as shown in fig. 9, after the creating user triggers the editing operation of the target group user selection area, target group users to be selected are displayed, and after the creating user selects any user as a target group user, the user displays the selected state, as shown in fig. 10, if the user a and the user B are the target group users selected by the creating user, and the user a and the user B belong to the work team 1 with the creating user, the user a and the user B display the selected state.

Optionally, in this embodiment of the application, a group may be selected as a target group user, for example, a target group user selected by a user is created as a first group, the first group displays a selected state, the first group includes a user D, a user E, and a user F, and the user D, the user E, and the user F are target group users.

Or, in this embodiment of the application, the creating user may select a plurality of groups to be selected and a plurality of independent contacts as target group users, which is not described herein again.

Step S304, the first application running in the first terminal responds to the saving operation triggered by the creation user on the shared calendar creation interface, and saves each edited content data of the newly created shared calendar, specifically, data such as calendar description information, calendar style information, target group user information, and the like.

In this embodiment of the present application, when the creating user performs a saving operation triggered by the creating user on the shared calendar creation interface, the creating user completes a process of creating a new shared calendar, so that a notification needs to be issued to each target group user through the first application server, where the notification is displayed in the first application corresponding to each target group user, that is, the notification is displayed in the first application operated by the second client.

In the embodiment of the present application, the notification may be displayed in the second client of each target group user, or the notification may be displayed in the sharing group by using each target group user as one sharing group.

Illustratively, the target group users selected by the creating user are user a, user B, user D, user E and user F, and the notification may be sent to the second clients corresponding to user a, user B, user D, user E and user F, and displayed in each second client; user a, user B, user D, user E, and user F may also establish a new sharing group and display a notification in the sharing group interface.

That is, the sharing group interface is displayed in the second client interfaces corresponding to the user a, the user B, the user D, the user E, and the user F, and the notification is displayed in the sharing group interface.

Of course, in the embodiment of the present application, there are other methods for displaying the notification, for example, when the target user selected by the creation user is a plurality of groups to be selected and a plurality of independent contacts, the notification may be displayed in the interface corresponding to each group to be selected, and the notification may be displayed in the notification display interface of the independent contacts.

Specifically, in step S305, the first client sends the newly created shared calendar information data to the first application server.

And step S306, the first application server stores the newly-built shared calendar information data.

Step S307, the first application server sends a notification of creating a shared calendar to the second client.

Step S308, after the first application running in the second client receives the notification of the newly-built shared calendar, the notification is displayed in the first application interface. In an alternative embodiment, the message list in the first application interface includes the message list of the "schedule" application, and the new shared calendar notification is displayed in the message list of the "schedule" application, as shown in fig. 11.

In the embodiment of the application, in order to facilitate the creation user to manage the newly-created shared calendar, the creation user can set the permissions for the target group of users, and the different permissions correspond to different operation ranges. In an optional embodiment, the optional permission comprises three permissions of being viewable, editable and only viewing idle and busy states.

Specifically, the view permission is a default permission, the target group user is allowed to view all information of the calendar and the schedule in the calendar, but the editing, the new creation and the deletion of the calendar and the schedule in the calendar are not allowed.

The editable authority is the highest authority, and the target group users are allowed to view, edit, create and delete the calendar and the schedule in the calendar.

Only the permission of the idle busy state is checked, only the target group user is allowed to check the calendar information and the time information of the schedule, the information of the theme, the place, the remark and the like of the schedule cannot be checked, and the calendar and the schedule in the calendar are not allowed to be edited, newly built and deleted. Illustratively, as shown in fig. 12, when viewing details of a schedule, a target group user having the right to view only a busy status can only view time information of the schedule and to which calendar the schedule belongs, but cannot view other information.

The method for setting the permission of the target group user may be exemplarily explained, as shown in fig. 13, after the user a and the user B are selected as the target group user, the permission may be set for the user a and the user B, and specific permission contents are shown in fig. 14, and include three permissions of being viewable, editable, and viewing only a busy state. When the creating user determines the user's right, the right displays the selected state.

After the process of creating a new shared calendar by the user is introduced, the process of creating a new schedule in the new shared calendar by the user is described below, as shown in fig. 15 in detail.

Step S1501, the creating user triggers a new schedule creating operation aiming at the first application running in the first client, and displays a new schedule creating interface.

In the embodiment of the application, there are various ways for the creating user to trigger the new schedule operation, for example, the ways of voice, gesture, etc., and the new schedule operation can also be triggered through the control.

In step S1502, the first application displays the editing content in the new schedule interface in response to the editing operation of the creation user.

In the embodiment of the application, the newly-built schedule interface at least comprises a schedule name editing area, and further comprises a schedule effective time editing area, the representation schedule takes effect in the set time range, and meanwhile, the newly-built schedule interface also comprises a schedule participation user selection editing area, the creation user can select a schedule participation user, and the schedule participation user can be all target group users or part of the target group users.

Further, the schedule may be a meeting schedule, so the newly-built schedule interface also includes a meeting room selection editing area, and the creation user is used to select a meeting room.

In an optional embodiment, when the effective time of the schedule is close, a notification can be sent to remind a schedule participant, so that a reminder editing area can be further included in the newly-built schedule interface.

Specifically, as shown in fig. 16, a newly created schedule interface is exemplarily displayed, and the interface includes a schedule name editing area, a schedule effective time editing area, a schedule participation user selection editing area, a meeting room selection editing area, and a reminder editing area.

Further, when the creating user creates the schedule, schedule data edited and generated by the target group user in other calendars can be acquired, and whether the creating schedule conflicts with schedules of the target group user in other calendars or not can be determined.

For example, in the embodiment of the present application, the target group users include user a, which is a group user in shared calendar a, shared calendar B, and shared calendar C, where user a has a schedule on 5 days, user a has a schedule on 7 days, and user C has a schedule on 8 days; when a creating user creates a 7-day schedule for a newly-created shared calendar, a conflict reminder is displayed to prompt the creating user to modify the schedule; when the creating user creates a 4-day schedule, there is no conflict and the schedule can be established.

In step S1503, the first application responds to the saving operation of the creation user for the new schedule interface, and saves the new schedule data.

In the embodiment of the application, after the creating user determines the new schedule, the creating user needs to notify each target group user, so that interaction with the first application server is needed. Specifically, in the embodiment of the present application, a notification of the newly-built schedule is sent to each target group user according to the following steps.

In step S1504, the first application sends the new schedule data to the first application server.

In step S1505, the first application server stores the new schedule data.

Step S1506, the first application server sends a new schedule notification to the second client corresponding to the target group user.

In step S1507, the second client displays a new schedule notification.

In the above embodiment, for the newly created shared calendar, the first application and the first application server store the newly created shared calendar information data and the newly created schedule information data, and the newly created schedule information data may be stored as part of the data in the newly created shared calendar information data, that is, the first application and the first application server store the newly created shared calendar information data, and the newly created shared calendar information data includes each newly created schedule information data.

In an alternative embodiment, when the first application sends the newly created shared calendar information data to the first application server, the first application sends the identification information of the newly created shared calendar information to the first application server, and the first application server may store the newly created shared calendar information data based on the identification information of the newly created shared calendar information.

Illustratively, a plurality of calendar information data are stored in the first application and the first application server, and the calendar information data are stored according to identification information, as shown in table 1, identification information 1 corresponds to calendar information data 1, identification information 2 corresponds to calendar information data 2, and identification information 3 corresponds to calendar information data 3 … …

TABLE 1

Identification information	Calendar information data
		Identification information 1	Calendar information data 1
Identification information 2	Calendar information data 2
		Identification information 3	Calendar information data 3
Identification information 4	Calendar information data 4
		……	……

For any of the calendar information data in table 1, the included contents may include a calendar name, a style, target group user information, target group user authority, and schedules in the calendar information as shown in table 2.

TABLE 2

For any schedule, the specifically included content may be as shown in table 3, and may include a schedule name, a schedule effective time, schedule participation user information, meeting room information, reminder information, and the like:

TABLE 3

Further, in the embodiment of the present application, since both the creating user and the target group user having editable authority may edit the newly created shared calendar, for example, edit the name of the newly created shared calendar, edit the style of the newly created shared calendar, or edit the schedule in the newly created shared calendar, in order to facilitate consistency of the newly created shared calendar, an operation sequence value is generated for the newly created shared calendar, the operation sequence value is used to represent the number of operations of the newly created shared calendar, and the initial value of the operation sequence value is 0.

When the creating user and the target group user with the editable authority edit the newly-built shared calendar, the operation sequence value is increased by 1 every time the editing operation is executed.

The local database of the first client and the local database of the second client both store the operation sequence value and send the operation sequence value to the first application server, and the first application server records the operation sequence value in the local database of the client and updates the newly-built shared calendar through the operation sequence value.

After the process of creating a new schedule for the new shared calendar by the user is introduced, the following introduces a process of acquiring the new shared calendar and the new schedule by the second client used by each target group user.

After the first application server sends the new shared calendar notification to the second clients used by the target group users, the first application running in each second client displays the new shared calendar notification, for example, as shown in fig. 11.

And after the notice of the newly-built shared calendar is displayed, acquiring calendar information data of the newly-built shared calendar, wherein the process of acquiring the calendar information data is an interactive process from the second client to the first application server.

Specifically, the second client acquires all calendar identification information stored by the first application service from the first application server, and the second client compares the calendar identification information stored in the local database with the calendar identification information stored in the first application server.

If some calendar identification information exists in the second client but the calendar identification information stored in the first application server does not exist, determining that the calendar corresponding to the calendar identification information is deleted, and deleting the calendar by the second client.

For example, the calendar identification information stored in the second client is calendar identification 1, calendar identification 2 and calendar identification 3, and the calendar identification information stored in the first application server is calendar identification 1 and calendar identification 2, which indicates that the calendar corresponding to calendar identification 3 has been deleted, so that the second client deletes the calendar information data corresponding to calendar identification 3 in the local data.

If the second client does not have certain calendar identification information stored in the first application server, the calendar corresponding to the calendar identification information can be determined to be newly added calendar information, and the newly added calendar information data is acquired from the first application server.

Specifically, when acquiring the newly added calendar information, the authority of a target group user using the second client needs to be determined, and the newly added calendar information data is acquired according to the authority of the target group user, for example, if the authority of the target group user is a viewable and editable authority, all information data of the newly added calendar information is acquired, and if the authority of the target group user is a busy-view only authority, information data corresponding to a busy-view only authority in the newly added calendar information is acquired.

In an alternative embodiment, whether the calendar has an update is determined by an operation sequence value locally stored in the second client and an operation sequence value of the calendar acquired by the first application server.

Illustratively, the operation sequence value of each calendar is represented by seq, the first client and the second client maintain a maximum seq value of local data for each calendar, and the seq value and the maximum acceptable result number limit are carried when acquiring a calendar update request from the first application server. And the first application server returns data larger than seq values of the first client and the second client in ascending order, and returns limit pieces of data at most. And after the first client and the second client receive a batch of data, taking the maximum seq value as the updated seq value in the local database.

The above-described contents can be explained with reference to fig. 17, in fig. 17, the first application server acquires the entire amount of calendar identification information, and acquires the calendar information data based on the calendar identification information stored in the local database of the first client or the second client and the authority of the creating user and the target group user.

Specifically, the local database of the first client or the second client may delete the calendar information data, add the calendar information data, and update the calendar information data.

In the above embodiment, the calendar information data includes the schedule information data, so through the above process, the calendar information data and the schedule information data in the calendars can be acquired.

Certainly, in the embodiment of the present application, the schedule information data may also be actively sent to the first client and the second client by the first application server after determining that there is schedule information update data, for example, after receiving the schedule information update data, the first client sends an update notification to the first client and the second client, so that the first client and the second client update the schedule information.

In the embodiment of the application, no matter the creating user or the target group user, multiple shared calendars can be received, so after the first client or the second client acquires the calendar information data, multiple pieces of calendar information and multiple pieces of schedule information in the multiple pieces of calendar information can be displayed in the first application running in the first client or the second client.

In an alternative embodiment, each user may select the displayed calendar information by triggering a "calendar setting control," which in turn enables selection of the displayed schedule.

Illustratively, as shown in fig. 18, user a has a shared calendar created by zhang, and a shared calendar created by lie, and can select which calendar to display, and when the user selects the calendar, the calendar in the interface is selected.

Further, as shown in fig. 19, when the user a clicks the date No. 7 in the calendar, in the shared calendar information data created by zhang san, the schedule 1 and the schedule 2 are set to the date No. 7, so that the schedule 1 and the schedule 2 are displayed in the schedule information list of the date No. 7, and the schedule 1 and the schedule 2 are displayed as belonging to the zhang calendar; in the shared calendar information data created by lie ii, schedule 3 is set to No. 7, so schedule 3 is also displayed in the schedule information list of date No. 7, and the calendar to which schedule 3 belongs is displayed.

In another optional embodiment, the shared calendar information data created by zhang, san, and zhu, also includes calendar style information, and in the display interface of the user a, the schedule 1 and the schedule 2 are displayed according to the calendar style set by zhang, and the schedule 3 is displayed according to the calendar style set by zhu, respectively.

For example, if the display color of the calendar style set by zhang san is red and the display font is regular script, schedule 1 and schedule 2 are displayed in red regular script when displayed. The display color in the calendar style set by the plum two is black, the display font is Song style, and the schedule 3 is displayed by the black Song style when being displayed.

After the process of the target group user obtaining the calendar information data and the schedule information data is introduced, the process of the target group user editing the calendar or the schedule is introduced below.

In the embodiment of the application, the first application in the second client determines the authority of the target group user firstly in response to the editing operation of the target group user on the calendar or the schedule.

In the embodiment of the application, the local database of the second client stores calendar information data, the calendar information data comprises user data of the target group user, and the user data comprises authority data, so that the authority of the target group user can be determined according to the authority data in the local database.

And when the authority of the target group user is determined to be capable of editing, displaying an editing interface, and editing the target group user in the editing interface.

And when the target group user triggers the storage operation aiming at the editing interface, the second client updates the calendar information data according to the editing content, the updated calendar information data is sent to the first application server, and the first application server sends a calendar information updating notice to other second clients and the first client.

Specifically, the calendar information update notification is displayed in the other second client and the first application running in the first client. And the operation sequence value corresponding to the calendar information in the local database of the second client is increased, so that other second clients and the first client can update the calendar information data conveniently.

And when the authority of the target group user is determined not to be edited, popping up prompt information, wherein in an optional embodiment, the prompt information is 'no editing authority'.

In the embodiment of the present application, when the target group user deletes the newly created shared calendar information, other target group users and the creating user can receive a notification.

Specifically, the target group user may select the calendar information to be deleted after triggering the "calendar setting control", and the target group user may delete a plurality of pieces of calendar information in one time or delete only one piece of calendar information in one calendar display interface, which is not limited herein.

When the target group user deletes the calendar information, the second client deletes the calendar information data stored in the local database, meanwhile, the second client sends a target group user update message aiming at the calendar information to the first application server, and the first application server sends a target group update notification to other second clients or the first client.

The creating user and the target group user can get the update notification through the message list in the first application interface, for example, as shown in fig. 20, in the calendar notification bar in the first application interface, it is displayed that XX user quits the new shared calendar notification, and further, when the creating user and the target group user click the notification message, the interface as shown in fig. 21 is displayed.

The interface of fig. 21 is a calendar information notification interface in which calendar image identification and notification specific content are included, and through which the creating user and the target group user can be notified of the update.

Optionally, in this embodiment of the application, the notification that the XX user exits from the new shared calendar is displayed in the display interfaces of the target group users and the creating user, and may also be displayed in the notification of the new shared calendar shared group formed by the target group users and the creating user.

Further, in the embodiment of the present application, since the first application is a team instant messaging application, and interaction can be performed between the team instant messaging application and the personal instant messaging application, all notifications in the embodiment of the present application can be displayed in the personal instant messaging applications of the target group users and the creating user.

An optional embodiment, taking the newly created shared calendar notification as an example, a first application sends notification indication information to a first application server through a first client, where the notification indication information is used to indicate that the first application server sends the newly created shared calendar notification to a second application corresponding to a target group user through a second application server, so that the newly created shared calendar notification is displayed in a first application notification platform in the second application, the second application is a personal instant messaging application, and the second application server is a personal instant messaging application server.

As shown in fig. 22, the process of interaction among the first client, the first application server, the second application server, and the second client is as follows:

step 2201, the first client sends notification instruction information to the first application server;

step S2202, the first application server sends a notice of creating a shared calendar and identification information of each target group user to the second application server;

step 2203, the second application server determines the second client of each target group user according to the identification information of each target group user;

step 2204, the second application server sends the notice of the newly-built shared calendar to each second client;

in step S2205, a new shared calendar notification is displayed in the first application notification platform in the second application running in the second client.

The target group user uses the second client to run the second application interface, as shown in fig. 23, in the message list in the second application interface, there is a message list of the first application, and a notification of creating the new shared calendar is displayed, where the message list of the first application is a message sent by the content sharing platform of the first application in the second application.

Of course, other notification messages in the embodiment of the present application may also be displayed in the message list of the first application in the second application interface, for example, the calendar information notification is edited, the calendar information notification exits, and the like, which are similar to the above interaction process and are not described herein again.

In order to better explain the embodiment of the present application, the information sharing method provided by the embodiment of the present application is described below with reference to a specific implementation scenario, specifically, there are a user a, a user B, and a user C, the user a creates a calendar a when using the first application, and sets the sharing user as the user B and the user C for the calendar a, and meanwhile, the user a newly creates a schedule 1 in the calendar a.

In the first application used by the user B and the user C, the calendar a and the schedule 1 can be displayed, and the user B has an editable authority, which is set by the user a, so that the user B newly creates a calendar 2 for the calendar a, and schedule information of the calendar a in the user a, the user B and the user C includes the schedule 1 and the schedule 2.

The above process is essentially an interactive process of clients of user a, user B, and user C with a team instant messaging application server, as shown for example in fig. 24.

In fig. 24, the clients of user a, user B, and user C send updated data to the team instant messaging application server, and obtain updated messages from the team instant messaging application server, thereby implementing a calendar sharing process.

Based on the same technical concept, an information sharing system 2500 is provided in the embodiment of the present application, as shown in fig. 25, and includes a first client 2501 and a first application server 2502 of a first application, where the first client 2501 is a client for a creating user to create a new shared calendar to log in through a first application account of the creating user, and the first application server 2502 is a team instant messaging application server;

the first client 2501 of the first application is to: responding to the operation of newly creating the shared calendar, displaying a shared calendar creation interface, wherein a first application is a team instant messaging application, and a first client 2501 corresponds to a creation user of the newly created shared calendar; displaying the shared calendar editing content in the shared calendar creation interface in response to the shared calendar content editing operation triggered in the shared calendar creation interface; responding to a sharing user selection operation triggered in the shared calendar creation interface, and displaying a target group user in the shared calendar creation interface; in response to the saving operation triggered by the shared calendar creation interface, sending the edited content data of the shared calendar and the user data of the target group user as newly-created shared calendar information data to the first application server 2502;

the first application server 2502 is specifically configured to: and issuing a notice of newly-built shared calendar to the target group users.

Optionally, the first client 2501 is further configured to:

Optionally, the sharing system further includes a second client 2503 of the first application, where the second client 2503 is a client on which a target group user creating a shared calendar logs in through a first application account of the target group user;

the second client 2503 is specifically configured to:

sending a request for obtaining calendar information to the first application server 2502 in response to a viewing operation triggered by the notification of the newly created shared calendar;

the first application server 2502 is further configured to: determining calendar information data according to the request for obtaining calendar information, and sending the calendar information data to the second client 2503;

the second client 2503 is specifically configured to: receiving calendar information data sent by the first application server 2502, wherein the calendar information data comprises each calendar information data stored in the first application server 2502 and each first calendar identification information corresponding to each calendar information data;

determining identification information of a newly-built shared calendar corresponding to the notification of the newly-built shared calendar and newly-built shared calendar information data according to each second calendar identification information, each first calendar identification information and a target authority of a target group user stored in a local database of the second client 2503;

Optionally, the second client 2503 is further configured to:

sending a schedule information acquisition request for the newly-built shared calendar to the first application server 2502, where the schedule acquisition request includes a first operation sequence value of the newly-built shared calendar stored in a local database of the second client 2503;

the first application server 2502 is further configured to: determining schedule information data based on a first operation sequence value in the schedule information acquisition request and a second operation sequence value of the newly-built shared calendar, and sending the schedule information data to the second client 2503, wherein the operation sequence value is used for representing the editing times of the newly-built shared calendar information data, the second operation sequence value is stored in a local database of the first client 2501 or other second clients 2503, and the first operation sequence value is not greater than the second operation sequence value;

the second client 2503 is specifically configured to: receiving schedule information data sent by the first application server 2502, and updating a first operation sequence value in a local database of the second client 2503 into a second operation sequence value;

Optionally, the first client 2501 is further configured to:

in response to the saving operation triggered by the schedule creation interface, sending the schedule editing content data to the first application server 2502, and updating a second operation sequence value of the newly created shared calendar in the local database of the first client 2501;

the first application server 2502 is further configured to: and issuing the new schedule notice to the target group user.

Optionally, the first client 2501 is specifically configured to:

acquiring reference schedule data information of a target group user, which is sent by a first application server 2502, wherein the reference schedule data is generated after a schedule is newly built in other calendars by the target group user;

Optionally, the first client 2501 is specifically configured to:

the data processing unit is specifically configured to:

sending the user data of the schedule-participating user and the time editing content data as schedule editing content data to the first application server 2502;

the first application server 2502 is specifically configured to: and prompting the schedule participation user to participate in the new schedule corresponding to the new schedule notification before the schedule effective time.

Optionally, the first client 2501 is specifically configured to:

acquiring style information of a newly-built shared calendar;

the interface display unit is specifically configured to:

Optionally, the second client 2503 is further configured to:

in response to the saving operation triggered on the schedule editing interface, sending schedule update information, which takes schedule information editing content data as a target date, to the first application server 2502, and updating a first operation sequence value in a local database of the second client 2503;

the first application server 2502 is specifically configured to: and issuing schedule updating notification of the target date to other target group users and the creating user.

Optionally, the first client 2501 is further configured to:

sending notification indication information to the first application server 2502, where the notification indication information is used to indicate that the first application server 2502 sends a newly-created shared calendar notification to a second application corresponding to a target group user through a second application server 2504, where the second application is a personal instant messaging application, and the second application server 2504 is a personal instant messaging application server;

the first application server 2502 is further configured to: a new shared calendar notification is sent to the second application server 2504 to cause the new shared calendar notification to be displayed in the first application notification platform in the second application.

Optionally, the first client 2501 is specifically configured to:

the first application server 2502 is specifically configured to: and issuing a notice of the newly-built shared calendar to a user group of the newly-built shared calendar.

Optionally, the first client 2501 is further configured to:

the first application server 2502 is further configured to: and issuing a notice of unsubscribing the newly-built shared calendar to the target group users and the creation users.

In one aspect, an information sharing apparatus provided in an embodiment of the present application is applied to a first application server 2502, and includes:

a receiving unit, configured to receive newly created shared calendar information data sent by a first client 2501, where the newly created shared calendar information data is determined after the first client 2501 responds to an operation of creating a shared calendar, the first application is a team instant messaging application, a first application server 2502 is a team instant messaging application server, and the first client 2501 and a client, which is a creating user of the newly created shared calendar, log in through a first application account of the creating user;

Optionally, the receiving unit is specifically configured to:

receiving notification indication information sent by a first client 2501;

the sending unit is specifically configured to:

based on the notification indication information, sending a new shared calendar notification to the second application server 2504, so that the second application device sends the new shared calendar notification to a second application, and displays the new shared calendar notification in a first application notification platform in the second application, where the second application is a personal instant messaging application, and the second application server 2504 is a personal instant messaging application server.

Optionally, the receiving unit is further configured to:

receiving a request for obtaining calendar information sent by a second client 2503, wherein the request for obtaining calendar information is determined after the second client 2503 responds to a viewing operation triggered by a notification of a newly-built shared calendar, and the second client 2503 is a client on which a target group user of the newly-built shared calendar logs in through a first application account of the target group user;

the sending unit is further configured to:

each calendar information data stored in the first application server 2502 and each first calendar identification information corresponding to each calendar information data are sent to the second client 2503, so that the second client 2503 displays the newly created shared calendar in the calendar display interface.

Optionally, the receiving unit is further configured to:

receiving a schedule information acquisition request for the newly-built shared calendar, which is sent by the second client 2503, wherein the schedule information acquisition request includes a first operation sequence value of the newly-built shared calendar stored in a local database of the second client 2503;

determining schedule information data according to the first operation sequence value and a second operation sequence value of the newly-built shared calendar acquired from the local databases of other clients, wherein the operation sequence value is used for representing the editing times of the newly-built shared calendar, the second operation sequence value is stored in the local database of the first client 2501 or the local databases of the other clients 2503, and the first operation sequence value is not greater than the second operation sequence value;

the sending unit is further configured to:

the schedule information data is transmitted to the first application to cause the second client 2503 to display schedule information in the calendar display interface.

In fig. 25, a solid line indicates a connection relationship between the first application server 2502 and the first client 2501 and the second client 2503, and a dashed line indicates a connection relationship between the second application server 2504 and the second application client, in this embodiment, the first client 2501 and the second client 2503 may also serve as the second application client, which is not described herein again.

Based on the same technical concept, an embodiment of the present application provides an information sharing apparatus 2600 applied to a first application server, as shown in fig. 26, including:

a receiving unit 2601, configured to receive newly created shared calendar information data sent by a first client, where the newly created shared calendar information data is determined after the first client responds to an operation of newly creating a shared calendar, a first application is a team instant messaging application, the first application server is a team instant messaging application server, and the first client and a client that is a creating user of the newly created shared calendar log in through a first application account of the creating user;

the sending unit 2602 is configured to determine user data of a target group user in the new shared calendar information data information, and issue a new shared calendar notification message to the target group user based on the user data of the target group user.

Optionally, the receiving unit 2601 is specifically configured to:

receiving notification indication information sent by a first client;

the sending unit 2602 is specifically configured to:

Optionally, the receiving unit 2601 is further configured to:

the sending unit 2602 is further configured to:

Optionally, the receiving unit 2601 is further configured to:

the sending unit 2602 is further configured to:

Based on the same technical concept, the embodiment of the present application provides a computer device, as shown in fig. 27, including at least one processor 2701 and a memory 2702 connected to the at least one processor, where a specific connection medium between the processor 2701 and the memory 2702 is not limited in this embodiment, and the processor 2701 and the memory 2702 are connected through a bus in fig. 27 as an example. The bus may be divided into an address bus, a data bus, a control bus, etc.

In this embodiment, the memory 2702 stores instructions executable by the at least one processor 2701, and the at least one processor 2701 can execute the steps included in any of the aforementioned information sharing methods by executing the instructions stored in the memory 2702.

The processor 2701 is a control center of the computer device, and may connect various parts of the terminal device by using various interfaces and lines, and obtain the client address by executing or executing the instructions stored in the memory 2702 and calling the data stored in the memory 2702. Alternatively, the processor 2701 may comprise one or more processing units and the processor 2701 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It is to be appreciated that the modem processor described above may not be integrated into processor 2701. In some embodiments, the processor 2701 and the memory 2702 may be implemented on the same chip, or in some embodiments, they may be implemented separately on separate chips.

The processor 2701 may be a general-purpose processor, such as a Central Processing Unit (CPU), a digital signal processor, an Application Specific Integrated Circuit (ASIC), a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, that implements or executes the methods, steps, and logic blocks disclosed in the embodiments of the present Application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

Memory 2702 is provided as a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 2702 may include at least one type of storage medium, and may include, for example, a flash Memory, a hard disk, a multimedia card, a card-type Memory, a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Programmable Read Only Memory (PROM), a Read Only Memory (ROM), a charged Erasable Programmable Read Only Memory (EEPROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. The memory 2702 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 2702 in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.

Based on the same technical concept, embodiments of the present application provide a computer-readable storage medium storing a computer program executable by a computer device, which, when the program is run on the computer device, causes the computer device to perform the steps of any of the information sharing methods.

The computer-readable storage medium may be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. An information sharing method, the method comprising:

a first client of a first application responds to the operation of creating the shared calendar and displays a shared calendar creation interface, wherein the first application is a team instant messaging application, and the first client is a client for a creation user of the newly created shared calendar to log in through a first application account of the creation user;

the first client responds to a shared calendar content editing operation triggered in the shared calendar creation interface, and displays shared calendar editing content in the shared calendar creation interface;

the first client responds to a sharing user selection operation triggered in the shared calendar creation interface, and displays a target group user in the shared calendar creation interface;

and the first client responds to the storage operation triggered by the shared calendar creation interface, and sends the edited content data of the shared calendar and the user data of the target group user to a first application server as newly-built shared calendar information data so that the first application server issues a newly-built shared calendar notification to the target group user, wherein the first application server is a team instant messaging application server.

2. The method of claim 1, wherein the first client, in response to a sharing user selection operation triggered in the shared calendar creation interface, further comprises:

the first client responds to the permission setting operation of the target group user and displays selectable permissions on a permission setting interface;

the first client responds to the storage operation of the authority setting interface, and establishes a target corresponding relation between the target group user and the selected target authority;

and the first client takes the target corresponding relation as the user data of the target group user.

3. The method of claim 2, wherein after the first client sends the shared calendar editing content data and the user data of the target group of users to the first application server as new shared calendar information data, the method further comprises:

a second client of the first application responds to a viewing operation triggered by the notification of the newly-built shared calendar and sends a request for obtaining calendar information to the first application server, wherein the second client is a client for logging in a target group user of the newly-built shared calendar through a first application account of the target group user;

the second client receives calendar information data sent by the first application server, wherein the calendar information data comprises each calendar information data stored in the first application server and each first calendar identification information corresponding to each calendar information data;

the second client determines the identification information of the newly-built shared calendar and the newly-built shared calendar information data corresponding to the newly-built shared calendar notification according to each second calendar identification information, each first calendar identification information and the target authority of the target group user stored in a local database of the second client;

and the second client displays the newly-built shared calendar in a calendar display interface based on the newly-built shared calendar information data.

4. The method of claim 3, wherein after the second client displays the new shared calendar in the calendar display interface based on the new shared calendar information data, the method further comprises:

the second client sends a schedule information acquisition request aiming at the newly-built shared calendar to the first application server, wherein the schedule acquisition request comprises a first operation sequence value of the newly-built shared calendar stored in a local database of the second client;

the second client receives schedule information data determined by the first application server based on the first operation sequence value and a second operation sequence value of the newly-built shared calendar, wherein the operation sequence value is used for representing the editing times of the newly-built shared calendar information data, the second operation sequence value is stored in a local database of the first client or other second clients, and the first operation sequence value is not greater than the second operation sequence value;

the second client displays schedule information in the calendar display interface according to the schedule information data;

the second client updates the first operational sequence value in a local database of the second client to the second operational sequence value.

5. The method of claim 4, wherein after the first client sends the shared calendar editing content data and the user data of the target group of users to the first application server as new shared calendar information data, further comprising:

the first client responds to a new calendar schedule operation triggered aiming at the new shared calendar and displays a schedule creation interface;

the first client responds to the schedule content editing operation triggered in the schedule creating interface and displays the schedule editing content in the schedule creating interface;

and the first client responds to the storage operation triggered by the schedule creation interface, and sends the schedule editing content data to the first application server, so that the first application server issues a newly-built schedule notice to the target group user, and updates the second operation sequence value of the newly-built shared calendar in the local database of the first client.

6. The method of claim 5, wherein the first client displays schedule edit content in the schedule creation interface in response to a schedule content edit operation triggered in the schedule creation interface, comprising:

the first client acquires reference schedule data information of the target group user, which is sent by a first application server, wherein the reference schedule data is generated after the target group user newly establishes schedules in other calendars;

and the first client determines whether the schedule editing content data conflicts with the reference schedule data, and if so, a prompt interface is displayed to prompt the creation user to modify the schedule editing content data.

7. The method of claim 5, wherein the first client displays schedule edit content in the schedule creation interface in response to a schedule content edit operation triggered in the schedule creation interface, comprising:

the first client responds to schedule participation user selection operation triggered by the schedule creation interface, and displays schedule participation users in a schedule participation user selection interface, wherein the schedule participation users are users in the target group users;

the first client responds to the schedule effective time editing operation triggered by the schedule creating interface and displays the schedule effective time editing content on the time setting interface;

the first client sends the schedule editing content data to a first application server in response to the storage operation triggered by the schedule creation interface, and the method comprises the following steps:

and the first client sends the user data of the schedule participation user and the time editing content data serving as the schedule editing content data to the first application server so as to enable the first application server to prompt the schedule participation user to participate in a new schedule corresponding to the new schedule notification before the effective time of the schedule.

8. The method of claim 4, wherein the first client displays schedule information in a calendar display interface according to the schedule information data, comprising:

the first client acquires style information of the newly-built shared calendar;

and the first client displays the schedule information according to the style information of the newly-built shared calendar.

9. The method according to claim 4, wherein after the first client displays schedule information in a calendar display interface according to the schedule information data, the method further comprises:

the second client responds to schedule information modification operation triggered by a target date in the newly-built shared calendar interface, and determines whether the operation permission of the target group user corresponding to the modification operation meets the requirement of preset operation permission;

if the second client side determines that the preset operation permission requirement is met, displaying a schedule information editing interface;

the second client responds to the schedule information editing operation triggered in the schedule editing interface and displays the schedule information editing content in the schedule editing interface;

and the second client responds to the storage operation triggered by the schedule editing interface, and sends schedule information editing content data serving as schedule updating information of the target date to the first application server, so that the first application server issues schedule updating notification of the target date to other target group users and the creation user, and updates the first operation sequence value in a local database of the second client.

10. The method according to any one of claims 1-9, wherein the first client, after responding to the save operation triggered by the target user, further comprises:

the first client sends notification indication information to the first application server, wherein the notification indication information is used for indicating the first application server to send a newly-built shared calendar notification to a second application corresponding to the target group user through a second application server, so that the newly-built shared calendar notification is displayed in a first application notification platform in the second application, the second application is a personal instant messaging application, and the second application server is a personal instant messaging application server.

11. The method of claim 10, wherein the first client displays a target group of users in the shared calendar creation interface, comprising:

the first client acquires information of a group to be selected and a contact list to be selected, and displays the group to be selected and the contact list to be selected;

the first client responds to the selection operation of a target group user and displays the selected group to be selected and/or the selected contact;

and the first client takes the selected group to be selected and/or the selected contact person as a new shared calendar user group, and takes the new shared calendar user group data as the user data of the target group user, so that the first application server issues a new shared calendar notification to the new shared calendar user group.

12. The method of claim 11, wherein after the first client sends the shared calendar editing content data and the user data of the target group of users to the first application server as new shared calendar information, the method further comprises:

the first client side responds to the operation of unsubscribing the newly-built shared calendar triggered by the newly-built shared calendar, and sends a user data updating message aiming at a target group user of the newly-built shared calendar to the first server, wherein the user data updating message comprises user data of an unsubscribing user of the newly-built shared calendar, and the user data updating message is used for indicating the first server to issue a notice that the unsubscribing user unsubscribes the newly-built shared calendar to a user group of the newly-built shared calendar.

13. An information sharing method, the method comprising:

the method comprises the steps that a first application server receives newly-built shared calendar information data sent by a first client of a first application, wherein the newly-built shared calendar information data are determined after the first client responds to newly-built shared calendar operation, the first application is team instant messaging application, the first application server is a team instant messaging application server, and the first client and a creating user of the newly-built shared calendar log in through a first application account of the creating user;

and the first application server determines the user data of the target group user in the newly-built shared calendar information data information, and issues a newly-built shared calendar notification message to the target group user based on the user data of the target group user.

14. An information sharing system is characterized by comprising a first client of a first application and a first application server, wherein the first client is a client for a creating user to create a shared calendar to log in through a first application account of the creating user, and the first application server is a team instant messaging application server;

the first client of the first application is to: responding to the operation of newly building the shared calendar, displaying a shared calendar building interface, wherein the first application is a team instant messaging application, and the first client corresponds to a building user of the newly built shared calendar; displaying shared calendar editing content in the shared calendar creation interface in response to a shared calendar content editing operation triggered in the shared calendar creation interface; in response to a sharing user selection operation triggered in the shared calendar creation interface, displaying a target group of users in the shared calendar creation interface; in response to the storage operation triggered by the shared calendar creation interface, sending the edited content data of the shared calendar and the user data of the target group users as newly-built shared calendar information data to a first application server;

the first application server is specifically configured to: and issuing a notice of newly creating a shared calendar to the target group user.

15. An information sharing apparatus applied to a first application server, comprising:

the system comprises a receiving unit, a creating unit and a processing unit, wherein the receiving unit is used for receiving newly-built shared calendar information data sent by a first client, the newly-built shared calendar information data is determined after the first client responds to the operation of newly-built shared calendar, the first application is a team instant messaging application, the first application server is a team instant messaging application server, and the first client and a client which is a creating user of the newly-built shared calendar and logs in through a first application account of the creating user;

and the sending unit is used for determining the user data of the target group user in the newly-built shared calendar information data information and issuing a newly-built shared calendar notification message to the target group user based on the user data of the target group user.