Schedule data synchronization method, system, device, equipment, storage medium and product

Abstract

The application relates to a schedule data synchronization method, system, device, equipment, storage medium and product. The method relates to the technical field of big data, and comprises the following steps: in the case that a user logs in a schedule application on a user terminal for the first time, establishing a long connection with the user terminal; obtaining user attribute information of the logged-in user and login attribute information of the user terminal; according to the user attribute information and the login attribute information, selecting target schedule data of the user terminal corresponding to the logged-in user from to-be-synchronized schedule data of different reference users; wherein the to-be-synchronized schedule data is obtained by an application server of the schedule application; and sending the target schedule data to the user terminal. The method can improve the schedule data synchronization efficiency.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of big data, and in particular, relates to a schedule data synchronization method, system, device, equipment, storage medium and product. BACKGROUND

[0002] With the development of big data technology, the amount of business data in various industries is gradually increasing. In order to improve the orderliness of business data processing and thus improve the efficiency of business processing, staff usually synchronizes business data in the form of schedule data to their own terminal in order to understand the business data to be processed on the day.

[0003] However, in general, the existing schedule data synchronization scheme will respond to the user's schedule data synchronization demand, pull all the schedule data in the entire period, have a relatively strict requirement on the network environment, and have the problem of low synchronization efficiency. SUMMARY

[0004] Therefore, it is necessary to provide a schedule data synchronization method, system, device, equipment, storage medium and product capable of improving the schedule data synchronization efficiency in view of the above technical problems.

[0005] In a first aspect, the present application provides a schedule data synchronization method applied to a transit server, comprising:

[0006] In the case that a user logs in to a schedule application for the first time using a user terminal, a long connection is established between the user and the user terminal;

[0007] User attribute information of the logged-in user and login attribute information of the user terminal are obtained;

[0008] According to the user attribute information and the login attribute information, target schedule data of the user terminal corresponding to the logged-in user is selected from the to-be-synchronized schedule data of different reference users; wherein the to-be-synchronized schedule data is obtained by a schedule application server;

[0009] The target schedule data is sent to the user terminal.

[0010] In one of the embodiments, according to the user attribute information and the login attribute information, the target schedule data of the user terminal corresponding to the logged-in user is selected from the to-be-synchronized schedule data of different reference users, comprising: according to the user attribute information, reference schedule data of the logged-in user is determined from the to-be-synchronized schedule data of different reference users; the reference schedule data is the to-be-synchronized schedule data corresponding to the logged-in user; and according to the login attribute information, the target schedule data of the user terminal corresponding to the logged-in user is selected from the reference schedule data.

[0011] In a second aspect, the present application further provides a schedule data synchronization method applied to a user terminal, comprising:

[0012] In the case that the login user logs in the schedule application through the user terminal, user attribute information of the login user and login attribute information of the user terminal are acquired;

[0013] According to the login attribute information, it is determined whether the login user is a user logging in for the first time through the user terminal;

[0014] If not, a long connection is established between the user terminal and the relay server, so that the relay server selects target schedule data of the user terminal corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information, wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0015] The target schedule data is acquired from the relay server.

[0016] In one of the embodiments, if the login user is a user logging in for the first time through the user terminal, a short connection is established between the user terminal and the application server, so that full-amount schedule data of the login user is acquired from the application server.

[0017] In one of the embodiments, the method further comprises: in response to a schedule updating operation of the login user, generating to-be-updated schedule data; establishing a short connection with the application server; and sending the to-be-updated schedule data to the application server, so that the application server synchronizes the to-be-updated schedule data to the relay server.

[0018] In a third aspect, the application further provides a schedule data synchronization system, comprising an application server of a schedule application, a relay server and a user terminal; wherein the application server, the relay server and the user terminal are in communication connection with each other; the application server is configured to store to-be-synchronized schedule data generated by different reference users in the process of using the schedule application, and synchronize the to-be-synchronized schedule data to the relay server;

[0019] In the case that the login user logs in the schedule application through the user terminal, user attribute information of the login user and login attribute information of the user terminal are acquired;

[0020] The user terminal determines whether the login user is a user logging in for the first time through the user terminal according to the user attribute information and the login attribute information.

[0021] If not, a long connection is established between the user terminal and the relay server;

[0022] The relay server selects target schedule data of the user terminal corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information, and sends the target schedule data to the user terminal.

[0023] In a fourth aspect, the application further provides a schedule data synchronization device configured in a relay server, comprising:

[0024] The first long connection module is configured to establish a long connection with the user terminal in the case that the login user is not a first-time user of the user terminal to log in to the schedule application.

[0025] The first information acquisition module is configured to acquire user attribute information of the login user and login attribute information of the user terminal.

[0026] The data selection module is configured to select target schedule data of the user terminal corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information, wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0027] The data sending module is configured to send the target schedule data to the user terminal.

[0028] In a fifth aspect, the present application further provides a schedule data synchronization device configured in a user terminal, comprising:

[0029] The second information acquisition module is configured to acquire user attribute information of the login user and login attribute information of the user terminal in the case that the login user logs in to the schedule application through the user terminal.

[0030] The first determination module is configured to determine whether the login user is a first-time user of the user terminal to log in according to the login attribute information.

[0031] The second long connection module is configured to establish a long connection with the relay server if the answer is no, so that the relay server selects target schedule data of the user terminal corresponding to the login user from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information, wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0032] The data acquisition module is configured to acquire the target schedule data from the relay server.

[0033] In a sixth aspect, the present application further provides a computer device comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the following steps when executing the computer program:

[0034] In the case that the login user is not a first-time user of the user terminal to log in to the schedule application, a long connection is established with the user terminal.

[0035] User attribute information of the login user and login attribute information of the user terminal are acquired.

[0036] Target schedule data of the user terminal corresponding to the login user is selected from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information, wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0037] sending the target schedule data to the user terminal.

[0038] In a seventh aspect, the present application provides a computer device, comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0039] In the case that the login user logs in the schedule application through the user terminal, obtaining user attribute information of the login user and login attribute information of the user terminal;

[0040] According to the login attribute information, determining whether the login user is a user who logs in for the first time through the user terminal;

[0041] If not, establishing a long connection with the transfer server, so that the transfer server selects target schedule data of the user terminal corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein the to-be-synchronized schedule data is obtained by an application server of the schedule application;

[0042] Obtaining the target schedule data from the transfer server.

[0043] In an eighth aspect, the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the following steps:

[0044] In the case that the login user logs in the schedule application through the user terminal, establishing a long connection with the user terminal;

[0045] Obtaining user attribute information of the login user and login attribute information of the user terminal;

[0046] According to the user attribute information and the login attribute information, selecting target schedule data of the user terminal corresponding to the login user from the to-be-synchronized schedule data of different reference users; wherein the to-be-synchronized schedule data is obtained by an application server of the schedule application;

[0047] Sending the target schedule data to the user terminal.

[0048] In a ninth aspect, the present application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the following steps:

[0049] In the case that the login user logs in the schedule application through the user terminal, obtaining user attribute information of the login user and login attribute information of the user terminal;

[0050] According to the login attribute information, determining whether the login user is a user who logs in for the first time through the user terminal;

[0051] If not, a long connection is established with the relay server, so that the relay server selects target schedule data of the user terminal corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0052] The target schedule data is obtained from the relay server.

[0053] In the tenth aspect, the application further provides a computer program product, comprising a computer program which, when executed by a processor, implements the following steps:

[0054] In the case that the login user is not the first time to use the user terminal to log in the schedule application, a long connection is established between the user terminal and the relay server;

[0055] The user attribute information of the login user and the login attribute information of the user terminal are obtained.

[0056] The target schedule data of the user terminal corresponding to the login user is selected from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0057] The target schedule data is sent to the user terminal.

[0058] In the eleventh aspect, the application further provides a computer program product, comprising a computer program which, when executed by a processor, implements the following steps:

[0059] In the case that the login user logs in the schedule application through the user terminal, the user attribute information of the login user and the login attribute information of the user terminal are obtained.

[0060] According to the login attribute information, it is determined whether the login user is the first time to use the user terminal to log in.

[0061] If not, a long connection is established with the relay server, so that the relay server selects target schedule data of the user terminal corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0062] The target schedule data is obtained from the relay server.

[0063] The above schedule data synchronization method, system, device, equipment, storage medium and product, in the case that the user logs in the schedule application for the first time, the long connection between the user terminal and the relay server is established, and the user attribute information of the logged-in user and the login attribute information of the user terminal are obtained. According to the user attribute information and the login attribute information, the target schedule data corresponding to the user terminal of the logged-in user is selected from the to-be-synchronized schedule data of different reference users cached in the relay server, and the target schedule data is sent to the user terminal. The embodiment of the application is not executed by the application server corresponding to the schedule application, but by the relay server in communication connection with the application server. Since the relay server does not bear the pressure of schedule application data processing, the use of the relay server for schedule data synchronization can improve the efficiency of schedule data synchronization to a certain extent. Since the target schedule data synchronized by the relay server to the user terminal is not the full amount of schedule data of the logged-in user, that is, the data amount of the target schedule data is small, the embodiment of the application can further improve the efficiency of schedule data synchronization. BRIEF DESCRIPTION OF DRAWINGS

[0064] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related art, the drawings needed to be used in the embodiments or the related art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0065] Figure 1 An application environment diagram of a schedule data synchronization method provided by the present embodiment;

[0066] Figure 2 A flowchart of a schedule data synchronization method provided by the present embodiment;

[0067] Figure 3 A flowchart of selecting target schedule data provided by the present embodiment;

[0068] Figure 4 Another flowchart of selecting target schedule data provided by the present embodiment;

[0069] Figure 5 A flowchart of synchronizing to-be-updated schedule data provided by the present embodiment;

[0070] Figure 6 Another flowchart of a schedule data synchronization method provided by the present embodiment;

[0071] Figure 7 Another application environment diagram of a schedule data synchronization method provided by the present embodiment;

[0072] Figure 8 A schematic diagram of an internal structure of a transit server is provided for the embodiment;

[0073] Figure 9 A structural block diagram of a schedule data synchronization device is provided for the embodiment;

[0074] Figure 10 A structural block diagram of another schedule data synchronization device is provided for the embodiment;

[0075] Figure 11 An internal structure diagram of a computer device is provided for the embodiment. DETAILED DESCRIPTION

[0076] In order to make the purposes, technical solutions and advantages of the present application clearer, the present application is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and not used to limit the present application.

[0077] Before introducing the schedule data synchronization method provided by the embodiments of the present application, it needs to be explained that the use of schedule data is very important in the office field. For example, schedule data can provide users with reasonable and clear work arrangements to improve work efficiency. However, the existing schedule data synchronization scheme is mainly based on the user end to actively pull data from the application server corresponding to the schedule application through an online interface, and the user end logs in the schedule application every time the user logs in the schedule application. The user end pulls all recent data to show and interact with the user. Therefore, the existing schedule data synchronization scheme has the following shortcomings: 1) low synchronization efficiency, long response time, and large pressure on the application server. The maximum pressure that the server can withstand is used to determine the data range of single synchronization, which cannot cover all the data of the user. 2) Since the application server only provides a public interface, the main synchronization mechanism is implemented by each user end. However, due to the diversity of user ends, such as iOS Input Output System (IOS end), Android end, and Personal Computer (PC), there may be great differences in the process of schedule data synchronization. For example, whether to use local cache, incremental or inventory synchronization, and other designs may not be unified, leading to fragmentation of the overall architecture, which is difficult to maintain. 3) If the fixed time range schedule data is updated in the user end, it will conflict with the local schedule data of the user end, and cannot accurately update the latest schedule data to the user end. 4) Not friendly to weak network scenarios. For example, if the user end uses the full update method, the network bandwidth occupation and delay will be large; if the incremental update method is used, the server interface development requirement is high, and data loss may occur in a weak network. The embodiments of the present application provide a schedule data synchronization method combining long connection, message queue and distributed cache technology to solve the above problems. A low-latency, high real-time, and high-data consistency schedule data synchronization scheme is proposed.

[0078] The schedule data synchronization method provided by the embodiments of the present application can be applied to, for example Figure 1The schedule data synchronization system shown includes an application server 106, a relay server 104, and a client 102. Each of the application server 106, relay server 104, and client 102 is connected in pairs. Both application server 106 and relay server 104 have corresponding data storage systems to store the data that their respective servers need to process. These data storage systems can be integrated onto the respective servers or hosted on the cloud or other network servers. Specifically, when a user logs into the schedule application through client 102, the system obtains the user's attribute information and the client's login attribute information. Based on the user attribute information and login attribute information, client 102 determines whether the user is logging in for the first time. If not, a long connection is established between client 102 and relay server 104. Based on the user attribute information and login attribute information, relay server 104 selects the target schedule data corresponding to client 102 from the schedule data to be synchronized for different reference users and sends the target schedule data to client 102. It should be noted that the application server stores the calendar data to be synchronized generated by different reference users during the use of the calendar application, and synchronizes the calendar data to be synchronized to the relay server. In other words, the calendar data to be synchronized in the relay server 104 is obtained by the application server 106 of the calendar application from the relay server 104. The user terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can include smartwatches, smart bracelets, head-mounted devices, etc. The relay server 104 and the application server can be implemented using independent servers or a server cluster consisting of multiple servers.

[0079] In one embodiment, such as Figure 2 As shown, a method for synchronizing schedule data is provided, which can be applied to... Figure 1 Taking relay server 104 as an example, the explanation includes the following steps:

[0080] S201: When a logged-in user is not logging into the calendar application for the first time, establish a long-lived connection with the client.

[0081] Here, the logged-in user refers to the user currently logged into the calendar application. The calendar application can be an application that allows logged-in users to process calendar data. For example, after logging into the calendar application, a logged-in user can perform operations such as adding, deleting, modifying, and viewing calendar data. During the long-term connection between the user's client and the relay server, multiple [data] can be sent continuously. .

[0082] It should be noted that the relay server is not responsible for determining whether the logged-in user is not the first time using the user terminal to log in to the schedule application, and the determination operation is performed by the user terminal, which is described in detail in the following embodiments.

[0083] Exemplarily, in this embodiment, the user terminal can send a long connection (bidirectional communication connection websocket) request to the relay server when it is determined that the logged-in user is not the first time using the user terminal to log in to the schedule application. Correspondingly, the relay server establishes a long connection with the user terminal in response to the long connection request sent by the user terminal. Generally, the relay server includes multiple containers, and in an optional embodiment, the relay server can randomly select a container in a normal operating state to establish a long connection between the user terminal.

[0084] It should be noted that the process of establishing a long connection between the relay server and the user terminal can be a common technical means for establishing a long connection, which will not be described here.

[0085] S202, obtaining user attribute information of the logged-in user and login attribute information of the user terminal.

[0086] The user attribute information can include basic information of the user and account information of the user, for example, it can include an identity document (Identity document, ID). The login attribute information can include login device information and login record information, and exemplarily, it can include a login device ID.

[0087] Exemplarily, in this embodiment, the relay server can obtain the user attribute information of the logged-in user and the login attribute information of the user terminal from the user terminal.

[0088] S203, according to the user attribute information and the login attribute information, selecting target schedule data of the user terminal corresponding to the logged-in user from the to-be-synchronized schedule data of different reference users.

[0089] The reference user can be all users who have used the schedule application, and the relay server caches the to-be-synchronized schedule data of different reference users, and all the to-be-synchronized schedule data is synchronized by the application server corresponding to the schedule application. The target schedule data can be the to-be-synchronized schedule data corresponding to the user terminal currently used by the logged-in user in the to-be-synchronized schedule data of the logged-in user.

[0090] It should be noted that all schedule data generated in the process of logging in to the schedule application by the reference user (i.e. to-be-updated schedule data) will be synchronized to the application server corresponding to the schedule application, and the application server will store each to-be-updated schedule data and synchronize each to-be-updated schedule data to the relay server as to-be-synchronized schedule data.

[0091] Exemplarily, in the embodiment, after obtaining the to-be-synchronized schedule data of different reference users, the transfer server records the user attribute information and login attribute information corresponding to each to-be-synchronized schedule data. That is, the user attribute information and login attribute information are in a corresponding relationship with the to-be-synchronized schedule data. Further, in the embodiment, the target schedule data of the user terminal corresponding to the login user can be determined according to the user attribute information, the login attribute information, and the corresponding relationship.

[0092] S204, sending the target schedule data to the user terminal.

[0093] Specifically, in the embodiment, the transfer server can send the target schedule data to the user terminal to show the latest schedule data to the user.

[0094] In the above schedule data synchronization method, in the case that the login user is not using the user terminal to log in to the schedule application for the first time, the transfer server establishes a long connection with the user terminal and obtains the user attribute information of the login user and the login attribute information of the user terminal. According to the user attribute information and the login attribute information, the target schedule data of the user terminal corresponding to the login user is selected from the to-be-synchronized schedule data of different reference users cached in the transfer server, and the target schedule data is sent to the user terminal. The embodiment of the application is not executed by the application server corresponding to the schedule application, but by the transfer server in communication connection with the application server. Since the transfer server does not bear the pressure of schedule application data processing, using the transfer server to synchronize schedule data can improve the efficiency of schedule data synchronization to a certain extent. Since the target schedule data synchronized by the transfer server to the user terminal is not the full amount of schedule data of the login user, that is, the data amount of the target schedule data is small, the embodiment of the application can further improve the efficiency of schedule data synchronization.

[0095] It should be noted that, in order to guarantee the high availability and performance expansion of the transfer server, the embodiment of the application can use multiple copies, such as Platform as a Service (PaaS) deployment. Moreover, since the Transmission Control Protocol (TCP) of the long connection needs to maintain a session with a single container, when the transfer server is preloaded by a load balancing, the load balancing needs to support session maintenance and tcp connection transparent transmission.

[0096] On the basis of the above embodiments, further, in order to make the process of selecting the target schedule data of the user terminal corresponding to the login user more clear, in one embodiment, the following method is provided, as shown in Figure 3 The method includes the following steps:

[0097] S301, determining reference schedule data of the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information.

[0098] The reference schedule data is the to-be-synchronized schedule data corresponding to the login user.

[0099] For ease of understanding, before the embodiment is introduced, it needs to be explained that the same login user can log in to the schedule application through multiple user terminals, but the synchronized schedule data on each user terminal can be different. Therefore, in order to distinguish which to-be-synchronized data is to be synchronized to the current user terminal corresponding to the login user, in the embodiment of the application, the transit server can buffer a corresponding number of to-be-synchronized schedule data according to the number of historical user terminals of the login user in the process of buffering the to-be-synchronized schedule data of the login user. In the embodiment, the to-be-synchronized schedule data corresponding to each user terminal of the login user is taken as the reference schedule data of the login user.

[0100] For example, the login user 1 has two user terminals, user terminal 1 and user terminal 2, so the login user has 2 to-be-synchronized data. Further, if the last login time of user terminal 1 is March 1, 2024, and the last login time of user terminal 2 is March 20, 2024. The synchronized schedule data of user terminal 1 (i.e., the local schedule data of user terminal 1) is updated to March 1, 2024, and the local schedule data of user terminal 2 is updated to March 20, 2024. Correspondingly, in the transit server, the to-be-synchronized schedule data corresponding to user terminal 1 includes the schedule data from March 1, 2023 to the present; the to-be-synchronized schedule data corresponding to user terminal 2 includes the schedule data from March 20, 2023 to the present. Correspondingly, the to-be-synchronized schedule data corresponding to user terminal 1 and the to-be-synchronized schedule data corresponding to user terminal 2 are the reference schedule data of login user 1.

[0101] Exemplarily, the reference schedule data corresponding to the same login user can be stored in the same database, each database corresponds to a database identifier, and the database identifier and the corresponding login user have a corresponding relationship. In the embodiment of the application, the database corresponding to the login user can be determined according to the user identifier of the login user and the corresponding relationship between the pre-determined user identifier and the database identifier, and all schedule data in the database is taken as the reference schedule data corresponding to the login user.

[0102] Exemplarily, the to-be-synchronized schedule data corresponding to different user terminals of the same login user can be respectively stored in different databases, and the to-be-synchronized schedule data corresponding to each user terminal corresponds to an identification information, and the identification information and the corresponding login user have a corresponding relationship. In the embodiment, each piece of to-be-synchronized schedule data corresponding to the user identification of the login user can be taken as the reference schedule data of the login user.

[0103] S302, selecting target schedule data of the user terminal corresponding to the login user from the reference schedule data according to the login attribute information.

[0104] The login attribute information includes device identification information of the user terminal.

[0105] Specifically, in the embodiment, each piece of to-be-synchronized schedule information corresponding to the login user corresponds to a device identification, and after determining the reference schedule data of the login user, the reference schedule data corresponding to the current user terminal in the reference schedule data is taken as the target schedule data of the user terminal corresponding to the login user.

[0106] In the above embodiment, the reference schedule data of the login user is first determined from the to-be-synchronized schedule data of different reference users according to the user attribute information, and then the target schedule data of the user terminal corresponding to the login user is selected from the reference schedule data of the login user according to the login attribute information. The process of determining the target schedule data is more clear, and the accuracy of determining the target schedule data is improved.

[0107] In one embodiment, as shown in Figure 4 , a schedule data synchronization method is provided, which is applied to the user terminal 102 in Figure 1 for example, and includes the following steps:

[0108] S401, in the case that the login user logs in the schedule application through the user terminal, obtaining user attribute information of the login user and login attribute information of the user terminal.

[0109] Specifically, in the embodiment of the present application, in the case that the login user logs in the schedule application through the user terminal, the user attribute information of the login user and the login attribute information of the user terminal are obtained. Exemplarily, the account information and the user basic information of the login user, and the device information of the user terminal are obtained.

[0110] S402, determining whether the login user is a user who logs in for the first time according to the login attribute information.

[0111] Exemplarily, in the embodiment of the present application, the user end records each time of history login information of the user end, and exemplarily, stores the attribute information of the history login user. For example, the attribute information of each history login user is stored in a preset database. After determining the login attribute information of the login user, it is judged whether the preset database includes the attribute information of the login user. If yes, it is determined that the login user is a user who has logged in the user end for the first time, and if no, it is determined that the login user is a user who has logged in the user end for the first time.

[0112] S403, if yes, a short connection is established with the application server to obtain full-amount schedule data of the login user from the application server.

[0113] The full-amount schedule data is all schedule data of the login user.

[0114] Specifically, in the case of determining that the login user is a user who has logged in the user end for the first time, in order to enable the user end to synchronize all schedule data of the login user, in the embodiment, a short connection between the user end and the application server is established, and full-amount schedule data of the login user is obtained from the application server.

[0115] S404, if no, a long connection is established with the relay server to enable the relay server to select target schedule data of the user end corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information.

[0116] The to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0117] Specifically, in the case of determining that the login user is a user who has logged in the user end for the first time, in the embodiment, a long connection is established with the relay server to enable the relay server to select target schedule data of the user end corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information. It should be noted that the process of establishing a long connection and selecting target schedule data of the user end corresponding to the login user has been described in detail in the above embodiment, and will not be described here.

[0118] S405, the target schedule data is obtained from the relay server.

[0119] In the above embodiments, when the user logs in the schedule application through the user terminal, the user attribute information of the logged-in user and the login attribute information of the user terminal are obtained, and it is determined according to the login attribute information whether the logged-in user is a user logging in for the first time through the user terminal. If not, a long connection is established with the relay server, so that the relay server selects target schedule data corresponding to the user terminal of the logged-in user from the cached different reference user's to-be-synchronized schedule data in the relay server according to the user attribute information and the login attribute information, and sends the target schedule data to the user terminal. The embodiments of the present application are not executed by the application server corresponding to the schedule application, but by the relay server in communication connection with the application server. Since the relay server does not bear the pressure of processing schedule application data, using the relay server to synchronize schedule data can improve the efficiency of schedule data synchronization to a certain extent. Since the target schedule data synchronized by the relay server to the user terminal is not the full amount of schedule data of the logged-in user, that is, the data amount of the target schedule data is small, the embodiments of the present application can further improve the efficiency of schedule data synchronization.

[0120] Further, in order to further improve the accuracy of the schedule data, the schedule application provides a schedule information initialization function. If the logged-in user finds that there is a difference in the inventory data and needs to perform inventory reconciliation, the logged-in user can initialize and then pull the schedule data from the application server again.

[0121] On the basis of the above embodiments, further, the source of the to-be-synchronized schedule data is introduced, as shown in the following steps: Figure 5

[0122] S501, in response to a schedule update operation of the logged-in user, generating to-be-updated schedule data.

[0123] The schedule update operation can be an operation performed by the logged-in user on the user terminal for updating the schedule data. For example, the logged-in user can add, modify or delete schedule data on the user terminal. The to-be-updated schedule data in the application server is equivalent to the to-be-synchronized schedule data in the relay server.

[0124] Specifically, the user terminal can generate to-be-updated data in response to the schedule update operation of the logged-in user. For example, when the user logs in the schedule application through the user terminal, a schedule update prompt can be output to the logged-in user for the logged-in user to perform schedule update.

[0125] S502, establishing a short connection with the application server.

[0126] ​Specifically, in the embodiment, after the user logs in the schedule application through the user terminal, the user can establish a short connection with the server. The method for establishing a short connection can be a common technical means in the communication field, and will not be described here.

[0127] S503, send the to-be-updated schedule data to the application server, so that the application server synchronizes the to-be-updated schedule data to the relay server.

[0128] Specifically, in the embodiment, the user terminal can send the to-be-updated schedule data to the application server, so that after the application server receives the to-be-updated schedule data, the application server synchronizes the to-be-updated schedule data to the relay server. It should be noted that the relay server receives the to-be-updated schedule data as to-be-synchronized schedule data.

[0129] Exemplarily, the application server can synchronize the to-be-updated schedule data to the relay server in the following manner: a message queue is newly created for transmitting the to-be-updated schedule data, a message queue producer is deployed in the schedule center container, and a message queue consumer is deployed in the long connection server. The to-be-updated schedule data is sent to the application server, first stored in the database, and then pushed to the relay server in time sequence through the message queue. Broadcast consumption mode is used, that is, each consumer can consume a copy of the message. The relay server consumes the schedule incremental operation message in sequence from the message queue buffer cluster, obtains the corresponding device ID (i.e. session object) in the long connection state cache according to the user ID in the message (for example, a user has multiple devices online at the same time, which may have multiple sessions), and synchronizes the target schedule data to the corresponding device through the session.

[0130] It should be noted that if a user has multiple registered devices, but not all devices are online, the relay server pushes the message to the online devices, and then stores the association relationship between the remaining offline devices and the message in the offline cache. Subsequently, when other devices are online, the association relationship is loaded and updated. For example, if the corresponding session is not found in the current relay server node but exists in other nodes, the current sending is abandoned (it is indicated that the corresponding session relationship exists in other nodes, and other nodes are responsible for sending). If there is no session globally (it is indicated that all devices of the user may have exited the schedule application) or there is a session in the node but the message sending fails through the session, the message body is stored in the offline information cache database of the relay server.

[0131] In order to facilitate those skilled in the art to understand the present scheme, in an embodiment, the embodiments of the present application are introduced in detail, as shown in Figure 6 The method comprises the following steps:

[0132] S601, the user terminal generates to-be-updated schedule data in response to a schedule update operation of the logged-in user.

[0133] S602, the user terminal establishes a short connection with the application server.

[0134] S603, the user terminal sends the to-be-updated schedule data to the application server.

[0135] S604, the application server synchronizes the to-be-updated schedule data to the relay server.

[0136] S605, the user terminal acquires user attribute information of the logged-in user and login attribute information of the user terminal upon detecting that the logged-in user logs in the schedule application via the user terminal.

[0137] S606, the user terminal determines, according to the login attribute information, whether the logged-in user is a user logging in for the first time via the user terminal. If yes, S610 is performed; if no, S607 is performed.

[0138] S607, the user terminal establishes a long connection with the relay server.

[0139] Specifically, the relay server includes a plurality of containers, and the long connection is established with one of the containers in the relay server. After the long connection is established with the relay server, long connection state information can be stored in a distributed shared cache database of the relay server. The long connection state information includes container ID, user ID, user equipment ID, and long connection session object (e.g., device 1-container 1 exists a long connection relationship).

[0140] It should be noted that, if the container in long connection with the logged-in user fails and restarts, the container registration information and the long connection state information of the node in the distributed cache are unregistered in the stop hook. The user terminal corresponding to the current logged-in user needs to automatically reconnect to other containers when the container connection is detected to be offline. Moreover, the cache needs to be planned for a certain life cycle, such as: long connection state cache: 24 hours; container registration information: 90 days; long connection offline information cache: 180 days; user equipment information: 30 days.

[0141] S608, the relay server selects target schedule data of the user terminal corresponding to the logged-in user from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information.

[0142] The to-be-synchronized schedule data is synchronized by the application server of the schedule application; specifically, the to-be-synchronized schedule data is obtained by the following steps: the user terminal generates to-be-updated schedule data in response to a schedule update operation of the logged-in user; a short connection is established with the application server; the to-be-updated schedule data is sent to the application server, so that the application server synchronizes the to-be-updated schedule data to the relay server.

[0143] S609, the transit server synchronizes the target schedule data to the user terminal.

[0144] It should be noted that, in order to reduce the operating pressure of the transit server, in the embodiment, when the connection between the user terminal and the transit server is closed, the transit server can automatically delete the long connection state information and the to-be-synchronized schedule data of the user terminal corresponding to the login user. That is, after synchronizing the to-be-synchronized schedule data to the corresponding user terminal, the transit server will delete the synchronized to-be-synchronized schedule data corresponding to the user.

[0145] S610, the user terminal establishes a short connection with the application server to obtain full-amount schedule data of the login user from the application server.

[0146] The steps of S601-S610 are applied in the application environment as shown in Figure 7 The schedule data synchronization method provided by the embodiment of the present application is described in detail, including:

[0147] After the login user logs in the schedule application through the user terminal (mobile terminal or PC terminal), the schedule data can be added, modified or deleted, that is, the login user inputs the to-be-updated schedule data through the user terminal, and the application server of the schedule application receives the to-be-updated schedule data, and then synchronizes the to-be-updated schedule data to the transit server through the message queue.

[0148] When the login user logs in the schedule application through the user terminal, the user terminal determines whether the login user is a user who does not use the user terminal to log in the schedule application for the first time according to the user attribute information and the login attribute information of the user terminal. If not, the user terminal establishes a short connection with the application server of the schedule application and obtains full-amount schedule data from the application server. If yes, a long connection is established with the transit server, the transit server determines the corresponding to-be-synchronized schedule data according to the user attribute information and the login attribute information, and synchronizes the to-be-synchronized schedule data to the user terminal.

[0149] The transit server is shown in Figure 8 The transit server includes a plurality of containers, and the process of establishing a long connection between each user terminal and the transit server is to establish a long connection with any container in a normal state.

[0150] For any container, the container receives the to-be-synchronized schedule data, judges whether the current container establishes a long connection with the corresponding user terminal, if not, caches the to-be-synchronized schedule data to the offline information cache, and synchronizes the offline cache data to the user terminal after the user terminal is logged in. After establishing a long connection with the user terminal, the long connection state information is stored in the distributed shared cache database of the transfer server. The long connection state information includes: container ID, user ID, user equipment ID, long connection session object (such as device 1-container 1 exists a long connection relationship). And after synchronizing the target schedule data, it is deleted.

[0151] It should be noted that if the container is down, the schedule data of the container in the cache is automatically deleted, and the user terminal will not establish a long connection relationship with the failed container.

[0152] It should be understood that although each step in the flowchart involved in each embodiment described above is displayed in sequence according to the arrow, these steps are not necessarily executed in the order indicated by the arrow. Unless otherwise stated herein, the execution of these steps has no strict order limitation, and these steps can be executed in other order. Moreover, at least part of the steps in the flowchart involved in each embodiment described above can include multiple steps or stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily sequential, but can be alternately executed with other steps or steps or stages in other steps.

[0153] Based on the same inventive concept, the embodiments of the present application also provide a schedule data synchronization device for implementing the above-mentioned schedule data synchronization method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so the specific limitations in one or more schedule data synchronization device embodiments provided below can refer to the limitations of the schedule data synchronization method in the above text, which will not be repeated here.

[0154] In one embodiment, as shown in Figure 9 A schedule data synchronization device is provided, comprising: a first long connection module 910, a first information acquisition module 920, a data selection module 930 and a data sending module 940, wherein:

[0155] The first long connection module 910 is configured to establish a long connection with the user terminal when the user logs in to the schedule application for the first time.

[0156] The first information acquisition module 920 is configured to acquire user attribute information of the logged-in user and login attribute information of the user terminal.

[0157] The data selection module 930 is configured to select target schedule data corresponding to the user terminal of the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information.

[0158] The to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0159] The data sending module 940 is configured to send the target schedule data to the user terminal.

[0160] In one embodiment, the data selection module 930 includes a reference schedule data determination unit configured to determine reference schedule data of the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information, the reference schedule data being to-be-synchronized schedule data corresponding to the login user; and a data selection unit configured to select target schedule data corresponding to the user terminal of the login user from the reference schedule data according to the login attribute information.

[0161] In one embodiment, as shown in Figure 10 a schedule data synchronization apparatus is provided, which includes a second information acquisition module 1010, a first determination module 1020, a second long connection module 1030, and a data acquisition module 1040. Specifically:

[0162] The second information acquisition module 1010 is configured to acquire user attribute information of a login user and login attribute information of a user terminal when the login user logs in a schedule application through the user terminal.

[0163] The first determination module 1020 is configured to determine whether the login user is a user who uses the user terminal to log in for the first time according to the login attribute information.

[0164] The second long connection module 1030 is configured to, if not, establish a long connection with a transfer server, so that the transfer server selects target schedule data corresponding to the user terminal of the login user from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information, wherein the to-be-synchronized schedule data is obtained by an application server of the schedule application.

[0165] The data acquisition module 1040 is configured to acquire the target schedule data from the transfer server.

[0166] In one embodiment, as shown in Figure 10 the schedule data synchronization apparatus further includes a short connection module configured to, if the login user is a user who uses the user terminal to log in for the first time, establish a short connection with the application server to acquire full schedule data of the login user from the application server.

[0167] In one embodiment, as shown in Figure 10The illustrated schedule data synchronization apparatus further includes an update data module, including a generation unit configured to generate to-be-updated schedule data in response to a schedule update operation of the logged-in user; a short connection unit configured to establish a short connection with the application server; and an update data unit configured to send the to-be-updated schedule data to the application server, so that the application server synchronizes the to-be-updated schedule data to the transit server.

[0168] The various modules in the above schedule data synchronization apparatus can be implemented in whole or in part by software, hardware, and combinations thereof. The above modules can be embedded in or independent of a processor in a computer device in hardware form, or stored in a memory in a computer device in software form, so as to be called and executed by a processor to perform the operations corresponding to the above modules.

[0169] In one exemplary embodiment, a computer device, which can be a terminal, is provided, and an internal structure diagram thereof can be as shown in the figure. Figure 11 The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, the memory, and the input / output interface are connected through a system bus, and the communication interface, the display unit, and the input device are connected to the system bus through the input / output interface. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operating system and the computer program in the non-volatile storage medium to run. The input / output interface of the computer device is configured to exchange information between the processor and external devices. The communication interface of the computer device is configured to perform wired or wireless communication with external terminals, and the wireless communication can be achieved through WIFI, mobile cellular network, NFC (Near Field Communication), or other technologies. The computer program is executed by the processor to implement a schedule data synchronization method. The display unit of the computer device is configured to form a visually visible picture, which can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer overlaid on the display screen, or a key, trackball, or touchpad arranged on the shell of the computer device, or an external keyboard, touchpad, or mouse, etc.

[0170] Those skilled in the art can understand that Figure 11 the structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. A specific computer device can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0171] In one example embodiment, a computer device is provided, comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0172] In a case where the login user is not a first-time user of the user terminal to log in to the schedule application, a long connection is established with the user terminal;

[0173] User attribute information of the login user and login attribute information of the user terminal are obtained;

[0174] According to the user attribute information and the login attribute information, target schedule data of the user terminal corresponding to the login user is selected from the to-be-synchronized schedule data of different reference users; the to-be-synchronized schedule data is obtained by a server of the schedule application;

[0175] The target schedule data is sent to the user terminal.

[0176] In one example embodiment, a computer device is provided, comprising a memory and a processor, the memory storing a computer program, and the processor implementing the following steps when executing the computer program:

[0177] In a case where the login user is not a first-time user of the user terminal to log in to the schedule application, a long connection is established with the user terminal;

[0178] According to the login attribute information, it is determined whether the login user is a first-time user of the user terminal to log in;

[0179] If not, a long connection is established with the relay server, so that the relay server selects target schedule data of the user terminal corresponding to the login user from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; the to-be-synchronized schedule data is obtained by a server of the schedule application;

[0180] The target schedule data is obtained from the relay server.

[0181] In one embodiment, a computer readable storage medium is provided, storing a computer program, and the computer program is executed by a processor to implement the following steps:

[0182] In a case where the login user is not a first-time user of the user terminal to log in to the schedule application, a long connection is established with the user terminal;

[0183] User attribute information of the login user and login attribute information of the user terminal are obtained;

[0184] According to the user attribute information and the login attribute information, target schedule data corresponding to the user terminal of the login user is selected from the to-be-synchronized schedule data of different reference users; wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0185] The target schedule data is sent to the user terminal.

[0186] In one embodiment, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program. The computer program is executed by a processor to implement the following steps:

[0187] In the case that the login user logs in the schedule application through the user terminal, user attribute information of the login user and login attribute information of the user terminal are obtained;

[0188] According to the login attribute information, it is determined whether the login user is a user who logs in for the first time through the user terminal;

[0189] If not, a long connection is established with the transfer server, so that the transfer server selects target schedule data corresponding to the user terminal of the login user from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application;

[0190] The target schedule data is obtained from the transfer server.

[0191] In one embodiment, a computer program product is provided, and the computer program product includes a computer program. The computer program is executed by a processor to implement the following steps:

[0192] In the case that the login user logs in the schedule application through the user terminal, user attribute information of the login user and login attribute information of the user terminal are obtained;

[0193] The user attribute information of the login user and the login attribute information of the user terminal are obtained;

[0194] According to the user attribute information and the login attribute information, target schedule data corresponding to the user terminal of the login user is selected from the to-be-synchronized schedule data of different reference users; wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0195] The target schedule data is sent to the user terminal.

[0196] In one embodiment, a computer program product is provided, and the computer program product includes a computer program. The computer program is executed by a processor to implement the following steps:

[0197] In the case that the login user logs in the schedule application through the user terminal, user attribute information of the login user and login attribute information of the user terminal are obtained;

[0198] According to the login attribute information, it is determined whether the login user is a user who uses the user terminal for the first time;

[0199] If not, a long connection is established with the transfer server, so that the transfer server selects target schedule data of the user terminal corresponding to the login user from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein the to-be-synchronized schedule data is obtained by the application server of the schedule application.

[0200] The target schedule data is obtained from the transfer server.

[0201] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant regulations.

[0202] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer readable storage medium, and when the computer program is executed, the processes of the above-mentioned embodiments of the methods can be included. Any reference to memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical storage, high-density embedded non-volatile memory, resistive memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration but not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc. The database involved in the embodiments provided in the present application can include at least one of a relational database and a non-relational database. The non-relational database can include a distributed database based on a block chain, etc., without being limited thereto. The processor involved in the embodiments provided in the present application can be a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., without being limited thereto.

[0203] Any combination of the technical features of the above embodiments can be made. In order to make the description simple, all possible combinations of the technical features in the above embodiments are not described, however, as long as the combination of the technical features does not exist, it should be considered as the scope of the present application.

[0204] The above embodiments only express several implementation manners of the present application, and the description is more specific and detailed, but it should not be understood as a limitation on the scope of the patent of the present application. It should be pointed out that for ordinary skilled in the art, without departing from the concept of the present application, a number of modifications and improvements can be made, which are all within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the appended claims.

Claims

1. A schedule data synchronization method characterized by comprising: The application is applied to a transfer server, and comprises the following steps: receiving to-be-updated schedule data sent by an application server; wherein, the to-be-updated schedule data is generated by a user terminal in response to a schedule updating operation of a login user, a short connection is established with the application server, and the to-be-updated schedule data is sent to the application server to obtain the to-be-updated schedule data; in a case where the login user uses the user terminal to log in to the schedule application for the first time, a long connection is established with the user terminal; obtaining user attribute information of the login user and login attribute information of the user terminal; according to the user attribute information and the login attribute information, target schedule data corresponding to the login user and the user terminal is selected from to-be-synchronized schedule data of different reference users; wherein, the to-be-synchronized schedule data is obtained by the application server of the schedule application; sending the target schedule data to the user terminal.

2. The method of claim 1, wherein, The step of selecting the target schedule data from the to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information comprises the following steps: according to the user attribute information, reference schedule data of the login user is determined from the to-be-synchronized schedule data of different reference users; the reference schedule data is to-be-synchronized schedule data corresponding to the login user; according to the login attribute information, target schedule data corresponding to the login user and the user terminal is selected from the reference schedule data.

3. A schedule data synchronization method characterized by comprising: The application is applied to a user terminal, and the method comprises the following steps: generating to-be-updated schedule data in response to a schedule updating operation of a login user; establishing a short connection with an application server; sending the to-be-updated schedule data to the application server, so that the application server synchronizes the to-be-updated schedule data to a transfer server; in a case where the login user logs in to the schedule application through the user terminal, obtaining user attribute information of the login user and login attribute information of the user terminal; determining whether the login user is a user who uses the user terminal to log in for the first time according to the login attribute information; if not, a long connection is established with the transfer server, so that the transfer server selects target schedule data corresponding to the login user and the user terminal from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein, the to-be-synchronized schedule data is obtained by the application server of the schedule application; obtaining the target schedule data from the transfer server.

4. The method of claim 3, wherein, if the login user is a user who uses the user terminal to log in for the first time, a short connection is established with the application server, so that full schedule data of the login user is obtained from the application server.

5. A schedule data synchronization system, characterized by comprising: The application comprises an application server, a transfer server and a user terminal of a schedule application; wherein, the application server, the transfer server and the user terminal are in communication connection with each other; the application server is used to store to-be-synchronized schedule data generated by different reference users in the process of using the schedule application, and synchronize the to-be-synchronized schedule data to the transfer server; In a case that a login user logs in a schedule application through the user terminal, user attribute information of the login user and login attribute information of the user terminal are acquired; The user terminal determines whether the login user is a user logging in for the first time according to the user attribute information and the login attribute information; If not, a long connection between the user terminal and the relay server is established; The relay server selects target schedule data corresponding to the login user and the user terminal from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information, and sends the target schedule data to the user terminal.

6. A schedule data synchronization apparatus characterized by comprising: The device is configured in a relay server, and the device comprises: A receiving module is configured to receive to-be-updated schedule data sent by an application server; wherein the to-be-updated schedule data is generated by a user terminal in response to a schedule updating operation of a login user, the to-be-updated schedule data is sent to the application server to obtain a short connection established with the application server; A first long connection module is configured to establish a long connection with the user terminal in a case that the login user is not logging in for the first time through the user terminal; A first information acquisition module is configured to acquire user attribute information of the login user and login attribute information of the user terminal; A data selection module is configured to select target schedule data corresponding to the login user and the user terminal from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein the to-be-synchronized schedule data is obtained by an application server of the schedule application; A data sending module is configured to send the target schedule data to the user terminal.

7. A schedule data synchronization apparatus characterized by comprising: The device is configured in a user terminal, and the device comprises: An updating data module comprises a generation unit configured to generate to-be-updated schedule data in response to a schedule updating operation of a login user, a short connection unit configured to establish a short connection with an application server, and an updating data unit configured to send the to-be-updated schedule data to the application server to synchronize the to-be-updated schedule data to a relay server by the application server; A second information acquisition module is configured to acquire user attribute information of the login user and login attribute information of the user terminal in a case that the login user logs in a schedule application through the user terminal; A first determination module is configured to determine whether the login user is a user logging in for the first time according to the login attribute information; A second long connection module is configured to establish a long connection with a relay server if not, so that the relay server selects target schedule data corresponding to the login user and the user terminal from to-be-synchronized schedule data of different reference users according to the user attribute information and the login attribute information; wherein the to-be-synchronized schedule data is obtained by an application server of the schedule application; A data acquisition module is configured to acquire the target schedule data from the relay server.

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that, The processor executes the computer program to implement the steps of the method in any one of claims 1-4.

9. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program, which when executed by a processor, implements the steps of the method of any one of claims 1-4.

10. A computer program product comprising a computer program, characterized in that, The computer program, which when executed by a processor, implements the steps of the method of any one of claims 1-4.

Images