Business data synchronization method and device, equipment and storage medium

Abstract

The invention relates to the technical field of data processing, and particularly provides a business data synchronization method and device, equipment and a storage medium, and the method comprises the steps: obtaining at least two pieces of business data associated with a right and interest processing request in response to the right and interest processing request; determining at least one feature tag of each piece of business data and a weight corresponding to the at least one feature tag; based on the at least one feature tag of each piece of service data and the weight corresponding to the at least one feature tag, calculating the priority order of each piece of service data through a weighting algorithm; and performing data synchronization on the at least two pieces of service data according to the priority sequence of each piece of service data. The synchronization sequence of the business data can be dynamically adjusted according to the feature tags of the business data and the weights of the feature tags, so that the data validity and the system response efficiency are improved.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a business data synchronization method, apparatus, device and storage medium. Background Art

[0002] Currently, in the Internet environment, users can obtain the right to use various products. During the validity period of the right, users can obtain the services provided by the corresponding products.

[0003] Typically, when a user activates the rights and interests of a product, the server needs to synchronize multiple business data related to the rights and interests to the recipient.

[0004] In the related art, in the synchronization solution of business data, the server can only synchronize each business data to the corresponding receiver in a pre-set order. Summary of the Invention

[0005] In order to solve the above technical problems, the present application provides a business data synchronization method, device, equipment and storage medium to achieve dynamic adjustment of data synchronization order, improve data validity and system response efficiency.

[0006] In a first aspect, the present application provides a business data synchronization method, which includes: in response to a rights processing request, obtaining at least two business data associated with the rights processing request; determining at least one feature tag of each business data and the weight corresponding to at least one feature tag; based on at least one feature tag of each business data and the weight corresponding to at least one feature tag, calculating the priority order of each business data through a weighted algorithm; and synchronizing at least two business data according to the priority order of each business data.

[0007] In the second aspect, the present application provides a business data synchronization device, which includes: a business data acquisition module, used to obtain at least two business data associated with the equity processing request in response to the equity processing request; a label and weight determination module, used to determine at least one feature label of each business data and the weight corresponding to at least one feature label; a priority determination module, used to calculate the priority order of each business data through a weighted algorithm based on at least one feature label of each business data and the weight corresponding to at least one feature label; a data synchronization module, used to synchronize at least two business data according to the priority order of each business data.

[0008] In a third aspect, the present application provides a business data synchronization device, which includes: one or more processors; a storage device for storing one or more programs; when one or more programs are executed by one or more processors, the one or more processors implement the business data synchronization method as described in the first aspect above.

[0009] In a fourth aspect, the present application provides a storage medium, which may be a computer-readable storage medium having a computer program stored thereon, and when the program is executed by a processor, the business data synchronization method as described in the first aspect above is implemented.

[0010] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes a computer program or instructions, and when the computer program or instructions are executed by a processor, implements any business data synchronization method as described in the first aspect above.

[0011] The technical solution provided by the embodiments of the present application has the following advantages compared with the prior art:

[0012] Embodiments of the present application provide a business data synchronization method, apparatus, device, and storage medium. The method includes: in response to a rights processing request, obtaining at least two business data associated with the rights processing request; determining at least one feature tag for each piece of business data and a weight corresponding to the at least one feature tag; calculating a priority order for each piece of business data using a weighted algorithm based on the at least one feature tag for each piece of business data and the weight corresponding to the at least one feature tag; and synchronizing the at least two pieces of business data according to the priority order of each piece of business data. Because the synchronization order of the business data can be dynamically adjusted based on the feature tags and weights of the feature tags of the business data, data validity and system response efficiency are improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0014] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0015] Figure 1 A flowchart of a method for synchronizing business data provided in an embodiment of the present application;

[0016] Figure 2 A flowchart of the optimized business data synchronization method provided in an embodiment of the present application;

[0017] Figure 3 A schematic diagram of adjusting the synchronization order of data provided in an embodiment of the present application;

[0018] Figure 4 A schematic diagram of the structure of a service data synchronization device provided in an embodiment of the present application;

[0019] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0020] In order to more clearly understand the above-mentioned objectives, features and advantages of the present application, the scheme of the present application will be further described below. It should be noted that, in the absence of conflict, the embodiments of the present application and the features therein can be combined with each other.

[0021] In the following description, many specific details are set forth to facilitate a full understanding of the present application, but the present application can also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present application, not all of the embodiments.

[0022] As used herein, the term "including" and its variations are open-ended, i.e., "including but not limited to." The term "based on" means "based, at least in part, on." The term "one embodiment" means "at least one embodiment," the term "another embodiment" means "at least one additional embodiment," and the term "some embodiments" means "at least some embodiments." Other terms are defined in the following description.

[0023] It should be noted that the concepts of "first" and "second" mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0024] It should be noted that the modifications of "one" and "multiple" mentioned in this application are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0025] The business data synchronization method provided by the present application is described in detail below with reference to the accompanying drawings and specific implementation methods.

[0026] Figure 1This is a flowchart of a business data synchronization method in an embodiment of the present application. This embodiment can be used to dynamically adjust the synchronization order of multiple business data. The method can be executed by a business data synchronization device. The business data synchronization device can be implemented in software and / or hardware. The business data synchronization device can be configured in the server.

[0027] like Figure 1 As shown, the business data synchronization method provided in the embodiment of the present application mainly includes steps S101-S104.

[0028] S101. In response to a rights processing request, obtain at least two pieces of business data associated with the rights processing request.

[0029] Benefits refer to the specific rights or benefits that users enjoy based on the agreement between them and the service provider. These benefits can be obtained through user registration, purchase of products or services, participation in activities, etc.

[0030] The aforementioned rights processing request refers to an instruction sent by the sender to the server to instruct the server to process rights-related business data. These rights processing requests include, but are not limited to, the following categories: rights activation requests, rights upgrade requests, etc.

[0031] Furthermore, the sender mentioned above refers to the client in a client-server architecture that forms a connection with the server. For example, the sender is software installed on a user's device, such as a video app on a mobile phone. The server refers to a remote server or server cluster that provides resources and services, receives business processing requests, processes them according to pre-defined business logic and rules, and then returns a response to the client.

[0032] Furthermore, the sender may also be a third-party platform other than a client-server architecture. Specifically, in response to the rights processing request, obtaining at least two pieces of business data associated with the rights processing request includes: in response to the rights processing request sent by the third-party platform, parsing the rights processing request to obtain the at least two pieces of business data carried in the rights processing request.

[0033] In a federated membership scenario, two or more service providers collaborate to offer a comprehensive membership. By signing up for a federated membership, users gain access to the services of all participating parties. The process of managing a federated membership typically involves coordination and integration among multiple stakeholders to ensure that users can seamlessly access all associated services.

[0034] Therefore, the sender mentioned above can also refer to a third-party platform that has established a cooperation agreement with the server. For example, a shopping platform and a video platform have established a joint membership through a cooperation agreement. When a user applies for benefits on the shopping platform, the shopping platform sends the benefits processing request to the video platform's server, so that the video platform's server can provide the user with the corresponding service.

[0035] In the embodiment of the present application, the business data synchronization order is decoupled from the third party and no longer relies on the third party to control the order. This can simplify and improve the efficiency of the partners and reduce the chance of errors by the partners in situations where there are many cooperating third parties.

[0036] The content of the rights and interests is usually set by the service provider. For example, for video service providers, the content of the rights and interests includes but is not limited to the following categories: ad-free viewing, HD / UHD picture quality, mobile viewing rights, TV viewing rights, iPad viewing rights, offline downloads, exclusive content access, early viewing rights, cloud disk space or favorites expansion, exclusive customer service support, points or reward programs, interactive functions, eligibility to participate in special events, etc.

[0037] Because benefits typically include multiple elements, each element has corresponding business data. For example, when a user activates a benefit, the benefits include: mobile service data for mobile services, TV service data for TV services, and points or reward programs for mobile or TV services.

[0038] Furthermore, the rights processing request usually includes the identifiers of various rights and interests content that the user applies to activate. In response to receiving the rights processing request, the rights processing request is parsed to obtain the identifiers of various rights and interests content carried in the rights processing request, and the business data corresponding to the identifiers of various rights and interests content are obtained from the server database as the business data that needs to be synchronized.

[0039] Furthermore, the recipients of service data can be one or more. For example, if a user only applies for mobile benefits, then multiple service data related to the mobile benefits will be synchronized to the mobile device. For example, if a user applies for mobile benefits, TV benefits, and PC benefits at the same time, then multiple service data related to the mobile benefits will be synchronized to the mobile device, multiple service data related to the TV benefits will be synchronized to the TV device, and multiple service data related to the PC benefits will be synchronized to the PC device.

[0040] S102: Determine at least one feature tag for each piece of business data and a weight corresponding to the at least one feature tag.

[0041] Furthermore, the feature tag is used to reflect additional feature information of the business data, such as whether the business data is important, whether the business data is urgent, whether the source of the business data is reliable, etc.

[0042] In one possible implementation, the feature tag includes at least one of the following tags: an importance tag, a time tag, and a source tag; the importance tag is used to reflect the importance level of the business data, the time tag is used to reflect the generation time or modification time of the business data, and the source tag is used to reflect the reliability level of the sender of the business data.

[0043] Among them, the importance label is used to reflect the importance level of business data, identifying which business data is most critical to the management and realization of member benefits. It is used to ensure that high-importance business data is given priority. For example: business data used for benefit activation is marked as "high importance" because the business data for benefit activation is directly related to whether the user can enjoy specific benefits. Business data related to viewing history is marked as "medium importance" because although this business data affects personalized recommendations, it is not immediately necessary. Business data related to promotional activity notifications is marked as "low importance" and even a slight delay will not seriously affect the user experience.

[0044] The time tag is used to reflect the urgency of business data, indicating the time when the business data was generated or last modified, so that the business data created first is synchronized first.

[0045] Source tags reflect the reliability of the sender of the provided business data, helping to assess the reliability of the source channel of the business data. They are used to distinguish the credibility of data from different sources and prioritize data from more reliable sources. When there are multiple business data sources, the source priority can be determined based on the recipient of the business data.

[0046] In one possible implementation, at least one characteristic tag corresponding to each business data is determined, including at least one of the following: determining the importance tag of each business data based on the business type of each business data and the relationship between the pre-set business type and the importance level; obtaining the generation time or modification time of each business data, and determining the time tag of each business data based on the difference between the generation time and the current time, or determining the time tag of each business data based on the difference between the modification time and the current time; determining the source tag of each business data based on the sender of the rights processing request.

[0047] The relationship between the pre-set business type and the importance level can be exemplified as including three levels: high, medium, and low. For example, the importance label corresponding to the business data used for rights activation is "high". The importance label corresponding to the business data related to viewing history records is "medium". The importance label corresponding to the business data related to promotional activity notifications is "low". It should be noted that in the embodiment of the present application, only three levels are used as an example for explanation, and a different number of importance levels can be designed according to actual conditions.

[0048] Then, based on the business type of the business data and the pre-defined relationship between business type and importance, the importance label of the business data is determined. For example, if the business type of the business data is benefit activation, the importance label of the business data is marked as "high". If the business type of the business data is viewing history, the importance label of the business data is marked as "medium". If the business type of the business data is promotion notification, the importance label of the business data is marked as "low".

[0049] Furthermore, the generation time or modification time of each business data is obtained, and the time tag of each business data is determined based on the difference between the generation time and the current time, or the time tag of each business data is determined based on the difference between the modification time and the current time.

[0050] Specifically, each piece of business data contains an accurate timestamp, indicating the specific time when the business data was generated or last modified. When prioritizing business data, obtain the current time and calculate the difference between the current time and the business data timestamp. Generate a time tag for each business data based on the calculated time difference. This tag can be directly displayed as a specific value, such as "3 days ago." It can also be converted into a more user-friendly description (such as "within the last week" or "more than a month"). Attach the generated time tags to the corresponding business data so that these time tags can be used for sorting operations in subsequent processing.

[0051] Determining the source tag of each piece of business data based on the sender of the rights processing request is a method for ensuring data source transparency and reliability. This allows us to identify the partner or channel from which each piece of business data originates, and manage and use this data based on pre-defined priority and reliability assessment rules.

[0052] Specifically, the sender of each rights processing request is identified, which could be a local mobile phone, a local TV, a third party, or other third parties. When there are multiple third parties, the third party's name can also be identified. Based on the sender's identity, a source tag is assigned to each piece of business data. During processing, the source tag is attached to the corresponding business data, allowing for quick identification of the data's source and attributes during subsequent processing.

[0053] In one possible implementation, a benefit processing request comes from a third-party platform named "XXX." The request includes two pieces of business data: benefit activation data and promotional data. The benefit activation data was last modified on January 14, 2025, and the promotional data was last modified on February 4, 2025.

[0054] Then, using the business type "Benefit Activation" as the keyword, we search the pre-defined relationship between business type and importance level, determining that its corresponding importance level is "High." Therefore, the importance label for the business data for "Benefit Activation" is "High." The last modification time for the business data for "Benefit Activation" is January 14, 2025, and the current time is March 21, 2025. Therefore, the difference between the two is 2 months and 7 days. The time label for the business data for "Benefit Activation" is "2 months ago." Since the source of the business data for "Benefit Activation" is third-party platform XXX, its corresponding source label is "Third-party platform XXX."

[0055] Then, using the business type "Promotional Activity" as the keyword, we query the pre-defined relationship between business type and importance level, determining that its corresponding importance level is "Low." Therefore, the importance label for the business data related to promotional activities is "Low." The business data related to promotional activities was last modified on February 4, 2025, and the current time is March 21, 2025. Therefore, the difference between the two is 1 month and 17 days. The time label for the business data related to promotional activities is "1 month ago." Since the source of the business data for promotional activities is third-party platform XXX, its source label is "Third-party platform XXX."

[0056] The weights corresponding to the various feature tags may be stored in the server or in a data path associated with the server. When calculating the priority of the service data, the pre-stored weights corresponding to the various feature tags are obtained from the storage location.

[0057] S103 : Calculate the priority order of each piece of business data using a weighted algorithm based on at least one feature tag of each piece of business data and a weight corresponding to the at least one feature tag.

[0058] The feature labels of each business data are quantified according to the set rules, and the quantified feature labels and weights are weighted to obtain the total weight. The total weight is sorted from large to small to obtain the priority order of each business data.

[0059] S104: Synchronize at least two pieces of business data according to the priority order of each piece of business data.

[0060] After determining the priority order of each business data, the business data is synchronized to the corresponding receiver in sequence according to the priority of each business data.

[0061] For example, if the priority order of each business data is: business data B, business data C, and business data A, then business data B will be synchronized first, followed by business data C, and finally business data B.

[0062] Embodiments of the present application provide a business data synchronization method, apparatus, device, and storage medium. The method includes: in response to a rights processing request, obtaining at least two business data associated with the rights processing request; determining at least one feature tag for each piece of business data and a weight corresponding to the at least one feature tag; calculating a priority order for each piece of business data using a weighted algorithm based on the at least one feature tag for each piece of business data and the weight corresponding to the at least one feature tag; and synchronizing the at least two pieces of business data according to the priority order of each piece of business data. Because the synchronization order of the business data can be dynamically adjusted based on the feature tags and weights of the feature tags of the business data, data validity and system response efficiency are improved.

[0063] Based on the above embodiments, the embodiments of the present application further optimize the business data synchronization method, such as Figure 2 As shown, the optimized business data synchronization method mainly includes S201-S208.

[0064] S201. In response to a rights processing request, obtain at least two pieces of business data associated with the rights processing request.

[0065] S202: Determine at least one characteristic tag for each piece of business data.

[0066] The processes of S201-S202 provided in the embodiment of the present application are the same as the processes of S101-S102 provided in the above embodiment. For details, please refer to the description in the above embodiment, and will not be repeated in the embodiment of the present application.

[0067] S203. Obtain the business scenario corresponding to the rights processing request and the pre-configured business scenario and weight relationship. The business scenario and weight relationship includes the weight corresponding to each feature tag in different business scenarios.

[0068] Business scenarios refer to the application scenarios for rights processing requests. Specifically, business scenarios are categorized into four main categories: time-priority scenarios, time-priority scenarios, source-priority scenarios, and other scenarios. For each business scenario, weights are assigned to the feature tags within that scenario. Table 1 shows a table of business scenarios and weights.

[0069] Business Scenario Weight Time priority scenario The weight of the time tag is 80%; the importance tag is 15%; and the source tag is 5%. Importance-priority scenarios The weight of the importance tag is 80%; the source tag is 10%; and the time tag is 10%. Source priority scenario The weight of the source tag is 80%; the importance tag is 15%; and the time tag is 5%. Other scenarios The weight of the time tag is 1 / 3; the importance tag is 1 / 3; the source tag is 1 / 3

[0070] As shown in Table 1, in the time-first scenario, the time tag has a higher weight than the importance and source tags. In the importance-first scenario, the importance tag has a higher weight than the time and source tags. In the source-first scenario, the source tag has a higher weight than the time and importance tags. In other scenarios, the weights of the source tag, time tag, and importance tag are evenly distributed.

[0071] Time-priority scenarios involve time-sensitive business data that requires rapid synchronization to ensure uninterrupted service. These scenarios require processing within a specific time window; failure to do so could result in user rights being compromised or opportunities being missed. For example, a benefit processing request might include discount information with specific start and end times; any delay could prevent the user from enjoying the discount.

[0072] Source-priority scenarios emphasize the reliability and priority of data sources, especially when third parties are requesting rights. For example, if the third party is a mobile app for a shopping platform and the rights request includes both mobile and TV rights for the video platform, then the user, if using a mobile phone, would prefer to prioritize mobile data synchronization to avoid data delays and a poor user experience.

[0073] Obtaining the business scenario corresponding to the rights processing request may include: determining the corresponding business scenario based on the data attributes, source channel, and other information of the rights processing request. For example: If the rights processing request comes from a third party, since it involves the interaction between the server and the third party, the business scenario corresponding to the rights processing request can be a source-priority scenario. If the rights processing request carries preferential information, the business scenario corresponding to the rights processing request is a time-priority scenario. If the rights processing request carries instructions for modifying key information, in order to avoid greater risks of tampering due to delayed data processing, the business scenario corresponding to the rights processing request is an importance-priority scenario.

[0074] Furthermore, if the business scenario corresponding to the rights processing request is not any of the time priority scenario, importance priority scenario, and source priority scenario, the business scenario corresponding to the rights processing request is directly set to other scenarios.

[0075] S204: Based on the business scenario corresponding to the rights processing request, query the relationship between the business scenario and the weight to obtain the weight corresponding to each feature tag.

[0076] Based on the business scenario corresponding to the rights processing request, a query is performed in the business scenario and weight relationship (as shown in Table 1), and the weight corresponding to each feature tag in the matched business scenario is used as the weight corresponding to the feature tag obtained by the query.

[0077] For example, when the business scenario corresponding to the rights processing request is a source-priority scenario, the weights of the feature tags are: source tag weight 80%; importance tag 15%; time tag 5%.

[0078] S205 : quantify at least two feature labels of each piece of business data respectively to obtain at least two quantized feature labels of each piece of business data.

[0079] Quantification of feature labels is the process of converting qualitative or categorical feature labels into numerical form so that they can be used in mathematical calculations. Specifically, each category is assigned a unique numerical identifier. Quantification makes it easier to understand and process non-numeric data.

[0080] Quantifying feature tags specifically refers to assigning a numerical value to each feature tag. For example, for importance tags, the importance tag is assigned a numerical value of 1, the medium importance tag is assigned a numerical value of 0.5, and the low importance tag is assigned a numerical value of 0. For importance tags, the local client is assigned a numerical value of 1, the third-party platform A is assigned a numerical value of 0.8, the third-party platform B is assigned a numerical value of 0.6, and the marketing system is assigned a numerical value of 0.4. If the time tag is 1 hour ago, the assigned numerical value is 1, the time tag is 30 minutes ago, the assigned numerical value is 0.5, and the time tag is within 30 minutes, the assigned numerical value is 0.

[0081] It should be noted that the above numerical values are only exemplary and the specific values can be set according to actual conditions.

[0082] When processing business data, quantifying the feature labels of each business data can ensure that different types of features can be calculated on the same scale.

[0083] S206 : Perform weighted calculation on at least two quantified feature labels of each piece of business data and the weights corresponding to each feature label to obtain the sum of the weights of each piece of business data.

[0084] For each piece of business data, the weight of each feature tag is determined in S204, and the feature tag is quantized in S205 to obtain a quantized feature tag. The quantized feature tag and the weight of each feature tag are weighted to obtain the total weight of the business data.

[0085] After this step, each business data has its corresponding weight sum.

[0086] S207 , sorting the sum of the weights of the various business data in descending order to obtain the priority order of the various business data.

[0087] Sort all business data in descending order by their total weight. Business data with larger total weights are ranked first, indicating higher priority. Based on the sorting results, the priority order of each business data is determined.

[0088] Specifically, the calculated total weight of business data 1 is 0.95, the calculated total weight of business data 2 is 0.8, the calculated total weight of business data 3 is 0.9, and the calculated total weight of business data 4 is 0.7. Sorting the business data in descending order by total weight yields the following priority order: business data 1 > business data 3 > business data 2 > business data 4.

[0089] S208: Synchronize at least two pieces of business data according to the priority order of each piece of business data.

[0090] S208 provided in the embodiment of the present application is the same as the execution process of S104 in the above embodiment. For details, please refer to the description in the above embodiment, which will not be repeated in the embodiment of the present application.

[0091] For example: The priority order of business data is: business data 1 > business data 3 > business data 2 > business data 4, then business data 1 is synchronized to its corresponding recipient first, then business data 3 is synchronized to its corresponding recipient, then business data 2 is synchronized to its corresponding recipient, and finally business data 4 is synchronized to its corresponding recipient.

[0092] In one possible implementation, such as Figure 3As shown, take the case where a third party 31 sends a rights processing request as an example. When the third party 31 sends a rights processing request to the server 32, the order of the business data indicated is business data A> business data B> business data C. In response, the order of the business data received by the server 32 is business data A> business data B> business data C. After the server 32 executes the business data synchronization method provided in the embodiment of the present application, the priority order of the business data obtained is: business data A> business data C> business data B. In response, the order of the business data received by the receiver 33 is: business data A> business data C> business data B.

[0093] Based on the above embodiment, the above business data synchronization method also includes: obtaining the response time of the recipient of each business data; if any response time exceeds the set time, using a machine learning algorithm to adjust the weight in the business scenario and weight relationship.

[0094] Obtain and determine the recipient of each business data, which can be a mobile phone, TV, etc. When synchronizing business data, record the difference between the start time of business data synchronization and the time when synchronization completion feedback is received from the recipient as the response time of the recipient.

[0095] Based on historical data and business needs, set reasonable response time thresholds for each business data. For example, for critical operations such as membership activation, you can set a lower threshold; for non-immediate tasks such as updating points accumulation records, you can set a higher threshold.

[0096] The system should have real-time monitoring capabilities, continuously tracking the response time of each business data point and comparing it against pre-set thresholds. If any response time exceeds the set duration, a weight adjustment mechanism will be triggered. For example, machine learning algorithms can be used to adjust the weights in the relationship between business scenarios and weights.

[0097] Specifically, select an appropriate machine learning algorithm, such as linear regression, decision tree, random forest, or reinforcement learning, to analyze the causes of response time anomalies and predict how to adjust weights to improve performance. Use historical data (including response time, business scenario characteristics, weight settings, etc.) to train the machine learning model so that it can identify the impact of different factors on response time. Based on the model's prediction results, automatically adjust the weights in the relationship between business scenarios and weights to optimize future response times. Specific adjustment strategies can be customized according to business needs, such as reducing the weight of certain low-priority tasks or increasing the weight of high-priority tasks.

[0098] By dynamically adjusting the weights, it can not only respond to emergencies in a timely manner, but also continuously optimize its own processing logic to provide a more stable and efficient data synchronization experience.

[0099] Figure 4 This is a structural diagram of a service data synchronization device in an embodiment of the present application. Figure 4 As shown, the business data synchronization device 40 provided in the embodiment of the present application mainly includes: a business data acquisition module 41, which is used to obtain at least two business data associated with the equity processing request in response to the equity processing request; a label and weight determination module 42, which is used to determine at least one feature label of each business data and the weight corresponding to at least one feature label; a priority determination module 43, which is used to calculate the priority order of each business data through a weighted algorithm based on at least one feature label of each business data and the weight corresponding to at least one feature label; a data synchronization module 44, which is used to synchronize at least two business data according to the priority order of each business data.

[0100] An embodiment of the present application provides a business data synchronization device, which is configured to execute the following process: in response to a rights processing request, obtaining at least two business data associated with the rights processing request; determining at least one feature tag for each piece of business data and a weight corresponding to the at least one feature tag; calculating a priority order for each piece of business data using a weighted algorithm based on the at least one feature tag for each piece of business data and the weight corresponding to the at least one feature tag; and synchronizing the at least two pieces of business data according to the priority order of each piece of business data. Because the synchronization order of the business data can be dynamically adjusted based on the feature tags and weights of the feature tags, data validity and system response efficiency are improved.

[0101] In one possible implementation, the feature tag includes at least one of the following tags: an importance tag, a time tag, and a source tag; the importance tag is used to reflect the importance of business data, the time tag is used to reflect the urgency of business data, and the source tag is used to reflect the reliability and priority of a third party.

[0102] In one possible implementation, the label and weight determination module 42 is used to execute at least one of the following processes: determining the importance label of each business data based on the business type of each business data and a pre-set relationship between the business type and importance; obtaining the timestamp of each business data, and determining the time label of each business data based on the difference between the timestamp and the current time; and determining the source label of each business data based on the sender of the rights processing request.

[0103] In one possible implementation, the priority determination module 43 is specifically used to quantify at least two feature labels of each business data respectively to obtain at least two quantized feature labels of each business data; perform weighted calculation on the at least two quantized feature labels of each business data and the weights corresponding to each feature label to obtain the sum of the weights of each business data; and sort the sum of the weights of each business data in descending order to obtain the priority order of each business data.

[0104] In one possible implementation, the label and weight determination module 42 is specifically used to obtain the business scenario corresponding to the rights processing request, as well as the pre-configured business scenario and weight relationship, where the business scenario and weight relationship includes the weights corresponding to each feature label in different business scenarios; based on the business scenario corresponding to the rights processing request, the business scenario and weight relationship is queried to obtain the weights corresponding to each feature label.

[0105] In one possible implementation, it also includes: a weight adjustment module for obtaining the response time of the recipient of each business data; if any response time exceeds the set time, the weight in the relationship between the business scenario and the weight is adjusted using a machine learning algorithm.

[0106] In a possible implementation, the business data acquisition module 41 is specifically configured to respond to a rights processing request sent by a third-party platform, parse the rights processing request, and obtain at least two pieces of business data carried in the rights processing request.

[0107] The business data synchronization device provided in the embodiment of the present application can execute the business data synchronization method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0108] Figure 5 This is a schematic diagram of the structure of an electronic device provided by this embodiment. The electronic device may include a service data synchronization device, such as Figure 5 As shown, the electronic device 500 includes a processor 510, a memory 520, an input device 530, and an output device 540; the number of processors 510 in the electronic device can be one or more. Figure 5 In the figure, a processor 510 is used as an example; the processor 510, memory 520, input device 530 and output device 540 in the electronic device can be connected via a bus or other means. Figure 5 The bus connection is taken as an example.

[0109] Memory 520, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the service data synchronization method in the embodiments of the present invention. Processor 510 executes the software programs, instructions, and modules stored in memory 520 to execute various functional applications and data processing of the electronic device, thereby implementing the service data synchronization method provided in the embodiments of the present invention.

[0110] The memory 520 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created based on the use of the terminal, etc. In addition, the memory 520 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 520 may further include a memory remotely located relative to the processor 510, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0111] The input device 530 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the electronic device, and may include a keyboard, a mouse, etc. The output device 540 may include a display device such as a display screen.

[0112] This embodiment further provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to implement the service data synchronization method provided in the embodiment of the present invention.

[0113] Of course, the computer executable instructions of the storage medium provided by the embodiment of the present invention are not limited to the operations of the method described above, but can also execute related operations in the business data synchronization method provided by any embodiment of the present invention.

[0114] Through the above description of the implementation methods, those skilled in the art can clearly understand that the present invention can be implemented with the help of software and necessary general-purpose hardware, and of course it can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as a computer floppy disk, read-only memory (ROM), random access memory (RAM), flash memory (FLASH), hard disk or optical disk, etc., including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute the methods described in each embodiment of the present invention.

[0115] It is worth noting that in the embodiment of the above-mentioned business data synchronization device, the various units and modules included are only divided according to functional logic, but are not limited to the above-mentioned division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the scope of protection of the present invention.

[0116] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

[0117] The foregoing description is intended only to provide specific embodiments of the present application, which will enable those skilled in the art to understand and implement the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments described herein, but is intended to be construed in the broadest manner consistent with the principles and novel features disclosed herein.

Claims

1. A business data synchronization method, characterized in that: The method comprises: In response to a benefit processing request, obtaining at least two pieces of business data associated with the benefit processing request; Determining at least one characteristic tag of each of the business data and a weight corresponding to at least one of the characteristic tags; Calculating the priority order of each of the business data using a weighted algorithm based on at least one feature tag of each of the business data and a weight corresponding to the at least one feature tag; Data synchronization is performed on at least two of the service data according to the priority order of each of the service data.

2. The method according to claim 1, characterized in that The feature tag includes at least one of the following tags: importance tag, time tag, source tag; The importance tag is used to reflect the importance level of the business data, the time tag is used to reflect the generation time or modification time of the business data, and the source tag is used to reflect the reliability level of the sender of the business data.

3. The method according to claim 2, characterized in that The determining of at least one feature tag corresponding to each piece of service data includes at least one of the following: Determining the importance label of each piece of business data based on the business type of each piece of business data and the relationship between the pre-set business type and the importance level; Obtaining a generation time or modification time of each piece of business data, and determining a time tag of each piece of business data based on a difference between the generation time and a current time, or determining a time tag of each piece of business data based on a difference between the modification time and the current time; Based on the sender of the rights processing request and the preset relationship between the sender and the reliability level, the source label of each business data is determined.

4. The method according to claim 1, wherein The calculating the priority order of each of the business data by a weighted algorithm based on at least one feature tag of each of the business data and a weight corresponding to the at least one feature tag includes: quantifying at least two feature labels of each of the business data respectively to obtain at least two quantified feature labels of each of the business data; Performing weighted calculation on at least two of the quantified feature tags of each of the business data and the weights corresponding to the feature tags to obtain a sum of the weights of the respective business data; The sum of the weights of the various business data are sorted in descending order to obtain the priority order of the various business data.

5. The method according to claim 4, characterized in that Determining a weight corresponding to at least one of the feature tags includes: Obtaining the business scenario corresponding to the rights processing request and a pre-configured business scenario-weight relationship, wherein the business scenario-weight relationship includes the weight corresponding to each of the feature tags in different business scenarios; Based on the business scenario corresponding to the rights processing request, a query is made in the relationship between the business scenario and the weight to obtain the weight corresponding to each of the feature tags.

6. The method according to claim 5, characterized in that Also includes: Obtaining the response time of each recipient of the business data; If any of the response times exceeds the set duration, the weights in the business scenario and weight relationship are adjusted using a machine learning algorithm.

7. The method according to any one of claims 1 to 6, characterized in that The step of obtaining, in response to the equity processing request, at least two pieces of business data associated with the equity processing request includes: In response to the rights processing request sent by the third-party platform, the rights processing request is parsed to obtain at least two business data carried by the rights processing request.

8. A service data synchronization device, characterized in that: The device is configured at the server end, and the method includes: A business data acquisition module, configured to acquire, in response to a rights processing request, at least two pieces of business data associated with the rights processing request; a label and weight determination module, configured to determine at least one characteristic label of each of the business data and a weight corresponding to at least one characteristic label; a priority determination module, configured to calculate the priority order of each of the service data by a weighted algorithm based on at least one feature tag of each of the service data and a weight corresponding to the at least one feature tag; The data synchronization module is used to synchronize at least two of the business data according to the priority order of each of the business data.

9. An electronic device, characterized in that: The device comprises: one or more processors; a storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the business data synchronization method according to any one of claims 1 to 7.

10. A storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the business data synchronization method according to any one of claims 1 to 7 is implemented.

Images