WO2023231413A1 - 服务处理方法、装置、级联系统、电子设备及存储介质 - Google Patents

服务处理方法、装置、级联系统、电子设备及存储介质 Download PDF

Info

Publication number
WO2023231413A1
WO2023231413A1 PCT/CN2022/143788 CN2022143788W WO2023231413A1 WO 2023231413 A1 WO2023231413 A1 WO 2023231413A1 CN 2022143788 W CN2022143788 W CN 2022143788W WO 2023231413 A1 WO2023231413 A1 WO 2023231413A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
service
data platform
level
platform
Prior art date
Application number
PCT/CN2022/143788
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
Priority claimed from CN202210612887.4A external-priority patent/CN115002228B/zh
Priority claimed from CN202211191697.6A external-priority patent/CN115481188A/zh
Application filed by 杭州数梦工场科技有限公司 filed Critical 杭州数梦工场科技有限公司
Publication of WO2023231413A1 publication Critical patent/WO2023231413A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems

Definitions

  • the present application relates to the field of computer technology, and in particular, to a service processing method, device, cascade system, electronic equipment and storage medium.
  • This application provides a service processing method, which can be applied to any level data platform in a multi-level data platform; a cascading module is deployed in the data platform, and the cascading module is used to perform communication between data platforms at different levels.
  • Data interaction; the method includes: receiving a target task request; in the case where the target task request is a service call request from a lower-level data platform for a target service registered on the current-level data platform, wherein the service The call request includes the service identification of the target service and the service call parameters related to the target service.
  • the corresponding relationship between the service identification and the service invocation interface of the service is determined, and the service invocation interface corresponding to the service identification of the target service is determined; the service invocation parameters are submitted to the queried service invocation interface to initiate the requested service invocation interface.
  • the lower-level data platform makes cascade calls to the target service.
  • the multi-level data platform includes at least one-level central data platform and at least one-level branch data platform; wherein, the central data platform is cascaded with lower-level data platforms; and the branch data platform is not cascaded with lower-level data platforms.
  • Data platform; the data platform at this level is the central data platform at this level; the central data platform at this level is cascaded with the subordinate branch data platform and/or the subordinate central data platform.
  • the cascading module of the central data platform includes: a platform management module for managing subordinate data platforms cascaded with the central data platform; the method further includes: obtaining Register on the central data platform at this level a platform cascading request for a subordinate data platform cascaded with the central data platform at this level; the platform cascading request includes the identification information of the subordinate data platform to be registered;
  • the platform management module is called to generate a cascading relationship between the identification information of the central data platform at this level and the identification information of the subordinate data platform to be registered, and The cascading relationship is maintained in the platform management module; and, cascading configuration information for cascading with the central data platform of this level is generated for the subordinate data platform to be registered, and the cascade configuration information is generated for the subordinate data platform to be registered.
  • the cascade configuration information is sent to the subordinate data platform to be registered, so that the subordinate data platform to be registered completes the cascade configuration with the central data platform of
  • the cascading module of the data platform includes: a service management module for managing registered services on the data platform; the method further includes: in response to obtaining the A service registration request to register a service on the data platform calls the service management module, and the service management module registers a service on the data platform at the same level based on the service registration request, and registers the service of the registered service
  • the corresponding relationship between the identification and the service calling interface of the service is maintained in the service management module.
  • the cascade module of the data platform includes: a service proxy module for initiating service calls for services registered on the data platform, and in response to the service call request, query the services of the service The corresponding relationship between the identifier and the service invocation interface of the service, and determining the service invocation interface corresponding to the service identifier of the target service, including: in response to the service invocation request, calling the service agent module to query the service management module Maintain the corresponding relationship between the service identification of the service and the service invocation interface of the service, determine the service invocation interface corresponding to the service identification of the target service; submit the service invocation parameters to the queried service invocation Interface to initiate the cascade call of the lower-level data platform for the target service, including: the service proxy module submits the service call parameters to the queried service call interface to initiate the lower-level
  • the data platform makes cascade calls to the target service.
  • calling the service management module, and having the service management module register a service on the data platform at the same level based on the service registration request includes: calling the service management module, and having the service agent module Register a service on the data platform of the current level based on the service registration request to query the data of all subordinates in the cascading relationship maintained by the platform management module that have a cascading relationship with the data platform of the current level.
  • the service management module in response to obtaining a set of data platforms that have the calling authority for the service on the data platform of this level among the lower-level data platforms that have a cascading relationship with the data platform of this level, at The service management module maintains the corresponding relationship between the service and the set of the data platform to complete the service registration for the service on the data platform at the same level.
  • the service agent module in response to the service invocation request, call the service agent module to query the corresponding relationship between the service identification of the service maintained by the service management module and the service invocation interface of the service, and determine the corresponding relationship with the target service.
  • the service invocation interface corresponding to the service identifier includes: in response to the service invocation request, calling the service agent module, querying the corresponding relationship between the service and the set of data platforms maintained by the service management module, and determining the subordinate Whether the data platform has the calling authority for the target service; if so, further query the corresponding relationship between the service identification of the service maintained by the service management module and the service calling interface of the service, and determine the corresponding relationship with the target service.
  • the service calling interface corresponding to the service ID in response to the service invocation request, calling the service agent module, querying the corresponding relationship between the service and the set of data platforms maintained by the service management module, and determining the subordinate Whether the data platform has the calling authority for the target service; if so, further query the corresponding relationship
  • the method further includes: the service agent module obtains the call result of the lower-level data platform's cascade call for the target service, and returns the obtained call result to the lower-level data platform. .
  • the service includes at least one of the following: directory sharing service, interface resource sharing service, and data resource sharing service.
  • the method further includes: in response to the creation request of the data aggregation task, based on the target subordinate data specified in the creation request. platform and data standards, create a data aggregation task associated with the target lower-level data platform; wherein the data aggregation task includes the data standard; and issue the data aggregation task to the Target lower-level data platform; upon receiving the preset notification sent by the target lower-level data platform to the cascade module, convert the source database of the target lower-level data platform into The data to be aggregated according to the data standard is written into the destination database of the data platform at the same level.
  • the cascading module maintains communication parameters of each lower-level data platform.
  • the cascading module establishes a communication connection with the lower-level data platform through the communication parameters and transmits it through the communication connection. data.
  • issuing the data aggregation task to the target lower-level data platform through the cascading module includes: responding to a timing polling request initiated by the target lower-level data platform to the cascading module. , query whether there is a data aggregation task associated with the target lower-level data platform; if there is, the cascade module delivers the queried data aggregation task to the target lower-level data platform.
  • the data standard includes information items used to define data; the information items include at least one of information item name, data type, data length, and description; the data standard is used to combine subordinate data platforms Convert data of other data standards into data of the data standard to be aggregated.
  • the cascading module writes the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform into the destination database of the current-level data platform, It includes: writing the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform through the cascading module into a preset front-end library, and completing the data aggregation task. The status is updated to complete; when the task status of the data aggregation tasks associated with all target lower-level data platforms is completed, the cascade module converts all the data provided by the target lower-level data platform stored in the front-end library into The data to be aggregated according to the data standard is written into the destination database of the data platform at the same level.
  • writing the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform into a preset front-end library through the cascading module includes: The cascading module starts the data exchange engine to write the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform into the preset pre-repository based on the data exchange engine; The cascading module writes the data to be aggregated and converted into the data standard provided by the target lower-level data platform stored in the front-end library into the target database of the current-level data platform, including : Start the data exchange engine through the cascade module, and write the data to be aggregated that has been converted into the data standard provided by the target lower-level data platform stored in the front-end library based on the data exchange engine. to the destination database of the data platform at this level.
  • This application also provides a service processing method, which method is applied to any level data platform in a multi-level data platform; a cascade module is deployed in the data platform, and the cascade module is used to process data at different levels.
  • the present application also provides a cascade system, which is configured to perform the above-mentioned method; wherein the cascade system includes a multi-level data platform; the multi-level data platform includes at least one central data platform and at least one level branch data platforms; the central data platform is cascaded with lower-level data platforms; the branch data platforms are not cascaded with lower-level data platforms; cascading modules are deployed in each data platform, and the cascading modules are used to perform Data interaction between data platforms at different levels.
  • This application also provides a service processing device, which is applied to any level data platform in a multi-level data platform; a cascading module is deployed in the data platform, and the cascading module is used to process data at different levels.
  • Data interaction between platforms; the device includes: a request receiving unit, used to receive a target task request; a relationship query unit, used to register on the data platform of the current level that the target task request is a subordinate data platform.
  • the level is queried
  • the application also provides an electronic device, including a communication interface, a processor, a memory and a bus.
  • the communication interface, the processor and the memory are connected to each other through a bus; machine-readable instructions are stored in the memory,
  • the processor executes the above method by calling the machine-readable instructions.
  • This application also provides a computer-readable storage medium, which stores machine-readable instructions. When called and executed by a processor, the machine-readable instructions implement the above method.
  • Figure 1 is a data platform architecture diagram illustrating an exemplary embodiment.
  • Figure 2 is a flow chart of a service processing method according to an exemplary embodiment.
  • Figure 3 is another data platform architecture diagram illustrating an exemplary embodiment.
  • Figure 4 is another data platform architecture diagram illustrating an exemplary embodiment.
  • Figure 5 is a flow chart of another service processing method according to an exemplary embodiment.
  • FIG. 6 is a schematic diagram of an operation interface according to an exemplary embodiment.
  • FIG. 7 is a flow chart of another service processing method according to an exemplary embodiment.
  • Figure 8 is a schematic diagram of service processing in a two-level cascading scenario according to an exemplary embodiment.
  • Figure 9 is a schematic diagram of service processing in a multi-level cascading scenario according to an exemplary embodiment.
  • FIG. 10 is a hardware structure diagram of an electronic device in which a service processing device is located, according to an exemplary embodiment.
  • Figure 11 is a block diagram of a service processing device according to an exemplary embodiment.
  • FIG. 12 is a schematic structural diagram of another service processing device according to an exemplary embodiment.
  • Figure 13 is a schematic structural diagram of another service processing device according to an exemplary embodiment.
  • the steps of the corresponding method are not necessarily performed in the order shown and described in this specification.
  • methods may include more or fewer steps than described in this specification.
  • a single step described in this specification may be broken down into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. describe.
  • multi-level data platforms can be shared through various services.
  • the various types of information may include data resources, compiled directories, etc.
  • catalogs can be shared among data platforms such as organizations, provinces, cities, and counties through catalog sharing services.
  • multi-level data platforms may also require data aggregation services.
  • the lower-level platform can aggregate various types of data and report the aggregated data to the upper-level platform, or the upper-level platform can obtain it from the lower-level platform.
  • the upper-level data platform and the lower-level data platform need to separately negotiate the sharing method for each information sharing service, such as implementing directory sharing services. It is through offline methods, such as sending by email and file transfer.
  • the upper-level data platform needs to package the data resources and put them on the shared server, and then the lower-level data platform obtains the data resources through the shared server.
  • there are still problems of data isolation and communication isolation between data platforms at different levels For example, data platforms at different levels may use different data standards when building them, resulting in the database in the upper-level platform being unable to identify the database in the lower-level platform.
  • embodiments of the present application provide a service processing method that can implement various services across multi-level platforms, such as sharing services, query services, data aggregation services, etc.
  • Figure 1 is an architecture diagram of a multi-level data platform illustrating an exemplary embodiment.
  • the multi-level data platform may include a provincial data platform directly connected to the provincial data platform.
  • the upper-level data platform may need to synchronize directories, data or provide other services to the lower-level data platform.
  • the upper-level data platform may need to synchronize directories, data or provide other services to the lower-level data platform.
  • the civil data platform needs to synchronize data with the municipal data platform
  • the county-level data platform needs to query data information through the municipal data platform, etc.
  • a traditional data platform When a traditional data platform synchronizes data, it usually requires the upper-level data platform to package the data into files and place them in the upper-level file synchronization server. The lower-level data platform then obtains the files through the file synchronization server. Moreover, this method can only synchronize data to specific lower-level data platforms, which is not flexible enough.
  • the upper-level data platform provides various services to the lower-level data platform. When the service status of the upper-level data platform changes, the lower level needs to be notified step by step, and the service processing process is relatively complicated.
  • the lower-level data platform can directly call the service provided by the upper-level data platform based on the service identifier.
  • cascade modules are deployed in data platforms at all levels, and the cascade modules are used for data interaction between data platforms at different levels.
  • the data platform at this level can receive target task requests, which can be service invocation requests, data aggregation requests, etc.
  • the target task request is a service invocation request from a lower-level data platform to a target service registered by the user on the current-level data platform
  • the service invocation request includes the service identifier of the target service and the connection with the target service.
  • Service call parameters related to the target service The data platform at this level can respond to the service call request by querying the service identifier of the service registered on the data platform at this level and the service call of the service maintained in the cascade module.
  • Correspondence of interfaces determine the service invocation interface corresponding to the service identifier of the target service; submit the service invocation parameters to the queried service invocation interface to initiate the lower-level data platform to target the target service cascading calls.
  • any one-level data platform in the multi-level data platform can maintain the relationship between the service identifier of the service registered on the data platform and the service invocation interface of the service through the cascade module.
  • the corresponding relationship and when the subordinate data platform needs to call the service registered by the superior data platform, it can directly initiate a cascade call for the service to the superior data platform, and the superior data platform will maintain the above-mentioned service identifier and the above-mentioned
  • the corresponding relationship between the service call interface of the service is determined to determine the service call interface corresponding to the service, and then the relevant service call parameters are submitted to the queried service call interface to complete the cascade call for the service.
  • the correspondence between the service identifiers and service call interfaces of services registered by the superior data platform will be maintained autonomously by the superior data platform through the cascading module.
  • the service call interfaces of these services will no longer be exposed to the subordinate data platform, thus Realize that the lower-level data platform can make one-way calls to the services provided by the upper-level data platform; for the lower-level data platform, it only needs to directly initiate cascade calls for the service based on the service identifier; and when the upper-level data platform
  • the superior data platform does not need to notify the subordinate data platform of the changed correspondence.
  • Figure 2 is a flow chart of a service cascading invocation method illustrating an exemplary embodiment.
  • the above method is applied to any level of data platform in the multi-level data platform shown in Figure 1; in this specification, the data platform maintains the corresponding relationship between the service identifier of the service registered on the data platform and the service call interface of the service through the cascade module, where the service identifier can be information such as service type and service version.
  • the service type can be directory sharing service
  • the service version is v1.1
  • service refers to the data-related services that each level of data platform can provide, such as directory sharing service, interface resource sharing service, data Resource sharing services, data aggregation services, etc.
  • Directory sharing service refers to a service that any level of data platform can publish the directory compiled by this platform to this data platform, and then call it by other data platforms.
  • the catalog may include a catalog compiled based on data resources, a catalog compiled based on various information sharing services, and so on.
  • the lower-level data platform can obtain these directories through the service call interface provided by the upper-level data platform and synchronize the directories.
  • Department A of the provincial data platform currently has 500 data tables that can be shared with lower-level data platforms.
  • Department A can compile these 500 data tables into a data directory through the directory service provided by the provincial data platform and publish them to the provincial data platform.
  • Data platform, Department B of the first municipal data platform can obtain this data directory through the service call interface provided by the provincial data platform, and further obtain the required data tables based on the data directory.
  • the interface resource sharing service means that any level of data platform can publish the interface resources provided by this platform to this platform.
  • Interface resources refer to the application program interfaces that the data platform can provide to the outside world, such as data query interfaces. , data table update interface, etc.
  • the lower-level data platform can obtain these interface resources through the service call interface provided by the upper-level data platform, and can directly use these interface resources in the application program to perform query actions or update actions.
  • Department A of the provincial data platform can publish the externally provided data table query interface to the provincial data platform, and Department B of the first municipal data platform can obtain this data table through the service call interface provided by the provincial data platform.
  • Query interface and can perform corresponding query actions based on this data table query interface.
  • the data resource sharing service means that any level of data platform can publish the interface resources provided by this platform to this platform, where data resources can refer to data tables, data files, file compression packages, etc.
  • the subordinate data platform can obtain these data resources through the service call interface provided by the superior data platform and synchronize the data resources.
  • Department A of the provincial data platform currently has 500 data tables that can be shared with lower-level data platforms.
  • Department B of the first municipal data platform can directly obtain 500 data tables through the service call interface provided by the provincial data platform. , you can also use the above directory sharing service to first obtain the data directory of 500 data tables, and then obtain the required data tables based on the data directory.
  • data aggregation services usually refer to data reporting and other services between upper and lower data platforms.
  • the upper-level data platform collects and summarizes data from the lower-level data platform.
  • Application examples of the service processing methods provided in this manual in specific scenarios that require data aggregation services will be described in detail later.
  • the multi-level data platform includes at least one level of central data platform and at least one level of branch data platform; wherein the central data platform is cascaded with lower-level data platforms; and the branch data platform is not cascaded with lower-level data platforms.
  • Data platform; the data platform at this level is the central data platform at this level. It should be noted that the central data platform at this level can be cascaded with the lower-level branch data platform and/or the lower-level central data platform.
  • the central data platform can be used as a service cascading unit to cascade with lower-level data platforms to form a tree-shaped cascade structure, and the sharing of various services can be completed through the central data platform;
  • a flexible and adjustable cascade structure is constructed. That is, according to the needs, when the cascade relationship with the subordinate data platform changes, the cascade relationship in the central data platform can be adjusted quickly and conveniently.
  • Figure 3 is an architecture diagram of another data platform illustrating an exemplary embodiment.
  • both the provincial data platform and the first municipal data platform are cascaded with lower-level data. platform, so the provincial data platform and the first municipal data platform are the central data platforms.
  • the second city-level platform, the first county-level data platform and the second county-level data platform are not cascaded to the lower-level data platforms, so the second city-level platform, the first county-level data platform and the second county-level data platform For the branch data platform.
  • Cascading modules are deployed in each data platform.
  • the cascading module of the central data platform includes a platform management module for managing the subordinate data platforms cascaded with it.
  • the central data platform at this level can obtain a platform cascading request for registering a lower-level data platform cascaded with the central data platform at this level on the central data platform at this level; the platform cascading request includes The identification information of the subordinate data platform to be registered; among them, users of the subordinate data platform can actively initiate a platform cascade request to the central data platform of the same level, or the newly deployed subordinate data platform can automatically initiate a request for the current level.
  • the identification information of the data platform may specifically be the name of the subordinate data platform, the IP address of the subordinate data platform, port address and other information.
  • the central data platform of the current level can call the above-mentioned platform management module to generate the identification information of the central data platform of the current level and the information of the lower-level data platform. Identify the cascade relationship between information, and maintain the cascade relationship in the platform management module.
  • the above cascade relationship is used to describe the logical relationship between the central data platform at this level and the lower-level data platform. For example, it can be a tree-like data structure, and the lower-level data platform can be used as a child of the central data platform at this level. Tree.
  • the central data platform at this level generates cascade configuration information for the lower-level data platform that is cascaded with the central data platform, and sends the cascade configuration information to the lower-level data platform to use the lower-level data platform.
  • the subordinate data platform completes the cascade configuration with the central data platform based on the cascade configuration information.
  • the cascade configuration information may specifically be a data platform account and corresponding key information or other configuration information used for authentication, which is stored in the platform management module.
  • the subordinate data platform completes the cascade configuration with the central data platform based on the data platform account and corresponding key information provided by the central data platform, as well as the IP address, port address and other information of the central data platform.
  • Figure 4 is another data platform architecture diagram illustrating an exemplary embodiment. Taking the data platform architecture diagram shown in Figure 4 as an example, when the third county-level data platform needs to be cascaded to When the first city-level data platform is used, the third county-level data platform can initiate a platform cascade request to the first city-level data platform.
  • the first city-level data platform calls the platform management module to generate the first city-level data platform and the third city-level data platform.
  • the cascade relationship between county-level data platforms is maintained in the platform management module.
  • a cascade configuration is generated for the third county-level data platform to cascade with the first city-level data platform. information, so that the third county-level data platform can complete the cascade configuration with the first city-level data platform.
  • the central data platform is equipped with a platform management module for managing the subordinate data platforms cascaded with it.
  • the platform management module can no longer be deployed. Save the cost of data platform deployment.
  • Step 202 receive a target task request; the target task request may be issued by the current-level data platform, or may be received from a lower-level data platform.
  • the target task request is a service invocation request from a lower-level data platform for a target service registered on the data platform at this level; wherein, the service invocation request includes the service identifier of the target service and the information related to the target service. Describe the service call parameters related to the target service.
  • the target service refers to the service that the lower-level data platform needs to call; for example, the lower-level data platform needs to obtain a certain data resource provided by the data platform at the same level, and the lower-level data platform needs to use the data provided by the data platform at the same level. A certain interface, etc.
  • the lower-level data platform can obtain several services registered on the current-level data platform in advance and initiate a service call request to the current-level data platform.
  • the service invocation request may include a service identifier of the target service and service invocation parameters related to the target service.
  • the first municipal data platform needs to obtain 10 data tables from the provincial data platform, and the first municipal data platform can initiate data resource sharing services to the provincial data platform
  • the call request may include the name, version number and other information of the data resource sharing service
  • the related service call parameters may include the type of data table and the number of data tables.
  • the cascading module of the data platform at any level may include a service management module for managing services registered on the data platform.
  • the data platform at this level may respond to obtaining a service registration request for registering a service on the data platform at this level, and the service management module registers a service on the data platform at this level based on the service registration request. and maintain the corresponding relationship between the registered service identifier of the service and the service invocation interface of the service in the service management module.
  • the above-mentioned service registration request can be initiated by the user.
  • users of the current-level data platform can synchronize certain data to the lower-level data platform and can actively initiate a service registration request; the application can also automatically initiate a service registration request.
  • the application can automatically initiate a service registration request.
  • a user in a certain department of the provincial data platform can synchronize 500 data tables to a lower-level data platform. Therefore, the user can register a data resource sharing service and provide a corresponding service calling interface.
  • the provincial data platform maintains the corresponding relationship between the service identifier of the data resource sharing service and the service call interface in the service management module of the provincial data platform.
  • different calling permissions for registered services can also be set for different data platforms.
  • the data platform at this level can call the service management module, and the service management module registers a service on the data platform based on the service registration request. Since the platform management module maintains the same level as the data platform at this level, Therefore, the service management module can interact with the platform management module to query the cascading relationship maintained by the platform management module with the data platform of this level. All subordinate data platforms.
  • the data platform set with the calling authority of the service maintains the corresponding relationship between the data platform set and the service in the service management module to complete the service registration for the service on the data platform at the same level.
  • the user when registering a service, the user can actively select one or more subordinate data platforms from all subordinate data platforms that have a cascading relationship with the data platform at this level to set the calling permission for the registered service, or the user can When registering a service, the application in the data platform at this level automatically selects the lower-level data platform to set the calling permissions.
  • the above-mentioned service management module maintains different data platform collections for different registered services, thereby setting different calling permissions for different data platforms.
  • a user in a certain department of the provincial data platform can synchronize 500 data tables to a lower-level data platform. Therefore, the user can register a data resource sharing service and provide a corresponding service calling interface.
  • the provincial data platform cascades two municipal data platforms. If the user only wants to synchronize the data table to the first municipal data platform, the user can set the first municipal data platform to have the data resource sharing function. The calling permission of the service.
  • the provincial data platform can obtain the first municipal platform, maintain the corresponding relationship between the data resource sharing service and the first municipal platform in the service management module, and complete the service registration for data services on the provincial data platform.
  • the user can also choose to set the first municipal data platform and the second municipal data platform to have the calling authority for the data resource sharing service.
  • the national data platform can obtain the data platform collection composed of the first municipal level platform and the second municipal level platform, and maintain the corresponding relationship between the data resource sharing service and the data platform collection in the service management module to complete the provincial data Service registration for data services on the platform.
  • Step 204 When the target task request is a service invocation request, in response to the service invocation request, query the corresponding relationship between the service identifier of the service and the service invocation interface of the service, and determine the corresponding relationship with the target service.
  • the service calling interface corresponding to the service ID.
  • the above-mentioned data platform at this level maintains the corresponding relationship between the service identifier of the service registered on the data platform at this level and the service call interface of the service, it is possible to query the service identifier and the service call of the service.
  • the corresponding relationship between the interfaces is based on the service identifier of the target service, and the service calling interface corresponding to the service identifier of the target service is determined.
  • the first municipal data platform needs to obtain 10 data tables from the provincial data platform, and the first municipal data platform can initiate data resource sharing services to the provincial data platform Call request.
  • the provincial data platform queries the correspondence between the service identifier and the service call interface of the service, and determines the call interface of the data resource sharing service.
  • the cascading module of any level of data platform may also include a service proxy module for initiating service calls for services registered on the data platform, and the lower-level data platform may send requests to the data platform of the same level.
  • the mounted service agent module initiates a call request, and the data platform at this level interacts with the service management module by calling the service agent module to query the correspondence between the service identifier maintained by the service management module and the service call interface of the service. Determine the service invocation interface corresponding to the service identifier of the target service.
  • the first municipal data platform needs to obtain 10 data tables from the provincial data platform.
  • the first municipal data platform can request the service agent module carried by the provincial data platform.
  • the service agent module installed on the provincial data platform interacts with the service management module, and queries the data maintained by the service management module according to the name, version number and other information of the data resource sharing service contained in the call request. The corresponding relationship determines the calling interface of the data resource sharing service.
  • the service agent module installed on the current level data platform can also interact with the service management module to determine whether the subordinate data platform has service invocation authority for the target service. Specifically, in response to the service invocation request, the service agent module is called, and the service agent module interacts with the service management module to call the service agent module to query all the data maintained by the service management module. The corresponding relationship between the above-mentioned services and the data platform set is determined to determine whether the subordinate data platform has the calling authority for the target service; if so, further interact with the service management module to query the data maintained by the service management module. The corresponding relationship between the service identifier and the service invocation interface of the service determines the service invocation interface corresponding to the service identifier of the target service.
  • users in a certain department of the provincial data platform can synchronize 500 data tables to lower-level data platforms, and set the first municipal data platform to have the calling authority for this data resource sharing service.
  • the first municipal data platform needs to obtain 10 data tables from the provincial data platform
  • the first municipal data platform can initiate a data resource sharing service call request to the service agent module installed on the provincial data platform.
  • the service agent module can interact with the service management module, query the correspondence between the data resource sharing service maintained by the service management module and the data platform collection, and determine that the first municipal data platform has the calling authority for the data resource sharing service. Therefore, you can continue to query the correspondence between the service identifier maintained by the service management module and the service calling interface of the service, and determine the calling interface of the data resource sharing service.
  • Step 206 Submit the service invocation parameters to the queried service invocation interface to initiate a cascade invocation of the target service by the subordinate data platform.
  • the data platform at this level can directly submit the service invocation parameters to the service invocation interface corresponding to the target service to initiate the cascade call of the target service by the subordinate data platform.
  • the first municipal data platform needs to obtain 10 data tables from the provincial data platform, and the first municipal data platform can initiate data resource sharing services to the provincial data platform
  • the provincial data platform queries the service calling interface of the corresponding data service, and submits the required data table type, number of data tables, etc. as service calling parameters to the queried data resource sharing service calling interface.
  • the data platform at any level can also be equipped with a service agent module for initiating service calls for services registered on the data platform, and the lower-level data platform can initiate calls to the service agent module installed on the data platform at the same level.
  • the service proxy module submits the service invocation parameter to the queried service invocation interface, so as to initiate the cascade call of the lower-level data platform for the target service.
  • the first municipal data platform needs to obtain 10 data tables from the provincial data platform.
  • the first municipal data platform can request the service agent module carried by the provincial data platform.
  • the service agent module After initiating a data resource sharing service call request, the service agent module queries the service management module to obtain the service call interface corresponding to the data service, and submits the required data table type, number of data tables, etc. as service call parameters to the query.
  • the calling interface of the data resource sharing service is accessed from the state of the data resource sharing service.
  • the service agent module obtains the call result of the cascade call of the target service by the lower-level data platform, and returns the obtained call result to the lower-level data platform.
  • the first municipal data platform needs to obtain 10 data tables from the provincial data platform. It can request the service agent installed on the provincial data platform from the first municipal data platform. After the module initiates a data resource sharing service call request, the service agent module submits the service call parameters to the queried data resource sharing service call interface, obtains these 10 data tables, and returns them to the first municipal data platform.
  • any one-level data platform in the multi-level data platform can maintain the correspondence between the service identifier of the service registered on the data platform and the service calling interface of the service, and the lower-level data platform needs to call
  • a service is registered on the upper-level data platform, it can directly initiate a cascade call for the service to the upper-level data platform.
  • the upper-level data platform determines the service correspondence based on the correspondence between the above-mentioned service identifier maintained and the service call interface of the service. call interface, and then submit the relevant service call parameters to the queried service call interface to complete the cascade call for the service.
  • the correspondence between the service identifiers and service call interfaces of services registered by the superior data platform will be maintained autonomously by the superior data platform.
  • the service call interfaces of these services will no longer be exposed to the lower-level data platform, thereby realizing the lower-level data
  • the platform makes one-way calls to the services provided by the upper-level data platform; for the lower-level data platform, it only needs to directly initiate cascade calls for the service based on the service identifier; and when the upper-level data platform maintains
  • the upper-level data platform does not need to notify the lower-level data platform of the changed corresponding relationship. Therefore, through one-way calling, there is no need to negotiate a sharing method for each service separately, thereby simplifying the process of cascading calls from lower-level data platforms to services on upper-level data platforms.
  • the data platform described in the embodiments of this application can be implemented as a single computer, a computer cluster composed of multiple computers, a single server, a server cluster composed of multiple servers, a site, etc.
  • the cascade module can be set up in the data platform as part of the data platform or outside the data platform, and can be implemented as software, hardware, firmware, or any combination thereof.
  • the cascade module may be in the form of a computer program product including computer instructions.
  • the functions of the above cascade module and each sub-module it contains for example, platform management module, service management module, service agent module, etc.
  • the cascade module (including each sub-module) is implemented by hardware, it may be a computer chip, a microprocessor, a DSP, a computer, a server, or a combination of one or more.
  • the service processing method of this application is mainly described by taking the target task request as a service invocation request as an example.
  • the service processing method of this application will be further described by taking the target task request as a data aggregation request as an example.
  • the target task request is a creation request for a data aggregation task.
  • This method can be applied to the upper-level data platform in a multi-level data platform, so The upper-level data platform corresponds to at least one lower-level data platform; the method may include the following steps:
  • Step 510 In response to the creation request of the data aggregation task, create a data aggregation task associated with the target lower-level data platform according to the target lower-level data platform and data standard specified in the creation request; wherein, in the data aggregation task Includes said data standards.
  • the cascade module maintains communication parameters of each lower-level data platform, the cascade module establishes a communication connection with the lower-level data platform through the communication parameters, and transmits data through the communication connection .
  • the communication between the cascade module and the lower-level data platform can be realized through a dedicated network to avoid the impact of the public network on platform security.
  • a data aggregation task associated with each target lower-level data platform may be created based on one or more target lower-level data platforms specified in the creation request, and the The data aggregation task includes the data standards specified in the creation request.
  • the data standard may include multiple information items for defining data; the information items include information item name (for example, Chinese name and/or English name), data type, data length ,describe.
  • the data standard is used to convert data of other data standards in each lower-level platform into data to be aggregated according to the data standard.
  • data standards can be defined in the form of information items.
  • the information items may include the content shown in Table 1 below:
  • the information item may include information such as the name of the information item (for example, Chinese name and/or English name), data type, whether it is a primary key, data length, description, etc.
  • the name of the information item for example, Chinese name and/or English name
  • data type whether it is a primary key
  • data length whether it is a primary key
  • description whether it is a primary key
  • lower-level platforms can prepare in advance data to be aggregated that meets the data standards.
  • users of the upper-level data platform can log in to this data platform (used as a data aggregation platform) and create the first data aggregation task in the operation interface of the data aggregation service to complete the designation of the lower-level data platform and the definition of data standards. definition.
  • Users of the upper-level data platform can edit in the data aggregation operation interface to enter relevant content.
  • the displayed editing content includes the "basic information" of the first data aggregation task, the "information items” of the data standard, and the subordinate data platform (not shown in Figure 6) , configuration information of the destination database, scheduling configuration, etc.
  • the specific filling fields and instructions are shown in Figure 6, and will not be described one by one here.
  • shortcut options can be displayed in the operation interface, and users of the upper-level data platform can trigger the shortcut options to determine the corresponding editing content. Users can select or fill in content through drop-down methods. The superior data platform automatically generates corresponding editing content after the user triggers the shortcut option.
  • the option content may be pre-configured by the developer.
  • developers can register accounts on the data aggregation platform for platforms that require data aggregation (of course, users of each platform can also register themselves); for data platforms with upper- and lower-level correspondences, upper-level data platforms and lower-level data can be established Relationships between platforms.
  • upper-level data platforms and lower-level data can be established Relationships between platforms.
  • the data aggregation platform supports the reuse of data standards; users of the upper-level data platform can directly load the relevant information items corresponding to the historical data standards after entering the operation interface and clicking the shortcut option of reusing historical data standards. content. If some information items need to be modified, users can do so at any time.
  • the upper-level platform (as a data aggregation platform)
  • users of the upper-level data platform only need to select shortcut options in the operation interface to complete the configuration, including defining data standards, specifying lower-level data platforms, configuring destination databases, etc.
  • the data aggregation is completely automatically performed by the data aggregation platform, which greatly improves the efficiency of data aggregation.
  • Step 520 Send the data aggregation task to the target lower-level data platform through the cascading module.
  • the upper-level data platform can actively distribute each data aggregation task to the corresponding target lower-level data platform through the cascading module; in an exemplary embodiment, the upper-level data platform The platform can issue the data aggregation task when the target lower-level data platform actively initiates a scheduled polling request through the cascading module.
  • step 520 may include: in response to a scheduled polling request initiated by the target lower-level data platform to the cascade module, query whether there is a data aggregation task associated with the target lower-level data platform; if there is , through the cascade module, the queried data aggregation task is sent to the target lower-level data platform.
  • the lower-level data platform can regularly obtain data aggregation tasks from the cascade module of the upper-level system during operation.
  • Step 530 Upon receiving the preset notification sent by the target lower-level data platform to the cascading module, use the cascading module to convert the source database of the target lower-level data platform into the The data to be aggregated according to the data standard is written into the destination database of the upper-level data platform.
  • the purpose of writing the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform to the upper-level data platform through the cascading module includes: using the cascade module to write the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform into the preset front-end database (that is, the front-end database) , and update the task status of the data aggregation task to complete; when the task status of the data aggregation tasks associated with all target lower-level data platforms is completed, the cascade module stores the data stored in the front-end library through the cascade module.
  • the data to be aggregated that has been converted into the data standard provided by all target lower-level data platforms is written into the destination database of the upper-level data platform.
  • the front-end database is configured in the data aggregation management subsystem of the data platform (the top-level data platform may not be configured), and is used to store the upstream data of this platform that is obtained by the superior data platform.
  • a front-end library can be set up to store the data to be aggregated provided by the lower-level system.
  • the upper-level data platform can first write the data to be aggregated in the source database of the lower-level data platform into the front-end library through the cascading module, and then The data to be aggregated in the front-end library is written to the destination database of the upper-level data platform.
  • data security risks caused by the source database in the lower-level data platform being exposed to the outside are avoided; and since there is no need to open a network policy from the source database to the upper-level data platform, implementation difficulty can be reduced.
  • the cascading module writes the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform into a preset front-end library, It includes: starting a data exchange engine through the cascade module to write the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform into a preset preset based on the data exchange engine.
  • Preparing the database writing the to-be-aggregated data provided by the target lower-level data platform stored in the front-end database and converted into the data standard into the destination database of the upper-level data platform through the cascading module including: starting the data exchange engine through the cascade module, and converting the data provided by the target lower-level data platform stored in the front-end library into the data standard to be aggregated based on the data exchange engine.
  • the data is written into the destination database of the upper-level data platform.
  • Step 710 Obtain the data aggregation task issued by the upper-level data platform through the cascade module; wherein, the data aggregation task Includes the data standards specified by the superior data platform.
  • the cascade module maintains the communication parameters of the lower-level data platform.
  • the cascading module establishes a communication connection with the lower-level data platform through the communication parameters and transmits data through the communication connection.
  • the communication between the cascade module and the lower-level data platform can be realized through a dedicated network to avoid the impact of the public network on platform security.
  • the upper-level data platform can send the data aggregation tasks to the lower-level data platforms through the cascade module.
  • the lower-level data platform can obtain the data aggregation task issued by the upper-level data platform through the cascade module; wherein the data aggregation task can include the data standards specified by the upper-level data platform.
  • the data standard may include multiple information items used to define data; the information items include information item names (for example, Chinese and English names), data types, data lengths, and descriptions;
  • the above-mentioned data standards are used to convert data of other data standards in each lower-level data platform into data to be aggregated according to the above-mentioned data standards.
  • definition of data standards reference may be made to the foregoing embodiments and will not be described again here.
  • step 710 may include: initiating a scheduled polling request to the cascade module of the upper-level data platform to query whether there is a data aggregation task associated with the lower-level data platform in the upper-level data platform; receiving all The upper-level data platform issues the queried data aggregation task through the cascade module.
  • the lower-level data platform can actively obtain data aggregation tasks from the upper-level platform through the lower-level cascading module at regular intervals during operation.
  • Step 720 In response to the data aggregation task, convert the data in the source database of the lower-level data platform into data to be aggregated that meets the data standard.
  • the lower-level data platform can convert the data in the local source database that does not meet the data standard specified by the upper-level data platform into the data to be aggregated according to the data standard.
  • the data in the source database of the lower-level data platform is converted into data to be aggregated that conforms to the data standard.
  • Data may include: creating aggregation codes that correspond to each subordinate department and a data aggregation sub-task containing the data standard, and distributing the data aggregation sub-tasks and aggregation codes to each subordinate department; so that each department Based on the data standard, the department converts the data in the corresponding source database into data to be aggregated that meets the data standard, and binds the corresponding aggregation code to the data to be aggregated.
  • each department can convert the data in the local database into data to be aggregated that conforms to the data standard based on the data standard in the assigned data aggregation subtask.
  • the data aggregation platform turns on the "aggregation coding" function by default, so that the aggregation coding corresponding to each department can be automatically generated when issuing data aggregation tasks.
  • the aggregation code includes a unique identification composed of a platform identification of the subordinate data platform and a department identification of a department.
  • aggregation coding (12 bits) UUID of the lower-level data platform (8 bits) + department ID (4 bits).
  • the UUID can be used as the platform identifier
  • the department ID can be used as the department identifier.
  • the "aggregation encoding" function of the data aggregation platform can also be turned off.
  • the platform identifier of the subordinate data platform is "00000001"
  • the department identifier of department 1 is "0001”
  • the department identifier of department 2 is "0002”.
  • the data to be aggregated provided by department 1 can be associated with the aggregation code 00000001-0001
  • the data to be aggregated provided by department 2 can be associated with the aggregation code 00000001-0002; in this way, even if department 1 and department 2 have exactly the same data to be aggregated, Differentiation can be made based on the associated aggregate encoding without causing data conflicts.
  • Step 730 Send a preset notification to the cascading module of the upper-level data platform, so that the upper-level data platform writes the data to be aggregated that has been converted into the data standard from the source database through the cascading module. into the target database of the upper-level data platform.
  • the lower-level data platform After the lower-level data platform converts the data in the local source database into data to be aggregated that meets the data standards, it can send a preset notification to the cascade module of the upper-level data platform to notify the upper-level data platform that the lower-level data platform is ready. Perform data aggregation.
  • the cascading mode of the cascading module can be divided into two-level cascading and multi-level cascading according to the different levels of the data platform in actual needs.
  • the two-level cascade may refer to the cascade of the upper-level data platform and the lower-level data platform.
  • the cascade of a data platform with only two levels is called a two-level cascade.
  • Multi-level cascades not only have two levels, such as the three-level cascade of a three-tier data platform, that is, the upper-level data platform is cascaded with the lower-level data platform, and the lower-level data platform is also cascaded with the lower-level data platform of the lower-level data platform.
  • the cascading module can be deployed in the upper-level data platform to provide data exchange services between the upper-level data platform and the lower-level data platform.
  • Step 1 The upper-level data platform A can create a data aggregation task associated with the lower-level data platform B, and synchronize the data aggregation task to the cascade module.
  • Step 2 The upper-level data platform A sends the data aggregation task to the lower-level data platform B through the cascading module.
  • the subordinate data platform B can convert the data in its corresponding database into the data to be aggregated according to the data standard in the data aggregation task.
  • Step 3 The cascade module starts the data exchange engine through the lower-level system.
  • the data exchange engine automatically creates the destination table in the front-end library based on the information items of the data standard. If the "aggregation encoding" service is enabled, the aggregation encoding column will be automatically added to the destination table.
  • Step 4-Step 5 The data exchange engine writes the data to be aggregated that has been converted into data standards from the source database of the subordinate data platform B to the destination table of the front-end library.
  • Step 6 The data exchange engine notifies the subordinate data platform B that the transfer from the source database to the front-end library is completed.
  • Step 7 The lower-level data platform B sends a preset notification to the cascade module of the upper-level data platform A; the preset notification can include information such as the front-end library address, the destination table of the front-end library, and whether to enable converged encoding.
  • Step 8 The upper-level data platform A starts the data exchange engine through the cascade module.
  • the data exchange engine is started to prepare to transmit the data to be aggregated in the front-end database to the destination database corresponding to the upper-level data platform A. If convergence encoding is enabled, the data exchange engine will add a convergence encoding column in the destination table of the destination database.
  • Step 9-Step 10 The data exchange engine writes the data to be aggregated that has been converted into data standards stored in the front-end library into the destination database of the upper-level data platform A.
  • the data exchange engine will transfer the data to be aggregated in the source database of the lower-level data platform B to the front-end database at the specified cycle, that is, step 4 in Figure 8 -Step 5, subsequent steps 6-10 are the same and will not be described again here.
  • the data aggregation process in a multi-level cascade scenario is similar to the data aggregation process in a two-level cascade scenario: after the data exchange engine completes transmitting the data to be aggregated from the source database of the lower-level data platform to the front-end database, it notifies the lower-level data The platform data transmission is completed, and the lower-level data platform sends a preset notification to the cascade module of the upper-level data platform.
  • the upper-level data platform starts the data exchange engine through the cascading module to transmit the data from the front-end library of the lower-level data platform to the current-level data platform. in the front-end library.
  • the data exchange engine transmits the data to be aggregated from the source database of data platform C to the front-end library (i.e. steps 6-7 in Figure 9).
  • the data platform C can notify the superior data platform B through the cascading module (i.e. step 9 in Figure 9); then the second-level data platform B starts the data exchange engine through the cascading module to transfer the data to be aggregated from the data platform C.
  • the front-end library is transferred to the front-end library of data platform B (i.e., steps 11-12 in Figure 9); while the second-level data platform B serves as the subordinate platform of data platform A, the data exchange engine will be aggregated after completion.
  • data platform B can notify the superior platform data A through the cascading module (i.e. step 14 in Figure 9); then the first-level data Platform A starts the data exchange engine through the cascading module to transfer the data to be aggregated from the front-end library of data platform B to the destination database of data platform A (ie, step 16-step 17 in Figure 9).
  • the embodiments of this specification realize data aggregation between platforms at different levels by adding a new cascade module.
  • the upper-level data platform can issue data aggregation tasks containing data standards to each lower-level data platform through the cascading module, and after receiving the lower-level data platform to the cascade
  • the cascading module writes the data to be aggregated that has been converted into the data standard from the source database of the lower-level data platform into the destination database of the upper-level data platform.
  • the lower-level data platform provides the function of customizing data standards for the upper-level data platform; through the data standards defined by the upper-level data platform, the lower-level data platform can provide data to be aggregated that conforms to the data standard; because each data to be aggregated before data aggregation All comply with the same data standards, the data quality is high and no additional data conversion is required, thus improving the efficiency of data aggregation.
  • the data to be aggregated in the source database of the lower-level data platform is first written into the front-end database, and then the data to be aggregated in the front-end database is written into the destination database of the upper-level data platform.
  • data security risks caused by the source database in the lower-level platform being exposed to the outside are avoided; and since there is no need to open a network policy from the source database to the upper-level platform, implementation difficulty can be reduced.
  • FIG. 10 is a hardware structure diagram of an electronic device in which a service processing device is located, according to an exemplary embodiment.
  • the device includes a processor 1002, an internal bus 1004, a network interface 1006, a memory 1008, and a non-volatile memory 1010.
  • the processor 1002 reads the corresponding computer program from the non-volatile memory 1010 into the memory 1008 and then runs it.
  • the execution subject of the following processing flow is not limited to each A logic unit can also be a hardware or logic device.
  • FIG. 11 is a block diagram of a service processing device according to an exemplary embodiment.
  • the service processing device can be applied to the electronic device shown in Figure 10 to implement the technical solution of this specification.
  • the above-mentioned service processing device may include: a request receiving unit 1102, used to receive a target task request; a relationship query unit 1104, used to target the target task request to a lower-level data platform that has been registered on the current-level data platform.
  • a service invocation request for a target service wherein the service invocation request includes a service identifier of the target service and service invocation parameters related to the target service
  • query the cascade The corresponding relationship between the service identification of the service registered on the data platform at this level and the service invocation interface of the service maintained in the module determines the service invocation interface corresponding to the service identification of the target service; cascade calling unit 1106 , used to submit the service invocation parameters to the queried service invocation interface, so as to initiate the cascade invocation of the target service by the subordinate data platform.
  • the multi-level data platform includes at least one level of central data platform and at least one level of branch data platform; wherein the central data platform is cascaded with lower-level data platforms; the branch data platform is not cascaded The data platform at the lower level; the data platform at this level is the central data platform at this level.
  • the central data platform at the same level is cascaded with the branch data platform at the lower level and/or the central data platform at the lower level.
  • the cascading module of the central data platform includes: a platform management module for managing subordinate data platforms cascaded with the central data platform; the device further includes: platform registration Unit, used to obtain a platform cascading request for registering a lower-level data platform cascaded with the central data platform of the same level on the central data platform of the same level; the platform cascading request includes the to-be-registered The identification information of the subordinate data platform; in response to the platform cascade request, the platform management module is called to generate the identification information of the central data platform at this level and the identification information of the subordinate data platform to be registered.
  • the cascade configuration information is sent to the subordinate data platform to be registered, so that the subordinate data platform to be registered completes the communication with the center of the same level based on the cascade configuration information. Cascading configuration between data platforms.
  • the cascading module of the data platform includes: a service management module for managing registered services on the data platform, and the device further includes: a service registration unit, configured to respond to obtaining A service registration request for registering a service on the data platform at this level calls the service management module, and the service management module registers a service on the data platform at this level based on the service registration request, and The corresponding relationship between the registered service identifier of the service and the service calling interface of the service is maintained in the service management module.
  • the cascade calling unit is specifically used to call the service management module.
  • the service management module registers services on the data platform of the same level based on the service registration request, and queries the platform.
  • all lower-level data platforms that have a cascading relationship with the central data platform at this level; in response to obtaining the lower-level data platforms that have a cascading relationship with the data platform at this level.
  • the data platform there is a collection of data platforms with the calling authority for the service on the data platform at this level, and the corresponding relationship between the service and the collection of data platforms is maintained in the service management module to complete the Service registration for the service on the data platform at the same level.
  • the cascade module of the data platform includes: a service proxy module for initiating service calls for services registered on the data platform; the cascade call unit is specifically used to respond to The service invocation request calls the service proxy module to query the corresponding relationship between the service identification of the service maintained by the service management module and the service invocation interface of the service, and determines the service corresponding to the service identification of the target service. Calling the interface; the service proxy module submits the service calling parameters to the queried service calling interface to initiate cascade calls by the subordinate data platform for the target service.
  • the relationship query unit is specifically configured to, in response to the service invocation request, call the service agent module to query the corresponding relationship between the service and the set of data platforms maintained by the service management module, Determine whether the subordinate data platform has the calling authority for the target service; if so, further query the corresponding relationship between the service identification of the service maintained by the service management module and the service calling interface of the service, and determine the corresponding relationship with the service calling interface.
  • the service calling interface corresponding to the service identifier of the target service.
  • the device further includes a result return unit: the service agent module obtains the call result of the lower-level data platform for the cascade call of the target service, and returns the obtained call result to the target service. Describe the lower-level data platform.
  • the data service includes at least one of the following: directory sharing service, interface resource sharing service, and data resource sharing service.
  • Figure 12 is a module diagram of a service processing device 1200 provided by an embodiment of this specification.
  • the device corresponds to the embodiment shown in Figure 5 and is applied to a higher-level data platform in a multi-level data platform.
  • the upper-level data platform Corresponding to at least one lower-level data platform, a cascading module is deployed in the upper-level data platform, and the cascading module is used for data interaction between data platforms at different levels;
  • the device includes: a creation unit 1210, in response to data The creation request of the aggregation task, according to the target lower-level data platform and data standard specified in the creation request, creates a data aggregation task associated with the target lower-level data platform; wherein the data aggregation task includes the data standard;
  • the sending unit 1220 sends the data aggregation task to the target lower-level data platform through the cascade module; the aggregation unit 1230 receives the preset sent by the target lower-level data platform to the cascade module.
  • the cascading module maintains communication parameters of the at least one lower-level data platform.
  • the cascading module establishes a communication connection with the corresponding lower-level data platform through the communication parameters, and uses the communication connection to transfer data.
  • the issuing unit 1220 further includes: a query subunit, in response to a scheduled polling request initiated by the target lower-level data platform to the cascade module, to query whether there is an association with the target lower-level data platform.
  • the data standard includes information items used to define data; the information items include at least one of information item name, data type, data length, and description; the data standard is used to combine data in lower-level data platforms Data of other data standards are converted into data of the data standard to be aggregated.
  • the aggregation unit 1230 further includes: a first writing subunit, which writes the data to be aggregated that has been converted into the data standard from the source database of the target lower-level data platform through the cascade module. Enter the preset pre-library and update the task status of the data aggregation task to complete; the second writing sub-unit, when the task status of the data aggregation tasks associated with all target lower-level data platforms is completed, Through the cascading module, the data to be aggregated and converted into the data standard provided by all target lower-level data platforms stored in the front-end library are written into the destination database of the upper-level data platform.
  • the first writing subunit further includes starting a data exchange engine through the cascade module to convert the source database of the target lower-level data platform into the The data to be aggregated according to the data standard is written to the preset library; the second writing subunit further includes starting the data exchange engine through the cascade module, and converting the frontend data to the preset database based on the data exchange engine.
  • the data to be aggregated and converted into the data standard provided by the target lower-level data platform and stored in the database are written into the target database of the upper-level data platform.
  • Figure 13 is a module diagram of a service processing device 1300 provided by an embodiment of this specification.
  • the device corresponds to the embodiment shown in Figure 8 and is applied to a lower-level data platform corresponding to a higher-level data platform in a multi-level data platform.
  • a cascade module is deployed in the upper-level data platform, and the cascade module is used for data interaction between data platforms at different levels;
  • the device includes: an acquisition unit 1310, which acquires the upper-level data platform through the cascade module The data aggregation task issued; wherein the data aggregation task includes the data standard specified by the upper-level data platform; the conversion unit 1320, in response to the data aggregation task, converts the data in the source database of the lower-level data platform Convert into data to be aggregated that meets the data standards; the aggregation unit 1330 sends a preset notification to the cascading module of the upper-level data platform, so that the upper-level data platform obtains data from the source database through the cascading module. Write the data to be aggregated that has been converted into the data standard into the destination database of the upper-level data platform.
  • the cascading module maintains communication parameters of the lower-level data platform, the cascading module establishes a communication connection with the lower-level data platform through the communication parameters, and transmits data through the communication connection. .
  • the acquisition unit 1310 further includes: a query subunit, which initiates a regular polling request to the cascade module of the upper-level data platform to query whether there is a query in the upper-level data platform associated with the lower-level data platform.
  • the conversion unit 1320 further includes: in the case where the subordinate data platform contains one or more different departments, create aggregation coding corresponding to each subordinate department and data containing the data standard. Aggregate subtasks, and distribute the data aggregation subtasks and aggregation codes to various subordinate departments; so that each department can convert the data in the corresponding source database into data to be aggregated that meets the data standards based on the data standards. , and bind the corresponding aggregation code to the data to be aggregated.
  • the aggregation code includes a unique identifier composed of the platform identifier of the subordinate data platform and the department identifier of the department.
  • the data standard includes information items used to define data; the information items include at least one of information item name, English name, data type, data length, and description; the data standard is used to define subordinate Data of other data standards in the data platform are converted into data of the data standard to be aggregated.
  • the device embodiment since it basically corresponds to the method embodiment, please refer to the partial description of the method embodiment for relevant details.
  • the device embodiments described above are only illustrative.
  • the units described as separate components may or may not be physically separated.
  • the components shown as units may or may not be physical units, that is, they may be located in a place, or can be distributed across multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Persons of ordinary skill in the art can understand and implement the method without any creative effort.
  • This specification also provides an embodiment of a computer-readable storage medium.
  • the computer-readable storage medium stores machine-readable instructions. When called and executed by a processor, the machine-readable instructions can implement the service processing method provided by any embodiment in this specification.
  • the computer-readable storage media may specifically include, but are not limited to, any type of disk (including floppy disk, hard disk, optical disk, CD-ROM, and magneto-optical disk), ROM (Read-Only Memory), RAM (Random Access Memory, random access memory), EPROM (Erasable Programmable Read-Only Memory, erasable programmable read-only memory), EEPROM (Electrically Erasable Programmable Read-Only Memory, electrically erasable programmable read-only memory), flash memory , magnetic cards or fiber optic cards. That is, readable storage media includes readable media that can store or transmit information.
  • the cascade system includes a multi-level data platform; the multi-level data platform includes at least one level central data platform and at least one level branch data platform; the central data platform cascades lower-level data platforms; the branch data platform Lower-level data platforms are not cascaded; cascading modules are deployed in each data platform, and the cascading modules are used for data interaction between data platforms at different levels.
  • the cascade system is used to execute the service processing method provided by any embodiment in this specification.
  • a typical implementation device is a computer, which may be in the form of a personal computer, a laptop, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, or a game controller. desktop, tablet, wearable device, or a combination of any of these devices.
  • a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in computer-readable media, random access memory (RAM) and/or non-volatile memory in the form of read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash random access memory
  • Computer-readable media includes both persistent and non-volatile, removable and non-removable media that can be implemented by any method or technology for storage of information.
  • Information may be computer-readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), and read-only memory.
  • PRAM phase change memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • RAM random access memory
  • read-only memory read-only memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory or other memory technology
  • compact disc read-only memory CD-ROM
  • DVD digital versatile disc
  • Magnetic tape cartridges magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium, can be used to store information that can be accessed by computing devices.
  • computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
  • first, second, third, etc. may use the terms first, second, third, etc. to describe various information, the information should not be limited to these terms. These terms are only used to distinguish information of the same type from each other.
  • first information may also be called second information, and similarly, the second information may also be called first information.
  • word “if” as used herein may be interpreted as "when” or “when” or “in response to determining.”

Abstract

本申请提供服务处理方法、装置、级联系统、电子设备及存储介质。所述方法包括：接收目标任务请求；在所述目标任务请求为下级的数据平台针对在本级的数据平台上已注册的目标服务的服务调用请求的情况下，其中，所述服务调用请求包括所述目标服务的服务标识以及与所述目标服务相关的服务调用参数，响应于所述服务调用请求，查询级联模块中维护的在本级的数据平台上已注册的服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。

Description

服务处理方法、装置、级联系统、电子设备及存储介质 技术领域
本申请涉及计算机技术领域，尤其涉及一种服务处理方法、装置、级联系统、电子设备及存储介质。
背景技术
垂直行业中存在具有纵向垂直关系的多级机构。例如，大数据行业存在具有纵向垂直管理关系的部，省，市，县多级机构。其中每级机构可以部署对应的数据平台。近年来，随着互联网垂直行业的不断发展，存在上级平台向下级平台提供各类服务以及汇聚下级平台上报的数据等的需求。在这种场景下，上级平台和下级平台需要对它们之间共享的每项业务，分别协商共享方式，以及建立单独的连接或通道等，导致平台的建设成本高、建设周期长，而且维护复杂。
发明内容
本申请提供一种服务处理方法，应用于多级数据平台中的任一级数据平台；所述数据平台中部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互；所述方法包括：接收目标任务请求；在所述目标任务请求为下级的数据平台针对在本级的数据平台上已注册的目标服务的服务调用请求的情况下，其中，所述服务调用请求包括所述目标服务的服务标识以及与所述目标服务相关的服务调用参数，响应于所述服务调用请求，查询所述级联模块中维护的在本级的数据平台上已注册的服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
可选的，所述多级数据平台包括至少一级中心数据平台和至少一级分支数据平台；其中，所述中心数据平台级联了下级的数据平台；所述分支数据平台未级联下级的数据平台；所述本级的数据平台为本级的中心数据平台；所述本级的中心数据平台与下级的分支数据平台和/或下级的中心数据平台进行级联。
可选的，所述中心数据平台的所述级联模块包括：用于对与所述中心数据平台级联的下级的数据平台进行管理的平台管理模块；所述方法还包括：获取用于在所述本级的中心数据平台上注册与所述本级的中心数据平台级联的下级的数据平台的平台级联请求；所述平台级联请求包括待注册的下级的数据平台的标识信息；响应于所述平台级联请求，调用所述平台管理模块，生成所述本级的中心数据平台的标识信息与所述待注册的下级的数据平台的标识信息之间的级联关系，并将所述级联关系在所述平台管理模块中进行维护；以及，为所述待注册的下级的数据平台生成与所述本级的中心数据平台进行级联的级联配置信息，并将所述级联配置信息发送至所述待注册的下级的数据平台，以由所述待注册的下级的数据平台基于所述级联配置信息完成与所述本级的中心数据平台之间的级联配置。
可选的，所述数据平台的所述级联模块包括：用于管理在该数据平台上已注册的服务的服务管理模块；所述方法还包括：响应于获取用于在所述本级的数据平台上注册服务的服务注册请求，调用所述服务管理模块，由所述服务管理模块基于所述服务注册请求在所述本级的数据平台上注册服务，并将注册的所述服务的服务标识与所述服务的服务调用接口的对应关系在所述服务管理模块中进行维护。
可选的，所述数据平台的所述级联模块包括：用于针对在该数据平台上已注册的服务发起服务调用的服务代理模块，响应于所述服务调用请求，查询所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口，包括：响应于所述服务调用请求，调用所述服务代理模块查询所述服务管理模块维护的所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；将所述服务调用参数提交至查询到的所述服务调 用接口，以发起所述下级的数据平台针对所述目标服务的级联调用，包括：由所述服务代理模块将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
可选的，调用所述服务管理模块，由所述服务管理模块基于所述服务注册请求在所述本级的数据平台上注册服务，包括：调用所述服务管理模块，由所述服务代理模块基于所述服务注册请求在所述本级的数据平台上注册服务，来查询所述平台管理模块维护的所述级联关系中与所述本级的数据平台具有级联关系的全部下级的数据平台；响应于获取到在与所述本级的数据平台具有级联关系的下级的数据平台中，具有针对在所述本级的数据平台上所述服务的调用权限的数据平台的集合，在所述服务管理模块中维护所述服务与所述数据平台的集合的对应关系，以完成在所述本级的数据平台上针对所述服务的服务注册。
可选的，响应于所述服务调用请求，调用所述服务代理模块查询所述服务管理模块维护的所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口，包括：响应于所述服务调用请求，调用所述服务代理模块，查询所述服务管理模块维护的所述服务与数据平台的集合的对应关系，确定所述下级的数据平台是否具有针对所述目标服务的调用权限；如果是，进一步查询所述服务管理模块维护的所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口。
可选的，所述方法还包括：所述服务代理模块获取所述下级的数据平台针对所述目标服务的级联调用的调用结果，并将获取到的调用结果返回至所述下级的数据平台。
可选的，所述服务包括以下至少一个：目录共享服务，接口资源共享服务，数据资源共享服务。
可选的，在所述目标任务请求为针对数据汇聚任务的创建请求的情况下，所述方法还包括：响应于所述数据汇聚任务的创建请求，根据所述创建请求中指定的目标下级数据平台和数据标准，创建与所述目标下级数据平台关联的数据汇聚任务；其中，所述数据汇聚任务中包括所述数据标准；通过所述级联模块将所述数据汇聚任务下发给所述目标下级数据平台；在接收到所述目标下级数据平台向所述级联模块发送的预设通知的情况下，通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中。
可选的，所述级联模块中维护有各个下级的数据平台的通信参数，所述级联模块通过所述通信参数建立与所述下级的数据平台的通信连接，并通过所述通信连接传输数据。
可选的，所述通过所述级联模块将所述数据汇聚任务下发给所述目标下级数据平台，包括：响应于所述目标下级数据平台向所述级联模块发起的定时轮询请求，查询是否存在与所述目标下级数据平台关联的数据汇聚任务；如果存在，通过所述级联模块将查询到的数据汇聚任务下发给所述目标下级数据平台。
可选的，所述数据标准包括用于定义数据的信息项；所述信息项包括信息项名称、数据类型、数据长度、描述中的至少一种；所述数据标准用于将下级的数据平台中其它数据标准的数据转换为所述数据标准的待汇聚数据。
可选的，所述通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中，包括：通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到预设的前置库，并将所述数据汇聚任务的任务状态更新为完成；在所有目标下级数据平台关联的数据汇聚任务的任务状态均完成的情况下，通过所述级联模块将所述前置库中存储的所有目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中。
可选的，所述通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到预设的前置库，包括：通过所述级联模块启动数据交换引擎，以基于所述数据交换引擎从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入预设的到前置库；所述通过所述级联模块将所述前置库中 存储的所述目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中，包括：通过所述级联模块启动所述数据交换引擎，基于所述数据交换引擎将所述前置库中存储的所述目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中。
本申请还提供一种服务处理方法，所述方法应用于多级数据平台中的任一级数据平台；所述数据平台中部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互：所述方法包括：获取上级的数据平台通过所述级联模块下发的数据汇聚任务；其中，所述数据汇聚任务中包括所述上级的数据平台指定的数据标准；响应于所述数据汇聚任务，将本级的数据平台的源数据库中的数据转换为符合所述数据标准的待汇聚数据；向所述上级的数据平台的所述级联模块发送预设通知，以使所述上级的数据平台通过所述级联模块从所述源数据库中将已转换为所述数据标准的待汇聚数据写入到所述上级的数据平台的目的数据库中。
本申请还提供一种级联系统，其被构造为执行以上所述的方法；其中，所述级联系统包括多级数据平台；所述多级数据平台包括至少一级中心数据平台和至少一级分支数据平台；所述中心数据平台级联了下级的数据平台；所述分支数据平台未级联下级的数据平台；各个数据平台中均部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互。
本申请还提供一种服务处理装置，所述装置应用于多级数据平台中的任一级数据平台；所述数据平台中部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互；所述装置包括：请求接收单元，用于接收目标任务请求；关系查询单元，用于在所述目标任务请求为下级的数据平台针对在本级的数据平台上已注册的目标服务的服务调用请求的情况下，其中，所述服务调用请求包括所述目标服务的服务标识以及与所述目标服务相关的服务调用参数，响应于所述服务调用请求，查询所述级联模块中维护的在本级的数据平台上已注册的服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；级联调用单元，用于将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
本申请还提供一种电子设备，包括通信接口、处理器、存储器和总线，所述通信接口、所述处理器和所述存储器之间通过总线相互连接；所述存储器中存储机器可读指令，所述处理器通过调用所述机器可读指令，执行上述方法。
本申请还提供一种计算机可读存储介质，所述计算机可读存储介质存储有机器可读指令，所述机器可读指令在被处理器调用和执行时，实现上述方法。
附图说明
图1是一示例性的实施例示出的一种数据平台架构图。
图2是一示例性的实施例示出的一种服务处理方法的流程图。
图3是一示例性的实施例示出的另一种数据平台架构图。
图4是一示例性的实施例示出的另一种数据平台架构图。
图5是一示例性实施例示出的另一种服务处理方法的流程图。
图6是一示例性实施例示出的操作界面的示意图。
图7是一示例性实施例示出的另一种服务处理方法的流程图。
图8是一示例性实施例示出的两级级联场景下的服务处理的示意图。
图9是一示例性实施例示出的多级级联场景下的服务处理的示意图。
图10是一示例性的实施例示出的一种服务处理装置所在电子设备的硬件结构图。
图11是一示例性的实施例示出的一种服务处理装置框图。
图12是一示例性的实施例示出的另一种服务处理装置的结构示意图。
图13是一示例性的实施例示出的另一种服务处理装置的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本申请相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本申请的一些方面相一致的装置和方法的例子。
需要说明的是：在其他实施例中并不一定按照本说明书示出和描述的顺序来执行相应方法的步骤。在一些其他实施例中，其方法所包括的步骤可以比本说明书所描述的更多或更少。此外，本说明书中所描述的单个步骤，在其他实施例中可能被分解为多个步骤进行描述；而本说明书中所描述的多个步骤，在其他实施例中也可能被合并为单个步骤进行描述。
为了使本技术领域的人员更好地理解本说明书实施例中的技术方案，下面先对本说明书实施例涉及的相关技术，进行简要说明。
通过各类服务可以将各类信息在多级数据平台中进行共享。所述各类信息可以包括数据资源，编制的目录等。比如，通过目录共享服务可以将目录在部、省、市、县等数据平台之间共享。除了共享服务以外，多级数据平台还可能存在数据汇聚服务的需求。例如，下级平台可以汇聚各个类型的数据并将所汇聚的数据上报给上级平台，或者由上级平台从下级平台中获取。
然而，由于每种信息共享需要使用的共享服务各不相同，在传统的数据平台中，需要上级的数据平台和下级的数据平台为每一种信息共享服务分别协商共享方式，例如实现目录共享服务是通过线下的方式，比如通过邮件发送、文件传输，而实现数据资源共享需要由上级的数据平台将数据资源打包后放在共享服务器，再由下级的数据平台通过共享服务器获取数据资源。另外，在实际应用中，不同层级的数据平台之间还存在数据隔离和通信隔离的问题。例如，不同层级的数据平台在构建时可能采用不同的数据标准，从而导致上级平台的数据库无法识别下级平台中的数据库。
由此可见，传统的数据平台很难以一种高效的方式来实现跨平台的服务，需要针对每一种服务单独制定跨平台的服务策略，导致平台建设成本高，周期长，而且维护复杂。
为此，本申请实施例提供一种服务处理方法，能够跨多级平台实现各类服务，例如共享服务、查询服务、数据汇聚服务等。
请参见图1，图1是一示例性的实施例示出的一种多级数据平台架构图，如图1所示，多级数据平台可以包括省级数据平台，与省级数据平台直接连接的多个市级数据平台，以及与市级数据平台直接连接的多个县级数据平台。
以在不同层级的数据平台之间共享服务为例，在实际应用中，上级的数据平台可能需要向下级的数据平台同步目录、数据或提供其他服务。例如，省级数据平台需要向市级数据平台同步数据，县级数据平台需要通过市级数据平台查询数据信息等等。
传统的数据平台在同步数据时，通常需要上级数据平台将数据打包成文件，放在上级文件同步服务器中，下级数据平台再通过文件同步服务器获取文件。而且这种方式，只能将数据同步给特定的下级数据平台，不够灵活。同时，上级数据平台向下级数据平台提供各项服务，当上级数据平台的服务状态发生变化时，需要向下级逐级进行通知，服务处理过程较为复杂。
然而，根据本申请实施例提供的服务处理方法，在多级数据平台场景下，下级的数据平台可以直接基于服务标识调用上级的数据平台上的提供的服务。
在实现时，各级的数据平台中部署有级联模块，该级联模块用于进行不同层级的数据平台之间的数据交互。本级的数据平台可以接收目标任务请求，该目标任务请求可以是服务调用请求，或者数据汇聚请求，等等。在该目标任务请求为下级的数据平台对用户在本级的数据平台上注册的目标服务的服务调用请求的情况下，其中，所述服务调用请求包括所述目标服务的服务标识以及与所述目标服务相关的服务调用参数，本级的数据平台可以响应于所述服务调用请求，查询级联模块中维护的在本级的数据平台上已注册的服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；将所述服务调用参数提交至查询到的所述服务调用接口， 以发起所述下级的数据平台针对所述目标服务的级联调用。
由此可见，在本说明书的技术方案中，多级数据平台中任一级数据平台，可以通过级联模块来维护在该数据平台上注册的服务的服务标识与该服务的服务调用接口之间的对应关系，而下级的数据平台在需要调用上级数据平台注册的服务时，可以直接向上级的数据平台发起针对该服务的级联调用，由上级的数据平台基于维护的上述服务标识和所述服务的服务调用接口的对应关系来确定该服务对应的服务调用接口，再将相关的服务调用参数提交至查询到的该服务调用接口，来完成针对该服务的级联调用。
上级的数据平台注册的服务的服务标识和服务调用接口的对应关系，将由上级的数据平台通过级联模块来自主的进行维护，这些服务的服务调用接口将不再暴露给下级的数据平台，从而实现下级的数据平台对上级的数据平台提供的服务进行单向调用；对于下级的数据平台而言，只需要基于服务的服务标识来直接发起针对该服务的级联调用即可；而当上级的数据平台维护的服务的服务标识与服务调用接口之间的对应关系发生变化时，对于上级数据平台来说，也无需将变化后的上述对应关系通知给下级数据平台。因此，通过单向调用的方式，无需对每一种服务分别协商共享方式，从而简化下级的数据平台对上级的数据平台上的服务的级联调用的过程。下面通过具体实施例，并结合具体的应用场景对本申请进行描述。
请参见图2，图2是一示例性的实施例示出的一种服务级联调用方法的流程图，上述方法应用于如图1示出的多级数据平台中的任一级数据平台；在本说明书中，数据平台通过级联模块维护了该数据平台上注册的服务的服务标识和所述服务的服务调用接口的对应关系，其中服务标识可以是服务类型、服务版本等信息。例如，服务类型可以是目录共享服务，服务版本是v1.1；在本说明书中，服务是指每级数据平台可以提供的与数据相关的服务，例如，目录共享服务、接口资源共享服务、数据资源共享服务、数据汇聚服务等等。
目录共享服务是指任一级的数据平台可以将本平台编制的目录发布到本数据平台，再由其它数据平台进行调用的服务。所述目录可以包括基于数据资源进行编制的目录、基于各类信息共享服务编制的目录等等。
在一实施例中，下级的数据平台可以通过上级的数据平台提供的服务调用接口，获取这些目录，进行目录的同步。
例如，省级数据平台的A部门现有500张数据表可以共享至下级的数据平台，A部门可以通过省级数据平台提供的目录服务将这500张数据表编制成数据目录并发布到省级数据平台，第一市级数据平台的B部门可以通过省级数据平台提供的服务调用接口，获取这个数据目录，并根据数据目录进一步获取需要的数据表。
相应的，接口资源共享服务是指任一级的数据平台可以将本平台提供的接口资源发布到本平台，其中，接口资源是指数据平台可以对外提供的应用程序接口，比如可以是数据查询接口、数据表更新接口等等。
在一实施例中，下级的数据平台可以通过上级的数据平台提供的服务调用接口，获取这些接口资源，并可以在应用程序中直接使用这些接口资源进行查询动作或更新动作。
例如，省级数据平台的A部门可以将对外提供的数据表查询接口发布到省级数据平台，第一市级数据平台的B部门可以通过省级数据平台提供的服务调用接口，获取这个数据表查询接口，并可以根据这个数据表查询接口进行相应的查询动作。
相应的，数据资源共享服务是指任一级的数据平台可以将本平台提供的接口资源发布到本平台，其中，数据资源可以是指数据表、数据文件、文件压缩包等。
在一实施例中，下级的数据平台可以通过上级的数据平台提供的服务调用接口，获取这些数据资源，进行数据资源的同步。
例如，省级数据平台的A部门现有500张数据表可以共享至下级的数据平台，第一市级数据平台的B部门可以通过省级数据平台提供的服务调用接口，直接获取500张数据表，也可以根据上述目录共享服务，先获取500张数据表的数据目录，再根据数据目录获取需要的数据表。
相应的，数据汇聚服务通常指上下级的数据平台之间的数据上报等业务。一般可以 是指上级数据平台对下级数据平台的数据进行收集和汇总。本说明书提供的服务处理方法在需要数据汇聚服务的特定场景中的应用示例，将在后文详细描述。
在一实施例中，多级的数据平台包括至少一级中心数据平台和至少一级分支数据平台；其中所述中心数据平台级联了下级的数据平台；所述分支数据平台未级联下级的数据平台；所述本级的数据平台为本级的中心数据平台。需要说明的是，本级的中心数据平台可以与下级的分支数据平台和/或下级的中心数据平台进行级联。
由此，第一，可以将中心数据平台作为服务级联单元，与下级的数据平台进行级联，构成了树形的级联结构，通过中心数据平台可以完成各类服务的共享；第二，构建了一种灵活可调的级联结构，即根据需求，当与下级的数据平台的级联关系发生变更时，对中心数据平台内的级联关系进行调整即可，方便快捷。
例如，请参见图3，图3是一示例性的实施例示出的另一种数据平台架构图，如图3所示，省级数据平台和第一市级数据平台均级联了下级的数据平台，因此省级数据平台和第一市级数据平台为中心数据平台。相应的，第二市级平台、第一县级数据平台和第二县级数据平台未级联下级的数据平台，因此第二市级平台、第一县级数据平台和第二县级数据平台为分支数据平台。在各个数据平台中均部署有级联模块。
在一实施例中，当数据平台为中心数据平台时，该中心数据平台的级联模块包括了用于对与其级联的下级的数据平台进行管理的平台管理模块，当下级的数据平台需要级联至本级的中心数据平台时，可以向本级的中心数据平台发起平台级联请求。本级的中心数据平台可以获取用于在所述本级的中心数据平台上注册与所述本级的中心数据平台级联的下级的数据平台的平台级联请求；所述平台级联请求包括待注册的下级的数据平台的标识信息；其中，可以由下级的数据平台的用户向本级的中心数据平台主动发起平台级联请求，也可以由新部署的下级数据平台自动发起针对本级的数据平台的平台级联请求。在平台级联请求中，数据平台的标识信息具体可以是下级数据平台的名称、下级数据平台的IP地址，端口地址等信息。
响应于下级的数据平台针对本级的中心数据平台的平台级联请求，本级的中心数据平台可以调用上述平台管理模块，生成本级的中心数据平台的标识信息与所述下级的数据平台的标识信息之间的级联关系，并将所述级联关系在所述平台管理模块中进行维护。其中上述级联关系用于描述本级的中心数据平台和下级的数据平台之间的逻辑关系，例如可以是一种树状的数据结构，下级的数据平台可以作为本级的中心数据平台的子树。
同时，本级的中心数据平台为下级的数据平台生成与所述中心数据平台进行级联的级联配置信息，并将所述级联配置信息发送至所述下级的数据平台，以由所述下级的数据平台基于所述级联配置信息完成与所述中心数据平台之间的级联配置。其中，所述级联配置信息具体可以是数据平台账号以及相应的密钥信息或是其他用于认证的配置信息，被存储在平台管理模块中。下级的数据平台基于中心数据平台提供的数据平台账号以及相应的密钥信息，以及中心数据平台的IP地址、端口地址等信息完成与中心数据平台之间的级联配置。
例如，请参见图4，图4是一示例性的实施例示出的另一种数据平台架构图，以图4示出的数据平台架构图为例，当第三县级数据平台需要级联至第一市级数据平台时，第三县级数据平台可以向第一市级数据平台发起平台级联请求，由第一市级数据平台调用平台管理模块，生成第一市级数据平台和第三县级数据平台之间的级联关系，并将所述级联关系在平台管理模块中进行维护，同时，为第三县级数据平台生成与第一市级数据平台进行级联的级联配置信息，以使第三县级数据平台完成与第一市级数据平台之间的级联配置。
上述例子中为中心数据平台搭载了用于对与其级联的下级的数据平台进行管理的平台管理模块，但当下级的数据平台无需再级联数据平台时，可以不再部署搭载平台管理模块，节约数据平台部署的成本。
上述方法可以包括以下步骤：步骤202，接收目标任务请求；该目标任务请求可以是本级数据平台发出的，也可以是接收自下级数据平台。在本示例中，该目标任务请求为下级的数据平台针对在本级的数据平台上已注册的目标服务的服务调用请求；其中， 所述服务调用请求包括所述目标服务的服务标识以及与所述目标服务相关的服务调用参数。
在本说明书中，目标服务是指下级的数据平台需要调用的服务；例如下级的数据平台需要获取本级的数据平台提供的某项数据资源，下级的数据平台需要使用到本级的数据平台提供的某个接口等。下级的数据平台可以预先获取本级的数据平台上注册的若干服务，并向本级的数据平台发起服务调用请求。其中，服务调用请求可以包括目标服务的服务标识以及与目标服务相关的服务调用参数。
例如，以图1示出的数据平台架构图为例，第一市级数据平台需要从省级数据平台获取10张数据表，第一市级数据平台可以向省级数据平台发起数据资源共享服务的调用请求；其中，该服务调用请求可以包括数据资源共享服务的名称、版本号等信息，以及相关的服务调用参数可以包括数据表的种类，数据表的数量。
在一实施例中，任一级的数据平台的级联模块可以包括用于管理在该数据平台上已注册的服务的服务管理模块。本级的数据平台可以响应于获取用于在所述本级的数据平台上注册服务的服务注册请求，由所述服务管理模块基于所述服务注册请求在所述本级的数据平台上注册服务，并将注册的所述服务的服务标识与所述服务的服务调用接口的对应关系在所述服务管理模块中进行维护。其中，上述服务注册请求可以由用户主动发起，比如本级的数据平台的用户可以将某些数据同步至下级的数据平台，可以主动发起服务注册请求；也可以由应用程序自动发起服务注册请求，比如当用户通过本级的数据平台上的应用程序中上传了某些数据时，可以由应用程序自动发起服务注册请求。
例如，省级数据平台某部门的用户可以将500个数据表同步至下级数据平台，因此该用户可以注册一项数据资源共享服务，并提供相应的服务调用接口。省级数据平台响应于用户发起的注册请求，将该项数据资源共享服务的服务标识与服务调用接口的对应关系，在省级数据平台的服务管理模块中进行维护。
在另一实施例中，还可以对已注册的服务对于不同的数据平台分别设置不同的调用权限。本级的数据平台可以调用所述服务管理模块，由所述服务管理模块基于所述服务注册请求在所述数据平台上注册服务，由于平台管理模块维护了与所述本级的数据平台具有级联关系的全部的下级数据平台之间的级联关系，因此服务管理模块可以与平台管理模块进行交互，来查询所述平台管理模块维护的级联关系中与本级的数据平台具有级联关系的全部下级的数据平台。
在查询所述平台管理模块维护的级联关系中与本级的数据平台具有级联关系的全部下级的数据平台后，可以获取这些下级的数据平台中具有针对在本级的数据平台上注册的服务的调用权限的数据平台集合，在所述服务管理模块中维护所述数据平台集合与该服务的对应关系，以完成在所述本级的数据平台上针对所述服务的服务注册。其中，可以在注册服务时，由用户主动从与本级的数据平台具有级联关系的全部下级的数据平台中选择一个或多个下级的数据平台设置针对注册的服务的调用权限，也可以在注册服务时由本级的数据平台中的应用程序自动选择下级的数据平台设置调用权限。上述服务管理模块分别针对不同的已注册服务维护了不同的数据平台集合，以此针对不同的数据平台分别设置不同的调用权限。
例如，省级数据平台某部门的用户可以将500个数据表同步至下级数据平台，因此该用户可以注册一项数据资源共享服务，并提供相应的服务调用接口。但省级数据平台级联了两个市级数据平台，如果该用户只想将数据表同步至第一市级数据平台，此时可以由用户设置第一市级数据平台具有针对该数据资源共享服务的调用权限。省级的数据平台可以获取第一市级平台，并在服务管理模块维护该数据资源共享服务与第一市级平台之间的对应关系，完成在省级数据平台上针对数据服务的服务注册。
相应的，用户也可以选择设置第一市级数据平台和第二市级数据平台均具有针对该数据资源共享服务的调用权限。省级的数据平台可以获取第一市级平台和第二市级平台构成的数据平台集合，并在服务管理模块维护该数据资源共享服务与数据平台集合之间的对应关系，完成在省级数据平台上针对数据服务的服务注册。
步骤204，在所述目标任务请求为服务调用请求的情况下，响应于所述服务调用请 求，查询所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口。
在本说明书，由于上述本级的数据平台维护了在本级的数据平台上注册的服务的服务标识和所述服务的服务调用接口的对应关系，因此可以查询服务标识和所述服务的服务调用接口的对应关系，基于目标服务的服务标识，确定与目标服务的服务标识对应的服务调用接口。
例如，以图1示出的数据平台架构图为例，第一市级数据平台需要从省级数据平台获取10张数据表，第一市级数据平台可以向省级数据平台发起数据资源共享服务调用请求。省级数据平台根据调用请求中包含的数据资源共享服务的名称、版本号等信息，查询服务标识和所述服务的服务调用接口的对应关系，确定该数据资源共享服务的调用接口。
在一实施例中，任一级的数据平台的级联模块还可以包括用于针对在该数据平台上已注册的服务发起服务调用的服务代理模块，下级的数据平台可以向本级的数据平台搭载的服务代理模块发起调用请求，由本级的数据平台通过调用服务代理模块与服务管理模块进行交互，来查询所述服务管理模块维护的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口。
例如，以图1示出的数据平台架构图为例，第一市级数据平台需要从省级数据平台获取10张数据表，第一市级数据平台可以向省级数据平台搭载的服务代理模块发起数据资源共享服务调用请求，省级数据平台搭载的服务代理模块与服务管理模块进行交互，根据调用请求中包含的数据资源共享服务的名称、版本号等信息，查询所述服务管理模块维护的对应关系，确定该数据资源共享服务的调用接口。
在另一实施例中，本级的数据平台搭载的服务代理模块还可以与服务管理模块进行交互，判断下级的数据平台针对于目标服务是否具有服务调用权限。具体的，响应于所述服务调用请求，调用所述服务代理模块，由所述服务代理模块与所述服务管理模块进行交互，来调用所述服务代理模块，查询所述服务管理模块维护的所述服务与数据平台集合的对应关系，确定所述下级的数据平台是否具有针对所述目标服务的调用权限；如果是，进一步与所述服务管理模块进行交互，来查询所述服务管理模块维护的所述服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口。
例如，上述例子中，省级数据平台某部门的用户可以将500个数据表同步至下级数据平台，并设置了第一市级数据平台具有该数据资源共享服务的调用权限。当第一市级数据平台需要从省级数据平台获取10张数据表时，第一市级数据平台可以向省级数据平台搭载的服务代理模块发起数据资源共享服务调用请求，省级数据平台搭载的服务代理模块可以和服务管理模块进行交互，查询服务管理模块维护的数据资源共享服务与数据平台集合的对应关系，确定第一市级数据平台具有针对该数据资源共享服务的调用权限。因此可以继续查询服务管理模块维护的服务标识与服务的服务调用接口的对应关系，确定该数据资源共享服务的调用接口。
步骤206，将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
在本说明书中，本级的数据平台可以将服务调用参数直接提交至目标服务对应的服务调用接口，以发起所述下级的数据平台针对目标服务的级联调用。
例如，以图1示出的数据平台架构图为例，第一市级数据平台需要从省级数据平台获取10张数据表，第一市级数据平台可以向省级数据平台发起数据资源共享服务调用请求后，省级数据平台查询到对应的数据服务的服务调用接口，将需要的数据表的种类、数据表的数量等作为服务调用参数提交至查询到的数据资源共享服务的调用接口。
在一实施例中，任一级的数据平台还可以搭载用于该数据平台上注册的服务发起服务调用的服务代理模块，下级的数据平台可以向本级的数据平台搭载的服务代理模块发起调用请求，由所述服务代理模块将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
例如，以图1示出的数据平台架构图为例，第一市级数据平台需要从省级数据平台获取10张数据表，第一市级数据平台可以向省级数据平台搭载的服务代理模块发起数据资源共享服务调用请求后，由服务代理模块查询服务管理模块，获取到数据服务对应的服务调用接口，并将需要的数据表的种类、数据表的数量等作为服务调用参数提交至查询到的数据资源共享服务的调用接口。
在另一实施例中，由服务代理模块获取所述下级的数据平台针对所述目标服务的级联调用的调用结果，并将获取到的调用结果返回至所述下级的数据平台。
例如，以图1示出的数据平台架构图为例，第一市级数据平台需要从省级数据平台获取10张数据表，可以在第一市级数据平台向省级数据平台搭载的服务代理模块发起数据资源共享服务调用请求后，由服务代理模块将服务调用参数提交至查询到的数据资源共享服务的调用接口，获取这10张数据表，并返回第一市级数据平台。
通过以上实施例，多级数据平台中任一级数据平台，可以维护在该数据平台上注册的服务的服务标识与该服务的服务调用接口之间的对应关系，而下级的数据平台在需要调用上级数据平台注册的服务时，可以直接向上级的数据平台发起针对该服务的级联调用，由上级的数据平台基于维护的上述服务标识和所述服务的服务调用接口对应关系来确定该服务对应的调用接口，再将相关的服务调用参数提交至查询到的该服务调用接口，来完成针对该服务的级联调用。
上级的数据平台注册的服务的服务标识和服务调用接口的对应关系，将由上级的数据平台来自主的进行维护，这些服务的服务调用接口将不再暴露给下级的数据平台，从而实现下级的数据平台对上级的数据平台提供的服务进行单向调用；对于下级的数据平台而言，只需要基于服务的服务标识来直接发起针对该服务的级联调用即可；而当上级的数据平台维护的服务的服务标识与服务调用接口之间的对应关系发生变化时，对于上级数据平台来说，也无需将变化后的上述对应关系通知给下级数据平台。因此，通过单向调用的方式，无需对每一种服务分别协商共享方式，从而简化下级的数据平台对上级的数据平台上的服务的级联调用的过程。
在本申请实施例中描述的数据平台可以实现为单独的计算机、多个计算机组成的计算机集群、单独的服务器、多个服务器组成的服务器集群、站点等。另外，级联模块作为一个独立运行的子系统，其可以设置在数据平台内作为数据平台的一部分或者设置在数据平台外，可以实现为软件、硬件、固件或者其任意组合。当级联模块通过软件实现时，级联模块可以是包括计算机指令的计算机程序产品的形式。通过处理器调用并执行该计算机指令，可以实现上述级联模块以及其包含的各个子模块(例如，平台管理模块，服务管理模块、服务代理模块等)的功能。当级联模块(包括各个子模块)通过硬件实现时，其可以是计算机芯片、微处理器、DSP、计算机、服务器等一个或多个的组合。
在上文中主要以目标任务请求为服务调用请求为例对本申请的服务处理方法进行了描述。在下文中，将以目标任务请求为数据汇聚请求为例对本申请的服务处理方法作进一步描述。
以下参考图5所示的一种服务处理方法为例加以介绍，在该方法中，目标任务请求为针对数据汇聚任务的创建请求，该方法可以应用于多级数据平台中的上级数据平台，所述上级数据平台对应于至少一个下级数据平台；所述方法可以包括以下步骤：
步骤510：响应于数据汇聚任务的创建请求，根据所述创建请求中指定的目标下级数据平台和数据标准，创建与所述目标下级数据平台关联的数据汇聚任务；其中，所述数据汇聚任务中包括所述数据标准。
在本说明书中，所述级联模块中维护有各个下级数据平台的通信参数，所述级联模块通过所述通信参数建立与所述下级数据平台的通信连接，并通过所述通信连接传输数据。其中，级联模块与下级数据平台之间的通信可以是通过专用网络实现，以避免公共网络对平台安全的影响。
在接收到用户发起的数据汇聚任务的创建请求的情况下，可以根据该创建请求中指定的一个或多个目标下级数据平台，创建与每个目标下级数据平台关联的数据汇聚任务，并且所述数据汇聚任务中包括创建请求中指定的数据标准。
在一示例性的实施例中，所述数据标准可以包括多个用于定义数据的信息项；所述信息项包括信息项名称(例如，中文名称和/或英文名称)、数据类型、数据长度、描述。
所述数据标准用于将各个下级平台中其它数据标准的数据转换为所述数据标准的待汇聚数据。
在本说明书中，可以通过信息项的形式定义数据标准。举例说明，信息项可以包括如下表1所示的内容：
信息项名称 英文名称 数据类型 是否主键 数据长度 描述
姓名 Name 字符串型C 否 10 姓名
年龄 Age 数值型N 否 10 年龄
性别 Sex 字符串型C 否 -- 性别
体重 Weight 数值型N 否 -- 体重
身高 Height 数值型N 否 -- 身高
家庭住址 Address 字符串型C 否 30 家庭住址
表1
如表1所示的，信息项可以包括信息项名称(例如，中文名称和/或英文名称)、数据类型、是否主键、数据长度、描述等信息。通过定义数据标准，可以使下级平台提前准备符合该数据标准的待汇聚数据。
在实际应用中，上级数据平台的用户可以登录本数据平台(用作数据汇聚平台)，并在数据汇聚服务的操作界面中创建第一数据汇聚任务，以完成下级数据平台的指定和数据标准的定义。
以下参考图6所示的操作界面中的示意图。上级数据平台的用户可以在数据汇聚的操作界面中进行编辑，以输入相关内容。
如图6中所示的，“在线编辑”功能下，显示的编辑内容包括第一数据汇聚任务的“基本信息”、数据标准的“信息项”、下级数据平台(图6中未示出)、目的数据库的配置信息、调度配置等。具体的填写字段和说明如图6中所示，这里不再一一进行赘述。
需要说明的是，图6中所示的操作界面仅是一种示例，并不是本说明书实施例具体的限定。
值得一提的是，为了简化用户的操作难度，所述操作界面中可以展示快捷选项，并由上级数据平台的用户触发快捷选项以确定对应的编辑内容。用户可以通过下拉方式选择或填写内容。由上级数据平台自动在用户触发快捷选项后生成对应的编辑内容。其中，所述下拉方式的快捷选项中，选项内容可以是由开发人员预先配置的。
例如，开发人员可以在数据汇聚平台上为有数据汇聚需求的平台注册账户(当然也可以由各平台的用户自己注册)；针对存在上下级对应关系的数据平台，可以建立上级数据平台和下级数据平台之间的关联关系。如此，在上级数据平台的用户进入操作界面并点击下级数据平台的快捷选项后，就可以以下拉方式展示与该上级数据平台存在关联的各个下级数据平台的选项。
再例如，数据汇聚平台支持数据标准的复用；上级数据平台的用户在进入操作界面并点击复用历史的数据标准的快捷选项后，就可以直接加载历史的数据标准对应的各个信息项的相关内容。如果某些信息项需要修改，用户也可以随时进行修改。
通过为上级平台(作为数据汇聚平台)提供快捷汇聚设置，上级数据平台的用户只需要在操作界面中选择快捷选项就可以完成配置包括定义数据标准、指定下级数据平台、配置目的数据库等。之后完全由数据汇聚平台全自动执行数据汇聚，大大提高了数据汇聚效率。
步骤520：通过所述级联模块将所述数据汇聚任务下发给所述目标下级数据平台。
在创建了与各个目标下级数据平台关联的数据汇聚任务之后，上级数据平台可以通过级联模块主动将各个数据汇聚任务分发给对应的目标下级数据平台；在一示例性的实施例中，上级数据平台可以是在目标下级数据平台通过级联模块主动发起定时轮询请求时，再下发数据汇聚任务。具体地，所述步骤520，可以包括：响应于所述目标下级数 据平台向所述级联模块发起的定时轮询请求，查询是否存在与所述目标下级数据平台关联的数据汇聚任务；如果存在，通过所述级联模块将查询到的数据汇聚任务下发给所述目标下级数据平台。
通过该实施例，下级数据平台在运行期间可以定时向上级系统的级联模块获取数据汇聚任务。
步骤530：在接收到所述目标下级数据平台向所述级联模块发送的预设通知的情况下，通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中。
在一示例性的实施例中，所述通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中，包括：通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到预设的前置库(也即前置数据库)，并将所述数据汇聚任务的任务状态更新为完成；在所有目标下级数据平台关联的数据汇聚任务的任务状态均完成的情况下，通过所述级联模块将所述前置库中存储的所有目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中。在一些示例中，所述前置数据库配置在数据平台(顶层数据平台可以不配置)的数据汇聚管理子系统中，用于存储供上级数据平台获取的、本平台的上行数据。
本说明书中可以设置用于存储下级系统提供的待汇聚数据的前置库，如此上级数据平台可以通过级联模块先将下级数据平台的源数据库中的待汇聚数据写入前置库，再将前置库中的待汇聚数据写入上级数据平台的目的数据库。如此，避免了下级数据平台中源数据库暴漏在外导致的数据安全风险；以及由于无需开通源数据库到上级数据平台的网络策略，因此可以降低实施难度。
在一示例性的实施例中，所述通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到预设的前置库，包括：通过所述级联模块启动数据交换引擎，以基于所述数据交换引擎从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入预设的到前置库；所述通过所述级联模块将所述前置库中存储的所述目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中，包括：通过所述级联模块启动所述数据交换引擎，基于所述数据交换引擎将所述前置库中存储的所述目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中。
本说明书中通过设置数据交换引擎可以提高源数据库、前置库和目的数据库之间数据的写入效率，从而减少数据汇聚所需的时间。
在介绍了上级数据平台相关的实施例后，接下来介绍与上级数据平台对应的下级数据平台相关的实施例。
以下请参考图7所示的一种服务处理方法为例加以介绍，所述方法可以应用于与上级数据平台对应的下级数据平台，所述上级数据平台中部署有级联模块，所述级联模块用于进行不同层级的平台间的数据交互；所述方法可以包括以下步骤：步骤710：获取所述上级数据平台通过所述级联模块下发的数据汇聚任务；其中，所述数据汇聚任务中包括所述上级数据平台指定的数据标准。
在本说明书中，所述级联模块中维护有所述下级数据平台的通信参数，所述级联模块通过所述通信参数建立与下级数据平台的通信连接，并通过所述通信连接传输数据。其中，级联模块与下级数据平台之间的通信可以是通过专用网络实现，以避免公共网络对平台安全的影响。
结合前述图7实施例的内容，上级数据平台在创建了与各个下级数据平台关联的数据汇聚任务之后，可以通过级联模块将数据汇聚任务下发给下级数据平台。相应地，下级数据平台就可以获取到上级数据平台通过级联模块下发的数据汇聚任务；其中，所述数据汇聚任务中可以包括所述上级数据平台指定的数据标准。
在一示例性的实施例中，所述数据标准可以包括多个用于定义数据的信息项；所述信息项包括信息项名称(例如，中英文名称)、数据类型、数据长度、描述；所述数据 标准用于将各个下级数据平台中其它数据标准的数据转换为所述数据标准的待汇聚数据。关于数据标准的定义可以参考前述实施例，这里不再进行赘述。
如前所述的，上级数据平台可以通过级联模块主动将各个数据汇聚任务分发给对应的目标下级数据平台；也可以由下级数据平台向级联模块主动获取数据汇聚任务。具体地，所述步骤710，可以包括：向所述上级数据平台的级联模块发起定时轮询请求，查询所述上级数据平台中是否存在与所述下级数据平台关联的数据汇聚任务；接收所述上级数据平台通过所述级联模块下发的查询到的数据汇聚任务。
通过该实施例，下级数据平台在运行期间可以定时通过下级级联模块主动向上级平台获取数据汇聚任务。
步骤720：响应于所述数据汇聚任务，将所述下级数据平台的源数据库中的数据转换为符合所述数据标准的待汇聚数据。
在接收到数据汇聚任务之后，下级数据平台可以将本地的源数据库中的不符合上级数据平台指定数据标准的数据转换为该数据标准的待汇聚数据。
在一示例性的实施例中，在所述下级数据平台包含一个或多个不同部门的情况下，所述将所述下级数据平台的源数据库中的数据转换为符合所述数据标准的待汇聚数据，可以包括：创建与下属的各个部门一一对应的汇聚编码和包含所述数据标准的数据汇聚子任务，并将所述数据汇聚子任务和汇聚编码分发给下属的各个部门；以使各个部门基于所述数据标准将对应的源数据库中的数据转换为符合所述数据标准的待汇聚数据，以及将对应的汇聚编码与待汇聚数据进行绑定。
在本说明书中，下级数据平台如果下属有至少一个部门时，还需要将数据汇聚任务拆分给各个部门，具体可以创建与各个部门对应的数据汇聚子任务；由于数据汇聚子任务中同样包括上级数据平台指定的数据标准，因此，各个部门可以基于分配到的数据汇聚子任务中的数据标准，将本地数据库中的数据转换为符合该数据标准的待汇聚数据。
在本说明书中，为了避免数据汇聚过程中同平台中的不同部门之间数据冲突，数据汇聚平台默认开启“汇聚编码”功能，这样在下发数据汇聚任务时可以自动生成各个部门对应的汇聚编码。
在一示例性的实施例中，所述汇聚编码包括所述下级数据平台的平台标识和部门的部门标识构成的唯一标识。例如，汇聚编码(12位)＝下级数据平台的UUID(8位)+部门ID(4位)。这里，UUID可以作为平台标识使用，部门ID可以作为部门标识使用。
如果各部门存在能够用于数据汇聚的唯一标识且不会导致数据冲突，那么也可以关闭数据汇聚平台的“汇聚编码”功能。
这里以开启“汇聚编码”功能为例，假设下发数据汇聚任务到下级数据平台的2个部门如下表2所示：
部门 converge_code(汇聚编码)
部门1 00000001-0001
部门2 00000001-0002
表2
其中，下级数据平台的平台标识为“00000001”，部门1的部门标识为“0001”，部门2的部门标识为“0002”。
进一步的，部门1提供的待汇聚数据可以关联汇聚编码00000001-0001，而部门2提供的待汇聚数据可以关联汇聚编码00000001-0002；这样即使部门1和部门2存在完全相同的待汇聚数据，也可以根据关联的汇聚编码进行区分，而不会引起数据冲突。
如此，通过汇聚编码可以避免数据汇聚过程中同平台中的不同部门之间数据冲突。
步骤730：向所述上级数据平台的级联模块发送预设通知，以使所述上级数据平台通过所述级联模块从所述源数据库中将已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中。
当下级数据平台将本地的源数据库中的数据转换为符合数据标准的待汇聚数据之后，可以向上级数据平台的级联模块发送预设通知，以通知上级数据平台本下级数据平台已经准备完毕可以进行数据汇聚。
关于所述上级数据平台通过所述级联模块从所述源数据库中将已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中，可以参考前述图5相关的实施例，这里不再进行赘述。
在本说明书中，可以根据实际需求中数据平台层级的不同，将级联模块的级联方式分为两级级联和多级级联。
其中两级级联可以是指上级数据平台和下级数据平台的级联，这样只有两个层级的数据平台的级联称为两级级联。而多级级联不只有两个层级，例如三层数据平台的三级级联，即上级数据平台与下级数据平台级联，而下级数据平台还与该下级数据平台的下级数据平台级联。
下面可以参考图8所示的两级级联场景下的数据汇聚的示意图。如图8所示，级联模块可以部署到上级数据平台中，以为上级数据平台与下级数据平台之间提供数据交换的服务。
步骤1：上级数据平台A可以创建与下级数据平台B关联的数据汇聚任务，并将该数据汇聚任务同步到级联模块。
步骤2：上级数据平台A通过级联模块将数据汇聚任务下发给下级数据平台B。这样，下级数据平台B就可以根据数据汇聚任务中的数据标准将自己对应的数据库中数据转换为该数据标准的待汇聚数据。
步骤3：级联模块通过下级系统启动数据交换引擎。数据交换引擎根据数据标准的信息项自动在前置库中创建目的表。如果开启有“汇聚编码”服务，则在目的表中自动增加汇聚编码列。
步骤4-步骤5：数据交换引擎从下级数据平台B的源数据库中将已转换为数据标准的待汇聚数据写入到前置库的目的表。
步骤6：数据交换引擎通知下级数据平台B从源数据库到前置库的传输完成。
步骤7：下级数据平台B向上级数据平台A的级联模块发送预设通知；该预设通知中可以包括前置库地址、前置库的目的表、是否启用汇聚编码等信息。
步骤8：上级数据平台A通过级联模块启动数据交换引擎。响应于步骤7的预设通知，启动数据交换引擎准备将前置库中待汇聚数据传输到上级数据平台A对应的目的数据库。如果启用汇聚编码，数据交换引擎会在目的数据库的目的表中增加汇聚编码列。
步骤9-步骤10：数据交换引擎将前置库中存储的已转换为数据标准的待汇聚数据写入到上级数据平台A的目的数据库中。
如果上级数据平台A创建的数据汇聚任务配置为周期自动调度，则数据交换引擎将以指定周期将下级数据平台B的源数据库中的待汇聚数据传输到前置库中，即图8中步骤4-步骤5，后续步骤6-10相同，这里不再进行赘述。
接下来请参考图9所示的多级级联场景下的数据汇聚的示意图。多级级联场景下的数据汇聚流程与两级级联场景下的数据汇聚流程类似：数据交换引擎在完成从下级数据平台的源数据库中将待汇聚数据传输到前置库后，通知下级数据平台数据传输完成，以及下级数据平台向上级数据平台的级联模块发送预设通知，上级数据平台则通过级联模块启动数据交换引擎将数据从下级数据平台的前置库传输到本级数据平台的前置库中。
例如，第三级的数据平台C作为数据平台B的下级数据平台时，数据交换引擎将数据平台C的源数据库的待汇聚数据传输到前置库(即图9中的步骤6-7)后，数据平台C可以通过级联模块通知上级的数据平台B(即图9中的步骤9)；进而第二级的数据平台B通过级联模块启动数据交换引擎将待汇聚数据从数据平台C的前置库传输到数据平台B的前置库中(即图9中的步骤11-12)；而第二级的数据平台B作为数据平台A的下级平台时，数据交换引擎在完成将待汇聚数据从数据平台C的前置库传输到数据平台B的前置库后，数据平台B可以通过级联模块通知上级的平台数据A(即图9中的步骤14)；进而第一级的数据平台A通过级联模块启动数据交换引擎将待汇聚数据从数据平台B的前置库传输到数据平台A的目的数据库中(即图9中的步骤16-步骤17)。
综上所述，本说明书实施例通过新增级联模块实现不同层级的平台之间的数据汇聚。 具体地，通过在上级数据平台中部署级联模块，从而使得上级数据平台可以通过级联模块向各个下级数据平台下发包含数据标准的数据汇聚任务，并在接收到下级数据平台向该级联模块发送的预设通知时，通过级联模块从下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到上级数据平台的目的数据库中。
一方面，针对上级数据平台提供自定义数据标准的功能；通过上级数据平台定义的数据标准，使得下级数据平台可以提供符合该数据标准的待汇聚数据；由于在进行数据汇聚之前的各个待汇聚数据都是符合相同的数据标准，数据质量较高且无需进行额外的数据转换，因此可以提高数据汇聚效率。
另一方面，通过设置前置库，先将下级数据平台的源数据库中的待汇聚数据写入前置库，再将前置库中的待汇聚数据写入上级数据平台的目的数据库。如此，避免了下级平台中源数据库暴漏在外导致的数据安全风险；以及由于无需开通源数据库到上级平台的网络策略，因此可以降低实施难度。
请参见图10，图10是一示例性的实施例示出的一种服务处理装置所在电子设备的硬件结构图。在硬件层面，该设备包括处理器1002、内部总线1004、网络接口1006、内存1008以及非易失性存储器1010，当然还可能包括其他业务所需要的硬件。本说明书一个或多个实施例可以基于软件方式来实现，比如由处理器1002从非易失性存储器1010中读取对应的计算机程序到内存1008中然后运行。当然，除了软件实现方式之外，本说明书一个或多个实施例并不排除其他实现方式，比如逻辑器件抑或软硬件结合的方式等等，也就是说以下处理流程的执行主体并不限定于各个逻辑单元，也可以是硬件或逻辑器件。
请参见图11，图11是一示例性的实施例示出的一种服务处理装置的框图。该服务处理装置可以应用于图10所示的电子设备中，以实现本说明书的技术方案。其中，上述服务处理装置可以包括：请求接收单元1102，用于接收目标任务请求；关系查询单元1104，用于在所述目标任务请求为下级的数据平台针对在本级的数据平台上已注册的目标服务的服务调用请求的情况下，其中，所述服务调用请求包括所述目标服务的服务标识以及与所述目标服务相关的服务调用参数，响应于所述服务调用请求，查询所述级联模块中维护的在本级的数据平台上已注册的服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；级联调用单元1106，用于将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
在本实施例中，所述多级的数据平台包括至少一级中心数据平台和至少一级分支数据平台；其中所述中心数据平台级联了下级的数据平台；所述分支数据平台未级联下级的数据平台；所述本级的数据平台为本级的中心数据平台。
在本实施例中，所述本级的中心数据平台与下级的分支数据平台和/或下级的中心数据平台进行级联。
在本实施例中，所述中心数据平台的所述级联模块包括：用于对与所述中心数据平台级联的下级的数据平台进行管理的平台管理模块；所述装置还包括：平台注册单元，用于获取用于在所述本级的中心数据平台上注册与所述本级的中心数据平台级联的下级的数据平台的平台级联请求；所述平台级联请求包括待注册的下级的数据平台的标识信息；响应于所述平台级联请求，调用所述平台管理模块，生成所述本级的中心数据平台的标识信息与所述待注册的下级的数据平台的标识信息之间的级联关系，并将所述级联关系在所述平台管理模块中进行维护；以及，为所述待注册的下级的数据平台生成与所述本级的中心数据平台进行级联的级联配置信息，并将所述级联配置信息发送至所述待注册的下级的数据平台，以由所述待注册的下级的数据平台基于所述级联配置信息完成与所述本级的中心数据平台之间的级联配置。
在本实施例中，所述数据平台的所述级联模块包括：用于管理在该数据平台上已注册的服务的服务管理模块，所述装置还包括：服务注册单元，用于响应于获取用于在所述本级的数据平台上注册服务的服务注册请求，调用所述服务管理模块，由所述服务管理模块基于所述服务注册请求在所述本级的数据平台上注册服务，并将注册的所述服务 的服务标识与所述服务的服务调用接口的对应关系在所述服务管理模块中进行维护。
在本实施例中，级联调用单元，具体用于调用所述服务管理模块，由所述服务管理模块基于所述服务注册请求在所述本级的数据平台上注册服务，并查询所述平台管理模块维护的所述级联关系中与所述本级的中心数据平台具有级联关系的全部下级的数据平台；响应于获取到在与所述本级的数据平台具有级联关系的下级的数据平台中，具有针对在所述本级的数据平台上所述服务的调用权限的数据平台的集合，在所述服务管理模块中维护所述服务与数据平台的集合的对应关系，以完成在所述本级的数据平台上针对所述服务的服务注册。
在本实施例中，所述数据平台的所述级联模块包括：用于针对在该数据平台上已注册的服务发起服务调用的服务代理模块；所述级联调用单元，具体用于响应于所述服务调用请求，调用所述服务代理模块查询所述服务管理模块维护的所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；由所述服务代理模块将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
在本实施例中，所述关系查询单元具体用于，响应于所述服务调用请求，调用所述服务代理模块，查询所述服务管理模块维护的所述服务与数据平台的集合的对应关系，确定所述下级的数据平台是否具有针对所述目标服务的调用权限；如果是，进一步查询所述服务管理模块维护的所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口。
在本实施例中，所述装置还包括结果返回单元：所述服务代理模块获取所述下级的数据平台针对所述目标服务的级联调用的调用结果，并将获取到的调用结果返回至所述下级的数据平台。
在本实施例中，所述数据服务，包括以下至少一个：目录共享服务，接口资源共享服务，数据资源共享服务。
上述装置中各个单元的功能和作用的实现过程具体详见上述方法中对应步骤的实现过程，在此不再赘述。
请参见图12，为本说明书一实施例提供的服务处理装置1200的模块图，所述装置对应了图5所示实施例，应用于多级数据平台中的上级数据平台，所述上级数据平台对应于至少一个下级数据平台，所述上级数据平台中部署有级联模块，所述级联模块用于进行不同层级的数据平台间的数据交互；所述装置包括：创建单元1210，响应于数据汇聚任务的创建请求，根据所述创建请求中指定的目标下级数据平台和数据标准，创建与所述目标下级数据平台关联的数据汇聚任务；其中，所述数据汇聚任务中包括所述数据标准；下发单元1220，通过所述级联模块将所述数据汇聚任务下发给所述目标下级数据平台；汇聚单元1230，在接收到所述目标下级数据平台向所述级联模块发送的预设通知的情况下，通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中。
可选的，所述级联模块中维护有所述至少一个下级数据平台的通信参数，所述级联模块通过所述通信参数建立与对应的下级数据平台的通信连接，并通过所述通信连接传输数据。
可选的，所述下发单元1220，进一步包括：查询子单元，响应于所述目标下级数据平台向所述级联模块发起的定时轮询请求，查询是否存在与所述目标下级数据平台关联的数据汇聚任务；下发子单元，如果存在，通过所述级联模块将查询到的数据汇聚任务下发给所述目标下级数据平台。
可选的，所述数据标准包括用于定义数据的信息项；所述信息项包括信息项名称、数据类型、数据长度、描述中的至少一种；所述数据标准用于将下级数据平台中其它数据标准的数据转换为所述数据标准的待汇聚数据。
可选的，所述汇聚单元1230，进一步包括：第一写入子单元，通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到预设的前置库，并将所述数据汇聚任务的任务状态更新为完成；第二写入子单元，在所 有目标下级数据平台关联的数据汇聚任务的任务状态均完成的情况下，通过所述级联模块将所述前置库中存储的所有目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中。
可选的，所述第一写入子单元，进一步包括通过所述级联模块启动数据交换引擎，以基于所述数据交换引擎从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入预设的到前置库；所述第二写入子单元，进一步包括通过所述级联模块启动所述数据交换引擎，基于所述数据交换引擎将所述前置库中存储的所述目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述上级的数据平台的目的数据库中。
请参见图13，为本说明书一实施例提供的服务处理装置1300的模块图，所述装置对应了图8所示实施例，应用于多级数据平台中的与上级数据平台对应的下级数据平台，所述上级数据平台中部署有级联模块，所述级联模块用于进行不同层级的数据平台间的数据交互；所述装置包括：获取单元1310，获取上级数据平台通过所述级联模块下发的数据汇聚任务；其中，所述数据汇聚任务中包括所述上级数据平台指定的数据标准；转换单元1320，响应于所述数据汇聚任务，将所述下级数据平台的源数据库中的数据转换为符合所述数据标准的待汇聚数据；汇聚单元1330，向所述上级数据平台的级联模块发送预设通知，以使所述上级数据平台通过所述级联模块从所述源数据库中将已转换为所述数据标准的待汇聚数据写入到所述上级数据平台的目的数据库中。
可选的，所述级联模块中维护有所述下级数据平台的通信参数，所述级联模块通过所述通信参数建立与所述下级数据平台的通信连接，并通过所述通信连接传输数据。
可选的，所述获取单元1310，进一步包括：查询子单元，向所述上级数据平台的级联模块发起定时轮询请求，查询所述上级数据平台中是否存在与所述下级数据平台关联的数据汇聚任务；接收子单元，接收所述上级数据平台通过所述级联模块下发的查询到的数据汇聚任务。
可选的，所述转换单元1320，进一步包括：在所述下级数据平台包含一个或多个不同部门的情况下，创建与下属的各个部门一一对应的汇聚编码和包含所述数据标准的数据汇聚子任务，并将所述数据汇聚子任务和汇聚编码分发给下属的各个部门；以使各个部门基于所述数据标准将对应的源数据库中的数据转换为符合所述数据标准的待汇聚数据，以及将对应的汇聚编码与待汇聚数据进行绑定。
可选的，所述汇聚编码包括所述下级数据平台的平台标识和部门的部门标识构成的唯一标识。
可选的，所述数据标准包括用于定义数据的信息项；所述信息项包括信息项名称、英文名称、数据类型、数据长度、描述中的至少一种；所述数据标准用于将下级数据平台中其它数据标准的数据转换为所述数据标准的待汇聚数据。
对于装置实施例而言，由于其基本对应于方法实施例，所以相关之处参见方法实施例的部分说明即可。以上所描述的装置实施例只是示意性的，其中所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部模块来实现本说明书方案的目的。本领域普通技术人员在不付出创造性劳动的情况下，即可以理解并实施。
本说明书还提供了一种计算机可读存储介质的实施例。所述计算机可读存储介质存储有机器可读指令，所述机器可读指令在被处理器调用和执行时，可以实现本说明书中任意一个实施例提供的所述服务处理方法。
本说明书实施例提供的计算机可读存储介质具体可以包括但不限于任何类型的盘(包括软盘、硬盘、光盘、CD-ROM、和磁光盘)、ROM(Read-Only Memory，只读存储器)、RAM(Random Access Memory，随机存储器)、EPROM(Erasable Programmable Read-Only Memory，可擦写可编程只读存储器)、EEPROM(Electrically Erasable Programmable Read-Only Memory，电可擦可编程只读存储器)、闪存、磁性卡片或光纤卡片。也就是，可读存储介质包括可以存储或传输信息的可读介质。
本说明书还提供了一种级联系统的实施例。所述级联系统包括多级数据平台；所述多级数据平台包括至少一级中心数据平台和至少一级分支数据平台；所述中心数据平台级联了下级的数据平台；所述分支数据平台未级联下级的数据平台；各个数据平台中均部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互。所述级联系统用于执行本说明书中任意一个实施例提供的服务处理方法。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机，计算机的具体形式可以是个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件收发设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任意几种设备的组合。
在一个典型的配置中，计算机包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带、磁盘存储、量子存储器、基于石墨烯的存储介质或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在本说明书一个或多个实施例中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本说明书一个或多个实施例。在本说明书一个或多个实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本说明书一个或多个实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本说明书一个或多个实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
以上所述仅为本说明书一个或多个实施例的较佳实施例而已，并不用以限制本说明书一个或多个实施例，凡在本说明书一个或多个实施例的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本说明书一个或多个实施例保护的范围之内。

Claims (20)

  1. 一种服务处理方法，其特征在于，所述方法应用于多级数据平台中的任一级数据平台；所述数据平台中部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互；所述方法包括：
    接收目标任务请求；
    在所述目标任务请求为下级的数据平台针对在本级的数据平台上已注册的目标服务的服务调用请求的情况下，其中，所述服务调用请求包括所述目标服务的服务标识以及与所述目标服务相关的服务调用参数，
    响应于所述服务调用请求，查询所述级联模块中维护的在本级的数据平台上已注册的服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；
    将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
  2. 根据权利要求1所述的方法，其特征在于，所述多级数据平台包括至少一级中心数据平台和至少一级分支数据平台；其中所述中心数据平台级联了下级的数据平台；所述分支数据平台未级联下级的数据平台；所述本级的数据平台为本级的中心数据平台；
    所述本级的中心数据平台与下级的分支数据平台和/或下级的中心数据平台进行级联。
  3. 根据权利要求2所述的方法，其特征在于，所述中心数据平台的所述级联模块包括：用于对与所述中心数据平台级联的下级的数据平台进行管理的平台管理模块；所述方法还包括：
    获取用于在所述本级的中心数据平台上注册与所述本级的中心数据平台级联的下级的数据平台的平台级联请求；所述平台级联请求包括待注册的下级的数据平台的标识信息；
    响应于所述平台级联请求，调用所述平台管理模块，生成所述本级的中心数据平台的标识信息与所述待注册的下级的数据平台的标识信息之间的级联关系，并将所述级联关系在所述平台管理模块中进行维护；以及，
    为所述待注册的下级的数据平台生成与所述本级的中心数据平台进行级联的级联配置信息，并将所述级联配置信息发送至所述待注册的下级的数据平台，以由所述待注册的下级的数据平台基于所述级联配置信息完成与所述本级的中心数据平台之间的级联配置。
  4. 根据权利要求1至3任意一项所述的方法，其特征在于，所述数据平台的所述级联模块包括：用于管理在该数据平台上已注册的服务的服务管理模块；所述方法还包括：
    响应于获取用于在所述本级的数据平台上注册服务的服务注册请求，调用所述服务管理模块，由所述服务管理模块基于所述服务注册请求在所述本级的数据平台上注册服务，并将注册的所述服务的服务标识与所述服务的服务调用接口的对应关系在所述服务管理模块中进行维护。
  5. 根据权利要求4所述的方法，其特征在于，所述调用所述服务管理模块，由所述服务管理模块基于所述服务注册请求在所述本级的数据平台上注册服务，包括：
    调用所述服务管理模块，由所述服务管理模块基于所述服务注册请求在所述本级的数据平台上注册服务，并查询所述平台管理模块维护的所述级联关系中与所述本级的数据平台具有级联关系的全部下级的数据平台；
    响应于获取到在与所述本级的数据平台具有级联关系的下级的数据平台中，具有针对在所述本级的数据平台上所述服务的调用权限的数据平台的集合，在所述服务管理模块中维护所述服务与所述数据平台的集合的对应关系，以完成在所述本级的数据平台上针对所述服务的服务注册。
  6. 根据权利要求5所述的方法，其特征在于，所述数据平台的所述级联模块包括：用于针对在该数据平台上已注册的服务发起服务调用的服务代理模块；
    所述响应于所述服务调用请求，查询所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口，包括：
    响应于所述服务调用请求，调用所述服务代理模块查询所述服务管理模块维护的所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；
    所述将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用，包括：
    由所述服务代理模块将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
  7. 根据权利要求6所述的方法，其特征在于，所述响应于所述服务调用请求，调用所述服务代理模块查询所述服务管理模块维护的所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口，包括：
    响应于所述服务调用请求，调用所述服务代理模块，查询所述服务管理模块维护的所述服务与所述数据平台的集合的对应关系，确定所述下级的数据平台是否具有针对所述目标服务的调用权限；
    如果是，进一步查询所述服务管理模块维护的所述服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口。
  8. 根据权利要求6所述的方法，其特征在于，所述方法还包括：
    所述服务代理模块获取所述下级的数据平台针对所述目标服务的级联调用的调用结果，并将获取到的调用结果返回至所述下级的数据平台。
  9. 根据权利要求1至8任意一项所述的方法，其特征在于，所述服务包括以下至少一个：目录共享服务，接口资源共享服务，数据资源共享服务。
  10. 根据权利要求1所述的方法，其特征在于，在所述目标任务请求为针对数据汇聚任务的创建请求的情况下，所述方法还包括：
    响应于所述数据汇聚任务的创建请求，根据所述创建请求中指定的目标下级数据平台和数据标准，创建与所述目标下级数据平台关联的数据汇聚任务；其中，所述数据汇聚任务中包括所述数据标准；
    通过所述级联模块将所述数据汇聚任务下发给所述目标下级数据平台；
    在接收到所述目标下级数据平台向所述级联模块发送的预设通知的情况下，通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中。
  11. 根据权利要求10所述的方法，其特征在于，所述级联模块中维护有各个下级的数据平台的通信参数，所述级联模块通过所述通信参数建立与所述下级的数据平台的通信连接，并通过所述通信连接传输数据。
  12. 根据权利要求10所述的方法，其特征在于，所述通过所述级联模块将所述数据汇聚任务下发给所述目标下级数据平台，包括：
    响应于所述目标下级数据平台向所述级联模块发起的定时轮询请求，查询是否存在与所述目标下级数据平台关联的数据汇聚任务；
    如果存在，通过所述级联模块将查询到的数据汇聚任务下发给所述目标下级数据平台。
  13. 根据权利要求10所述的方法，其特征在于，所述数据标准包括用于定义数据的信息项；所述信息项包括信息项名称、数据类型、数据长度、描述中的至少一种；
    所述数据标准用于将下级的数据平台中其它数据标准的数据转换为所述数据标准的待汇聚数据。
  14. 根据权利要求10所述的方法，其特征在于，所述通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中，包括：
    通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到预设的前置库，并将所述数据汇聚任务的任务状态更新为完成；
    在所有目标下级数据平台关联的数据汇聚任务的任务状态均完成的情况下，通过所述级联模块将所述前置库中存储的所有目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中。
  15. 根据权利要求14所述的方法，其特征在于，所述通过所述级联模块从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入到预设的前置库，包括：
    通过所述级联模块启动数据交换引擎，以基于所述数据交换引擎从所述目标下级数据平台的源数据库中将已转换为所述数据标准的待汇聚数据写入预设的到前置库；
    所述通过所述级联模块将所述前置库中存储的所述目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中，包括：
    通过所述级联模块启动所述数据交换引擎，基于所述数据交换引擎将所述前置库中存储的所述目标下级数据平台提供的已转换为所述数据标准的待汇聚数据写入到所述本级的数据平台的目的数据库中。
  16. 一种服务处理方法，其特征在于，所述方法应用于多级数据平台中的任一级数据平台；所述数据平台中部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互：所述方法包括：
    获取上级的数据平台通过所述级联模块下发的数据汇聚任务；其中，所述数据汇聚任务中包括所述上级的数据平台指定的数据标准；
    响应于所述数据汇聚任务，将本级的数据平台的源数据库中的数据转换为符合所述数据标准的待汇聚数据；
    向所述上级的数据平台的所述级联模块发送预设通知，以使所述上级的数据平台通过所述级联模块从所述源数据库中将已转换为所述数据标准的待汇聚数据写入到所述上级的数据平台的目的数据库中。
  17. 一种级联系统，其特征在于，所述级联系统被构造为执行如权利要求1至15任意一项或如权利要求16所述的方法；
    其中，所述级联系统包括多级数据平台；所述多级数据平台包括至少一级中心数据平台和至少一级分支数据平台；所述中心数据平台级联了下级的数据平台；所述分支数据平台未级联下级的数据平台；各个数据平台中均部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互。
  18. 一种服务处理装置，其特征在于，所述装置应用于多级数据平台中的任一级数据平台；所述数据平台中部署有级联模块，所述级联模块用于进行不同层级的数据平台之间的数据交互；所述装置包括：
    请求接收单元，用于接收目标任务请求；
    关系查询单元，用于在所述目标任务请求为下级的数据平台针对在本级的数据平台上已注册的目标服务的服务调用请求的情况下，其中，所述服务调用请求包括所述目标服务的服务标识以及与所述目标服务相关的服务调用参数，响应于所述服务调用请求，查询所述级联模块中维护的在本级的数据平台上已注册的服务的服务标识和所述服务的服务调用接口的对应关系，确定与所述目标服务的服务标识对应的服务调用接口；
    级联调用单元，用于将所述服务调用参数提交至查询到的所述服务调用接口，以发起所述下级的数据平台针对所述目标服务的级联调用。
  19. 一种电子设备，其特征在于，包括通信接口、处理器、存储器和总线，所述通信接口、所述处理器和所述存储器之间通过总线相互连接；
    所述存储器中存储机器可读指令，所述处理器通过调用所述机器可读指令，执行权利要求1至15任一项或权利要求16所述的方法。
  20. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质存储有机器可读指令，所述机器可读指令在被处理器调用和执行时，实现权利要求1至15任一项或权利要求16所述的方法。
PCT/CN2022/143788 2022-05-31 2022-12-30 服务处理方法、装置、级联系统、电子设备及存储介质 WO2023231413A1 (zh)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210612887.4A CN115002228B (zh) 2022-05-31 2022-05-31 服务级联调用方法、装置、电子设备及存储介质
CN202210612887.4 2022-05-31
CN202211191697.6A CN115481188A (zh) 2022-09-28 2022-09-28 数据汇聚方法及装置、电子设备
CN202211191697.6 2022-09-28

Publications (1)

Publication Number Publication Date
WO2023231413A1 true WO2023231413A1 (zh) 2023-12-07

Family

ID=89026875

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/143788 WO2023231413A1 (zh) 2022-05-31 2022-12-30 服务处理方法、装置、级联系统、电子设备及存储介质

Country Status (1)

Country Link
WO (1) WO2023231413A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140244809A1 (en) * 2011-11-04 2014-08-28 Huawei Technologies Co., Ltd. Service configuration method and apparatus
CN113094393A (zh) * 2021-03-16 2021-07-09 杭州数梦工场科技有限公司 数据汇聚方法及装置、电子设备
CN113472781A (zh) * 2021-06-30 2021-10-01 平安证券股份有限公司 一种服务获取方法、服务器及计算机可读存储介质
CN113760398A (zh) * 2020-09-29 2021-12-07 北京沃东天骏信息技术有限公司 接口调用方法、服务器、系统以及存储介质
CN114285852A (zh) * 2021-12-28 2022-04-05 杭州数梦工场科技有限公司 基于多级服务平台的服务调用方法及装置
CN115002228A (zh) * 2022-05-31 2022-09-02 杭州数梦工场科技有限公司 服务级联调用方法、装置、电子设备及存储介质
CN115481188A (zh) * 2022-09-28 2022-12-16 杭州数梦工场科技有限公司 数据汇聚方法及装置、电子设备

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140244809A1 (en) * 2011-11-04 2014-08-28 Huawei Technologies Co., Ltd. Service configuration method and apparatus
CN113760398A (zh) * 2020-09-29 2021-12-07 北京沃东天骏信息技术有限公司 接口调用方法、服务器、系统以及存储介质
CN113094393A (zh) * 2021-03-16 2021-07-09 杭州数梦工场科技有限公司 数据汇聚方法及装置、电子设备
CN113472781A (zh) * 2021-06-30 2021-10-01 平安证券股份有限公司 一种服务获取方法、服务器及计算机可读存储介质
CN114285852A (zh) * 2021-12-28 2022-04-05 杭州数梦工场科技有限公司 基于多级服务平台的服务调用方法及装置
CN115002228A (zh) * 2022-05-31 2022-09-02 杭州数梦工场科技有限公司 服务级联调用方法、装置、电子设备及存储介质
CN115481188A (zh) * 2022-09-28 2022-12-16 杭州数梦工场科技有限公司 数据汇聚方法及装置、电子设备

Similar Documents

Publication Publication Date Title
US20230222003A1 (en) System and Method for a Workload Management and Scheduling Module to Manage Access to a Compute Environment According to Local and Non-Local User Identity Information
US11637889B2 (en) Configuration recommendation for a microservice architecture
US8914469B2 (en) Negotiating agreements within a cloud computing environment
US9274848B2 (en) Optimizing cloud service delivery within a cloud computing environment
JP7092736B2 (ja) コンテナオーケストレーションサービスを使用した動的ルーティング
US9800650B2 (en) Resource management for multiple desktop configurations for supporting virtual desktops of different user classes
WO2017157156A1 (zh) 一种用户请求的处理方法和装置
EP2005709A1 (en) Service registry and relevant system and method
US20110258320A1 (en) Elastic management of compute resources between a web server and an on-demand compute environment
CN109889480A (zh) 基于容器和云平台的全国产化融合云平台管理方法及系统
WO2021227999A1 (zh) 云计算服务系统和方法
WO2023040502A1 (zh) 用户服务注册
US10761869B2 (en) Cloud platform construction method and cloud platform storing image files in storage backend cluster according to image file type
WO2020001162A1 (zh) 容器管理方法、装置和设备
Shu-Qing et al. The improvement of PaaS platform
WO2023207082A1 (zh) 负载均衡方法及装置和电子设备
US10152449B1 (en) User-defined capacity reservation pools for network-accessible resources
WO2023040496A1 (zh) 基于区块链的虚拟资源分配
WO2024016547A1 (zh) 一种基于多方协作的数据查询方法及装置
US8978041B2 (en) Service virtualization container
WO2023231413A1 (zh) 服务处理方法、装置、级联系统、电子设备及存储介质
US20210243246A1 (en) Mechanism for a work node scan process to facilitate cluster scaling
WO2023040450A1 (zh) 区块链服务网络的组建
US10587725B2 (en) Enabling a traditional language platform to participate in a Java enterprise computing environment
US10628594B2 (en) Managing multi-tenant systems using object-oriented models

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: 22944714

Country of ref document: EP

Kind code of ref document: A1