本發明提供了一種資料同步系統、方法、伺服器、客戶端及電子設備，以減輕伺服器下行資料至客戶端的過程中，伺服器的壓力。 為達到上述目的，本發明的實施例採用如下技術方案： 第一方面，提供了一種基於C/S架構的資料同步系統，包括：伺服器和客戶端； 所述伺服器向所述客戶端下發業務變更資料，所述業務變更資料包括至少一個業務的業務資料和計算邏輯； 所述客戶端採用所述計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 第二方面，提供了一種基於C/S架構的資料同步方法，包括： 向客戶端下發業務變更資料，所述業務變更資料包括至少一個業務的業務資料和計算邏輯； 其中，所述計算邏輯用於，對當前登錄客戶端的使用者的屬性資料進行邏輯計算，以使所述客戶端根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，進行本地業務資料同步。 第三方面，提供了另一種基於C/S架構的資料同步方法，包括： 接收伺服器下發的業務變更資料，所述業務變更資料包括至少一個業務的業務資料和計算邏輯； 採用所述計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 第四方面，提供了一種伺服器，包括： 資料下發模組，用於向客戶端下發業務變更資料，所述業務變更資料包括至少一個業務的業務資料和計算邏輯； 其中，所述計算邏輯用於，對當前登錄客戶端的使用者的屬性資料進行邏輯計算，以使所述客戶端根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，進行本地業務資料同步。 第五方面，提供了一種客戶端，包括： 資料接收模組，用於接收伺服器下發的業務變更資料，所述業務變更資料包括至少一個業務的業務資料和計算邏輯； 資料同步模組，用於採用所述計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 第六方面，提供了一種電子設備，包括： 儲存器，用於儲存程式； 處理器，耦接至所述儲存器，用於執行所述程式，以用於： 向客戶端下發業務變更資料，所述業務變更資料包括至少一個業務的業務資料和計算邏輯； 其中，所述計算邏輯用於，對當前登錄客戶端的使用者的屬性資料進行邏輯計算，以使所述客戶端根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，進行本地業務資料同步。 第七方面，提供了另一種電子設備，包括： 儲存器，用於儲存程式； 處理器，耦接至所述儲存器，用於執行所述程式，以用於： 接收伺服器下發的業務變更資料，所述業務變更資料包括至少一個業務的業務資料和計算邏輯； 採用所述計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 本發明提供的資料同步系統、方法、伺服器、客戶端及電子設備，伺服器在向客戶端同步業務資料時，只需向客戶端下發一次業務變更資料即可，該業務變更資料包括至少一個業務的業務資料和計算邏輯；客戶端採用該計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從業務資料中提取與該客戶端相適用的資料部分，進行本地業務資料同步，從而降低伺服器的業務處理壓力。 上述說明僅是本發明技術方案的概述，為了能夠更清楚瞭解本發明的技術手段，而可依照說明書的內容予以實施，並且為了讓本發明的上述和其它目的、特徵和優點能夠更明顯易懂，以下特舉本發明的具體實施方式。The present invention provides a data synchronization system, method, server, client and electronic device, so as to reduce the pressure on the server in the process of downloading data from the server to the client. In order to achieve the above object, the embodiments of the present invention adopt the following technical solutions: In the first aspect, a data synchronization system based on a C/S architecture is provided, including: a server and a client; the server downloads the client to the client Sending business change data, the business change data includes the business data and calculation logic of at least one business; The client uses the calculation logic to perform logical calculation on the attribute data of the user currently logged in the client, according to the calculation result from the The data part applicable to the client is extracted from the business data, and the local business data is synchronized. In a second aspect, a data synchronization method based on a C/S architecture is provided, including: delivering service change data to a client, where the service change data includes business data and calculation logic of at least one service; wherein, the calculation logic It is used to perform logical calculation on the attribute data of the user currently logged in to the client, so that the client can extract the data part suitable for the client from the business data according to the calculation result, and synchronize the local business data. In a third aspect, another method for synchronizing data based on a C/S architecture is provided, including: receiving service change data issued by a server, where the service change data includes service data and calculation logic of at least one service; using the calculation The logic performs logical calculation on the attribute data of the user currently logged in to the client, extracts the data part suitable for the client from the business data according to the calculation result, and synchronizes the local business data. In a fourth aspect, a server is provided, comprising: a data delivery module for delivering service change data to a client, where the service change data includes service data and calculation logic of at least one service; wherein, the calculation The logic is used to perform logical calculation on the attribute data of the user currently logged in the client, so that the client can extract the data part suitable for the client from the business data according to the calculation result, and synchronize the local business data. In a fifth aspect, a client is provided, comprising: a data receiving module for receiving service change data issued by a server, the service change data including business data and calculation logic of at least one service; a data synchronization module, The calculation logic is used to perform logical calculation on the attribute data of the user currently logged in the client terminal, extract the data part suitable for the client terminal from the business data according to the calculation result, and synchronize the local business data. In a sixth aspect, an electronic device is provided, comprising: a storage for storing a program; a processor, coupled to the storage, for executing the program, for: delivering service change data to a client , the business change data includes business data and calculation logic of at least one business; Wherein, the calculation logic is used to perform logical calculation on the attribute data of the user currently logging in the client, so that the client can change from The data part applicable to the client is extracted from the business data, and the local business data is synchronized. In a seventh aspect, another electronic device is provided, comprising: a storage for storing a program; a processor, coupled to the storage, for executing the program, so as to: receive a service issued by a server Change data, the business change data includes business data and calculation logic of at least one business; Use the calculation logic to perform logical calculation on the attribute data of the user currently logged in the client, and extract the data from the business data according to the calculation result. Applicable data part of the client, and synchronize local business data. In the data synchronization system, method, server, client and electronic device provided by the present invention, when the server synchronizes the business data to the client, it only needs to send the business change data to the client once, and the business change data includes at least one The business data and calculation logic of a business; the client uses the calculation logic to logically calculate the attribute data of the user currently logged in to the client, and extracts the data part applicable to the client from the business data according to the calculation result, and performs local business Data synchronization, thereby reducing the server's business processing pressure. The above description is only an overview of the technical solutions of the present invention, in order to be able to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.
下面將參照圖式更詳細地描述本揭露的示例性實施例。雖然圖式中顯示了本揭露的示例性實施例，然而應當理解，可以以各種形式實現本揭露而不應被這裡闡述的實施例所限制。相反，提供這些實施例是為了能夠更透徹地理解本揭露，並且能夠將本揭露的範圍完整的傳達給所屬技術領域中具有通常知識者。 本發明改變了現有技術中，在C/S架構下的伺服器下行資料同步過程中，伺服器需先向客戶端下發資料變更通知，然後根據各客戶端的不同的資料請求，有針對性的組織和下發業務資料，其核心思想在於，伺服器通過將當次變更的全部業務資料以及計算邏輯一次性下發給所有客戶端，使客戶端通過將當前登錄的使用者的屬性資料經上述計算邏輯計算，然後根據計算結果從下發的業務資料中提取出適用於本客戶端的業務資料，然後進行業務資料同步，從而減輕了伺服器因針對不同客戶端進行組織和下發業務資料帶來的業務負擔，提高了下行業務資料同步的效率。 首先，結合圖1所示，對傳統的C/S架構進行簡單說明。 現有的C/S架構中，伺服器的接入層與客戶端的網路層之間形成資料傳輸通路，使得客戶端和伺服器之間可進行資料交互，這其中也包括伺服器向客戶端進行業務資料同步。對於C/S架構的交互程式，為了降低客戶端多次調用介面完成每次建立鏈接所消耗的時間，以及伺服器能實時的下發資料到達客戶端，客戶端都會選擇與伺服器建立一個長連接。 客戶端在需要資料的時候會發起一個資料請求從伺服器拉取需要的業務資料。這種請求一般是http請求。客戶端拉取到業務資料之後，這個http請求對應的底層鏈接就會斷開。有些客戶端為了避免頻繁發起資料請求導致頻繁建立底層鏈接帶來的消耗，會在客戶端和伺服器之間建立一個長連接。在長連接之上發起http請求。客戶端獲取到業務資料之後，在本地進行業務處理。當然客戶端也可先將獲取到的業務資料進行資料儲存以備後續使用。 如圖2所示，為基於傳統C/S架構的伺服器下行資料的資料同步處理流程。在傳統C/S架構下，伺服器實時下行業務資料到客戶端的過程包括如下步驟： 伺服器通過長連接下行一個業務資料變更的通知； 客戶端收到業務變更的通知後，對通知內容進行處理，從中解析出客戶端需要處理的業務； 客戶端發起獲取此業務對應的介面調用，以向伺服器請求相應的業務資料； 伺服器根據不同客戶端資料請求，組織和產生相應的業務資料； 伺服器將產生的業務資料下發給客戶端，以使客戶端使用業務數。 以上的基於傳統C/S架構下，伺服器實時下行業務資料到客戶端的過程存在如下技術缺陷： 成本高：當客戶端同時向伺服器發起資料請求時，會對伺服器造成瞬間壓力升高。據不完全統計：當同時在線使用者達700萬時，伺服器下行資料一般在一個心跳週期90秒內完成，即90秒內會有700萬的客戶端同步發起資料請求，每秒的資料請求量會達到700萬/90秒≈8萬/秒。這個資料請求量是非常巨大的，假如每台處理機可以處理2000/秒的資料請求，也需要40台機器，而且處理機增多，會導致伺服器的不穩定，影響其他的業務。 效率低：因為客戶端請求資料會給伺服器造成巨大的壓力，所以一般在實際實施時會有一些權衡方案。一般的權衡方案如下： a）伺服器在下行業務變更的通知的時候會降低頻率，這個頻率的設置會考慮到當前伺服器能承受的壓力來計算。比如：30分鐘內通知到全部在線使用者，此時伺服器的壓力為700萬/30*60秒≈3.9千/秒。 b）伺服器在短時間內下行業務變更通知給全部在線客戶端，但是客戶端在30分鐘內隨機請求伺服器，壓力和a）方案一樣。 c）伺服器在短時間內下行業務變更通知給全部的在線客戶端，客戶端請求伺服器，但是伺服器進行流量控制，同一時間只能服務部分客戶端。 以上這些權衡方案都在效率上面做了犧牲，對於某些對時間要求比較高的業務仍沒辦法滿足要求。 本發明要解決的問題是：對於C/S架構的應用如何以低成本、高效率的方式同步資料到客戶端，並且能做到不同類型的使用者使用不同的資料。 為了解決上述問題，本方案提供了一種改進後的C/S架構，如圖3所示，該C/S架構在傳統的C/S架構的基礎上，在各客戶端中增加了資料計算層。與現有伺服器下行業務資料至客戶端不同的是，在改進後的C/S架構中，伺服器不在下發業務變更的通知到客戶端，轉而下發業務資料以及計算邏輯，客戶端將當前登錄的使用者的屬性資料在本地經上述計算邏輯進行邏輯計算，從而根據計算結果從業務資料中提取自身需要的業務資料部分，而不需要再向伺服器請求具體的業務資料。 如圖4所示，為基於圖3所示的C/S架構的伺服器下行資料的資料同步處理流程。在圖3所示的C/S架構下，伺服器實時下行業務資料到客戶端的過程包括如下步驟： 伺服器通過其與客戶端之間建立的長連接直接下行已變更的所有業務資料和計算邏輯； 客戶端收到業務資料和計算邏輯後，將當前登錄的使用者的屬性資料經計算邏輯進行本地計算，並根據計算結果從業務資料中提取中適用於本客戶端的業務資料部分，並進行業務處理； 客戶端處理業務資料成功後，向伺服器回執處理成功的訊息； 伺服器接收到回執處理成功的訊息後，標記相應使用者的業務資料處理成功，以進行記錄。 改進後的伺服器下行業務資料的資料同步流程較現有技術在以下幾個方面有所提升： 成本：因為沒有客戶端向伺服器額外發送獲取業務資料的資料請求，伺服器不必針對每個客戶端組織和下發業務資料，所以沒有相應壓力的增長，提升了伺服器的穩定性，不會對伺服器的其他正常業務造成影響，不需要額外增加機器來支撐這些資料請求，降低了伺服器的成本。 效率：基本上一個資料變更可以在一個長連接心跳週期（一個心跳週期一般在90秒-4分鐘左右）可以同步到全部在線客戶端，客戶端本身處理基本上在幾十ms之內。 基於改進後的C/S架構的伺服器下行資料的資料同步處理流程，本發明實施例提供了一種基於C/S架構的資料同步系統，用以減輕伺服器下行業務資料至客戶端過程中的壓力，同時提高下行資料的同步效率。如圖5所示，該系統包括：伺服器510和客戶端520。其中，伺服器510用於向客戶端下發業務變更資料，該業務變更資料包括至少一個業務的業務資料和計算邏輯； 客戶端520用於採用計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 其中，伺服器510和客戶端520之間可通過預先建立的長連接，進行資料傳輸。 具體地，伺服器510包括： 資料下發模組，用於向客戶端520下發業務變更資料，該業務變更資料包括至少一個業務的業務資料和計算邏輯； 其中，所述計算邏輯用於，對當前登錄客戶端的使用者的屬性資料進行邏輯計算，以使客戶端根據計算結果從業務資料中提取與該客戶端相適用的資料部分，進行本地業務資料同步。 資料下發模組，通過客戶端520與伺服器510之間建立的長連接，向客戶端520下發業務變更資料。客戶端520接收到業務變更資料後，採用計算邏輯對當前登錄客戶端520的使用者的屬性資料進行邏輯計算，並根據計算結果從業務資料中提取與該客戶端520相適用的資料部分，進行本地業務資料同步。 進一步地，伺服器510還可包括： 接收處理模組，用於接收客戶端發送的業務資料同步成功訊息，並在伺服器將登錄該客戶端的使用者的本次業務資料標記為同步成功狀態。 如果客戶端520成功提取出業務資料中與其相適用的資料部分，並完成本地業務資料同步，會向伺服器510發送的業務資料同步成功訊息，伺服器510收到這樣的訊息後，會在本地將登錄該客戶端的使用者的本次業務資料標記為同步成功狀態，以對該使用者的業務資料進行記錄。 進一步地，伺服器510還可包括： 狀態查詢模組，用於針對本次待下發的業務資料，查詢登錄該客戶端的使用者的業務資料是否標記為同步成功狀態，如果否，則觸發資料下發模組執行向客戶端下發業務變更資料的操作。 如果針對本次待下發的業務資料，伺服器510本地已經儲存了登錄當前客戶端的使用者業務資料標記為同步成功狀態的記錄，則不再向該客戶端發送業務變更資料；否則，觸發資料下發模組執行向該客戶端下發業務變更資料的操作。 客戶端520包括： 資料接收模組，用於接收伺服器510下發的業務變更資料，該業務變更資料包括至少一個業務的業務資料和計算邏輯； 資料接收模組，通過客戶端520與伺服器510之間建立的長連接，接收客戶端520下發業務變更資料。 資料同步模組，用於採用計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 進一步地，客戶端520還包括： 訊息發送模組，用於在本次業務資料同步成功後，向伺服器510發送業務資料同步成功訊息，以使伺服器510將登錄該客戶端的使用者的本次業務資料標記為同步成功狀態。 本發明實施例提供的基於C/S架構的資料同步系統，由於省去了客戶端向伺服器額外發送獲取業務資料的資料請求，伺服器不必針對每個客戶端組織和下發業務資料，所以沒有相應壓力的增長，提升了伺服器的穩定性，並且利用客戶端在本地計算得到其所需要的業務資料，合理發揮了客戶端的效力，提高了伺服器下行資料的同步效率。 下面通過多個實施例來進一步說明本發明的技術方案。 實施例一 基於上述客戶端在本地通過邏輯計算獲取其所需的業務資料的方案思想，如圖6所示，其為本發明實施例示出的基於C/S架構的資料同步方法流程圖一，該方法的執行主為C/S架構下的伺服器。如圖6所示，該基於C/S架構的資料同步方法包括如下步驟： S610，向客戶端下發業務變更資料，該業務變更資料包括至少一個業務的業務資料和計算邏輯；其中，所述計算邏輯用於，對當前登錄客戶端的使用者的屬性資料進行邏輯計算，以使所述客戶端根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，進行本地業務資料同步。 其中，用於供客戶端從下發的所有業務資料中選取其所需的業務資料的計算邏輯可以是採用Lua編寫的腳本程式。Lua是一個小巧的腳本語言，它具有以下一些特性：輕量級、可擴展、高效率、跨平臺。Lua幾乎可以運行在所有系統上，例如目前主流的行動端IOS系統，以及Android也都很好的支援了Lua語言。計算邏輯的作用，就是將伺服器下發的業務資料與不同的客戶端的進行匹配，從而使客戶端能夠從下發的所有業務資料中提取出其自身所需的業務資料部分，而匹配的依據，就是登錄當前客戶端的使用者的屬性資料。 如此，伺服器不必再根據各客戶端請求資料的差異，有針對性的組織和下發業務資料，減輕了伺服器的工作壓力。 進一步地，如果客戶端成功從下發的業務資料中提取出與該客戶端相適用的資料部分，並完成了本地業務資料同步，則相應的，伺服器還會執行如下步驟，即接收客戶端發送的業務資料同步成功訊息，並在伺服器將登錄該客戶端的使用者的本次業務資料標記為同步成功狀態，以進行記錄。這樣，伺服器在下發業務資料時，就可以知道哪些客戶端已經下發了業務資料，哪些客戶端還沒有下發業務資料，並向還沒有下發本次業務資料的客戶端下發業務資料。 在此基礎上，在伺服器下發業務變更資料至客戶端時，可先執行如下步驟： 針對本次待下發的業務資料，查詢登錄該客戶端的使用者的業務資料是否標記為同步成功狀態，如果否，則執行所述向客戶端下發業務變更資料的操作，從而更加準確的下發業務資料。 進一步地，伺服器向客戶端下發業務變更資料可包括：伺服器基於與客戶端之間建立的長連接，向客戶端下發業務變更資料。 本實施例提供的基於C/S架構的資料同步方法，以伺服器為執行主體，通過一次性下發所有的業務資料和計算邏輯至客戶端，由客戶端在其本地對登錄使用者的屬性資料經計算邏輯進行計算，以從業務資料中提取其所需的業務資料，從而減輕了伺服器的業務壓力。 實施例二 如圖7所示，其為本發明實施例示出的基於C/S架構的資料同步方法流程圖二，該方法的執行主為C/S架構下的客戶端。如圖7所示，該基於C/S架構的資料同步方法包括如下步驟： S710，接收伺服器下發的業務變更資料，該業務變更資料包括至少一個業務的業務資料和計算邏輯； 其中，所述的計算邏輯可以是採用Lua編寫的腳本程式。計算邏輯的作用，是將伺服器下發的業務資料與不同的客戶端的進行匹配，從而使客戶端能夠從下發的所有業務資料中提取出其自身所需的業務資料部分。 S720，採用計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 其中，所述的使用者的屬性資料為當前使用者登錄客戶端之後，從伺服器獲取的，該屬性資料可包括使用者的：使用者名、使用者ID、客戶端版本等資訊。 具體地，客戶端採用計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，計算的結果即為當前業務資料是否適用於客戶端的標識或指示。 進一步地，客戶端在本次業務資料同步成功後，還可向伺服器發送業務資料同步成功訊息，以使伺服器將登錄該客戶端的使用者的本次業務資料標記為同步成功狀態。 進一步地，客戶端接收伺服器下發的業務變更資料可包括：客戶端基於與伺服器之間建立的長連接，接收伺服器下發的業務變更資料。 本實施例提供的基於C/S架構的資料同步方法，以客戶端為執行主體，在接收到伺服器下發的業務資料和計算邏輯後，通過在客戶端本地，對登錄使用者的屬性資料經計算邏輯進行計算，並從業務資料中提取其所需的業務資料，並採用該業務資料進行業務處理，從而減輕了伺服器的業務壓力，提高了伺服器下行資料至客戶端的資料同步效率。 實施例三 如圖8所示，為本發明實施例的伺服器的結構示意圖，該伺服器可用於執行如圖6所示的方法步驟，其包括： 資料下發模組810，用於向客戶端下發業務變更資料，所述業務變更資料包括至少一個業務的業務資料和計算邏輯； 其中，所述計算邏輯用於，對當前登錄客戶端的使用者的屬性資料進行邏輯計算，以使客戶端根據計算結果從業務資料中提取與該客戶端相適用的資料部分，進行本地業務資料同步。 進一步地，如圖8所示，上述伺服器還可包括： 接收處理模組820，用於接收客戶端發送的業務資料同步成功訊息，並在伺服器將登錄該客戶端的使用者的本次業務資料標記為同步成功狀態。 進一步地，如圖8所示，上述伺服器還可包括： 狀態查詢模組830，用於針對本次待下發的業務資料，查詢登錄該客戶端的使用者的業務資料是否標記為同步成功狀態，如果否，則觸發資料下發模組810執行向客戶端下發業務變更資料的操作。 本實施例提供的伺服器，通過一次性下發所有的業務資料和計算邏輯至客戶端，由客戶端在其本地對登錄使用者的屬性資料經計算邏輯進行計算，以從業務資料中提取其所需的業務資料，從而減輕了伺服器的業務壓力。 實施例四 如圖9所示，為本發明實施例的客戶端的結構示意圖，該客戶端可用於執行如圖7所示的方法步驟，其包括： 資料接收模組910，用於接收伺服器下發的業務變更資料，該業務變更資料包括至少一個業務的業務資料和計算邏輯； 資料同步模組920，用於採用計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 進一步地，在圖9所示的客戶端中，還可包括： 訊息發送模組930，用於在本次業務資料同步成功後，向伺服器發送業務資料同步成功訊息，以使伺服器將登錄該客戶端的使用者的本次業務資料標記為同步成功狀態。 本實施例提供的客戶端，在接收到伺服器下發的業務資料和計算邏輯後，通過在客戶端本地，對登錄使用者的屬性資料經計算邏輯進行計算，並從業務資料中提取其所需的業務資料，並採用該業務資料進行業務處理，從而減輕了伺服器的業務壓力，提高了伺服器下行資料至客戶端的資料同步效率。 實施例五 前面描述了伺服器的整體架構，該伺服器的功能可借助一種電子設備實現完成，如圖10所示，其為本發明實施例的電子設備的結構示意圖，具體包括：儲存器101和處理器102。 儲存器101，用於儲存程式。 除上述程式之外，儲存器101還可被配置為儲存其它各種資料以支援在電子設備上的操作。這些資料的示例包括用於在電子設備上操作的任何應用程式或方法的指令，連絡人資料，電話簿資料，訊息，圖片，影片等。 儲存器101可以由任何類型的易失性或非易失性儲存設備或者它們的組合實現，如靜態隨機存取儲存器（SRAM），電可抹除可程式化唯讀儲存器（EEPROM），可抹除可程式化唯讀儲存器（EPROM），可程式化唯讀儲存器（PROM），唯讀儲存器（ROM），磁儲存器，快閃儲存器，磁碟或光碟。 處理器102，耦接至儲存器101，用於執行儲存器101中的程式，以用於： 向客戶端下發業務變更資料，該業務變更資料包括至少一個業務的業務資料和計算邏輯； 其中，所述計算邏輯用於，對當前登錄客戶端的使用者的屬性資料進行邏輯計算，以使客戶端根據計算結果從所述業務資料中提取與該客戶端相適用的資料部分，進行本地業務資料同步。 上述的具體處理操作已經在前面實施例中進行了詳細說明，在此不再贅述。 進一步，如圖10所示，電子設備還可以包括：通信組件103、電源組件104、音頻組件105、顯示器106等其它組件。圖10中僅示意性給出部分組件，並不意味著電子設備只包括圖10所示組件。 通信組件103被配置為便於電子設備和其他設備之間有線或無線方式的通信。電子設備可以接入基於通信標準的無線網路，如WiFi，2G或3G，或它們的組合。在一個示例性實施例中，通信組件103經由廣播信道接收來自外部廣播管理系統的廣播信號或廣播相關資訊。在一個示例性實施例中，通信組件103還包括近場通信（NFC）模組，以促進短程通信。例如，在NFC模組可基於射頻識別（RFID）技術，紅外資料協會（IrDA）技術，超寬頻（UWB）技術，藍牙（BT）技術和其他技術來實現。 電源組件104，為電子設備的各種組件提供電力。電源組件104可以包括電源管理系統，一個或多個電源，及其他與為電子設備產生、管理和分配電力相關聯的組件。 音頻組件105被配置為輸出及/或輸入音頻信號。例如，音頻組件105包括一個麥克風（MIC），當電子設備處於操作模式，如呼叫模式、記錄模式和語音識別模式時，麥克風被配置為接收外部音頻信號。所接收的音頻信號可以被進一步儲存在儲存器101或經由通信組件103發送。在一些實施例中，音頻組件105還包括一個揚聲器，用於輸出音頻信號。 顯示器106包括螢幕，其螢幕可以包括液晶顯示器（LCD）和觸摸面板（TP）。如果螢幕包括觸摸面板，螢幕可以被實現為觸摸屏，以接收來自使用者的輸入信號。觸摸面板包括一個或多個觸摸傳感器以感測觸摸、滑動和觸摸面板上的手勢。觸摸傳感器可以不僅感測觸摸或滑動動作的邊界，而且還檢測與觸摸或滑動操作相關的持續時間和壓力。 實施例六 前面描述了客戶端的整體架構，該客戶端的功能可借助一種電子設備實現完成，如圖11所示，其為本發明實施例的電子設備的結構示意圖，具體包括：儲存器111和處理器112。 儲存器111，用於儲存程式。 除上述程式之外，儲存器111還可被配置為儲存其它各種資料以支援在電子設備上的操作。這些資料的示例包括用於在電子設備上操作的任何應用程式或方法的指令，連絡人資料，電話簿資料，訊息，圖片，影片等。 儲存器111可以由任何類型的易失性或非易失性儲存設備或者它們的組合實現，如靜態隨機存取儲存器（SRAM），電可抹除可程式化唯讀儲存器（EEPROM），可抹除可程式化唯讀儲存器（EPROM），可程式化唯讀儲存器（PROM），唯讀儲存器（ROM），磁儲存器，快閃儲存器，磁碟或光碟。 處理器112，耦接至儲存器111，用於執行儲存器111中的程式，以用於： 接收伺服器下發的業務變更資料，該業務變更資料包括至少一個業務的業務資料和計算邏輯； 採用計算邏輯對當前登錄客戶端的使用者的屬性資料進行邏輯計算，根據計算結果從業務資料中提取與該客戶端相適用的資料部分，並進行本地業務資料同步。 上述的具體處理操作已經在前面實施例中進行了詳細說明，在此不再贅述。 進一步，如圖11所示，電子設備還可以包括：通信組件113、電源組件114、音頻組件115、顯示器116等其它組件。圖11中僅示意性給出部分組件，並不意味著電子設備只包括圖11所示組件。 通信組件113被配置為便於電子設備和其他設備之間有線或無線方式的通信。電子設備可以接入基於通信標準的無線網路，如WiFi，2G或3G，或它們的組合。在一個示例性實施例中，通信組件113經由廣播信道接收來自外部廣播管理系統的廣播信號或廣播相關資訊。在一個示例性實施例中，通信組件113還包括近場通信（NFC）模組，以促進短程通信。例如，在NFC模組可基於射頻識別（RFID）技術，紅外資料協會（IrDA）技術，超寬頻（UWB）技術，藍牙（BT）技術和其他技術來實現。 電源組件114，為電子設備的各種組件提供電力。電源組件114可以包括電源管理系統，一個或多個電源，及其他與為電子設備產生、管理和分配電力相關聯的組件。 音頻組件115被配置為輸出及/或輸入音頻信號。例如，音頻組件115包括一個麥克風（MIC），當電子設備處於操作模式，如呼叫模式、記錄模式和語音識別模式時，麥克風被配置為接收外部音頻信號。所接收的音頻信號可以被進一步儲存在儲存器111或經由通信組件113發送。在一些實施例中，音頻組件115還包括一個揚聲器，用於輸出音頻信號。 顯示器116包括螢幕，其螢幕可以包括液晶顯示器（LCD）和觸摸面板（TP）。如果螢幕包括觸摸面板，螢幕可以被實現為觸摸屏，以接收來自使用者的輸入信號。觸摸面板包括一個或多個觸摸傳感器以感測觸摸、滑動和觸摸面板上的手勢。觸摸傳感器可以不僅感測觸摸或滑動動作的邊界，而且還檢測與觸摸或滑動操作相關的持續時間和壓力。 所屬技術領域中具有通常知識者可以理解：實現上述各方法實施例的全部或部分步驟可以通過程式指令相關的硬體來完成。前述的程式可以儲存於一電腦可讀取儲存媒介中。該程式在執行時，執行包括上述各方法實施例的步驟；而前述的儲存媒介包括：ROM、RAM、磁碟或者光碟等各種可以儲存程式代碼的媒介。 最後應說明的是：以上各實施例僅用以說明本發明的技術方案，而非對其限制；儘管參照前述各實施例對本發明進行了詳細的說明，所屬技術領域中具有通常知識者應當理解：其依然可以對前述各實施例所記載的技術方案進行修改，或者對其中部分或者全部技術特徵進行等同替換；而這些修改或者替換，並不使相應技術方案的本質脫離本發明各實施例技術方案的範圍。 Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those of ordinary skill in the art. The present invention changes the prior art, in the server downlink data synchronization process under the C/S architecture, the server needs to first issue a data change notification to the client, and then according to the different data requests of each client, targeted The core idea of organizing and distributing business data is that the server distributes all the business data and calculation logic of the current change to all clients at one time, so that the client can pass the attribute data of the currently logged in user through the above-mentioned Calculate logical calculation, and then extract business data suitable for this client from the issued business data according to the calculation result, and then synchronize the business data, thereby reducing the server's problems caused by organizing and distributing business data for different clients. This improves the efficiency of downlink service data synchronization. First, the traditional C/S architecture is briefly described with reference to FIG. 1 . In the existing C/S architecture, a data transmission channel is formed between the access layer of the server and the network layer of the client, so that the client and the server can exchange data, which also includes the server to the client. Business data synchronization. For interactive programs with C/S architecture, in order to reduce the time it takes for the client to call the interface multiple times to complete each link, and the server can deliver data to the client in real time, the client will choose to establish a long-term connection with the server. connect. When the client needs data, it will initiate a data request to pull the required business data from the server. Such requests are generally http requests. After the client pulls the business data, the underlying link corresponding to the http request will be disconnected. Some clients will establish a long connection between the client and the server in order to avoid the consumption caused by frequent establishment of underlying links due to frequent data requests. Initiate an http request over a persistent connection. After the client obtains the business data, it performs business processing locally. Of course, the client can also store the acquired business data for subsequent use. As shown in FIG. 2 , it is the data synchronization processing flow of the server downlink data based on the traditional C/S architecture. Under the traditional C/S architecture, the process of real-time downlink business data from the server to the client includes the following steps: The server downlinks a notification of business data change through a long connection; after the client receives the notification of business change, it processes the content of the notification , parse out the business that the client needs to process; the client initiates a call to obtain the interface corresponding to this business to request the corresponding business data from the server; the server organizes and generates the corresponding business data according to different client data requests; The server sends the generated business data to the client, so that the client can use the business data. Based on the above traditional C/S architecture, the process of real-time downlink business data from the server to the client has the following technical defects: High cost: When the client initiates a data request to the server at the same time, it will cause an instantaneous increase in pressure on the server. According to incomplete statistics: When the number of simultaneous online users reaches 7 million, the server downlink data is generally completed within 90 seconds of a heartbeat cycle, that is, 7 million clients will initiate data requests synchronously within 90 seconds, and the data requests per second The volume will reach 7 million/90 seconds ≈ 80,000/second. The amount of data requests is very huge. If each processor can process 2000 data requests per second, 40 machines are needed, and the increase in the number of processors will lead to instability of the server and affect other businesses. Low efficiency: Because the client's request for data will cause huge pressure on the server, there are generally some trade-offs in the actual implementation. The general trade-off plan is as follows: a) The server will reduce the frequency when it is notified of downlink service changes. The setting of this frequency will be calculated in consideration of the pressure that the current server can withstand. For example, all online users will be notified within 30 minutes. At this time, the pressure of the server is 7 million/30*60 seconds ≈ 3.9 thousand/second. b) The server will notify all online clients of downlink business changes within a short period of time, but the client will randomly request the server within 30 minutes, and the pressure is the same as that of the a) scheme. c) The server notifies all online clients of downlink service changes in a short period of time. The client requests the server, but the server performs traffic control and can only serve some clients at the same time. All of the above trade-offs have sacrificed efficiency, and still cannot meet the requirements for some businesses that require relatively high time. The problem to be solved by the present invention is: for the application of the C/S architecture, how to synchronize data to the client in a low-cost and high-efficiency manner, and enable different types of users to use different data. In order to solve the above problems, this solution provides an improved C/S architecture, as shown in Figure 3, the C/S architecture adds a data computing layer to each client on the basis of the traditional C/S architecture . The difference from the existing server downlinking business data to the client is that in the improved C/S architecture, the server does not send business change notifications to the client, but instead sends business data and calculation logic. The attribute data of the currently logged in user is logically calculated locally through the above calculation logic, so as to extract the part of the service data required by the user from the service data according to the calculation result, without requesting the server for specific service data. As shown in FIG. 4 , it is a data synchronization processing flow of the server downlink data based on the C/S architecture shown in FIG. 3 . Under the C/S architecture shown in Figure 3, the real-time downlink business data from the server to the client includes the following steps: The server directly downlinks all changed business data and computing logic through the long connection established between it and the client ; After the client receives the business data and the calculation logic, it calculates the attribute data of the currently logged-in user through the calculation logic, and extracts the part of the business data applicable to the client from the business data according to the calculation result, and executes the business Processing; After the client has successfully processed the business data, it will send a receipt to the server that the processing is successful; the server will mark the corresponding user's business data processing successfully for recording after receiving the message of the successful processing of the receipt. Compared with the prior art, the improved data synchronization process of downlink business data of the server is improved in the following aspects: Cost: Because there is no additional data request sent by the client to the server to obtain business data, the server does not have to target each client Organize and distribute business data, so there is no corresponding increase in pressure, which improves the stability of the server and does not affect other normal services of the server. There is no need to add additional machines to support these data requests, reducing the server's cost. Efficiency: Basically, a data change can be synchronized to all online clients in a long connection heartbeat cycle (a heartbeat cycle is generally about 90 seconds to 4 minutes), and the client itself is basically processed within tens of ms. Based on the data synchronization processing flow of the server downlink data based on the improved C/S architecture, the embodiment of the present invention provides a data synchronization system based on the C/S architecture, which is used to reduce the process of downlinking business data from the server to the client. pressure, while improving the synchronization efficiency of downlink data. As shown in FIG. 5 , the system includes: a server 510 and a client 520 . The server 510 is used for delivering service change data to the client, and the service change data includes service data and calculation logic of at least one service; Logical calculation, according to the calculation result, extract the data part suitable for the client from the business data, and synchronize the local business data. The data transmission can be performed between the server 510 and the client 520 through a pre-established long connection. Specifically, the server 510 includes: a data delivery module for delivering service change data to the client 520, where the service change data includes service data and calculation logic of at least one service; wherein the calculation logic is used to: Logic calculation is performed on the attribute data of the user who is currently logged in to the client, so that the client can extract the part of the data suitable for the client from the business data according to the calculation result, and synchronize the local business data. The data distribution module distributes service change data to the client 520 through the long connection established between the client 520 and the server 510 . After the client 520 receives the service change data, it uses calculation logic to perform logical calculation on the attribute data of the user who is currently logged in to the client 520, and extracts the part of the data that is applicable to the client 520 from the service data according to the calculation result. Local business data synchronization. Further, the server 510 may further include: a receiving processing module for receiving a business data synchronization success message sent by the client, and marking the current business data of the user logging in the client as a synchronization successful state at the server. If the client 520 successfully extracts the applicable data part of the business data and completes the local business data synchronization, it will send a business data synchronization success message to the server 510. After the server 510 receives such a message, it will locally Mark the current business data of the user logging in to the client as a successful synchronization state, so as to record the business data of the user. Further, the server 510 may further include: a status query module, which is used for querying whether the business data of the user logging in to the client is marked as a successful synchronization state for the business data to be distributed this time, and if not, triggering the data The delivery module executes the operation of delivering service change data to the client. If the server 510 has locally stored a record of the business data of the user logging in to the current client marked as a successful synchronization state for the business data to be delivered this time, it will no longer send the business change data to the client; otherwise, trigger the data The delivery module executes the operation of delivering service change data to the client. The client 520 includes: a data receiving module, which is used to receive service change data issued by the server 510, the service change data including the business data and calculation logic of at least one service; a data receiving module, which communicates with the server through the client 520. The long connection established between 510 receives the service change data issued by the client 520 . The data synchronization module is used to perform logical calculation on the attribute data of the user who is currently logged in to the client by using the calculation logic, extract the data part suitable for the client from the business data according to the calculation result, and synchronize the local business data. Further, the client terminal 520 further includes: a message sending module, configured to send a business data synchronization success message to the server 510 after the business data synchronization is successful this time, so that the server 510 will send the current data of the user logged into the client terminal. The secondary business profile is marked as sync successful. In the data synchronization system based on the C/S architecture provided by the embodiment of the present invention, since the client side is not required to send an additional data request to the server to obtain business data, the server does not need to organize and issue business data for each client. There is no corresponding pressure increase, which improves the stability of the server, and uses the client to calculate the business data it needs locally, which rationally exerts the effectiveness of the client and improves the synchronization efficiency of the server's downstream data. The technical solutions of the present invention are further described below through a plurality of embodiments. Embodiment 1 is based on the solution idea of the above-mentioned client locally obtaining the required business data through logical calculation, as shown in FIG. The execution of this method is mainly for the server under the C/S architecture. As shown in FIG. 6 , the data synchronization method based on the C/S architecture includes the following steps: S610: Deliver service change data to the client, where the service change data includes service data and calculation logic of at least one service; wherein, the The calculation logic is used to perform logical calculation on the attribute data of the user currently logged in the client, so that the client can extract the data part suitable for the client from the business data according to the calculation result, and synchronize the local business data . Wherein, the calculation logic for the client to select the required business data from all the issued business data may be a script program written in Lua. Lua is a small scripting language with some of the following features: lightweight, extensible, efficient, and cross-platform. Lua can run on almost all systems, such as the current mainstream mobile IOS systems, and Android also support the Lua language very well. The function of the calculation logic is to match the business data issued by the server with those of different clients, so that the client can extract the part of the business data it needs from all the business data issued, and the matching basis , which is the attribute data of the user logging in to the current client. In this way, the server no longer has to organize and distribute business data in a targeted manner according to the difference in data requested by each client, which reduces the work pressure of the server. Further, if the client successfully extracts the data part applicable to the client from the delivered business data, and completes the synchronization of the local business data, the server will also perform the following steps accordingly, that is, receiving the client The sent business data synchronization success message, and the server will mark the current business data of the user logging in the client as a synchronization success status for recording. In this way, when the server distributes the business data, it can know which clients have already issued the business data and which clients have not yet issued the business data, and distribute the business data to the clients that have not yet issued the current business data. . On this basis, when the server sends the business change data to the client, the following steps can be performed first: For the business data to be sent this time, query whether the business data of the user who logs in to the client is marked as a successful synchronization state , if not, execute the operation of delivering the service change data to the client, so as to deliver the service data more accurately. Further, the server delivering the service change data to the client may include: the server delivering the service change data to the client based on the long connection established with the client. The data synchronization method based on the C/S architecture provided by this embodiment takes the server as the execution body, and sends all the business data and calculation logic to the client at one time, and the client locally updates the attributes of the logged-in user. The data is calculated by the calculation logic to extract the required business data from the business data, thereby reducing the business pressure on the server. Embodiment 2 As shown in FIG. 7 , it is the second flowchart of the data synchronization method based on the C/S architecture shown in the embodiment of the present invention, and the execution of the method is mainly performed by the client under the C/S architecture. As shown in FIG. 7 , the data synchronization method based on the C/S architecture includes the following steps: S710: Receive service change data delivered by the server, where the service change data includes service data and calculation logic of at least one service; The calculation logic described above can be a script program written in Lua. The function of the calculation logic is to match the business data issued by the server with those of different clients, so that the client can extract the part of the business data it needs from all the business data issued. S720, using computing logic to perform logical calculation on the attribute data of the user currently logged in to the client, extracting the data part applicable to the client from the business data according to the calculation result, and synchronizing the local business data. The attribute data of the user is obtained from the server after the current user logs in to the client, and the attribute data may include information of the user: user name, user ID, client version and other information. Specifically, the client uses calculation logic to perform logical calculation on the attribute data of the user currently logged in to the client, and the result of the calculation is the identification or indication of whether the current business data is applicable to the client. Further, after the current business data synchronization is successful, the client can also send a business data synchronization success message to the server, so that the server marks the current business data of the user logging into the client as a synchronization successful state. Further, the client terminal receiving the service change data sent by the server may include: the client terminal receives the service change data sent by the server based on the long connection established with the server. The data synchronization method based on the C/S architecture provided by this embodiment takes the client as the execution body, and after receiving the business data and calculation logic issued by the server, the attribute data of the logged-in user is updated locally on the client. The calculation logic is used to calculate, and the required business data is extracted from the business data, and the business data is used for business processing, thereby reducing the business pressure of the server and improving the data synchronization efficiency of the server downlink data to the client. Embodiment 3 As shown in FIG. 8 , which is a schematic structural diagram of a server according to an embodiment of the present invention, the server can be used to execute the method steps shown in FIG. The terminal issues service change data, and the service change data includes business data and calculation logic of at least one service; wherein, the calculation logic is used to perform logical calculation on the attribute data of the user currently logged in to the client, so that the client According to the calculation result, the data part suitable for the client is extracted from the business data, and the local business data is synchronized. Further, as shown in FIG. 8 , the above-mentioned server may further include: a receiving and processing module 820 for receiving a business data synchronization success message sent by the client, and recording the current business of the user logged in the client on the server The data is marked as synced successfully. Further, as shown in FIG. 8 , the above-mentioned server may further include: a status query module 830, which is used to query whether the business data of the user logging in the client is marked as a successful synchronization state for the business data to be distributed this time. , if not, triggering the data delivery module 810 to perform the operation of delivering the service change data to the client. The server provided by this embodiment sends all the business data and calculation logic to the client at one time, and the client locally calculates the attribute data of the logged-in user through the calculation logic, so as to extract the data from the business data. The required business information, thereby reducing the business pressure on the server. Embodiment 4 As shown in FIG. 9 , which is a schematic structural diagram of a client terminal according to an embodiment of the present invention, the client terminal can be used to execute the method steps as shown in FIG. The business change data sent by the server, the business change data includes the business data and calculation logic of at least one business; the data synchronization module 920 is used to perform logical calculation on the attribute data of the user currently logged in the client by using the calculation logic, and according to the calculation result, from The data part applicable to the client is extracted from the business data, and the local business data is synchronized. Further, the client shown in FIG. 9 may further include: a message sending module 930, configured to send a business data synchronization success message to the server after the business data synchronization is successful this time, so that the server will log in The current business data of the user of the client is marked as a successful synchronization state. The client provided by this embodiment, after receiving the business data and calculation logic issued by the server, calculates the attribute data of the logged-in user through the calculation logic locally on the client, and extracts all the data from the business data. The required business data is used, and the business data is used for business processing, thereby reducing the business pressure of the server and improving the data synchronization efficiency of the server's downlink data to the client. Embodiment 5 The overall structure of the server is described above, and the function of the server can be realized by means of an electronic device. As shown in FIG. 10 , which is a schematic structural diagram of the electronic device according to the embodiment of the present invention, it specifically includes: a storage 101 and processor 102. The storage 101 is used to store programs. In addition to the above-mentioned programs, the memory 101 can also be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phone book data, messages, pictures, videos, etc. The memory 101 may be implemented by any type of volatile or non-volatile storage device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk. The processor 102, coupled to the storage 101, is used for executing the program in the storage 101, so as to: deliver service change data to the client, the service change data including the service data and calculation logic of at least one service; wherein , the calculation logic is used to perform logical calculation on the attribute data of the user currently logged in the client, so that the client can extract the data part suitable for the client from the business data according to the calculation result, and perform local business data. Synchronize. The above-mentioned specific processing operations have been described in detail in the previous embodiments, and are not repeated here. Further, as shown in FIG. 10 , the electronic device may further include: a communication component 103 , a power supply component 104 , an audio component 105 , a display 106 and other components. Only some components are schematically shown in FIG. 10 , which does not mean that the electronic device only includes the components shown in FIG. 10 . Communication component 103 is configured to facilitate wired or wireless communication between electronic devices and other devices. Electronic devices can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 103 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 103 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies. The power supply assembly 104 provides power to various components of the electronic device. Power components 104 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to electronic devices. Audio component 105 is configured to output and/or input audio signals. For example, the audio component 105 includes a microphone (MIC) that is configured to receive external audio signals when the electronic device is in operating modes, such as calling mode, recording mode, and voice recognition mode. The received audio signal may be further stored in the storage 101 or transmitted via the communication component 103 . In some embodiments, the audio component 105 also includes a speaker for outputting audio signals. Display 106 includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. A touch sensor can sense not only the boundaries of a touch or swipe action, but also the duration and pressure associated with the touch or swipe action. Embodiment 6 The overall architecture of the client has been described above, and the functions of the client can be implemented with the help of an electronic device, as shown in FIG. device 112. The storage 111 is used to store programs. In addition to the above programs, the memory 111 can also be configured to store various other data to support operations on the electronic device. Examples of such data include instructions for any application or method operating on the electronic device, contact data, phone book data, messages, pictures, videos, etc. The storage 111 may be implemented by any type of volatile or non-volatile storage device or combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Disk or Optical Disk. The processor 112, coupled to the storage 111, is configured to execute the program in the storage 111, so as to: receive service change data sent by the server, where the service change data includes service data and calculation logic of at least one service; Calculation logic is used to logically calculate the attribute data of the user currently logged in to the client, and according to the calculation result, the part of the data suitable for the client is extracted from the business data, and the local business data is synchronized. The above-mentioned specific processing operations have been described in detail in the previous embodiments, and are not repeated here. Further, as shown in FIG. 11 , the electronic device may further include: a communication component 113 , a power supply component 114 , an audio component 115 , a display 116 and other components. Only some components are schematically shown in FIG. 11 , which does not mean that the electronic device only includes the components shown in FIG. 11 . Communication component 113 is configured to facilitate wired or wireless communication between electronic devices and other devices. Electronic devices can access wireless networks based on communication standards, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 113 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication component 113 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies. The power supply assembly 114 provides power to various components of the electronic device. Power components 114 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to electronic devices. Audio component 115 is configured to output and/or input audio signals. For example, the audio component 115 includes a microphone (MIC) that is configured to receive external audio signals when the electronic device is in operating modes, such as calling mode, recording mode, and voice recognition mode. The received audio signal may be further stored in the storage 111 or transmitted via the communication component 113 . In some embodiments, the audio component 115 also includes a speaker for outputting audio signals. Display 116 includes a screen, which may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. A touch sensor can sense not only the boundaries of a touch or swipe action, but also the duration and pressure associated with the touch or swipe action. Those skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be implemented by program instructions related to hardware. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the steps including the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other mediums that can store program codes. Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, but not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those with ordinary knowledge in the technical field should understand that : It is still possible to modify the technical solutions recorded in the foregoing embodiments, or to perform equivalent replacements on some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the techniques of the embodiments of the present invention. scope of the programme.
