CN115576706A - Method and device for interfacing with third-party system, electronic equipment and readable medium - Google Patents

Method and device for interfacing with third-party system, electronic equipment and readable medium Download PDF

Info

Publication number
CN115576706A
CN115576706A CN202110686397.4A CN202110686397A CN115576706A CN 115576706 A CN115576706 A CN 115576706A CN 202110686397 A CN202110686397 A CN 202110686397A CN 115576706 A CN115576706 A CN 115576706A
Authority
CN
China
Prior art keywords
docking
interface
party system
docking process
driving
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.)
Pending
Application number
CN202110686397.4A
Other languages
Chinese (zh)
Inventor
许劲松
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Priority to CN202110686397.4A priority Critical patent/CN115576706A/en
Priority to PCT/CN2022/097313 priority patent/WO2022267878A1/en
Publication of CN115576706A publication Critical patent/CN115576706A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/547—Remote procedure calls [RPC]; Web services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer And Data Communications (AREA)
  • Stored Programmes (AREA)

Abstract

The utility model provides a method for docking with a third-party system, which comprises determining a corresponding docking process according to docking process information in a received service call request, wherein the docking process is a service processing process which is configured in advance and is docked with the third-party system; processing the initial to-be-processed service data in the service calling request according to the docking process to obtain a service processing result; the method and the device have the advantages that the butt joint process is configured in advance, the butt joint process is directly effective after configuration, business data processing is achieved according to the butt joint process when the device is in butt joint with a third-party system, the butt joint with the third-party system can be achieved without developing bottom codes, operations such as development, version upgrading, patching, deployment and restarting caused by butt joint are correspondingly omitted, the butt joint period can be shortened, and the butt joint cost is reduced; the method can flexibly deal with the butt joint of any third-party system by configuring the butt joint flow in advance, thereby improving the flexibility and the applicability. The disclosure also provides a docking device, an electronic device and a readable medium.

Description

Method and device for interfacing with third-party system, electronic equipment and readable medium
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for interfacing with a third-party system, an electronic device, and a readable medium.
Background
The south drive of the network arrangement system adopts an adaptation technology to be connected with a third-party system, and aiming at the interface provided by the third-party system, the adaptation interface corresponding to the third-party system is found in the network arrangement system, and then the interfaces are arranged and combined to realize the south drive.
The premise that the technology can be successfully docked at one time is that all the third-party interfaces participating in all docking can find the corresponding adaptive interfaces in the network arranging system. However, in actual docking, due to the fact that the interfaces of each third-party system have factors such as differentiation, privatization, non-standardization, unknown and variability, a considerable part of interfaces cannot find the matched adaptive interfaces in the network arrangement system, and thus the docking cannot be completed. Due to the factors, the docking can be completed only after the development needs to be returned again during docking, the adaptive development work of the corresponding interface is restarted, and the network editing system is redeployed after a series of compiling. Furthermore, the newly developed adapter interface may not be passed through at one time, and needs to be modified again, and then the above operations are repeated for many times. The above operations are the operations of upgrading and patching the traditional software version, and the operations may be repeated for many times to be finally successful, so that the whole docking period is prolonged, the docking cannot be completed quickly, and the docking cost is increased.
Disclosure of Invention
The present disclosure provides a method, an apparatus, an electronic device, and a readable medium for interfacing with a third-party system.
In a first aspect, an embodiment of the present disclosure provides a method for interfacing with a third-party system, including:
acquiring the carried docking process information and initial to-be-processed service data according to the received service calling request;
determining a corresponding docking process according to the docking process information, wherein the docking process is a service processing process which is configured in advance and is docked with a third-party system;
and processing the initial to-be-processed service data according to the docking process to obtain a service processing result.
In some embodiments, the processing the initial to-be-processed service data according to the docking process to obtain a service processing result includes:
and aiming at each step of the docking process, sending the first data generated in the current step to the third-party system, and determining the next step of the docking process according to the second data returned by the third-party system and the current step.
In some embodiments, each step of the docking process is pre-configured with an interface template for defining interface processing content, and the processing the initial to-be-processed service data according to the docking process to obtain a service processing result includes:
converting the butt joint flow into a driving flow, wherein each step of the driving flow corresponds to each step of the butt joint flow one by one;
deploying the driver flow into a driver engine;
and calling each step of the driving flow by using the driving engine, and performing data processing on the initial service data to be processed according to the interface template corresponding to each step to obtain a service processing result.
In some embodiments, said converting said docking procedure to a driving procedure comprises:
and implanting an execution mark into the docking process according to a preset standard, and converting into a generation driving process, wherein the execution mark is used for indicating whether the step is executed successfully or not.
In some embodiments, the step types of the docking process and the driving process include a normal step and a rollback step, each normal step corresponds to a rollback step, a previous step of an nth normal step is an (N-1) th normal step, and a next step of the nth rollback step is an (N-1) th rollback step corresponding to the (N-1) th normal step;
the last step in the docking process and the driving process includes a last normal step and a first rollback step.
In some embodiments, the interface template includes an interface input template and an interface output template, and the sending, for each step of the docking process, the first data generated in the current step to the third-party system for determining a next step of the docking process according to the second data returned by the third-party system and the current step includes:
determining an interface input template and an interface output template corresponding to the current step for each step of the driving process, processing the to-be-processed service data of the current step according to the interface input template to obtain first data, and sending the first data to the third-party system;
processing second data returned by the third-party system according to the interface output template to obtain a service data processing result and an execution mark value of the current step;
and determining the next step of the driving flow according to the value of the execution mark of the current step and the step type.
In some embodiments, the determining the next step of the driving flow according to the value of the execution flag of the current step and the step type includes:
if the value of the execution flag of the current step indicates that the execution is successful and the current step is a normal step, determining that the next step of the driving process is the next normal step of the normal steps;
and if the value of the execution mark of the current step indicates that the execution fails and the current step is a normal step, determining that the next step of the driving process is a rollback step corresponding to the normal step.
In some embodiments, the method further comprises the step of configuring a docking procedure and configuring an interface template, comprising:
configuring a docking process, and respectively configuring an interface template for each step of the docking process.
In some embodiments, the configuration docking process comprises:
if a first butt-joint flow with at least part of the same steps is obtained in a preset first database, modifying the first butt-joint flow to obtain a second butt-joint flow, and configuring the second butt-joint flow;
and if the first butt-joint process with at least part of the same steps is not acquired in a preset first database, establishing a second butt-joint process and configuring the second butt-joint process.
In some embodiments, the configuring an interface template for each step of the docking process separately includes:
for each step of the docking process, if a first interface template with at least part of interface processing contents being the same is obtained in a preset second database, modifying the first interface template to obtain a second interface template of the current step, and configuring the second interface template;
and aiming at each step of the docking process, if the first interface template with at least part of interface processing contents identical is not acquired in a preset second database, establishing a second interface template of the current step, and configuring the second interface template.
In another aspect, an embodiment of the present disclosure further provides a docking apparatus, including an obtaining module, a first processing module, and a second processing module, where the obtaining module is configured to obtain, according to a received service call request, docking process information and initial to-be-processed service data carried in a service call request;
the first processing module is used for determining a corresponding docking process according to the docking process information, wherein the docking process is a service processing process which is configured in advance and is docked with a third-party system;
and the second processing module is used for processing the initial to-be-processed service data according to the docking process to obtain a service processing result.
In another aspect, an embodiment of the present disclosure further provides an electronic device, including:
one or more processors;
a storage device having one or more programs stored thereon;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of interfacing with a third party system as previously described.
In yet another aspect, the disclosed embodiments also provide a computer readable medium, on which a computer program is stored, wherein the program when executed implements the method of interfacing with a third party system as described above.
The embodiment of the disclosure provides a method for docking with a third-party system, wherein a corresponding docking process is determined according to docking process information in a received service call request, and the docking process is a service processing process which is configured in advance and is docked with the third-party system; processing the initial to-be-processed service data in the service calling request according to the docking process to obtain a service processing result; the method and the device have the advantages that the butt joint process is configured in advance, the butt joint process is directly effective after configuration, business data processing is realized according to the butt joint process when the butt joint is carried out with the third-party system, the butt joint with the third-party system can be realized without developing bottom codes, the operations of development, version upgrading, patching, deployment, restarting and the like caused by butt joint are correspondingly omitted, the butt joint period can be shortened, and the butt joint cost is reduced; the method can flexibly deal with the butt joint of any third-party system by pre-configuring the butt joint process, thereby improving the flexibility and the applicability.
Drawings
FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present disclosure;
fig. 2 is a schematic flow chart of a method for interfacing with a third-party system according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram illustrating a method for docking a third-party system according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart of processing the initial to-be-processed service data according to the docking process and the interface template according to the embodiment of the present disclosure;
FIG. 5 is a schematic view of a U-shaped driving flow provided by the embodiment of the present disclosure;
fig. 6 is a flowchart illustrating a next step of the docking process according to the embodiment of the present disclosure;
fig. 7 is a schematic diagram illustrating a successful execution of the nth normal step in the U-shaped driving flow according to the embodiment of the present disclosure;
FIG. 8 is a schematic diagram illustrating an execution failure of the Nth normal step in the U-shaped driving process according to the present disclosure;
FIG. 9 is a schematic diagram illustrating a failure in executing the (N-1) th normal step in the U-type driving process according to the embodiment of the disclosure;
FIG. 10 is a schematic flow chart illustrating a configuration docking process and a configuration interface template provided by an embodiment of the present disclosure;
fig. 11 is a first schematic structural diagram of a docking device according to an embodiment of the present disclosure;
fig. 12 is a schematic structural diagram of a docking device according to an embodiment of the present disclosure.
Detailed Description
Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but which may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes," and/or "made from" \8230; \8230 ";" made from ";" specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Embodiments described herein may be described with reference to plan and/or cross-sectional views in idealized representations of the present disclosure. Accordingly, the example illustrations can be modified in accordance with manufacturing techniques and/or tolerances. Accordingly, the embodiments are not limited to the embodiments shown in the drawings, but include modifications of configurations formed based on a manufacturing process. Thus, the regions illustrated in the figures have schematic properties, and the shapes of the regions shown in the figures illustrate specific shapes of regions of elements, but are not intended to be limiting.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
The embodiment of the present disclosure provides a method for interfacing with a third-party system, where the method may be applied to a network orchestration system, as shown in fig. 1, the network orchestration system includes a service system 1, an interfacing apparatus 2, and a third-party system 3, where the service system 1 is configured to manage a life cycle of a service, and specifically includes performing service invocation operations such as creating, modifying, deleting, starting, stopping, suspending, resuming, and querying on the service, where the service invocation operations may be directly performed through an interface, may also be performed through a northbound interface, and may also be performed at a background timing, and the service system 1 sends a service invocation request for performing the operations to the interfacing apparatus 2. The docking device 2 is configured to perform input, issue, and output processing of service data for an interface of the third-party system 3 based on the service call request, and send a service data processing result to the third-party system 3.
In the embodiment of the present disclosure, in the initialization stage, a docking process and an interface template are configured in the docking apparatus 2, the docking process includes at least one step for representing a complete service invocation operation, and the interface template is used for defining interface processing contents, that is, defining processing logic of service data. Each step of the docking process corresponds to a group of interface templates, each group of interface templates includes an input interface template and an output interface template, and the docking process and the interface templates can be configured on the interface of the docking device 2.
The method for interfacing with a third-party system provided by the embodiment of the present disclosure is shown in fig. 1 and fig. 2, and includes the following steps:
and step 11, acquiring the docking process information and the initial to-be-processed service data carried in the received service calling request.
The service system 1 may issue the service call request in one of the interface, the northbound interface, and the timing task. In this step, the docking device 2 receives a service invocation request sent by the service system 1, and obtains the docking flow information and the initial to-be-processed service data carried in the service invocation request. In some embodiments, the docking procedure information may include vendor information of the third-party system, business module information, business call operation information (e.g., create, delete, query, etc.), version number, and the like. The initial to-be-processed service data refers to service data to be processed in the first step in the docking process executed by the docking device 2.
And step 12, determining a corresponding docking process according to the docking process information, wherein the docking process is a service processing process which is configured in advance and is docked with a third-party system.
The docking device 2 may store a plurality of docking flows, in this step, the docking flow corresponding to the service invocation request may be queried according to one or several items of the docking flow information, for example, the docking flow corresponding to the third-party system 3 for processing the service invocation request may be queried and obtained according to the manufacturer information and the service invocation operation information of the third-party system as indexes.
And step 13, processing the initial to-be-processed service data according to the docking process to obtain a service processing result.
In this step, after the final service processing result is obtained, the service processing result is sent to the service system 1.
The method for docking with the third-party system provided by the embodiment of the disclosure determines a corresponding docking process according to docking process information in a received service call request, wherein the docking process is a service processing process configured in advance for docking with the third-party system; processing the initial to-be-processed service data in the service calling request according to the docking process to obtain a service processing result; the method and the device have the advantages that the butt joint process is configured in advance, the butt joint process is directly effective after configuration, business data processing is achieved according to the butt joint process when the device is in butt joint with a third-party system, the butt joint with the third-party system can be achieved without developing bottom codes, operations such as development, version upgrading, patching, deployment and restarting caused by butt joint are correspondingly omitted, the butt joint period can be shortened, and the butt joint cost is reduced; the method can flexibly deal with the butt joint of any third-party system by pre-configuring the butt joint process, thereby improving the flexibility and the applicability.
In some embodiments, the processing the initial to-be-processed service data according to the docking process to obtain a service processing result (i.e. step 13), includes: and aiming at each step of the docking process, sending the first data generated in the current step to a third-party system, and determining the next step of the docking process according to the second data returned by the third-party system and the current step. That is, the docking device 2 processes the service data according to each step of the docking process, the service processing result (i.e., the first data) of each step is sent to the third-party system 3, the third-party system 3 processes the first data and then returns the second data to the docking device 2, the docking device 2 processes the second data, and the next step of the docking process is determined according to the processing result and the currently executed step.
In some embodiments, each step of the docking process is pre-configured with an interface template for defining interface processing content, and the driving process and the interface template are invoked to implement processing of the service data by converting the docking process into a driving process corresponding to the docking process. Fig. 3 is a schematic diagram of the principle of the embodiment of the present disclosure, and with reference to fig. 3 and fig. 4, the processing of the initial to-be-processed service data according to the docking process to obtain a service processing result (i.e., step 13) includes the following steps:
and step 131, converting the docking process into a driving process, wherein each step of the driving process corresponds to each step of the docking process one by one.
And the docking flow module converts the docking flow into a driving flow after receiving the service calling request and determining the corresponding docking flow, wherein the conversion operation is not performed on an interface but is performed based on the received service calling request.
In some embodiments, the converting the docking procedure into the driving procedure includes: and implanting the execution marker into the docking process according to a preset standard, and converting the docking process into a driving process. It should be noted that, each step of the docking process is implanted with an execution flag, where the execution flag is used to indicate whether the step is successfully executed, and for example, if the value of the execution flag of a certain step is Ture, it indicates that the step is successfully executed; if the value of the execution flag of a certain step is False, it indicates that the step has failed to be executed.
Step 132, deploy the driver flow to the driver engine.
The docking process module deploys the driving process to a driving engine, and the driving engine is used for carrying out life cycle management operation on the driving process, including deployment, starting and operation of the driving process.
And step 133, calling each step of the driving process by using the driving engine, and performing data processing on the initial to-be-processed service data according to the interface template corresponding to each step to obtain a service processing result.
Each step of the driving process corresponds to a driving unit, and fig. 3 illustrates one driving unit as an example, where one driving unit is used to execute a single step of the driving process, a driving engine is used to drive the driving unit of a certain step, and the driving unit calls a corresponding interface template to perform data processing, so as to obtain a service processing result of the step. The functions of the drive unit include: the method comprises the steps of converting first data, calling a third-party system interface and processing second data. The initial to-be-processed business data is used as initial data of the driving process, the driving engine is used for starting the driving process, and after the driving process is started, the driving engine drives the driving unit in the first step of the driving process, so that the business data is processed step by step according to the driving process.
In order to realize the complete erasure of data and ensure the correctness of the data, a corresponding rollback step is set for each normal step in the docking process and the driving process. Therefore, in some embodiments, the step types of the docking process and the driving process include a normal step and a rollback step, each normal step corresponds to a rollback step, a previous step of the nth normal step is an (N-1) th normal step, and a next step of the nth rollback step is an (N-1) th rollback step corresponding to the (N-1) th normal step; the last step in the docking flow and the driving flow may be the last normal step (i.e., nth normal step) or the first rollback step (i.e., 1 st rollback step). As shown in fig. 5, the normal steps of the docking process and the driving process include steps 1 to N, where N is greater than or equal to 1, and if the step N is successfully executed, the process is successfully ended, the rollback steps of the docking process and the driving process include a 1 st rollback step to an nth rollback step, and the 1 st rollback step to the nth rollback step respectively correspond to the steps 1 to N. If the nth rollback step is executed, the nth rollback step → the (N-1) th rollback step are sequentially executed until after the 1 st rollback step, the process fails to end, and at this time, data rollback is restored to the initial to-be-processed service data. And setting corresponding rollback steps for each step in the docking flow and the driving flow, so that once data rollback occurs, the docking flow and the driving flow are in a U shape until the data rollback is recovered to be the original initial data, and the correctness of the data is ensured. If the data rollback does not occur, the docking process and the driving process are in an I shape, and the process is successfully finished.
The number of the driving units is the sum of the number of normal steps and the number of rollback steps in the driving process. When the driving engine calls the driving flow, the driving engine calls driving units with variable quantity, which is related to whether the driving units execute corresponding steps successfully, if the current driving unit corresponds to a normal step and the execution is successful, the driving unit of the next normal step is driven by the driving engine; if the current driving unit corresponds to the normal step and the execution fails, the driving unit of the rollback step corresponding to the normal step will be driven by the driving engine. If the current driving unit corresponds to the rollback step, regardless of whether the rollback step is successfully executed, the driving unit of the next rollback step (i.e., the rollback step corresponding to the previous normal step) is driven by the driving engine.
In some embodiment examples, the interface template includes an interface input template and an interface output template, as shown in fig. 6, for each step of the docking process, the step of sending the first data generated in the current step to the third-party system for determining the next step of the docking process (i.e., step 13) according to the second data returned by the third-party system includes the following steps:
and 21, determining an interface input template and an interface output template corresponding to the current step for each step of the driving process, processing the to-be-processed service data of the current step according to the interface input template to obtain first data, and sending the first data to a third-party system.
In this step, as shown in fig. 3, for each step of the driving process, each driving unit determines an interface input template and an interface output template corresponding to the current step, processes the data to be processed in the current step by using the interface input template to obtain first data (the first data is data output by the current driving unit), sends the first data to the third-party system 3 through the southbound interface channel, and waits for the third-party system 3 to return data. The southbound interface channel is a channel through which the docking equipment 2 is connected with the third-party system 3, is responsible for getting through the interface authentication with the third-party system 3, and provides a unobstructed channel for issuing the first data. It should be noted that the data to be processed in the current step is current drive flow data, and the current drive flow data may be a summary of the first data in one or more previous steps.
And step 22, processing second data returned by the third-party system according to the interface output template to obtain a service data processing result and an execution mark value of the current step.
In this step, after the driving unit receives the second data returned by the third-party system 3 through the southbound interface channel, the second data is processed according to the interface output template, so that on one hand, a service data processing result of the current step can be obtained, and on the other hand, whether the current step is successfully executed can be determined, so as to obtain an execution flag value of the current step. Illustratively, if the current step is successfully executed, the execution flag has a value of true; if the current step fails to be executed, the value of the execution flag is False. It should be noted that, in this step, the first data, the second data, the execution flag, and the service data processing result of the current step are also added to the current drive flow data.
And step 23, determining the next step of the driving flow according to the value of the execution mark of the current step and the step type.
In this step, the drive engine identifies the next drive unit from the drive flow based on the value of the execution flag and the step type of the current step, thereby determining the next step to be executed.
It should be noted that the service data processing result in the last step of the driving process is the service processing result of the whole service invocation request, and the service data processing result in the current step may be the service data to be processed in the next step.
The next step of the driving flow may be a next normal step, or a rollback step corresponding to the current step, or a rollback step corresponding to the previous step, and thus, the next step is determined according to the value (success or failure) of the execution flag of the current step and the step type (normal step or rollback step) of the current step.
In some embodiments, the determining the next step of the driving process according to the value of the execution flag of the current step and the step type includes: if the value of the execution mark of the current step indicates that the execution is successful and the current step is a normal step, determining that the next step of the driving process is the next normal step of the normal step; and if the value of the execution mark of the current step indicates that the execution fails and the current step is a normal step, determining that the next step of the driving process is a rollback step corresponding to the current normal step.
It should be noted that, as shown in fig. 7, for a rollback step, whether the value of the execution flag of the step indicates success or failure, the next step is the rollback step corresponding to the previous normal step, so that the U-shaped driving flow is completed until the failure of the entire driving flow is completed. If the current step is the nth rollback step, sequentially executing the rollback steps (namely executing data rollback for N times) according to the reverse order of the normal steps of the driving flow so as to restore the service processing result to the initial service data to be processed. That is, if the normal step is successfully executed, the I-font driver flow is continuously executed, and if the normal step is unsuccessfully executed, the U-font driver flow is executed from the step of the failed execution.
For example, as shown in fig. 7, if the driving unit determines that the value of the current step execution flag is bore, and the current step is the (N-1) th normal step, the next step of the driving flow is determined as: the Nth normal step, the whole driving process is the normal 1 st normal step- > the 2 nd normal step- > the 3 rd normal step- > \8230; \ 8230; - > the (N-1) normal step- > the Nth normal step- > the successful end. As shown in fig. 8, if the driving unit determines that the value of the execution flag of the current step is False and the current step is the nth normal step, it determines that the next step of the driving process is the nth rollback step, and the entire driving process is as follows: the 1 st normal step- > the 2 nd normal step- > the 3 rd normal step- > 8230- > \8230- > the (N-1) th normal step- > the nth rollback step- > the (N-1) th rollback step- > 8230- > \8230; > the 3 rd rollback step- > the 2 nd rollback step- > the 1 st rollback step- > the end of failure. As shown in fig. 9, if the driving unit determines that the value of the current step execution flag is False and the current step is the (N-1) th normal step, it determines that the next step of the driving flow is the (N-1) th rollback step, and the entire driving flow is: the method comprises the following steps of 1 normal step- > 2 normal step- > 3 normal step- > 8230; \8230; > the (N-1) normal step- > the (N-1) rollback step- > 8230; \8230; > the 3 rd rollback step- > the 2 nd rollback step- > 1 rollback step- > the failure end.
In some embodiments, the method for interfacing with a third-party system further includes the steps of configuring the docking process and configuring the interface template, where the steps of configuring the docking process and configuring the interface template are performed in an initialization stage, and the docking process and the interface template become effective immediately after the configuration is completed. As shown in fig. 10, the method for interfacing with the third-party system further includes the steps of configuring the interfacing process and configuring the interface template, including the steps of:
and step 31, configuring a docking process.
In the step, the docking process is configured according to the service logic of the third-party system and a preset first database, the docking process is stored in the docking process module after the configuration of the docking process is finished, the docking process takes effect immediately, and the network arrangement system does not need to be compiled, deployed or restarted.
In some embodiments, if a docking procedure with all the same steps is found in the existing docking procedure library (i.e., the first database), the docking procedure may be directly copied and the identity of the docking procedure may be modified; if some steps are the same in the existing docking process library, the docking process can be copied and modified; and if the docking process with the same steps or part of the same steps cannot be found in the existing docking process library, reestablishing the docking process. The life cycle management operation of the docking process comprises creation, modification, deletion, conversion, query and the like, the creation, modification and deletion operations can be carried out on the interface, text content can be edited directly on the interface, and edited files conforming to the docking process format can be uploaded through the interface.
And 32, respectively configuring an interface template for each step of the docking process.
In this step, a set of interface templates is respectively configured for each step in the docking process according to a preset second database, and the set of interface templates includes an input interface template and an output interface template. The interface template is written in two forms, namely, conversion independent of a program, namely template conversion, and conversion dependent on the program, namely program conversion, wherein the program can be any programming language. But in either case the same input and output will be maintained. After the interface template configuration is finished, the interface template takes effect immediately without compiling, deploying and restarting the network arranging system.
In some embodiments, the step of configuring the interface template for each step of the docking process separately (i.e., step 32) includes the steps of: for each step of the docking process, if a first interface template with at least part of interface processing contents being the same is obtained in a preset second database, modifying the first interface template to obtain a second interface template of the current step, and configuring the second interface template; and aiming at each step of the docking process, if the first interface template with at least part of interface processing contents being the same is not acquired in a preset second database, establishing a second interface template of the current step, and configuring the second interface template. That is, if an interface template having the same interface processing content is found in the existing interface template database (i.e., the second database), the interface template may be directly copied and the identifier of the interface template may be modified; if the interface processing contents are found to be similar (i.e. partially identical) in the existing interface template database, the interface template can be copied, then the processing contents can be modified, and the identifier of the interface template can be modified; and if the interface processing contents are not found to be the same or similar in the existing interface template database, reestablishing the interface template. The above operations may be performed through an interface.
The embodiment of the present disclosure takes the southbound access of the network arrangement system as an example, and can be applied to the following scenarios: accessing a new type of third-party system, accessing a new version of third-party system, adding an interface to the accessed third-party system, and modifying an interface to the accessed third-party system. The embodiments of the present disclosure may also be applied to a Network management system, an SDN (Software Defined Network) controller system.
In the method for docking with the third-party system provided by the embodiment of the disclosure, in an initialization stage, a required docking process and an interface template can be configured on an interface. After a service call request of a service system is obtained, a corresponding butt joint flow is found and converted into a U-shaped driving flow, a driving engine deploys and starts the driving flow, a driving unit of each step of the driving flow obtains a corresponding interface template, the driving unit carries out input, distribution and output processing on service data aiming at an interface of a third-party system 3 to obtain a value of an execution mark, the driving engine identifies the value of the execution mark and then enters a driving unit corresponding to the next driving flow step, and a service processing result is notified to the service system after the whole driving flow is finished. According to the embodiment of the invention, operations such as development, version upgrading, patching, deployment and restarting are not required to be executed, the docking period can be greatly shortened, the docking speed is improved, the development cost is reduced, the user experience is improved, and the docking of any third-party system interface can be flexibly coped with. By configuring the docking process and the interface template in advance, the software version can be directly validated without upgrading or patching, and the aim of rapid docking is fulfilled.
Based on the same technical concept, an embodiment of the present disclosure further provides a docking device, as shown in fig. 11, where the docking device includes an obtaining module 101, a first processing module 102, and a second processing module 103, and the obtaining module 101 is configured to obtain, according to a received service invocation request, docking flow information and initial to-be-processed service data carried in the service invocation request.
The first processing module 102 is configured to determine a corresponding docking process according to the docking process information, where the docking process is a service processing process configured in advance to dock with a third-party system.
The second processing module 103 is configured to process the initial to-be-processed service data according to the docking procedure, so as to obtain a service processing result.
In some embodiments, the second processing module 103 is configured to, for each step of the docking process, send the first data generated in the current step to the third-party system, so as to determine a next step of the docking process according to the second data returned by the third-party system and the current step.
In some embodiments, each step of the docking process is pre-configured with an interface template for defining interface processing content, and the second processing module 103 is configured to convert the docking process into a driving process, where each step of the driving process corresponds to each step of the docking process in a one-to-one manner; deploying the driver flow into a driver engine; and calling each step of the driving flow by using the driving engine, and performing data processing on the initial to-be-processed service data according to the interface template corresponding to each step to obtain a service processing result.
In some embodiments, the interface template includes an interface input template and an interface output template, and the second processing module 103 is configured to implant an execution flag into the docking process according to a preset specification standard, and convert the docking process into a generation driving process, where the execution flag is used to indicate whether the step is successfully executed.
In some embodiments, the types of the steps of the docking process and the driving process include a normal step and a rollback step, each normal step corresponds to a rollback step, a previous step of an nth normal step is an (N-1) th normal step, and a next step of the nth rollback step is an (N-1) th rollback step corresponding to the (N-1) th normal step; the last step in the docking process and the driving process includes a last normal step and a first rollback step.
In some embodiments, the interface template includes an interface input template and an interface output template, and the second processing module 103 is configured to determine, for each step of the driving process, the interface input template and the interface output template corresponding to the current step, process the to-be-processed service data of the current step according to the interface input template to obtain first data, and send the first data to the third-party system;
processing second data returned by the third-party system according to the interface output template to obtain a service data processing result and an execution mark value of the current step;
and determining the next step of the driving flow according to the value of the execution mark of the current step and the step type.
In some embodiments, the second processing module 103 is configured to determine that a next step of the driving process is a next normal step of the normal steps if the value of the execution flag of the current step indicates that the execution is successful and the current step is a normal step; and if the value of the execution mark of the current step indicates that the execution fails and the current step is a normal step, determining that the next step of the driving process is a rollback step corresponding to the normal step.
In some embodiments, as shown in fig. 12, the docking apparatus further includes a configuration module 104, where the configuration module 104 is configured to configure a docking procedure and configure an interface template for each step of the docking procedure.
In some embodiments, the configuration module 104 is configured to, if a first docking procedure with at least part of the same steps is obtained in a preset first database, modify the first docking procedure to obtain a second docking procedure, and configure the second docking procedure; and if the first butt-joint process with at least part of the same steps is not acquired in a preset first database, establishing a second butt-joint process and configuring the second butt-joint process.
In some embodiments, the configuration module 104 is configured to, for each step of the docking process, if a first interface template with at least part of interface processing contents being the same is obtained in a preset second database, modify the first interface template to obtain a second interface template of the current step, and configure the second interface template; and aiming at each step of the docking process, if the first interface template with at least part of interface processing contents being the same is not acquired in a preset second database, establishing a second interface template of the current step, and configuring the second interface template.
An embodiment of the present disclosure also provides an electronic device, including: one or more processors and storage; the storage device stores one or more programs thereon, and when the one or more programs are executed by the one or more processors, the one or more processors implement the method for interfacing with a third-party system as provided in the foregoing embodiments.
Embodiments of the present disclosure also provide a computer readable medium, on which a computer program is stored, where the computer program when executed implements the method for interfacing with a third party system as provided in the foregoing embodiments.
It will be understood by those of ordinary skill in the art that all or some of the steps of the methods disclosed above, functional modules/units in the apparatus, may be implemented as software, firmware, hardware, and suitable combinations thereof. In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as is well known to those skilled in the art.
Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted in a generic and descriptive sense only and not for purposes of limitation. In some instances, features, characteristics and/or elements described in connection with a particular embodiment may be used alone or in combination with features, characteristics and/or elements described in connection with other embodiments, unless expressly stated otherwise, as would be apparent to one skilled in the art. It will therefore be understood by those skilled in the art that various changes in form and details may be made therein without departing from the scope of the invention encompassed by the appended claims.

Claims (13)

1. A method of interfacing with a third party system, the method comprising:
acquiring the carried butt joint flow information and initial to-be-processed service data according to the received service calling request;
determining a corresponding docking process according to the docking process information, wherein the docking process is a service processing process which is configured in advance and is docked with a third-party system;
and processing the initial to-be-processed service data according to the docking process to obtain a service processing result.
2. The method of claim 1, wherein the processing the initial to-be-processed service data according to the docking process to obtain a service processing result comprises:
and aiming at each step of the docking process, sending the first data generated in the current step to the third-party system, and determining the next step of the docking process according to the second data returned by the third-party system and the current step.
3. The method according to claim 2, wherein each step of the docking process is pre-configured with an interface template for defining interface processing content, and the processing the initial to-be-processed service data according to the docking process to obtain a service processing result includes:
converting the butt joint flow into a driving flow, wherein each step of the driving flow corresponds to each step of the butt joint flow one by one;
deploying the driver flow into a driver engine;
and calling each step of the driving flow by using the driving engine, and performing data processing on the initial service data to be processed according to the interface template corresponding to each step to obtain a service processing result.
4. The method of claim 3, wherein said converting said docking process to a driver process comprises:
and implanting an execution mark into the docking process according to a preset standard, and converting into a generation driving process, wherein the execution mark is used for indicating whether the step is executed successfully or not.
5. The method according to claim 4, wherein the types of the steps of the docking process and the driving process include a normal step and a rollback step, each normal step corresponds to one rollback step, a previous step of the nth normal step is an (N-1) th normal step, and a next step of the nth rollback step is an (N-1) th rollback step corresponding to the (N-1) th normal step;
the last step in the docking process and the driving process includes a last normal step and a first rollback step.
6. The method of claim 5, wherein the interface template comprises an interface input template and an interface output template, and wherein for each step of the docking process, sending the first data generated by the current step to the third-party system for determining a next step of the docking process according to the second data returned by the third-party system and the current step comprises:
aiming at each step of the driving process, determining an interface input template and an interface output template corresponding to the current step, processing the to-be-processed service data of the current step according to the interface input template to obtain first data, and sending the first data to the third-party system;
processing second data returned by the third-party system according to the interface output template to obtain a service data processing result and an execution mark value of the current step;
and determining the next step of the driving flow according to the value of the execution mark of the current step and the step type.
7. The method of claim 6, wherein said determining a next step of said driving procedure based on a value of an execution flag of said current step and a step type comprises:
if the value of the execution flag of the current step indicates that the execution is successful and the current step is a normal step, determining that the next step of the driving process is the next normal step of the normal step;
and if the value of the execution mark of the current step indicates that the execution fails and the current step is a normal step, determining that the next step of the driving process is a rollback step corresponding to the normal step.
8. The method of any one of claims 3-7, wherein the method further comprises the step of configuring a docking procedure and configuring an interface template, the configuring a docking procedure and configuring an interface template comprising:
configuring a docking process, and respectively configuring an interface template for each step of the docking process.
9. The method of claim 8, wherein the configuring the docking process comprises:
if a first butt-joint process with at least part of the same steps is acquired in a preset first database, modifying the first butt-joint process to acquire a second butt-joint process, and configuring the second butt-joint process;
and if the first butt-joint process with at least part of the same steps is not acquired in a preset first database, establishing a second butt-joint process and configuring the second butt-joint process.
10. The method of claim 8, wherein the configuring interface templates for each step of the docking process separately comprises:
for each step of the docking process, if a first interface template with at least part of interface processing contents being the same is obtained in a preset second database, modifying the first interface template to obtain a second interface template of the current step, and configuring the second interface template;
and aiming at each step of the docking process, if the first interface template with at least part of interface processing contents identical is not acquired in a preset second database, establishing a second interface template of the current step, and configuring the second interface template.
11. A docking device is characterized by comprising an acquisition module, a first processing module and a second processing module, wherein the acquisition module is used for acquiring docking process information and initial to-be-processed service data carried in a received service call request;
the first processing module is used for determining a corresponding docking process according to the docking process information, wherein the docking process is a service processing process which is configured in advance and is docked with a third-party system;
and the second processing module is used for processing the initial to-be-processed service data according to the docking process to obtain a service processing result.
12. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon;
the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of interfacing with a third party system of any of claims 1-10.
13. A computer readable medium having stored thereon a computer program, wherein said program when executed implements a method of interfacing with a third party system as claimed in any one of claims 1 to 10.
CN202110686397.4A 2021-06-21 2021-06-21 Method and device for interfacing with third-party system, electronic equipment and readable medium Pending CN115576706A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110686397.4A CN115576706A (en) 2021-06-21 2021-06-21 Method and device for interfacing with third-party system, electronic equipment and readable medium
PCT/CN2022/097313 WO2022267878A1 (en) 2021-06-21 2022-06-07 Method for interfacing with third-party system, and apparatus, electronic device, and readable medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110686397.4A CN115576706A (en) 2021-06-21 2021-06-21 Method and device for interfacing with third-party system, electronic equipment and readable medium

Publications (1)

Publication Number Publication Date
CN115576706A true CN115576706A (en) 2023-01-06

Family

ID=84544119

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110686397.4A Pending CN115576706A (en) 2021-06-21 2021-06-21 Method and device for interfacing with third-party system, electronic equipment and readable medium

Country Status (2)

Country Link
CN (1) CN115576706A (en)
WO (1) WO2022267878A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117033032A (en) * 2023-09-28 2023-11-10 北京谷器数据科技有限公司 Platform for automatically analyzing and calling third-party service interface

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7089583B2 (en) * 2000-01-14 2006-08-08 Saba Software, Inc. Method and apparatus for a business applications server
CN107613506B (en) * 2016-07-11 2022-05-31 中兴通讯股份有限公司 Automatic configuration method for north interface LTE service and north interface device
CN110519730B (en) * 2019-09-11 2021-11-26 杭州芯云智创科技有限公司 Method and device for managing, arranging and docking service system and NFV
CN110990303B (en) * 2019-11-05 2021-05-25 北京华商三优新能源科技有限公司 Data processing method and device for charging pile, storage medium and processor
CN112686583A (en) * 2021-03-12 2021-04-20 中国民用航空总局第二研究所 Method and system for generating automatic handling flow of civil aviation event
CN112884447A (en) * 2021-03-12 2021-06-01 中国民用航空总局第二研究所 Civil aviation airport data cooperation method and system

Also Published As

Publication number Publication date
WO2022267878A1 (en) 2022-12-29

Similar Documents

Publication Publication Date Title
CN105045663B (en) The method and system of rapid deployment virtual machine
US10447814B2 (en) Joint servicing of software packages
CN110389766B (en) HBase container cluster deployment method, system, equipment and computer readable storage medium
CN111857801B (en) Construction method of mobile application
CN111104151B (en) Shell script-based Git code simplification management method
CN106569863B (en) Resource and code modularization-based android app resource updating and repairing method
CN111176665B (en) High-capacity emmc mirror image manufacturing method and device
CN104881311A (en) Method and apparatus for judging version compatibility
CN115576706A (en) Method and device for interfacing with third-party system, electronic equipment and readable medium
CN116737117A (en) Model development method based on Autosar architecture
CN106874047B (en) Distributed system scheduling method and device and distributed system
CN111158751A (en) Windows environment deployment method, electronic equipment and storage medium
CN113434283B (en) Service scheduling method and device, server and computer readable storage medium
KR102106449B1 (en) Method, device and server for checking a defective function
CN114020323A (en) Model processing method, code obtaining method, device and electronic equipment
CN116991758A (en) Spatial layout updating method, device, equipment and medium
CN111399866B (en) Updating method and device of VNF (virtual network function) package
CN113760312A (en) Base station data upgrading method, base station and computer readable medium
CN111857953A (en) Container cluster management method, device, equipment and readable storage medium
CN111897543A (en) Software management method, device, management equipment and storage medium
US20240045733A1 (en) Method and apparatus for deploying deep learning system
CN115480785A (en) Container-based service deployment method and device and server
CN109531730B (en) Terminal nailing method, device and storage medium
CN110377298B (en) Distributed cluster upgrading method and distributed cluster
CN106886420B (en) Program code management device and method and program code manager

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