CN115002228A - Service cascade calling method and device, electronic equipment and storage medium - Google Patents
Service cascade calling method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN115002228A CN115002228A CN202210612887.4A CN202210612887A CN115002228A CN 115002228 A CN115002228 A CN 115002228A CN 202210612887 A CN202210612887 A CN 202210612887A CN 115002228 A CN115002228 A CN 115002228A
- Authority
- CN
- China
- Prior art keywords
- service
- data platform
- calling
- platform
- level
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 55
- 230000015654 memory Effects 0.000 claims description 28
- 230000004044 response Effects 0.000 claims description 13
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 238000004891 communication Methods 0.000 claims description 4
- 239000003795 chemical substances by application Substances 0.000 description 30
- 238000010586 diagram Methods 0.000 description 18
- 230000008569 process Effects 0.000 description 10
- 230000009471 action Effects 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 238000012545 processing Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- OKTJSMMVPCPJKN-UHFFFAOYSA-N Carbon Chemical compound [C] OKTJSMMVPCPJKN-UHFFFAOYSA-N 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 229910021389 graphene Inorganic materials 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Abstract
The application provides a service cascade calling method, a device, an electronic device and a storage medium, wherein the method comprises the following steps: receiving a service calling request of a lower-level data platform for a registered target service on the data platform of the current level; the service calling request comprises a service identifier of the target service and a service calling parameter related to the target service; responding to the service calling request, inquiring a service identifier of a service and a service calling interface of the service, and determining the service calling interface corresponding to the service identifier of the target service; and submitting the service calling parameter to the inquired service calling interface so as to initiate the cascade calling of the lower-level data platform for the target service. Therefore, the direct calling of the registered service on the upper data platform by the lower data platform can simplify the cascade calling of the service on the upper data platform by the lower data platform.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for service cascade call, an electronic device, and a storage medium.
Background
There are multiple levels of mechanisms in the vertical domain industry that have a vertical relationship. For example, the big data industry has department, province, city, county, and multi-level organizations with vertical management relationships. Wherein the multi-level organization can deploy the corresponding data platform. In recent years, with the continuous development of the industry in the vertical field of the internet, a scene that an upper-level platform provides various services to a lower-level platform exists. Various kinds of information can be shared in the multi-level data platform through various kinds of services. The various types of information may include data resources, catalogs, etc. For example, directories may be shared between data platforms such as department, province, city, county, etc. via a directory sharing service.
However, since each information sharing service needs to be used differently, in a conventional data platform, an upper level data platform and a lower level data platform need to negotiate a sharing mode for each information sharing service, for example, to implement the directory sharing service through a offline mode, such as sending through mail and file transmission, while implementing the data resource sharing requires the upper level data platform to package the data resource and then place the data resource on a sharing server, and then the lower level data platform obtains the data resource through the sharing server.
Therefore, when the traditional data platform realizes the information sharing service, each service needs to negotiate a sharing mode respectively, so that the cost is high, the construction period is long, and the maintenance is complex.
Disclosure of Invention
The application provides a service cascade calling method which is applied to any one stage of data platform in a multi-stage data cascade platform; the data platform maintains the corresponding relation between the service identification of the registered service on the data platform and the service calling interface of the service; the method comprises the following steps:
receiving a service calling request of a lower-level data platform for a registered target service on the data platform of the current level; the service calling request comprises a service identifier of the target service and a service calling parameter related to the target service;
responding to the service calling request, inquiring the corresponding relation between the service identifier of the service and the service calling interface of the service, and determining the service calling interface corresponding to the service identifier of the target service;
and submitting the service calling parameter to the inquired service calling interface so as to initiate the cascade calling of the lower-level data platform for the target service.
Optionally, the multi-stage data platform includes at least one stage of central data platform and at least one stage of branch data platform; wherein, the central data platform is cascaded with a subordinate data platform; the branch data platform is not cascaded with a lower-level data platform; the data platform of the current level is a central data platform of the current level.
Optionally, the central data platform of the current stage is cascaded with the branch data platform of the next stage and/or the central data platform of the next stage.
Optionally, the central data platform carries a platform management module for managing a subordinate data platform cascaded with the central data platform; the method further comprises the following steps:
acquiring a platform cascade request for registering a lower-level data platform cascaded with the current-level central data platform on the current-level central data platform; the platform cascade request comprises identification information of a subordinate data platform to be registered;
responding to the platform cascade request, calling the platform management module, generating a cascade relation between the identification information of the current-level central data platform and the identification information of the next-level data platform, and maintaining the cascade relation in the platform management module; and the number of the first and second groups,
generating cascade configuration information for the lower-level data platform to be cascaded with the current-level central data, and sending the cascade configuration information to the lower-level data platform, so that the lower-level data platform completes cascade configuration with the current-level central data platform based on the cascade configuration information.
Optionally, the data platform is equipped with a service management module for managing services registered on the data platform; the method further comprises the following steps:
and calling the service management module in response to the service registration request for registering the service on the data platform of the current level, registering the service on the data platform of the current level by the service management module based on the service registration request, and maintaining the corresponding relationship between the service identification of the registered service and the service calling interface of the service in the service management module.
Optionally, the data platform is equipped with a service agent module for initiating a service call for a service registered on the data platform, and in response to the service call request, the data platform queries a correspondence between a service identifier of the service and a service call interface of the service, and determines the service call interface corresponding to the service identifier of the target service, including:
responding to the service calling request, calling the service agent module to inquire the service identification of the service maintained by the service management module and the corresponding relation of the service calling interface of the service, and determining the service calling interface corresponding to the service identification of the target service;
submitting the service calling parameter to the inquired service calling interface so as to initiate the cascade call of the subordinate data platform for the target service, wherein the cascade call comprises the following steps:
and submitting the service calling parameters to the inquired service calling interface by the service agent module so as to initiate the cascade calling of the subordinate data platform for the target service.
Optionally, invoking the service management module, and registering, by the service management module, the service on the data platform of the current stage based on the service registration request includes:
calling the service management module, and registering services on the data platform of the current level by the service agent module based on the service registration request to inquire all lower-level data platforms which have a cascade relationship with the data platform of the current level in the cascade relationship maintained by the platform management module;
in response to acquiring a data platform set with a calling authority for the service on the data platform of the current level in a lower data platform of the current level having a cascade relation, maintaining the data platform set in the service management module to complete service registration for the service on the data platform of the current level; the data platform set comprises at least one data platform with the service calling authority on the data platform of the current level in all lower-level data platforms with the cascade relation of the data platform of the current level.
Optionally, in response to the service invocation request, invoking the service agent module to query a correspondence between the service identifier of the service and the service invocation interface of the service, which is maintained by the service management module, and determining the service invocation interface corresponding to the service identifier of the target service, includes:
responding to the service calling request, calling the service agent module, inquiring the corresponding relation between the service maintained by the service management module and a data platform set, and determining whether the lower-level data platform has the calling authority aiming at the target service;
if yes, further inquiring the corresponding relation between the service identification of the service and the service calling interface of the service, which is maintained by the service management module, and determining the service calling interface corresponding to the service identification of the target service.
Optionally, the method further includes:
and the service agent module acquires a calling result of the lower-level data platform for the cascade calling of the target service and returns the acquired calling result to the lower-level data platform.
Optionally, the service includes at least one of: directory sharing service, interface resource sharing service, and data resource sharing service.
The application also provides a service cascade calling device, which is applied to any one stage data platform in the multi-stage data cascade platforms; the data platform maintains the corresponding relation between the service identification of the registered service on the data platform and the service calling interface of the service; the device comprises:
the request receiving unit is used for receiving a service calling request of a lower-level data platform for a target service registered on the data platform of the current level; the service calling request comprises a service identifier of the target service and a service calling parameter related to the target service;
the relation query unit is used for responding to the service calling request, querying the corresponding relation and determining a service calling interface corresponding to the service identifier of the target service;
and the cascade call unit is used for submitting the service call parameter to the inquired service call interface so as to initiate the cascade call of the subordinate data platform for the target service.
The application also provides an electronic device, which comprises a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are mutually connected through the bus;
the memory stores machine-readable instructions, and the processor executes the method by calling the machine-readable instructions.
The present application also provides a computer readable storage medium having stored thereon machine readable instructions which, when invoked and executed by a processor, implement the above method.
Through the embodiment, any one stage data platform in the multi-stage data cascading platforms can maintain the corresponding relation between the service identification of the service registered on the data platform and the service calling interface of the service, while the lower stage data platform can directly initiate cascading calling aiming at the service to the upper stage data platform when the service registered by the upper stage data platform needs to be called, the upper stage data platform determines the calling interface corresponding to the service based on the maintained corresponding relation between the service identification and the service calling interface of the service, and then submits the relevant service calling parameters to the inquired service calling interface to complete cascading calling aiming at the service.
The corresponding relation between the service identification of the service registered by the upper data platform and the service calling interface is autonomously maintained by the upper data platform, and the service calling interfaces of the services are not exposed to the lower data platform any more, so that the lower data platform can unidirectionally call the service provided by the upper data platform; for a lower-level data platform, cascade call aiming at the service is directly initiated only by a service identifier based on the service; when the corresponding relationship between the service identifier of the service maintained by the upper data platform and the service call interface changes, it is not necessary for the upper data platform to notify the lower data platform of the changed corresponding relationship. Therefore, through the unidirectional calling mode, the sharing mode does not need to be negotiated for each service, and the process of cascade calling of the lower-level data platform to the service on the upper-level data platform is simplified.
Drawings
FIG. 1 is a diagram of a data cascading platform architecture, in accordance with an illustrative embodiment.
FIG. 2 is a flow diagram illustrating a method for service cascading calls in accordance with an exemplary embodiment.
FIG. 3 is another data cascading platform architecture diagram shown in an exemplary embodiment.
FIG. 4 is another data cascading platform architecture diagram shown in an exemplary embodiment.
Fig. 5 is a hardware structure diagram of an electronic device in which a service cascade invocation apparatus is located according to an exemplary embodiment.
Fig. 6 is a block diagram of an apparatus for service cascade invocation in accordance with an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the following briefly describes the related technologies related to the embodiments of the present specification.
Referring to fig. 1, fig. 1 is a diagram illustrating an exemplary embodiment of a multi-level data cascading platform architecture, as shown in fig. 1, the multi-level data cascading platform may include a provincial data platform, a plurality of city data platforms directly connected to the provincial data platform, and a plurality of county data platforms directly connected to the city data platforms.
In practical applications, the superior data platform may need to synchronize directories, data or provide other services to the inferior data platform. For example, a provincial data platform needs to synchronize data with a city data platform, a county data platform needs to query data information through the city data platform, and the like.
When a traditional data platform synchronizes data, a superior level generally needs to pack the data into a file, the file is placed in an upper-level file synchronization server, and a subordinate level obtains the file through the file synchronization server. Moreover, this method can only synchronize data to a specific lower data platform, and is not flexible. Meanwhile, the upper-level data platform provides various services for the lower-level data platform, and when the service state of the upper-level data platform changes, the lower-level data platform needs to be notified step by step, so that the service processing process is complex.
In view of this, the present specification provides a technical solution that, in a scenario of a multi-level data cascade platform, a lower-level data platform can directly invoke a service provided on an upper-level data platform based on a service identifier.
During implementation, a service call request of a lower-level data platform for a target service registered by a user on the data platform of the current level can be received; the service calling request comprises a service identifier of the target service and a service calling parameter related to the target service;
responding to the service calling request, inquiring the corresponding relation, and determining a service calling interface corresponding to the service identifier of the target service;
and submitting the service call parameter to the inquired service call interface so as to initiate the cascade call of the lower-level data platform for the target service.
Therefore, in the technical solution of the present specification, any one of the multiple data cascading platforms may maintain a corresponding relationship between a service identifier of a service registered on the data platform and a service call interface of the service, and when a lower data platform needs to call a service registered on an upper data platform, a cascading call for the service may be directly initiated to the upper data platform, and the upper data platform determines a call interface corresponding to the service based on the maintained corresponding relationship between the service identifier and the service call interface of the service, and then submits a relevant service call parameter to the queried service call interface to complete the cascading call for the service.
The service identification of the service registered by the superior data platform and the corresponding relation of the service calling interface are maintained by the superior data platform independently, the service calling interface of the service is not exposed to the inferior data platform any more, so that the inferior data platform can carry out one-way calling on the service provided by the superior data platform, for the inferior data platform, only the service identification based on the service is needed to directly initiate the cascade calling aiming at the service, and when the corresponding relation between the service identification of the service maintained by the superior data platform and the service calling interface is changed, for the superior data platform, the changed corresponding relation is not needed to be notified to the inferior data platform; therefore, through the unidirectional calling mode, each service does not need to be negotiated with a sharing mode respectively, and the process of cascade calling of the lower-level data platform to the service on the upper-level data platform is simplified.
The present application is described below with reference to specific embodiments and specific application scenarios.
Referring to fig. 2, fig. 2 is a flowchart illustrating a method for a service cascading call applied to any one of the multi-stage data cascading platforms shown in fig. 1 according to an exemplary embodiment;
in this specification, a data platform maintains a corresponding relationship between a service identifier of a service registered on the data platform and a service call interface of the service, where the service identifier may be information such as a service type and a service version. For example, the service type may be a directory sharing service, the service version is v 1.1;
in this specification, a service refers to a data-related service that can be provided by each level of data platform, for example, a data sharing service at an e-government-related data platform, or the like. Specifically, the services may include a directory sharing service, an interface resource sharing service, a data resource sharing service, and the like.
The directory sharing service refers to a service that any one level of data platform can release the directory compiled by the level of data platform to the level of data platform and then is called by other data platforms. The catalog may include catalogs organized based on data resources, catalogs organized based on various types of information sharing services, and the like.
In an embodiment, the subordinate data platform may obtain the directories through a service call interface provided by the superior data platform, so as to synchronize the directories.
For example, 500 existing data sheets of department a of the provincial data platform can be shared to the lower data platform, the department a can compile the 500 data sheets into a data directory through directory services provided by the provincial data platform and issue the data directory to the provincial data platform, and the department B of the first city data platform can acquire the data directory through a service call interface provided by the provincial data platform and further acquire a required data sheet according to the data directory.
Correspondingly, the interface resource sharing service refers to that the data platform at any level can issue the interface resource provided by the data platform to the data platform at the level, where the interface resource refers to an application program interface that the data platform can provide externally, such as a data query interface, a data table update interface, and the like.
In an embodiment, the lower level data platform may obtain the interface resources through a service call interface provided by the upper level data platform, and may directly use the interface resources to perform a query action or an update action in the application program.
For example, the department a of the provincial data platform may issue an externally provided data table query interface to the provincial data platform, and the department B of the first urban data platform may obtain the data table query interface through a service call interface provided by the provincial data platform, and may perform a corresponding query action according to the data table query interface.
Correspondingly, the data resource sharing service means that the data platform of any level can issue the interface resource provided by the data platform to the data platform of the level, wherein the data resource may refer to a data table, a data file, and a file compression package.
In an embodiment, the lower-level data platform may obtain the data resources through a service call interface provided by the upper-level data platform, and perform synchronization of the data resources.
For example, 500 existing data sheets of department a of the provincial data platform may be shared to the lower-level data platform, and department B of the first urban data platform may directly obtain 500 data sheets through the service call interface provided by the provincial data platform, or may obtain the data directories of 500 data sheets first according to the directory sharing service, and then obtain the required data sheets according to the data directories.
In one embodiment, the multi-level data platform comprises 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 the subordinate data platforms; the branch data platform is not cascaded with the data platform of the next stage. It should be noted that the central data platform of the current stage may be cascaded with the central data platform of the next stage and/or the central data platform of the next stage.
Therefore, firstly, the central data platform can be used as a service cascade unit and cascaded with the lower-level data platform to form a tree-shaped cascade structure, and various services can be shared through the central data platform; secondly, a flexible and adjustable cascade structure is constructed, namely when the cascade relation with a lower-level data platform is changed according to requirements, the cascade relation in the central data platform can be adjusted, and the method is convenient and fast.
For example, referring to fig. 3, fig. 3 is another data cascading platform architecture diagram shown in an exemplary embodiment, as shown in fig. 3, a lower-level data platform is cascaded by both a provincial-level data platform and a first urban-level data platform, so that the provincial-level data platform and the first urban-level data platform are central data platforms. Correspondingly, the second city-level platform, the first county-level data platform and the second county-level data platform are not cascaded to form a lower-level data platform, so that the second city-level platform, the first county-level data platform and the second county-level data platform are branch data platforms.
In an embodiment, the central data platform is equipped with a platform management module for managing a lower-level data platform cascaded with the central data platform, and when the lower-level data platform needs to be cascaded to the central data platform of the current level, a platform cascade request can be initiated to the central data platform of the current level. The central data platform of the current stage can acquire a platform cascade request for registering a lower-stage data platform cascaded with the central data platform of the current stage on the central data platform of the current stage; the platform cascade request comprises identification information of a subordinate data platform to be registered; the user of the subordinate data platform can actively initiate a platform cascade request to the current-level central data platform, and the newly deployed subordinate data platform can automatically initiate a platform cascade request for the current-level data platform. In the platform cascade request, the identification information of the data platform may specifically be information such as a name of a subordinate data platform, an IP address of the subordinate data platform, and a port address.
Responding to a platform cascade request of a lower-level data platform for the current-level central data platform, the current-level central data platform can call the platform management module to generate a cascade relation between the identification information of the current-level central data platform and the identification information of the lower-level data platform, and the cascade relation is maintained in the platform management module. The cascade relationship is used to describe a logical relationship between the current-level central data platform and the lower-level data platform, and may be, for example, a tree-like data structure, and the lower-level data platform may be a sub-tree of the current-level central data platform.
Meanwhile, the central data platform of the current level generates cascading configuration information for the data platform of the next level, and the cascading configuration information is sent to the data platform of the next level, so that the data platform of the next level completes cascading configuration with the central data platform based on the cascading configuration information. The cascade configuration information may specifically be a data platform account number and corresponding key information or other configuration information for authentication. And the lower-level data platform completes cascade configuration with the central data platform based on the data platform account number and the corresponding key information provided by the central data platform, and the information such as the IP address and the port address of the central data platform.
For example, referring to fig. 3, fig. 3 is another data cascading platform architecture diagram shown in an exemplary embodiment, taking the data cascading platform architecture diagram shown in fig. 4 as an example, when a third county-level data platform needs to be cascaded to a first city-level data platform, the third county-level data platform may initiate a platform cascading request to the first city-level data platform, the first city-level data platform calls a platform management module, generate a cascading relationship between the first city-level data platform and the third county-level data platform, maintain the cascading relationship in the platform management module, and simultaneously generate cascading configuration information for the third county-level data platform to be cascaded with the first city-level data platform, so that the third county-level data platform completes a cascading configuration with the first city-level data platform.
Through the platform management module which is used for managing the cascaded subordinate data platform and is carried on the central data platform, when the subordinate data platform does not need to be cascaded with the data platform, the carrying platform management module can not be deployed any more, and the deployment cost of the data platform is saved.
The above method may comprise the steps of:
In this specification, a target service refers to a service that a subordinate data platform needs to call; for example, the lower level data platform needs to acquire a certain data resource provided by the current level data platform, and the lower level data platform needs to use a certain interface provided by the current level data platform. The lower-level data platform can acquire a plurality of services registered on the data platform of the current level in advance and initiate a service calling request to the data platform of the current level. The service invocation request may include, among other things, a service identification of the target service and service invocation parameters associated with the target service.
For example, taking the data cascade platform architecture diagram shown in fig. 1 as an example, the first market-level data platform needs to obtain 10 data tables from the provincial data platform, and the first market-level data platform may initiate a call request of the data resource sharing service to the provincial data platform; the service call request may include information such as a name and a version number of the data resource sharing service, and the related service call parameter may include a type of the data table and a number of the data table.
In one embodiment, a data platform at any level may host a service management module for managing services registered on the data platform. The data platform of the current stage may respond to a service registration request for registering a service on the data platform of the current stage, and the service management module registers the service on the data platform of the current stage based on the service registration request, and maintains a corresponding relationship between a service identifier of the registered service and a service calling interface of the service in the service management module. The service registration request may be initiated actively by a user, for example, a user of the current-level data platform may synchronize some data to a lower-level data platform, and may initiate the service registration request actively; the service registration request can also be automatically initiated by the application program, for example, when the user uploads some data through the application program on the data platform of the current stage, the service registration request can be automatically initiated by the application program.
For example, a user in a certain department of the provincial data platform can synchronize 500 data tables to a lower-level data platform, so that the user can register a data resource sharing service and provide a corresponding service calling interface. And the provincial data platform responds to a registration request initiated by a user, and maintains the corresponding relation between the service identification of the data resource sharing service and the service calling interface in a service management module of the provincial data platform.
In another embodiment, different invocation rights can be set for the registered service for different data platforms respectively. The data platform of the current stage can call the service management module, the service management module registers service on the data platform based on the service registration request, and the service management module can interact with the platform management module to inquire all subordinate data platforms which have cascade relation with the data platform of the current stage in the cascade relation maintained by the platform management module as the platform management module maintains the cascade relation among all subordinate data platforms which have cascade relation with the data platform of the current stage.
After querying all the subordinate data platforms having a cascade relationship with the current-level data platform in the cascade relationship maintained by the platform management module, a data platform set having a call authority for the service registered on the current-level data platform in the subordinate data platforms may be obtained, and the corresponding relationship between the data platform set and the service is maintained in the service management module, so as to complete the service registration for the service on the current-level data platform. When registering service, a user can actively select one or more lower-level data platforms from all lower-level data platforms which have a cascade relation with the current-level data platform to set calling authority for the registered service, and also can automatically select the lower-level data platforms to set the calling authority by an application program in the current-level data platforms when registering service. The service management module maintains different data platform sets respectively for different registered services, so that different calling authorities are respectively set for different data platforms.
For example, a user in a certain department of the provincial data platform can synchronize 500 data tables to a subordinate data platform, so that the user can register a data resource sharing service and provide a corresponding service calling interface. However, the provincial data platform is cascaded with two municipal data platforms, and 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 calling authority for the data resource sharing service. The provincial data platform can acquire the first city-level platform, maintain the corresponding relation between the data resource sharing service and the first city-level platform in the service management module, and complete service registration for the data service on the provincial data platform.
Correspondingly, the user can also select to set that both the first market-level data platform and the second market-level data platform have the calling authority for the data resource sharing service. The provincial data platform can obtain a data platform set formed by the first municipal platform and the second municipal platform, maintain the corresponding relation between the data resource sharing service and the data platform set in the service management module, and complete service registration for the data service on the provincial data platform.
Step 204, responding to the service calling request, inquiring the corresponding relation between the service identifier of the service and the service calling interface of the service, and determining the service calling interface corresponding to the service identifier of the target service.
In this specification, since the data platform of this level maintains the correspondence between the service identifier of the service registered on the data platform of this level and the service invocation interface of the service, the correspondence between the service identifier of the service and the service invocation interface of the service may be queried, and the service invocation interface corresponding to the service identifier of the target service may be determined based on the service identifier of the target service.
For example, taking the data cascading platform architecture diagram shown in fig. 1 as an example, the first market-level data platform needs to obtain 10 data tables from the provincial data platform, and the first market-level data platform may initiate a data resource sharing service call request to the provincial data platform. And the provincial data platform inquires the corresponding relation between the service identification and the service calling interface of the service according to the name, the version number and other information of the data resource sharing service contained in the calling request, and determines the calling interface of the data resource sharing service.
In an embodiment, the data platform of any stage may further be equipped with a service agent module for initiating service invocation for a service registered on the data platform, the data platform of a lower stage may initiate an invocation request to the service agent module equipped on the data platform of the present stage, and the data platform of the present stage interacts with the service management module through the invocation service agent module to query a correspondence between a service identifier maintained by the service management module and a service invocation interface of the service, and determine the service invocation interface corresponding to the service identifier of the target service.
For example, taking the data cascade platform architecture diagram shown in fig. 1 as an example, the first urban data platform needs to obtain 10 data tables from the provincial data platform, the first urban data platform may initiate a data resource sharing service call request to the service agent module carried by the provincial data platform, the service agent module carried by the provincial data platform interacts with the service management module, and according to information such as the name and version number of the data resource sharing service included in the call request, the corresponding relationship maintained by the service management module is queried, and the call interface of the data resource sharing service is determined.
In another embodiment, the service agent module carried by the data platform of the current stage may further interact with the service management module to determine whether the data platform of the next stage has a service invocation authority for the target service. Specifically, the service agent module is called in response to the service calling request, the service agent module interacts with the service management module to call the service agent module, a corresponding relation between the service maintained by the service management module and a data platform set is inquired, and whether the lower-level data platform has a calling authority for the target service is determined; if so, further interacting with the service management module to inquire the corresponding relation between the service identifier maintained by the service management module and the service calling interface of the service, and determining the service calling interface corresponding to the service identifier of the target service.
For example, in the above example, a user in a department of the provincial data platform may synchronize 500 data tables to a lower level data platform, and set the first city level data platform with the invocation authority of the data resource sharing service. When the first market-level data platform needs to obtain 10 data sheets from the provincial-level data platform, the first market-level data platform can initiate a data resource sharing service calling request to a service agent module carried by the provincial-level data platform, the service agent module carried by the provincial-level data platform can interact with a service management module, the corresponding relation between the data resource sharing service maintained by the service management module and a data platform set is inquired, and the first market-level data platform is determined to have a calling authority for the data resource sharing service. Therefore, the corresponding relation maintained by the service management module can be continuously inquired, and the calling interface of the data resource sharing service is determined.
And step 206, submitting the service call parameter to the queried service call interface so as to initiate a cascade call of the lower-level data platform for the target service.
In this specification, the data platform of this stage may directly submit the service invocation parameter to the service invocation interface corresponding to the target service, so as to initiate the cascade invocation of the data platform of the lower stage for the target service.
For example, taking the data cascade platform architecture diagram shown in fig. 1 as an example, the first market-level data platform needs to obtain 10 data tables from the provincial data platform, after the first market-level data platform can initiate a data resource sharing service call request to the provincial data platform, the provincial data platform queries the service call interface of the corresponding data service, and submits the type of the required data tables, the number of the data tables, and the like as service call parameters to the query call interface of the queried data resource sharing service.
In an embodiment, the data platform of any stage may further carry a service agent module for initiating service call for service registered on the data platform, the data platform of the lower stage may initiate a call request to the service agent module carried on the data platform of the present stage, and the service agent module submits the service call parameter to the service call interface queried to initiate cascade call of the data platform of the lower stage for the target service.
For example, taking the data cascade platform architecture diagram shown in fig. 1 as an example, the first market-level data platform needs to obtain 10 data tables from the provincial data platform, after the first market-level data platform can initiate a data resource sharing service call request to a service agent module carried by the provincial data platform, the service agent module queries the service management module, obtains a service call interface corresponding to the data service, and submits the type of the needed data tables, the number of the data tables, and the like as service call parameters to the call interface of the queried data resource sharing service.
In another embodiment, the service agent module obtains a calling result of the cascade call of the subordinate data platform to the target service, and returns the obtained calling result to the subordinate data platform.
For example, taking the data cascade platform architecture diagram shown in fig. 1 as an example, the first market-level data platform needs to obtain 10 data tables from the provincial data platform, and after the first market-level data platform can initiate a data resource sharing service call request to the service agent module carried by the provincial data platform, the service agent module service call parameters are submitted to the call interface of the queried data resource sharing service, so as to obtain the 10 data tables, and return to the first market-level data platform.
Through the embodiment, any one of the multiple data cascading platforms can maintain the corresponding relation between the service identifier of the service registered on the data platform and the service calling interface of the service, while the lower data platform can directly initiate cascading calling aiming at the service to the upper data platform when the service registered by the upper data platform needs to be called, the upper data platform determines the calling interface corresponding to the service based on the maintained service identifier and the service calling interface corresponding relation of the service, and then submits the relevant service calling parameters to the inquired service calling interface to complete cascading calling aiming at the service.
The service identification of the service registered by the superior data platform and the corresponding relation of the service calling interface are maintained by the superior data platform independently, the service calling interface of the service is not exposed to the inferior data platform any more, so that the inferior data platform can carry out one-way calling on the service provided by the superior data platform, for the inferior data platform, only the service identification based on the service is needed to directly initiate the cascade calling aiming at the service, and when the corresponding relation between the service identification of the service maintained by the superior data platform and the service calling interface is changed, for the superior data platform, the changed corresponding relation is not needed to be notified to the inferior data platform; therefore, through the unidirectional calling mode, each service does not need to be negotiated with a sharing mode respectively, and the process of cascade calling of the lower-level data platform to the service on the upper-level data platform is simplified.
Referring to fig. 5, fig. 5 is a hardware structure diagram of an electronic device where a service cascade invoking device is located according to an exemplary embodiment. At the hardware level, the device includes a processor 502, an internal bus 504, a network interface 506, a memory 508, and a non-volatile memory 510, although other hardware required for the service may also be included. One or more embodiments of the present description may be implemented in software, such as by processor 502 reading corresponding computer programs from non-volatile storage 510 into memory 508 and then running. Of course, besides the software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combination of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Referring to fig. 6, fig. 6 is a block diagram illustrating a service cascade invocation apparatus according to an exemplary embodiment. The service cascade calling device can be applied to the electronic device shown in fig. 5 to implement the technical solution of the present specification. The service cascade calling apparatus may include:
a request receiving unit 602, configured to receive a service invocation request of a lower-level data platform for a target service registered on the current-level data platform; the service calling request comprises a service identifier of the target service and service calling parameters related to the target service;
a relation query unit 604, configured to query the corresponding relation in response to the service invocation request, and determine a service invocation interface corresponding to the service identifier of the target service;
a cascade call unit 606, configured to submit the service call parameter to the queried service call interface, so as to initiate a cascade call of the subordinate data platform for the target service.
In this embodiment, the multi-stage data platform includes at least one stage of central data platform and at least one stage of branch data platform; wherein the central data platform is cascaded with the subordinate data platforms; the branch data platform is not cascaded with a lower-level data platform; the data platform of the current level is a central data platform of the current level.
In this embodiment, the current-stage central data platform is cascaded with the lower-stage branch data platform and/or the lower-stage central data platform.
In this embodiment, the central data platform carries a platform management module for managing a lower-level data platform cascaded with the central data platform; the device further comprises:
a platform registration unit, configured to acquire a platform cascade request for registering, on the current-stage central data platform, a lower-stage data platform cascaded with the current-stage central data platform; the platform cascade request comprises identification information of a subordinate data platform to be registered;
responding to the platform cascade request, calling the platform management module, generating a cascade relation between the identification information of the current-level central data platform and the identification information of the next-level data platform, and maintaining the cascade relation in the platform management module; and the number of the first and second groups,
generating cascade configuration information for the lower-level data platform to be cascaded with the current-level central data, and sending the cascade configuration information to the lower-level data platform, so that the lower-level data platform completes cascade configuration with the current-level central data platform based on the cascade configuration information.
In this embodiment, the data platform is equipped with a service management module for managing services registered on the data platform, and the apparatus further includes:
and the service registration unit is used for responding to a service registration request for registering services on the data platform of the current level, calling the service management module, registering the services on the data platform of the current level by the service management module based on the service registration request, and maintaining the corresponding relation between the registered service identification of the services and the service calling interface of the services in the service management module.
In this embodiment, the cascade call unit is specifically configured to call the service management module, and the service management module registers a service on the data platform of the current stage based on the service registration request and queries all lower-stage data platforms having a cascade relationship with the central data platform of the current stage in the cascade relationship maintained by the platform management module;
in response to acquiring a data platform set with a calling authority for the service on the data platform of the current level in a lower data platform with a cascade relation of the data platform of the current level, maintaining a corresponding relation between the service and the data platform set in the service management module to complete service registration for the service on the data platform of the current level; the data platform set comprises at least one data platform with the service calling authority on the data platform of the current level in all lower-level data platforms with cascade relations of the data platform of the current level.
In this embodiment, the data platform is equipped with a service agent module for initiating a service call for a service registered on the data platform; the cascade call unit is specifically configured to, in response to the service call request, call the service agent module to query a correspondence between a service identifier of the service and a service call interface of the service, which is maintained by the service management module, and determine the service call interface corresponding to the service identifier of the target service; and submitting the service calling parameters to the inquired service calling interface by the service agent module so as to initiate the cascade calling of the subordinate data platform for the target service.
In this embodiment, the relationship query unit is specifically configured to, in response to the service invocation request, invoke the service proxy module, query a corresponding relationship between the service and a data platform set maintained by the service management module, and determine whether the subordinate data platform has an invocation permission for the target service;
if yes, further inquiring the corresponding relation between the service identification of the service and the service calling interface of the service, which is maintained by the service management module, and determining the service calling interface corresponding to the service identification of the target service.
In this embodiment, the apparatus further includes a result returning unit: and the service agent module acquires a calling result of the lower-level data platform for the cascade calling of the target service and returns the acquired calling result to the lower-level data platform.
In this embodiment, the data service includes at least one of: directory sharing service, interface resource sharing service, and data resource sharing service.
The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are only illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.
This specification also provides an embodiment of a computer-readable storage medium. The computer readable storage medium stores machine readable instructions, which when called and executed by a processor, can implement the service cascade calling method provided by any one of the embodiments in this specification.
The computer-readable storage medium provided by the embodiments of the present description may specifically include, but is not limited to, any type of disk (including floppy disks, hard disks, optical disks, CD-ROMs, and magneto-optical disks), ROMs (Read-Only memories), RAMs (Random Access memories), EPROMs (Erasable Programmable Read-Only memories), EEPROMs (Electrically Erasable Programmable Read-Only memories), flash memories, magnetic cards, or optical fiber cards. That is, readable storage media includes readable media that can store or transfer information.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.
Claims (13)
1. A service cascade calling method is characterized in that the method is applied to any one stage data platform in a multi-stage data cascade platform; the data platform maintains the corresponding relation between the service identification of the registered service on the data platform and the service calling interface of the service; the method comprises the following steps:
receiving a service calling request of a lower-level data platform for a registered target service on the data platform of the current level; the service calling request comprises a service identifier of the target service and a service calling parameter related to the target service;
responding to the service calling request, inquiring the corresponding relation between the service identifier of the service and the service calling interface of the service, and determining the service calling interface corresponding to the service identifier of the target service;
and submitting the service call parameter to the inquired service call interface so as to initiate the cascade call of the lower-level data platform for the target service.
2. The method of claim 1, wherein the multi-level data platforms include at least one central data platform and at least one branch data platform; wherein the central data platform is cascaded with a subordinate data platform; the branch data platform is not cascaded with a lower-level data platform; the data platform of the current level is a central data platform of the current level.
3. The method according to claim 2, wherein the current-stage central data platform is cascaded with the subordinate branch data platforms and/or the subordinate central data platforms.
4. The method according to claim 2, wherein the central data platform is loaded with a platform management module for managing a lower data platform cascaded therewith; the method further comprises the following steps:
acquiring a platform cascade request for registering a lower-level data platform cascaded with the current-level central data platform on the current-level central data platform; the platform cascade request comprises identification information of a subordinate data platform to be registered;
responding to the platform cascade request, calling the platform management module, generating a cascade relation between the identification information of the current-level central data platform and the identification information of the next-level data platform, and maintaining the cascade relation in the platform management module; and the number of the first and second groups,
generating cascade configuration information for the lower-level data platform to be cascaded with the current-level central data, and sending the cascade configuration information to the lower-level data platform, so that the lower-level data platform completes cascade configuration with the current-level central data platform based on the cascade configuration information.
5. The method of claim 1, wherein the data platform is loaded with a service management module for managing services registered on the data platform; the method further comprises the following steps:
and calling the service management module in response to the service registration request for registering the service on the data platform of the current level, registering the service on the data platform of the current level by the service management module based on the service registration request, and maintaining the corresponding relation between the registered service identifier of the service and the service calling interface of the service in the service management module.
6. The method of claim 5, wherein said invoking the service management module, registering a service by the service management module on the current-level data platform based on the service registration request, comprises:
calling the service management module, registering services on the data platform of the current stage by the service management module based on the service registration request, and inquiring all lower-stage data platforms which have a cascade relationship with the data platform of the current stage in the cascade relationship maintained by the platform management module;
in response to acquiring a data platform set with a calling authority for the service on the data platform of the current level in a lower data platform with a cascade relation of the data platform of the current level, maintaining a corresponding relation between the service and the data platform set in the service management module to complete service registration for the service on the data platform of the current level; the data platform set comprises at least one data platform with the service calling authority on the data platform of the current level in all lower-level data platforms with cascade relations of the data platform of the current level.
7. The method of claim 6, wherein the data platform is loaded with a service agent module for initiating service calls for services registered on the data platform;
responding to the service calling request, inquiring the corresponding relation between the service identifier of the service and the service calling interface of the service, and determining the service calling interface corresponding to the service identifier of the target service, wherein the method comprises the following steps:
responding to the service calling request, calling the service agent module to inquire the service identification of the service maintained by the service management module and the corresponding relation of the service calling interface of the service, and determining the service calling interface corresponding to the service identification of the target service;
submitting the service calling parameter to the inquired service calling interface so as to initiate the cascade call of the subordinate data platform for the target service, wherein the cascade call comprises the following steps:
and submitting the service calling parameters to the inquired service calling interface by the service agent module so as to initiate the cascade calling of the subordinate data platform for the target service.
8. The method of claim 7, wherein in response to the service invocation request, invoking the service agent module to query a correspondence between the service identifier of the service maintained by the service management module and the service invocation interface of the service, and determining the service invocation interface corresponding to the service identifier of the target service comprises:
responding to the service calling request, calling the service agent module, inquiring the corresponding relation between the service maintained by the service management module and a data platform set, and determining whether the lower-level data platform has the calling authority aiming at the target service;
if yes, further inquiring the corresponding relation between the service identification of the service and the service calling interface of the service, which is maintained by the service management module, and determining the service calling interface corresponding to the service identification of the target service.
9. The method of claim 7, further comprising:
and the service agent module acquires a calling result of the lower-level data platform for the cascade calling of the target service and returns the acquired calling result to the lower-level data platform.
10. The method of claim 1, wherein the service comprises at least one of: directory sharing service, interface resource sharing service, and data resource sharing service.
11. The device for calling the service cascade is characterized in that the device is applied to any one stage of data platform in a multi-stage data cascade platform; the data platform maintains the corresponding relation between the service identification of the registered service on the data platform and the service calling interface of the service; the device comprises:
the request receiving unit is used for receiving a service calling request of a lower-level data platform for a target service registered on the data platform of the current level; the service calling request comprises a service identifier of the target service and a service calling parameter related to the target service;
the relation query unit is used for responding to the service calling request, querying the corresponding relation and determining a service calling interface corresponding to the service identifier of the target service;
and the cascade call unit is used for submitting the service call parameter to the inquired service call interface so as to initiate the cascade call of the subordinate data platform for the target service.
12. An electronic device is characterized by comprising a communication interface, a processor, a memory and a bus, wherein the communication interface, the processor and the memory are connected with each other through the bus;
the memory has stored therein machine-readable instructions, which the processor executes by calling to perform the method of any one of claims 1 to 10.
13. A computer readable storage medium having stored thereon machine readable instructions which, when invoked and executed by a processor, carry out the method of any of claims 1 to 10.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210612887.4A CN115002228B (en) | 2022-05-31 | 2022-05-31 | Service cascade calling method and device, electronic equipment and storage medium |
| PCT/CN2022/143788 WO2023231413A1 (en) | 2022-05-31 | 2022-12-30 | Service processing method, apparatus, cascade system, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210612887.4A CN115002228B (en) | 2022-05-31 | 2022-05-31 | Service cascade calling method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115002228A true CN115002228A (en) | 2022-09-02 |
| CN115002228B CN115002228B (en) | 2023-12-26 |
Family
ID=83032010
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210612887.4A Active CN115002228B (en) | 2022-05-31 | 2022-05-31 | Service cascade calling method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115002228B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023231413A1 (en) * | 2022-05-31 | 2023-12-07 | 杭州数梦工场科技有限公司 | Service processing method, apparatus, cascade system, electronic device and storage medium |
| CN117453257A (en) * | 2023-12-25 | 2024-01-26 | 深圳万物安全科技有限公司 | Upgrading method based on hierarchical management, terminal equipment and readable storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011134318A1 (en) * | 2010-04-30 | 2011-11-03 | 中兴通讯股份有限公司 | Internet of things service architecture and method for realizing internet of things service |
| CN110430196A (en) * | 2019-08-08 | 2019-11-08 | 杭州阿启视科技有限公司 | Video big data cloud platform cascade servers method |
| CN110597739A (en) * | 2019-06-03 | 2019-12-20 | 上海云盾信息技术有限公司 | Configuration management method, system and equipment |
| CN111787082A (en) * | 2020-06-22 | 2020-10-16 | 珠海格力电器股份有限公司 | Method, equipment and system for reporting multi-stage service data |
| CN111885172A (en) * | 2020-07-27 | 2020-11-03 | 高新兴科技集团股份有限公司 | Cross-network platform cascading method, computer storage medium and electronic device |
| CN111953931A (en) * | 2020-06-30 | 2020-11-17 | 视联动力信息技术股份有限公司 | Data sharing method and device and storage medium |
| US20200404027A1 (en) * | 2019-01-02 | 2020-12-24 | Boe Technology Group Co., Ltd. | Network conference management method and apparatus and storage medium, and network conference platform and system |
| WO2021143025A1 (en) * | 2020-01-15 | 2021-07-22 | 平安科技（深圳）有限公司 | Internet-of-things data transmission method and apparatus, and medium and electronic device |
| CN113645251A (en) * | 2021-08-24 | 2021-11-12 | 北京英创思信息技术有限公司 | Data transmission method and device suitable for cross-regional service |
| CN113722114A (en) * | 2020-05-25 | 2021-11-30 | 北京达佳互联信息技术有限公司 | Data service processing method and device, computing equipment and storage medium |
| CN114285852A (en) * | 2021-12-28 | 2022-04-05 | 杭州数梦工场科技有限公司 | Service calling method and device based on multi-stage service platform |
| CN114327941A (en) * | 2021-12-22 | 2022-04-12 | 杭州数梦工场科技有限公司 | Service providing method and device |
| CN114422581A (en) * | 2021-12-22 | 2022-04-29 | 网络通信与安全紫金山实验室 | Service creation method, service creation apparatus, computer device, and storage medium |
-
2022
- 2022-05-31 CN CN202210612887.4A patent/CN115002228B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2011134318A1 (en) * | 2010-04-30 | 2011-11-03 | 中兴通讯股份有限公司 | Internet of things service architecture and method for realizing internet of things service |
| US20200404027A1 (en) * | 2019-01-02 | 2020-12-24 | Boe Technology Group Co., Ltd. | Network conference management method and apparatus and storage medium, and network conference platform and system |
| CN110597739A (en) * | 2019-06-03 | 2019-12-20 | 上海云盾信息技术有限公司 | Configuration management method, system and equipment |
| CN110430196A (en) * | 2019-08-08 | 2019-11-08 | 杭州阿启视科技有限公司 | Video big data cloud platform cascade servers method |
| WO2021143025A1 (en) * | 2020-01-15 | 2021-07-22 | 平安科技（深圳）有限公司 | Internet-of-things data transmission method and apparatus, and medium and electronic device |
| CN113722114A (en) * | 2020-05-25 | 2021-11-30 | 北京达佳互联信息技术有限公司 | Data service processing method and device, computing equipment and storage medium |
| CN111787082A (en) * | 2020-06-22 | 2020-10-16 | 珠海格力电器股份有限公司 | Method, equipment and system for reporting multi-stage service data |
| CN111953931A (en) * | 2020-06-30 | 2020-11-17 | 视联动力信息技术股份有限公司 | Data sharing method and device and storage medium |
| CN111885172A (en) * | 2020-07-27 | 2020-11-03 | 高新兴科技集团股份有限公司 | Cross-network platform cascading method, computer storage medium and electronic device |
| CN113645251A (en) * | 2021-08-24 | 2021-11-12 | 北京英创思信息技术有限公司 | Data transmission method and device suitable for cross-regional service |
| CN114327941A (en) * | 2021-12-22 | 2022-04-12 | 杭州数梦工场科技有限公司 | Service providing method and device |
| CN114422581A (en) * | 2021-12-22 | 2022-04-29 | 网络通信与安全紫金山实验室 | Service creation method, service creation apparatus, computer device, and storage medium |
| CN114285852A (en) * | 2021-12-28 | 2022-04-05 | 杭州数梦工场科技有限公司 | Service calling method and device based on multi-stage service platform |
Non-Patent Citations (1)
| Title |
|---|
| 卢佳河;姜芸;王军;: "基于SOA的多级树结构目录服务模型研究", 测绘与空间地理信息, no. 08 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2023231413A1 (en) * | 2022-05-31 | 2023-12-07 | 杭州数梦工场科技有限公司 | Service processing method, apparatus, cascade system, electronic device and storage medium |
| CN117453257A (en) * | 2023-12-25 | 2024-01-26 | 深圳万物安全科技有限公司 | Upgrading method based on hierarchical management, terminal equipment and readable storage medium |
| CN117453257B (en) * | 2023-12-25 | 2024-03-26 | 深圳万物安全科技有限公司 | Upgrading method based on hierarchical management, terminal equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115002228B (en) | 2023-12-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11626972B2 (en) | Data processing method and apparatus | |
| CN115002228B (en) | Service cascade calling method and device, electronic equipment and storage medium | |
| CN111898139B (en) | Data reading and writing method and device and electronic equipment | |
| CN112380294B (en) | Block chain cross-chain access method and device | |
| CN107018174B (en) | Unitized system service processing method and device and business processing system | |
| CN106878367B (en) | Method and device for realizing asynchronous call of service interface | |
| CN113220717B (en) | Block chain-based data verification method and device and electronic equipment | |
| CN111786984B (en) | Pod communication connection method and device, electronic equipment and storage medium | |
| CN110060153B (en) | Data evidence storage method and system based on multiple block chain networks | |
| CN107203882B (en) | Service processing method and device | |
| WO2023040502A1 (en) | User service registration | |
| CN112400182A (en) | Method and device for executing intelligent contracts in block chain and electronic equipment | |
| WO2020024648A1 (en) | Data processing method and device, client, and server | |
| WO2023207082A1 (en) | Load balance method and apparatus, and electronic device | |
| CN113542435B (en) | User service using method and device | |
| CN111651467A (en) | Block chain link point interface issuing and calling method and device | |
| CN113194143B (en) | Block chain account creating method and device and electronic equipment | |
| WO2023040450A1 (en) | Blockchain service network establishment | |
| CN110837499B (en) | Data access processing method, device, electronic equipment and storage medium | |
| CN114710350B (en) | Method and device for distributing callable resources, electronic equipment and storage medium | |
| CN113205424B (en) | Method and apparatus for deploying and invoking contracts in blockchain | |
| CN111464312B (en) | Method and device for processing account addresses in blockchain and electronic equipment | |
| CN112163035A (en) | Method and device for calling intelligent contract | |
| CN117093419A (en) | Unstructured data storage method and device, electronic equipment and storage medium | |
| CN111506577B (en) | Data operation method and device based on multiple state organization modes on block chain |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |