WO2016184341A1 - 一种业务处理方法和设备 - Google Patents

一种业务处理方法和设备 Download PDF

Info

Publication number
WO2016184341A1
WO2016184341A1 PCT/CN2016/081824 CN2016081824W WO2016184341A1 WO 2016184341 A1 WO2016184341 A1 WO 2016184341A1 CN 2016081824 W CN2016081824 W CN 2016081824W WO 2016184341 A1 WO2016184341 A1 WO 2016184341A1
Authority
WO
WIPO (PCT)
Prior art keywords
sub
service
services
identifier
offline platform
Prior art date
Application number
PCT/CN2016/081824
Other languages
English (en)
French (fr)
Inventor
李炉阳
Original Assignee
阿里巴巴集团控股有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2016184341A1 publication Critical patent/WO2016184341A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/566—Grouping or aggregating service requests, e.g. for unified processing

Definitions

  • the embodiments of the present application relate to the field of communications technologies, and in particular, to a service processing method and device.
  • the scheduling system manages specific services (including one or more sub-services), dependencies between sub-services, and running time of sub-services; the offline platform provides storage and computing capabilities; generally, each scheduling system will By using a separate offline account to submit the service to the offline platform, it is difficult to correspond to the sub-service of the scheduling system once the service is submitted to the offline platform, and therefore, the resource consumption of the offline platform cannot be counted.
  • Specific personnel because the accounts on the offline platform are generally shared by multiple people and cannot be distinguished by account number), the offline platform cannot perceive the priority information of each sub-service, and the jobs performed on the offline platform (processing Business) is unmanageable.
  • a service processing method including:
  • the service scheduling system acquires a service to be processed, and the service includes one or more sub-services;
  • the service scheduling system determines a processing sequence of the sub-services
  • the service scheduling system establishes an identifier for each sub-service, and sends the sub-service and the identifier corresponding to the sub-service to the offline platform according to the processing sequence.
  • the service scheduling system sends the identifiers corresponding to the sub-services and the sub-services to the offline platform according to the processing sequence, which specifically includes:
  • the service scheduling system sends the first sub-services and the identifiers corresponding to the top sub-services to the offline platform;
  • the service scheduling system Upon receiving the confirmation message of the last sub-service completion of the feedback from the offline platform, the service scheduling system sorts the currently-preserved sub-services in the sub-services that need to be processed and the current remaining sub-services to be processed. The identifier corresponding to the first sub-service is sent to the offline platform.
  • the identifier is specifically a character string
  • the identifier includes a plurality of pieces of identification information, and the identifier information is separated and separated by a separator in the character string, where the identifier information includes the responsible person information corresponding to the sub-service and/or the data information corresponding to the sub-service and / or priority information of the sub-service.
  • the present application also provides a service processing method, which includes:
  • the offline platform receives the sub-service sent by the service scheduling system and the identifier corresponding to the sub-service;
  • the offline platform processes the sub-service based on the identifier.
  • the offline platform processes the sub-service based on the identifier, and further includes:
  • the offline platform Each time the sub-service is processed, the offline platform returns a confirmation message of the sub-service processing completion to the service scheduling system.
  • the offline platform processes the sub-service based on the identifier, and specifically includes:
  • the offline platform determines whether the responsible person information is legal; if the determination result is yes, the offline platform processes the sub-service; if the judgment result is no The offline platform discards the sub-service;
  • the offline platform searches for data required for processing the sub-service based on the data information, and processes the sub-service based on the found data;
  • the offline platform prioritizes the sub-services based on the priority information, and according to the priority Processing is performed in order from high to low.
  • the present application also provides a service scheduling system, which includes:
  • the service scheduling system acquires a service to be processed, and the service includes one or more sub-services;
  • a determining module configured to determine a processing order of the sub-services
  • a sending module configured to send, by using the processing sequence, the identifier corresponding to the sub-service and the sub-service to an offline platform.
  • the sending module is specifically configured to:
  • the service scheduling system sends the first sub-services and the identifiers corresponding to the top sub-services to the offline platform;
  • the service scheduling system Upon receiving the confirmation message of the last sub-service completion of the feedback from the offline platform, the service scheduling system sorts the currently-preserved sub-services in the sub-services that need to be processed and the current remaining sub-services to be processed. The identifier corresponding to the first sub-service is sent to the offline platform.
  • the identifier is specifically a character string
  • the identifier includes a plurality of pieces of identification information, and the identifier information is separated and separated by a separator in the character string, where the identifier information includes the responsible person information corresponding to the sub-service and/or the data information corresponding to the sub-service and / or priority information of the sub-service.
  • the present application also provides an offline platform, which includes:
  • a receiving module configured to receive a sub-service sent by the service scheduling system and an identifier corresponding to the sub-service
  • a processing module configured to process the sub-service based on the identifier.
  • the offline platform further includes:
  • the returning module is configured to return a confirmation message of the completion of the sub-service processing to the service scheduling system each time a sub-service is processed.
  • the processing module is specifically configured to:
  • the identifier includes the responsible person information corresponding to the sub-service, determining whether the responsible person information is legal; if the judgment result is yes, processing the sub-service; if the judgment result is no, discarding the sub-service;
  • the identifier includes the data information corresponding to the sub-service, searching for data required for processing the sub-service based on the data information, and processing the sub-service based on the found data;
  • the sub-services are prioritized based on the priority information, and the priority is from the highest to the highest Low processing in sequence.
  • the service scheduling system establishes an identifier for each sub-service through the service scheduling system, and sends the identifier corresponding to the sub-service and the sub-service to the offline platform, thereby connecting the service scheduling system and the offline platform by using the identifier, so that the offline
  • the sub-services processed on the platform are traceable, and the priority information of each sub-service is perceived on the offline platform, and the sub-services are managed on the offline platform.
  • FIG. 1 is a schematic flowchart of a service processing method according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a service processing method according to an embodiment of the present application.
  • FIG. 3 is a schematic structural diagram of a service scheduling system according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an offline platform according to an embodiment of the present application.
  • the method includes the following steps:
  • Step 101 The service scheduling system acquires a service to be processed, and the service includes one or more sub-services.
  • the service may be a data processing service, for example, determining a seller's rating according to the user's evaluation, obtaining a user's evaluation within a certain period of time, and then obtaining a rating rule, and then calculating the seller's rating through the rating rule and the evaluation, and obtaining
  • the service to be processed (for example, service 1) will include one or more sub-services, for example, service 1 has three sub-services (for example, obtaining the user's evaluation within a certain period of time, which is a sub-service in the service)
  • the obtaining the service 1 to be processed is to acquire the three sub-services included in the service 1.
  • Step 102 The service scheduling system determines a processing sequence of the sub-services.
  • the service scheduling system is a management system of the service to be processed, which is used to ensure normal processing of the service, and since there are sequential or dependent relationships among the plurality of sub-services included in the service, the service scheduling system is required to determine each The processing sequence of the sub-services, the service scheduling system may specifically be a system composed of multiple devices running management software, and the service scheduling system may determine the processing order of the sub-services based on the dependencies of the sub-services, when there is only one sub-service, In the case of a sub-service, that is, a service, the order of processing is to directly process the sub-service. When there are multiple sub-services, there may be dependencies between the sub-services.
  • the input data of the sub-services is the same as the sub-service 2 and the sub-service 3.
  • the processing result of the service is the processing result of the three sub-services, that is, there is no order or affiliation between the three sub-services, so that the processing order It may be arbitrary, as long as one order is selected as an order of processing in any of a plurality of orders.
  • Step 103 The service scheduling system establishes an identifier for each sub-service.
  • the identifier is specifically a string; when the identifier is established, the mapping table may be established based on the correspondence between the sub-service and the identifier, so that after a sub-service is sent to the offline platform for processing, it can trace back which sub-service is processed;
  • the identifier may be directly part of the sub-service; the identifier includes multiple identifiers, and the identifier information is separated and separated by a separator in the string, and the identifier information includes the responsible person information corresponding to the sub-service and/or the data corresponding to the sub-service. Priority information for information and/or sub-services.
  • the identifier includes multiple identifier information, for example, corresponding to a sub-service.
  • Responsible person information, data information corresponding to the sub-service, priority information of the sub-service, etc. may be set as the identification information based on the need, and the identification information is separated in the identified character string.
  • the characters are separated, for example, the separator is ⁇ , taking the above identifier as an example, wherein the last part of the character "5" can be expressed as the priority of the sub-service.
  • Step 104 The service scheduling system sends the identifier corresponding to the sub-service and the sub-service to the offline platform according to the processing sequence.
  • the specific sending process specifically includes:
  • the service scheduling system determines the top-ranked sub-services of the remaining sub-services to be processed based on the processing order; the service scheduling system sends the top-ranked sub-services and the identifiers corresponding to the top-ranked sub-services to the offline platform; When the acknowledgment message of the previous sub-service is completed, the service scheduling system sends the current sub-services of the sub-services that need to be processed, and the currently-represented sub-services of the sub-services that need to be processed, to the offline The platform; wherein the offline platform may be a server or other processing device for storing data required for processing the service and processing the received service by using the stored data.
  • the processing sequence is sub-service 1 - sub-service 2 - sub-service 3, and first, the service scheduling system determines the top-ranked sub-services of the remaining sub-services to be processed based on the sequence, if Not entering In the case of row processing, the top priority is sub-service 1. In this case, the sub-service 1 and the identifier corresponding to the sub-service are sent to the offline platform, and after the sub-service 1 is processed by the offline platform, the confirmation message of the processing completion is sent. To the business scheduling system, business scheduling system.
  • the current sub-service 2 is sub-service 2
  • the sub-service 2 is And the identifier corresponding to the sub-service 2 is sent to the offline platform, and so on, until all the sub-services are processed.
  • the embodiment of the present application further discloses a service processing method, as shown in FIG. 2, including:
  • Step 201 The offline platform receives the identifier corresponding to the sub-service and the sub-service sent by the service scheduling system.
  • Step 201 The offline platform processes the sub-service based on the identifier.
  • the identification information includes the responsible person information corresponding to the sub-service, the data information corresponding to the sub-service, and the priority information of the sub-service as an example,
  • the offline platform determines whether the responsible person information is legal; if the judgment result is yes, the offline platform processes the sub-service; if the judgment result is no, the offline platform discards the sub-service; for example, when the identifier The information of the responsible person corresponding to the sub-service is user 1, but the user 1 has left the job, which means that the responsible person information is illegal. In this case, the corresponding one corresponding to the identifier of the user 1 can be directly discarded. Sub-business.
  • the offline platform searches for data required for processing the sub-service based on the data information, and processes the sub-service based on the found data; since some sub-services require special data processing
  • the data information may be stored in the identifier, for example, by modifying the time, or the number of times of running within the modification time, to identify the required data, so that the offline platform obtains the sub-service and the identifier corresponding to the sub-service. After that, the data information of the data required for processing the sub-service can be obtained from the identifier, so that the required data is found according to the data information to process the sub-service.
  • the offline platform When the identifier includes the priority information of the sub-service and the offline platform receives the plurality of sub-services at the same time, the offline platform prioritizes the sub-services based on the priority information, and processes the sub-services according to the priority from high to low. Since there may be multiple service scheduling systems, it may cause the offline platform to receive multiple sub-services at the same time (and also be identified by multiple sub-services). Therefore, since some services are important, they can be in the identification. Setting priority information so that the offline platform can sort the received sub-services based on the priority information, and Processing is performed in order of priority from high to low, so that sub-services and services with high priority can be processed as quickly as possible.
  • the sub-service is processed based on the identifier, and then includes:
  • the offline platform Whenever a sub-service is processed, the offline platform returns a confirmation message that the sub-service processing is completed to the service scheduling system.
  • the embodiment of the present application further discloses a service scheduling system, as shown in FIG. 3, including:
  • An obtaining module 301 the service scheduling system acquires a service to be processed, where the service includes one or more sub-services;
  • a determining module 302 configured to determine a processing sequence of the sub-services
  • An establishing module 303 is configured to establish an identifier for each sub-service
  • the sending module 304 is configured to send, by using the processing sequence, the identifier corresponding to the sub-service and the sub-service to an offline platform.
  • the sending module 304 is specifically configured to:
  • the service scheduling system sends the first sub-services and the identifiers corresponding to the top sub-services to the offline platform;
  • the service scheduling system Upon receiving the confirmation message of the last sub-service completion of the feedback from the offline platform, the service scheduling system sorts the currently-preserved sub-services in the sub-services that need to be processed and the current remaining sub-services to be processed. The identifier corresponding to the first sub-service is sent to the offline platform.
  • the identifier is specifically a character string
  • the identifier includes a plurality of pieces of identification information, and the identifier information is separated and separated by a separator in the character string, where the identifier information includes the responsible person information corresponding to the sub-service and/or the data information corresponding to the sub-service and / or priority information of the sub-service.
  • An embodiment of the present application further discloses an offline platform, as shown in FIG. 4, including:
  • the receiving module 401 is configured to receive a sub-service sent by the service scheduling system and an identifier corresponding to the sub-service;
  • the processing module 402 is configured to process the sub-service based on the identifier.
  • the offline platform also includes:
  • the processing module 402 is specifically configured to:
  • the identifier includes the responsible person information corresponding to the sub-service, determining whether the responsible person information is legal; if the judgment result is yes, processing the sub-service; if the judgment result is no, discarding the sub-service;
  • the identifier includes the data information corresponding to the sub-service, searching for data required for processing the sub-service based on the data information, and processing the sub-service based on the found data;
  • the sub-services are prioritized based on the priority information, and the priority is from the highest to the highest Low processing in sequence.
  • the service scheduling system establishes an identifier for each sub-service through the service scheduling system, and sends the identifier corresponding to the sub-service and the sub-service to the offline platform, thereby connecting the service scheduling system and the offline platform by using the identifier, so that the offline
  • the sub-services processed on the platform are traceable, and the priority information of each sub-service is perceived on the offline platform, and the sub-services are managed on the offline platform.
  • the present application can be implemented by hardware, or by software plus a necessary general hardware platform.
  • the technical solution of the present application may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including several The instructions are for causing a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various implementation scenarios of the present application.
  • modules in the apparatus in the implementation scenario may be distributed in the apparatus for implementing the scenario according to the implementation scenario description, or may be correspondingly changed in one or more devices different from the implementation scenario.
  • the modules of the above implementation scenarios may be combined into one module, or may be further split into multiple sub-modules.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本申请公开了一种业务处理方法和设备，该方法包括：业务调度系统获取需要处理的业务，所述业务包括一个或多个子业务；所述业务调度系统确定所述子业务的处理顺序；所述业务调度系统为每个子业务建立标识，并基于所述处理顺序将所述子业务和所述子业务对应的标识发送给离线平台，本申请实施例中通过标识来来连通业务调度系统与离线平台，使得在离线平台上处理的子业务都是可以追溯的，也可以实现在离线平台上感知各个子业务的优先级信息，并在离线平台上对子业务进行管理。

Description

一种业务处理方法和设备
本申请要求2015年05月19日递交的申请号为201510257495.0、发明名称为“一种业务处理方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，特别涉及一种业务处理方法和设备。
背景技术
随着大数据时代的到来，企业的数据仓库或者商业智能部的重要性越来越突出。随着数据量越来越大，很多企业会倾向于把数据放到一个离线平台里；此外随着业务处理的逻辑越来越复杂，出现了一个或者多个调度系统来管理业务处理的逻辑，业务的处理涉及到调度系统和离线平台独立的两个系统。
其中，调度系统管理具体的需要处理的业务(包括一个或多个子业务)、子业务之间的依赖关系、子业务的运行时机等；离线平台提供存储和计算的能力；一般每个调度系统会通过使用一个单独的离线账号到离线平台里去提交业务，这样导致一旦业务提交到离线平台后，就很难再与调度系统的子业务对应了，也因此，使得离线平台的资源消耗无法统计到具体的人员(因为离线平台上的账号一般是多人共同拥有使用权的，无法通过账号来区分人员)，离线平台就无法感知各个子业务的优先级信息，离线平台上进行的作业(处理子业务)是无法管理的。
发明内容
针对现有技术中的缺陷，本申请提出了一种业务处理方法，包括：
业务调度系统获取需要处理的业务，所述业务包括一个或多个子业务；
所述业务调度系统确定所述子业务的处理顺序；
所述业务调度系统为每个子业务建立标识，并基于所述处理顺序将所述子业务和所述子业务对应的标识发送给离线平台。
优选的，所述业务调度系统基于所述处理顺序将所述子业务和所述子业务对应的标识发送给离线平台，具体包括：
所述业务调度系统基于所述处理顺序确定剩余的需要处理的子业务中排序最前的子业务；
所述业务调度系统将排序最前的子业务和排序最前的子业务对应的标识发送给离线平台；
在接收到所述离线平台反馈的上一个子业务完成的确认消息时，所述业务调度系统将当前剩余的需要处理的子业务中排序最前的子业务和当前剩余的需要处理的子业务中排序最前的子业务对应的标识发送给离线平台。
优选的，所述标识具体为字符串；
所述标识中包含有多个标识信息，所述标识信息在所述字符串中通过分隔符进行分隔区分，所述标识信息包括子业务对应的责任人信息和/或子业务对应的数据信息和/或子业务的优先级信息。
本申请还提出了一种业务处理方法，其特征在于，包括：
离线平台接收业务调度系统发送的子业务和所述子业务对应的标识；
所述离线平台基于所述标识对所述子业务进行处理。
优选的，所述离线平台基于所述标识对所述子业务进行处理，之后还包括：
每当处理完一个子业务，所述离线平台向所述业务调度系统返回子业务处理完成的确认消息。
优选的，所述离线平台基于所述标识对所述子业务进行处理，具体包括：
当所述标识中包含有子业务对应的责任人信息时，所述离线平台判断所述责任人信息是否合法；若判断结果为是，所述离线平台处理所述子业务；若判断结果为否，所述离线平台丢弃所述子业务；
当所述标识中包含有子业务对应的数据信息时，所述离线平台基于所述数据信息查找处理所述子业务所需的数据，并基于查找到的数据对所述子业务进行处理；
当所述标识中包含有子业务的优先级信息且所述离线平台同时接收到多个子业务时，离线平台基于所述优先级信息对所述子业务进行优先级的排序，并按照优先级从高到低依次进行处理。
本申请还提出了一种业务调度系统，其特征在于，包括：
获取模块，业务调度系统获取需要处理的业务，所述业务包括一个或多个子业务；
确定模块，用于确定所述子业务的处理顺序；
建立模块，用于为每个子业务建立标识；
发送模块，用于基于所述处理顺序将所述子业务和所述子业务对应的标识发送给离线平台。
所述发送模块，具体用于：
所述业务调度系统基于所述处理顺序确定剩余的需要处理的子业务中排序最前的子业务；
所述业务调度系统将排序最前的子业务和排序最前的子业务对应的标识发送给离线平台；
在接收到所述离线平台反馈的上一个子业务完成的确认消息时，所述业务调度系统将当前剩余的需要处理的子业务中排序最前的子业务和当前剩余的需要处理的子业务中排序最前的子业务对应的标识发送给离线平台。
优选的，所述标识具体为字符串；
所述标识中包含有多个标识信息，所述标识信息在所述字符串中通过分隔符进行分隔区分，所述标识信息包括子业务对应的责任人信息和/或子业务对应的数据信息和/或子业务的优先级信息。
本申请还提出了一种离线平台，其特征在于，包括：
接收模块，用于接收业务调度系统发送的子业务和所述子业务对应的标识；
处理模块，用于基于所述标识对所述子业务进行处理。
优选的，离线平台还包括：
返回模块，用于每当处理完一个子业务时，向所述业务调度系统返回子业务处理完成的确认消息。
优选的，所述处理模块，具体用于：
当所述标识中包含有子业务对应的责任人信息时，判断所述责任人信息是否合法；若判断结果为是，处理所述子业务；若判断结果为否，丢弃所述子业务；
当所述标识中包含有子业务对应的数据信息时，基于所述数据信息查找处理所述子业务所需的数据，并基于查找到的数据对所述子业务进行处理；
当所述标识中包含有子业务的优先级信息且所述离线平台同时接收到多个子业务时，基于所述优先级信息对所述子业务进行优先级的排序，并按照优先级从高到低依次进行处理。
与现有技术相比，本申请中通过业务调度系统为每个子业务建立标识，并将子业务和子业务对应的标识发送给离线平台，从而通过标识来连通业务调度系统与离线平台，使得在离线平台上处理的子业务都是可以追溯的，也可以实现在离线平台上感知各个子业务的优先级信息，并在离线平台上对子业务进行管理。
附图说明
图1为本申请实施例提出的一种业务处理方法的流程示意图；
图2为本申请实施例提出的一种业务处理方法的流程示意图；
图3为本申请实施例提出的一种业务调度系统的结构示意图；
图4为本申请实施例提出的一种离线平台的结构示意图。
具体实施方式
如背景技术所述，针对现有技术中的缺陷，本申请中提出了一种业务处理方法，如图1所示，包括以下步骤：
步骤101、业务调度系统获取需要处理的业务，业务包括一个或多个子业务。
具体的，业务可以是数据处理业务，例如根据用户的评价确定卖家的评分，需要获取一段时间内用户的评价，然后获取评分规则，再通过评分规则和评价对卖家的评分进行计算，在得出评分之后再进行展示；需要进行处理的业务(例如为业务1)会包括一个或多个子业务，例如业务1有三个子业务(例如获取一段时间内用户的评价，就是该业务中的一个子业务)，其中，获取需要处理的业务1就是获取业务1所包括的三个子业务。
步骤102、业务调度系统确定子业务的处理顺序。
具体的，业务调度系统是需要处理的业务的管理系统，用于保证业务的正常处理，而由于业务中包括的多个子业务之间是有顺序或者依赖关系，因此就需要业务调度系统来确定各子业务的处理顺序，该业务调度系统具体可以为运行有管理软件的多个设备组成的系统，业务调度系统可以基于子业务的依赖关系来确定子业务的处理顺序，当只有一个子业务，也即子业务即业务时，处理的顺序自然就是直接处理该子业务，而当存在多个子业务时，由于子业务之间可能会存在依赖关系，例如当业务1存在多个子业务时，多个子业务之间可能会存在顺序关系，例如存在三个子业务，子业务1，子业务2，子业 务3，子业务2需要以子业务1的处理结果作为输入数据，而子业务3需要以子业务2的处理结果作为输入数据，因此子业务的处理顺序就是子业务1-子业务2-子业务3；当然，除此以外，也有可能子业务之间不存在依赖关系，也即是并列的，仍以上述三个子业务为例来进行说明，例如子业务1的处理结果不需要作为别的子业务的输入数据，同样的子业务2和子业务3也是一样，业务的处理结果就是这三个子业务的处理结果，也即这三个子业务之间并不存在顺序或附属关系，这样，处理顺序就可以是任意的，只要在任意的多个顺序中选择一个顺序来作为处理顺序即可。
步骤103、业务调度系统为每个子业务建立标识。
标识具体为字符串；在建立标识时，可以基于子业务与标识的对应关系建立映射表，以此后续当将某子业务发送给离线平台进行处理之后，可以回溯找到处理的哪个子业务；也可以将标识直接作为子业务的一部分；标识中包含有多个标识信息，标识信息在字符串中通过分隔符进行分隔区分，标识信息包括子业务对应的责任人信息和/或子业务对应的数据信息和/或子业务的优先级信息。
具体的，该标识中的信息可以是字符串，例如标识可以是一个ID，该ID＝036349^12345^20150416^1^1^5，标识中包含有多个标识信息，例如有子业务对应的责任人信息，子业务对应的数据信息，子业务的优先级信息等等，当然除此以外，还可以基于需要设置其他的信息作为标识信息，具体的，标识信息在标识的字符串中通过分隔符进行分隔区分，例如分割符为^，以上述标识为例，其中最后一部分的字符“5”就可以表示为子业务的优先级。
步骤104、业务调度系统基于处理顺序将子业务和子业务对应的标识发送给离线平台。
具体的发送过程，具体包括：
业务调度系统基于处理顺序确定剩余的需要处理的子业务中排序最前的子业务；业务调度系统将排序最前的子业务和排序最前的子业务对应的标识发送给离线平台；在接收到离线平台反馈的上一个子业务完成的确认消息时，业务调度系统将当前剩余的需要处理的子业务中排序最前的子业务和当前剩余的需要处理的子业务中排序最前的子业务对应的标识发送给离线平台；其中，离线平台可以是服务器，也可以是其他处理设备，用于存储处理业务所需要的数据和利用所存储的数据对接收到的业务进行处理。
具体的，仍以上述例子来进行说明，处理顺序为子业务1-子业务2-子业务3，首先业务调度系统基于该顺序判断剩余的需要处理的子业务中排序最前的子业务，若还未进 行处理，则排序最前的是子业务1，在此情况下，就将子业务1以及子业务对应的标识发送给离线平台，在离线平台处理完子业务1后，会发送处理完成的确认消息给业务调度系统，业务调度系统。
接收到该确认消息后，继续判断当前剩余的需要处理的子业务中排序最前的子业务，此时，由于子业务1已经处理完成，因此当前排序最前的是子业务2，就将子业务2以及子业务2所对应的标识发送给离线平台，以此类推，直到处理完所有的子业务。
为了进一步对本申请进行说明，本申请实施例还公开了一种业务处理方法，如图2所示，包括：
步骤201、离线平台接收业务调度系统发送的子业务和子业务对应的标识。
步骤201离线平台基于标识对子业务进行处理。
具体的，以标识信息中包括子业务对应的责任人信息，子业务对应的数据信息，子业务的优先级信息为例来进行说明，
当标识中包含有子业务对应的责任人信息时，离线平台判断责任人信息是否合法；若判断结果为是，离线平台处理子业务；若判断结果为否，离线平台丢弃子业务；例如当标识中包含子业务对应的责任人信息为用户1，但该用户1已经离职，也就表示该责任人信息是不合法的，在此情况下，就可以直接丢弃该包含用户1的标识所对应的子业务。
当标识中包含有子业务对应的数据信息时，离线平台基于数据信息查找处理子业务所需的数据，并基于查找到的数据对子业务进行处理；由于有些子业务的处理是需要特殊的数据的，在此，可以将数据信息存储在标识中，例如通过修改时间，或者在修改时间内运行的次数等来对需要的数据进行标识，这样当离线平台获取到子业务以及子业务对应的标识后，就可以从标识中获取处理该子业务所需要的数据的数据信息，从而根据数据信息找到所需要的数据来对该子业务进行处理。
当标识中包含有子业务的优先级信息且离线平台同时接收到多个子业务时，离线平台基于优先级信息对子业务进行优先级的排序，并按照优先级从高到低依次进行处理。由于可能存在多个业务调度系统，这样有可能导致离线平台同时收到多个子业务(同时也会受到多个子业务对应的标识)，这样，由于某些业务是很重要的，因此可以在标识中设置优先级信息，这样离线平台可以基于优先级信息对接收到的子业务进行排序，并 基于按照优先级从高到低的顺序进行处理，从而保证优先级高的子业务和业务能尽快进行处理。
而在离线平台基于标识对子业务进行处理，之后还包括：
每当处理完一个子业务，离线平台向业务调度系统返回子业务处理完成的确认消息。
本申请实施例还公开了一种业务调度系统，如图3，包括：
获取模块301，业务调度系统获取需要处理的业务，所述业务包括一个或多个子业务；
确定模块302，用于确定所述子业务的处理顺序；
建立模块303，用于为每个子业务建立标识；
发送模块304，用于基于所述处理顺序将所述子业务和所述子业务对应的标识发送给离线平台。
所述发送模块304，具体用于：
所述业务调度系统基于所述处理顺序确定剩余的需要处理的子业务中排序最前的子业务；
所述业务调度系统将排序最前的子业务和排序最前的子业务对应的标识发送给离线平台；
在接收到所述离线平台反馈的上一个子业务完成的确认消息时，所述业务调度系统将当前剩余的需要处理的子业务中排序最前的子业务和当前剩余的需要处理的子业务中排序最前的子业务对应的标识发送给离线平台。
所述标识具体为字符串；
所述标识中包含有多个标识信息，所述标识信息在所述字符串中通过分隔符进行分隔区分，所述标识信息包括子业务对应的责任人信息和/或子业务对应的数据信息和/或子业务的优先级信息。
本申请实施例还公开了一种离线平台，如图4所示，包括：
接收模块401，用于接收业务调度系统发送的子业务和所述子业务对应的标识；
处理模块402，用于基于所述标识对所述子业务进行处理。
该离线平台，还包括：
返回模块，用于每当处理完一个子业务时，向所述业务调度系统返回子业务处理完 成的确认消息。
所述处理模块402，具体用于：
当所述标识中包含有子业务对应的责任人信息时，判断所述责任人信息是否合法；若判断结果为是，处理所述子业务；若判断结果为否，丢弃所述子业务；
当所述标识中包含有子业务对应的数据信息时，基于所述数据信息查找处理所述子业务所需的数据，并基于查找到的数据对所述子业务进行处理；
当所述标识中包含有子业务的优先级信息且所述离线平台同时接收到多个子业务时，基于所述优先级信息对所述子业务进行优先级的排序，并按照优先级从高到低依次进行处理。
与现有技术相比，本申请中通过业务调度系统为每个子业务建立标识，并将子业务和子业务对应的标识发送给离线平台，从而通过标识来连通业务调度系统与离线平台，使得在离线平台上处理的子业务都是可以追溯的，也可以实现在离线平台上感知各个子业务的优先级信息，并在离线平台上对子业务进行管理。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到本申请可以通过硬件实现，也可以借助软件加必要的通用硬件平台的方式来实现。基于这样的理解，本申请的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质(可以是CD-ROM，U盘，移动硬盘等)中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施场景所述的方法。
本领域技术人员可以理解附图只是一个优选实施场景的示意图，附图中的模块或流程并不一定是实施本申请所必须的。
本领域技术人员可以理解实施场景中的装置中的模块可以按照实施场景描述进行分布于实施场景的装置中，也可以进行相应变化位于不同于本实施场景的一个或多个装置中。上述实施场景的模块可以合并为一个模块，也可以进一步拆分成多个子模块。
上述本申请序号仅仅为了描述，不代表实施场景的优劣。
以上公开的仅为本申请的几个具体实施场景，但是，本申请并非局限于此，任何本领域的技术人员能思之的变化都应落入本申请的保护范围。

Claims (12)

  1. 一种业务处理方法，其特征在于，包括：
    业务调度系统获取需要处理的业务，所述业务包括一个或多个子业务；
    所述业务调度系统确定所述子业务的处理顺序；
    所述业务调度系统为每个子业务建立标识，并基于所述处理顺序将所述子业务和所述子业务对应的标识发送给离线平台。
  2. 如权利要求1所述的方法，其特征在于，所述业务调度系统基于所述处理顺序将所述子业务和所述子业务对应的标识发送给离线平台，具体包括：
    所述业务调度系统基于所述处理顺序确定剩余的需要处理的子业务中排序最前的子业务；
    所述业务调度系统将排序最前的子业务和排序最前的子业务对应的标识发送给离线平台；
    在接收到所述离线平台反馈的上一个子业务完成的确认消息时，所述业务调度系统将当前剩余的需要处理的子业务中排序最前的子业务和当前剩余的需要处理的子业务中排序最前的子业务对应的标识发送给离线平台。
  3. 如权利要求1所述的方法，其特征在于，所述标识具体为字符串；
    所述标识中包含有多个标识信息，所述标识信息在所述字符串中通过分隔符进行分隔区分，所述标识信息包括子业务对应的责任人信息和/或子业务对应的数据信息和/或子业务的优先级信息。
  4. 一种业务处理方法，其特征在于，包括：
    离线平台接收业务调度系统发送的子业务和所述子业务对应的标识；
    所述离线平台基于所述标识对所述子业务进行处理。
  5. 如权利要求4所述的方法，其特征在于，所述离线平台基于所述标识对所述子业务进行处理，之后还包括：
    每当处理完一个子业务，所述离线平台向所述业务调度系统返回子业务处理完成的确认消息。
  6. 如权利要求4所述的方法，其特征在于，所述离线平台基于所述标识对所述子业务进行处理，具体包括：
    当所述标识中包含有子业务对应的责任人信息时，所述离线平台判断所述责任人信息是否合法；若判断结果为是，所述离线平台处理所述子业务；若判断结果为否，所述离线平台丢弃所述子业务；
    当所述标识中包含有子业务对应的数据信息时，所述离线平台基于所述数据信息查找处理所述子业务所需的数据，并基于查找到的数据对所述子业务进行处理；
    当所述标识中包含有子业务的优先级信息且所述离线平台同时接收到多个子业务时，离线平台基于所述优先级信息对所述子业务进行优先级的排序，并按照优先级从高到低依次进行处理。
  7. 一种业务调度系统，其特征在于，包括：
    获取模块，业务调度系统获取需要处理的业务，所述业务包括一个或多个子业务；
    确定模块，用于确定所述子业务的处理顺序；
    建立模块，用于为每个子业务建立标识；
    发送模块，用于基于所述处理顺序将所述子业务和所述子业务对应的标识发送给离线平台。
  8. 如权利要求7所述的系统，其特征在于，所述发送模块，具体用于：
    所述业务调度系统基于所述处理顺序确定剩余的需要处理的子业务中排序最前的子业务；
    所述业务调度系统将排序最前的子业务和排序最前的子业务对应的标识发送给离线平台；
    在接收到所述离线平台反馈的上一个子业务完成的确认消息时，所述业务调度系统将当前剩余的需要处理的子业务中排序最前的子业务和当前剩余的需要处理的子业务中排序最前的子业务对应的标识发送给离线平台。
  9. 如权利要求7所述的系统，其特征在于，所述标识具体为字符串；
    所述标识中包含有多个标识信息，所述标识信息在所述字符串中通过分隔符进行分隔区分，所述标识信息包括子业务对应的责任人信息和/或子业务对应的数据信息和/或子业务的优先级信息。
  10. 一种离线平台，其特征在于，包括：
    接收模块，用于接收业务调度系统发送的子业务和所述子业务对应的标识；
    处理模块，用于基于所述标识对所述子业务进行处理。
  11. 如权利要求10所述的平台，其特征在于，还包括：
    返回模块，用于每当处理完一个子业务时，向所述业务调度系统返回子业务处理完成的确认消息。
  12. 如权利要求10所述的平台，其特征在于，所述处理模块，具体用于：
    当所述标识中包含有子业务对应的责任人信息时，判断所述责任人信息是否合法；若判断结果为是，处理所述子业务；若判断结果为否，丢弃所述子业务；
    当所述标识中包含有子业务对应的数据信息时，基于所述数据信息查找处理所述子业务所需的数据，并基于查找到的数据对所述子业务进行处理；
    当所述标识中包含有子业务的优先级信息且所述离线平台同时接收到多个子业务时，基于所述优先级信息对所述子业务进行优先级的排序，并按照优先级从高到低依次进行处理。
PCT/CN2016/081824 2015-05-19 2016-05-12 一种业务处理方法和设备 WO2016184341A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510257495.0 2015-05-19
CN201510257495.0A CN106169979B (zh) 2015-05-19 2015-05-19 一种业务处理方法和设备

Publications (1)

Publication Number Publication Date
WO2016184341A1 true WO2016184341A1 (zh) 2016-11-24

Family

ID=57319385

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/081824 WO2016184341A1 (zh) 2015-05-19 2016-05-12 一种业务处理方法和设备

Country Status (2)

Country Link
CN (1) CN106169979B (zh)
WO (1) WO2016184341A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106779363A (zh) * 2016-12-02 2017-05-31 浪潮通信信息系统有限公司 一种业务处理方法及装置
CN106899666B (zh) * 2017-02-21 2019-12-24 阿里巴巴集团控股有限公司 一种针对业务标识的数据处理方法及装置
CN109327321B (zh) * 2017-08-01 2021-10-15 中兴通讯股份有限公司 网络模型业务执行方法、装置、sdn控制器及可读存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102402606A (zh) * 2011-11-28 2012-04-04 中国科学院计算机网络信息中心 一种高效的文本数据挖掘方法
US20130227147A1 (en) * 2012-02-27 2013-08-29 Xerox Corporation Systems and methods for creating web service compositions
CN104239148A (zh) * 2013-06-06 2014-12-24 腾讯科技（深圳）有限公司 一种分布式任务调度方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070143169A1 (en) * 2005-12-21 2007-06-21 Grant Chad W Real-time workload information scheduling and tracking system and related methods
US8185899B2 (en) * 2007-03-07 2012-05-22 International Business Machines Corporation Prediction based priority scheduling
CN102402423A (zh) * 2010-09-19 2012-04-04 百度在线网络技术（北京）有限公司 一种在网络设备中进行多任务处理的方法和设备
CN103533070A (zh) * 2013-10-22 2014-01-22 华为技术有限公司 业务同步方法、内容管理设备及策略管理设备
CN104571958B (zh) * 2014-12-27 2019-06-07 北京奇虎科技有限公司 一种任务执行方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102402606A (zh) * 2011-11-28 2012-04-04 中国科学院计算机网络信息中心 一种高效的文本数据挖掘方法
US20130227147A1 (en) * 2012-02-27 2013-08-29 Xerox Corporation Systems and methods for creating web service compositions
CN104239148A (zh) * 2013-06-06 2014-12-24 腾讯科技（深圳）有限公司 一种分布式任务调度方法及装置

Also Published As

Publication number Publication date
CN106169979B (zh) 2020-07-31
CN106169979A (zh) 2016-11-30

Similar Documents

Publication Publication Date Title
US11068964B2 (en) Method and device for processing service request
US8473493B2 (en) System and method for selective information and resource sharing
US10229208B2 (en) Optimization of query execution
US9202173B1 (en) Using link analysis in adversarial knowledge-based authentication model
CN105447046A (zh) 一种分布式系统数据一致性处理方法、装置和系统
WO2021057084A1 (zh) 一种基于区块链的数据处理方法、装置、系统及电子设备
CN105224396B (zh) 一种业务数据处理方法和装置
US9152775B1 (en) Question generation in knowledge-based authentication for an enterprise
JP2019507424A5 (zh)
CN104486129B (zh) 分布式环境下保障应用服务质量的方法及系统
EP3188051B1 (en) Systems and methods for search template generation
WO2016184341A1 (zh) 一种业务处理方法和设备
US20190268377A1 (en) Platform for automated regulatory compliance monitoring of messaging services
CN107622060A (zh) 订单跟踪分析方法及装置
CN109242405A (zh) 政务处理方法及装置、计算机设备与可读存储介质
WO2014180392A1 (zh) 一种基于m2m的信息处理方法和m2m业务平台
CN114201278A (zh) 任务处理方法、任务处理装置、电子设备以及存储介质
US10929412B2 (en) Sharing content based on extracted topics
CN102902574B (zh) 一种多信息流节点的协同处理方法及装置
WO2019062066A1 (zh) 终端设备联机任务执行方法、服务器及可读存储介质
CN106257520A (zh) 解析应答方法及系统
WO2019062020A1 (zh) 异步任务统一处理方法、装置及存储介质
US20150106899A1 (en) System and method for cross-cloud identity matching
CN111930653A (zh) 一种usb设备的远程分配使用方法及装置
CN112187719A (zh) 被攻击服务器的信息获取方法、装置和电子设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16795828

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16795828

Country of ref document: EP

Kind code of ref document: A1