Business process orchestration method, operation method and orchestration device

Abstract

The process orchestration method, operation method and orchestration device provided in the embodiments of the present application, when orchestrating a business process, determine the calling order and process instances of network elements at each level based on business requirements, and further establish a sending relationship between the upper-level network element and the target network element in the lower-level network element based on the network element type of the lower-level network element. Based on the calling order of network elements at each level, the sending relationship between the upper-level network element and the lower-level network element, and the process instance, a business process corresponding to the business requirement is generated. During orchestration, by directly establishing a sending relationship between the upper-level network element and a single network element in the lower-level network element, the problem of the upper-level network element directly sending a process instance to the lower-level network element that is not a single network element type, resulting in the lower-level network element being unable to accurately receive the process instance, is avoided. This makes the orchestration not only applicable to business process types that only contain single network elements, but can also be applied to more business process types that contain other network element types.

Description

Technical Field

[0001] The present application relates to the technical field of business flow management, and in particular to a business process orchestration method, operation method, and orchestration device. Background Art

[0002] A business process is an overall process consisting of related businesses connected by time sequence or business logic. A business process is defined by a process definition (Process Definition) that defines the calling order and tasks performed by network elements at each level in the overall process, and provides corresponding calling methods, namely process instances, for network elements at each level. When running a business process, network elements at each level call the next level network element in the calling order. When calling the next level network element, the corresponding process instance is sent to the next level network element, so that the next level network element can use the corresponding calling method in the process instance to perform the corresponding task.

[0003] Based on business requirements, developers orchestrate business processes to automate the process. When orchestrating business processes, developers typically use existing process orchestration templates. Existing process orchestration templates can only orchestrate call relationships between network elements at all levels. Specifically, existing process orchestration templates can only establish call relationships between upper-level and lower-level network elements. Consequently, business processes orchestrated using existing process orchestration templates only enable the upper-level network element to send process instances to each lower-level network element.

[0004] A process instance can only run on a single network element (NE) and cannot run concurrently on multiple NEs. If the next-level NE is a single NE, the previous-level NE can accurately send the process instance to the next-level NE using the existing process orchestration template, allowing the next-level NE to run the process instance. However, with the increasing complexity of NE structures, next-level NEs are no longer simply single NEs, but rather multiple NEs with more complex structures, such as a NE group consisting of multiple single NEs. Using the existing process orchestration template, the previous-level NE can only send one process instance to the next-level NE group and cannot accurately send the process instance to each NE in the next-level NE group. Consequently, the next-level NE group cannot run the received process instance. Therefore, using the existing process orchestration template to orchestrate a business process can only orchestrate business processes involving a single NE, not business processes involving other NE types, such as NE groups. Consequently, the orchestration only applies to a limited number of business processes. Summary of the Invention

[0005] The present application provides a business process orchestration method, an operation method, and an orchestration device to increase the types of business processes applicable to the orchestration.

[0006] In a first aspect, the present application provides a business process orchestration method, the method comprising:

[0007] Determine the calling sequence and process instances of network elements at all levels based on business requirements, and the process instances are used to provide corresponding calling methods for network elements at all levels;

[0008] Based on the network element type of the next-level network element, establishing a sending relationship between the previous-level network element and a target network element in the next-level network element, wherein the target network element is a single network element, and the sending relationship is used to instruct the previous-level network element to send a corresponding process instance to the target network element in the next-level network element;

[0009] Based on the calling sequence of the network elements at each level, the issuing relationship between the upper-level network element and the lower-level network element, and the process instance, a business process corresponding to the business demand is generated.

[0010] In one implementation, before establishing a delivery relationship between the upper-level network element and the target network element in the lower-level network element based on the network element type of the lower-level network element, the method further includes:

[0011] Acquire interface parameters of the next-level network element, where the interface parameters include a network element type value parameter of the next-level network element, where the network element type value parameter is used to indicate the network element type of the next-level network element;

[0012] The network element type of the next-level network element is determined based on the network element type value parameter of the next-level network element.

[0013] In one implementation, establishing a delivery relationship between the upper-level network element and the target network element in the lower-level network element based on the network element type of the lower-level network element includes:

[0014] determining a target network element in the next-level network element based on the network element type of the next-level network element,

[0015] Wherein, if the network element type of the next-level network element is a single network element type, the target network element refers to each of the next-level network elements;

[0016] If the network element type of the next-level network element is a network element group type, the target network element refers to one or all single network elements in the next-level network elements.

[0017] In one implementation, if the network element type of the next-level network element is a network element group type, determining the target network element in the next-level network element based on the network element type of the next-level network element includes:

[0018] Identify the network element relationship between each single network element in the next-level network element, wherein the network element relationship includes a master-slave relationship and a non-master-slave relationship;

[0019] If the network element relationship between the single network elements is the master-standby relationship, the target network element refers to a single network element in the next-level network element;

[0020] If the network element relationship between the single network elements is the non-active / standby relationship, the target network elements refer to all the single network elements in the next-level network elements.

[0021] In one implementation, if the network element relationship between the single network elements is the master-standby relationship, determining the target network element in the next-level network element based on the network element type of the next-level network element includes:

[0022] Obtaining a usage order between each single network element in the next-level network element;

[0023] Test each network element in turn to see if it has logged in successfully according to the order of use described above;

[0024] The first single network element that successfully logs in is determined as the target network element.

[0025] In one implementation, if the network element type of the next-level network element is a single network element type, establishing a delivery relationship between the previous-level network element and the target network element in the next-level network element includes:

[0026] A sending relationship is established between the upper-level network element and each of the lower-level network elements respectively, and the sending relationship instructs the upper-level network element to send a corresponding process instance to the corresponding lower-level network element.

[0027] In one implementation, if the network element type of the next-level network element is a network element group type, and the network element relationship between the single network elements in the next-level network element is a master-slave relationship, then establishing a delivery relationship between the upper-level network element and the target network element in the next-level network element includes:

[0028] A sending relationship is established between the upper-level network element and the target network element, wherein the sending relationship instructs the upper-level network element to directly send a corresponding process instance to the target network element, where the process instance refers to a process instance corresponding to the lower-level network element.

[0029] In one implementation, if the network element type of the next-level network element is a network element group type, and the network element relationship between the individual network elements in the next-level network element is a non-active / standby relationship, then establishing a delivery relationship between the upper-level network element and the target network element in the next-level network element includes:

[0030] A sending relationship is established between the next-level network element and each single network element in the next-level network element, and the sending relationship instructs the next-level network element to send a corresponding node process instance to the corresponding single network element, wherein the node process instance corresponds one-to-one to the single network element, different single network elements correspond to different node process instances, and the summary of all the node process instances is the same as a process instance corresponding to the next-level network element.

[0031] In a second aspect, the present application further provides a service process operation method, which runs the service process described in the first aspect on network elements at all levels, the method comprising:

[0032] Determine the next level network element of the current level network element based on the calling order of the network elements at each level;

[0033] Determining a target network element in the next-level network element based on the issuing relationship;

[0034] The current-level network element sends the corresponding process instance to the target network element in the next-level network element;

[0035] Run the process instance on the target network element.

[0036] In a third aspect, the present application further provides a business process orchestration device, the device comprising:

[0037] A determination unit, configured to determine a calling sequence and a process instance of network elements at each level based on business requirements, wherein the process instance is used to provide corresponding calling methods for the network elements at each level;

[0038] an establishing unit, configured to establish, based on a network element type of a next-level network element, a sending relationship between an upper-level network element and a target network element in the next-level network element, wherein the target network element is a single network element, and the sending relationship is used to instruct the upper-level network element to send a corresponding process instance to the target network element in the next-level network element;

[0039] A generating unit is configured to generate a business process corresponding to the business requirement based on the calling sequence of the network elements at each level, the issuing relationship between the upper-level network element and the lower-level network element, and the process instance.

[0040] From the above technology, it can be seen that the process orchestration method, operation method and orchestration device provided by the embodiments of the present application, when orchestrating a business process, determine the calling order and process instances of network elements at all levels based on business needs, and further establish a sending relationship between the upper-level network element and the target network element in the lower-level network element based on the network element type of the lower-level network element. Based on the calling order of network elements at all levels, the sending relationship between the upper-level network element and the lower-level network element, and the process instance, a business process corresponding to the business need is generated. During orchestration, by directly establishing a sending relationship between the upper-level network element and a single network element in the lower-level network element, the problem of the upper-level network element directly sending a process instance to the lower-level network element that is not a single network element type, resulting in the lower-level network element being unable to accurately receive the process instance, is avoided. This makes the orchestration not only applicable to business process types that only contain single network elements, but can also be applied to more business process types that contain other network element types. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for use in the embodiments. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0042] Figure 1 A flowchart of a business process orchestration method provided in an embodiment of the present application;

[0043] Figure 2 A business process diagram obtained by arranging the existing process arrangement template provided in the embodiment of the present application;

[0044] Figure 3 A schematic diagram showing that a network element at the same level provided in an embodiment of the present application includes multiple network element types;

[0045] Figure 4 A schematic diagram of a process for determining the network element type of a next-level network element provided in an embodiment of the present application;

[0046] Figure 5 A schematic diagram of issuing a process instance in which the next-level network element is a single network element type provided in an embodiment of the present application;

[0047] Figure 6 A schematic diagram of a process for determining a target network element in a network element group provided in an embodiment of the present application;

[0048] Figure 7 A schematic diagram of a process for determining a target network element in a network element group provided in an embodiment of the present application;

[0049] Figure 8 A schematic diagram of a process instance for issuing a next-level network element of a network element group type provided in an embodiment of the present application;

[0050] Figure 9 A flowchart of a node process instance for determining a target network element in a network element group provided in an embodiment of the present application;

[0051] Figure 10 A schematic diagram of a process instance for issuing multiple network element types to the same network element provided in an embodiment of the present application;

[0052] Figure 11 A flow chart of running a service process on network elements at all levels provided in an embodiment of the present application;

[0053] Figure 12 A schematic diagram of the structure of a business process orchestration device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] The following will provide a clear and complete description of the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present invention without making any creative efforts shall fall within the scope of protection of the present invention.

[0055] A business process is an overall flow composed of related services connected by time sequence or business logic. When a business process is executed, the corresponding process instances are run within each network element within the business process to perform the corresponding tasks, thereby achieving the business requirements corresponding to each task. Therefore, different business processes need to be orchestrated based on different business requirements. Figure 1 A flowchart of a business process orchestration method provided in an embodiment of the present application is shown below:

[0056] S101. Determine the calling sequence and process instances of network elements at all levels based on business requirements, where the process instances are used to provide corresponding calling methods for the network elements at all levels.

[0057] Typically, business requirements are met by running one or more services. These services run in various network elements, and each network element performs tasks corresponding to the services. In other words, the fulfillment of business requirements depends on the tasks performed by each network element. Each network element not only has its own tasks, but also has a specific order in which tasks are executed. Specifically, a network element executes its corresponding tasks by using its corresponding calling methods to invoke other network elements to execute tasks, access databases to retrieve data to be executed, and so on. The calling methods used by network elements are referred to as process instances. Based on business logic, there is a specific order in which tasks are executed between network elements, known as the calling order between network elements. Among network elements with a direct calling relationship, the one that calls the other is considered the upper-level network element, and the one called by the other is considered the lower-level network element. Based on this calling relationship, network elements can be divided into different levels. A complete calling path can be formed between network elements at each level. The upper-level network element calls the lower-level network element according to this calling order and sends the corresponding process instance to the lower-level network element, enabling the lower-level network element to use the corresponding process instance and execute the corresponding task.

[0058] For example, service requirement 1 is implemented by running services a, b, and c. The business logic between the services is to execute service a first, then service b, and finally service c. Network element A is used to execute service a, network element B is used to execute service b, and network element C is used to execute service c. Based on this business logic, the calling relationship between network elements A, B, and C is: network element A calls network element B, and network element B calls network element C. If the process instance used to execute service a is process instance a, the process instance used to execute service b is process instance b, and the process instance used to execute service c is process instance c, then based on this calling relationship, network element A runs process instance a and sends process instance b to network element B. Network element B runs process instance b and sends process instance c to network element C. Network element C runs process instance c. In this way, each network element completes the execution of the corresponding process instance to complete the execution of the corresponding task, thereby achieving service requirement 1. In one implementation, network element A, as the highest-level network element, can obtain all process instances including process instance a, process instance b, and process instance c, and send process instance b and process instance c to network element B. Network element B can send process instance c to network element C. In another implementation, network element A, as the highest-level network element, can obtain all process instances including process instance a, process instance b, and process instance c, and send all process instances to network element B. Network element B selects process instance b to run. Network element B can send all process instances to network element C, and network element C selects process instance c to run.

[0059] The existing process orchestration model can only establish call relationships between network elements at all levels. Using the existing process orchestration template to orchestrate the business process corresponding to the above business requirement 1, we can get the following: Figure 2 The business process shown in FIG3 shows a business process in which each dotted box represents a level of network element, and each circle represents a single network element. For example, network element A corresponds to the first-level network element, network element B corresponds to the second-level network element, and network element C corresponds to the third-level network element. Each arrow represents the direction in which the process instance is sent down. It can be seen that for the business process orchestrated using the existing process orchestration template, the process instance is sent down between network elements at all levels, that is, from the first-level network element to the second-level network element, and then from the second-level network element to the third-level network element. Based on the above example, since each level of network elements only contains a single network element, the business process orchestrated by the existing process orchestration template can realize the sending of process instances between single network elements. As a result, each single network element can run a corresponding process instance.

[0060] However, if each level of network elements contains more than just a single network element, e.g. Figure 3 As shown in ①, the second-level network elements include network element B and network element D, or as shown in Figure 3 As shown in Figure ②, the second-level network elements include network element group E, which contains network elements B and D. Using existing process orchestration templates, a process instance delivered from a first-level network element to a second-level network element will not be able to simultaneously run network elements B and D. Alternatively, a process instance delivered from a first-level network element to network element group E will not determine which single network element in group E to run on. This shows that, if a business process orchestrated using existing process orchestration templates contains multiple single network elements at the same level, or contains other types of network elements, the resulting business process will not function properly.

[0061] S102. Based on the network element type of the next-level network element, a sending relationship is established between the previous-level network element and the target network element in the next-level network element, wherein the target network element is a single network element, and the sending relationship is used to instruct the previous-level network element to send a corresponding process instance to the target network element in the next-level network element.

[0062] In order to solve the problem that the process instance cannot be accurately delivered to a single network element when the above-mentioned business process is running, when arranging the business process, a delivery relationship is established between the upper-level network element and each single network element in the lower-level network element, so that the upper-level network element can accurately deliver the process instance to the single network element in the lower-level network element according to the delivery relationship.

[0063] As can be seen from the above, in the process of the upper-level network element sending the process instance to the lower-level network element, the network element type of the lower-level network element will affect the way the upper-level network element sends the process instance, that is, it affects the number of process instances sent by the upper-level network element and the object to which the process instance is sent (the target network element in the lower-level network element). Therefore, based on the calling order of network elements at all levels, after determining the lower-level network element corresponding to the upper-level network element, the target network element for receiving the process instance sent by the upper-level network element is further determined in the lower-level network element based on the network element type of the lower-level network element. Then, a sending relationship is established between the upper-level network element and the target network element to instruct the upper-level network element to send the process instance to the target network element, so that the upper-level network element can accurately send the process instance to a single network element in the lower-level network element, so that the target network element can normally operate the received process instance.

[0064] You can refer to Figure 4 The process shown determines the network element type of the next level network element. The specific process is as follows:

[0065] S401. Obtain interface parameters of the next-level network element, where the interface parameters include a network element type value parameter of the next-level network element, and the network element type value parameter is used to indicate the network element type of the next-level network element.

[0066] S402: Determine the network element type of the next-level network element based on the network element type value parameter of the next-level network element.

[0067] The upper-level network element calls the lower-level network element in the calling sequence, which specifically means that the upper-level network element calls the interface provided by the lower-level network element in the calling sequence, such as the Application Programming Interface (API). These API interfaces on the lower-level network element can be pre-defined, for example, pre-defined interface parameters so that the defined interface parameters can reflect the network element properties of the lower-level network element. In this embodiment, the interface parameters of the lower-level network element are pre-defined, and the interface parameters at least include a network element type value parameter corresponding to the network element type. Therefore, when the upper-level network element recognizes the network element type value parameter of the lower-level network element, it can determine the network element type of the lower-level network element based on the correspondence between the network element type value parameter and the network element type.

[0068] In this embodiment, the network element type includes a single network element type and a network element group type. Figure 3The network elements B and D shown in ① refer to the next-level network elements as independent single network elements, that is, each next-level network element runs its own corresponding process instance in parallel. Each next-level network element can perform the same task, that is, each next-level network element runs the same process instance. Each next-level network element can also perform different tasks, that is, each next-level network element runs its own corresponding process instance, and at least two process instances in each process instance are different. Network element group type (can refer to Figure 3 The network element group E) shown in ② means that the next-level network element is a network element group. A network element group consists of at least two single network elements, and there is an association relationship between the single network elements in a network element group, that is, the single network elements in a network element group run the same process instance together.

[0069] Therefore, based on different network element types, the corresponding methods of running process instances are different, and the target network elements in the next-level network element for receiving process instances issued by the previous-level network element are different, that is, the issuing relationship between the previous-level network element and the target network element in the next-level network element is different. The details are as follows:

[0070] If the network element type of the next-level network element is a single network element type, it means that each next-level network element requires an independent process instance, then the upper-level network element needs to send the process instance corresponding to each next-level network element to each next-level network element, that is, each next-level network element is a target network element, and a sending relationship needs to be established between the upper-level network element and each next-level network element to instruct the upper-level network element to send each process instance to the corresponding next-level network element according to each sending relationship. Figure 5 As shown, based on Figure 3 In the example shown in (1), the first-level and second-level network elements are network elements B and D. It is recognized that both network elements B and D are single-level network elements. In this case, the first-level network element (network element A) establishes a distribution relationship with network elements B and D, respectively. Therefore, when executing a service process, network element A, based on the calling relationship between the first-level and second-level network elements, calls the second-level network elements, namely, network elements B and C, respectively. Based on the distribution relationship between network elements A and B, network element A distributes the process instance corresponding to network element B, namely, process instance b, to network element B. Based on the distribution relationship between network elements A and B, network element A distributes the process instance corresponding to network element D, such as process instance d, to network element D. This allows the upper-level network element (network element A) to accurately distribute process instances to the single network elements (network elements B and D) in the lower-level network element, allowing the lower-level network elements to properly run the received process instances. In other words, each single network element runs the corresponding process instance. Avoid situations where some single network elements in the next-level network elements have no process instances or the process instances are not accurately delivered.

[0071] In some embodiments, each single network element can perform the same task, that is, run the same process instance, or perform different tasks, that is, run different process instances. In this embodiment, there is no restriction on the specific tasks performed by the single network element.

[0072] If the network element type of the next-level network element is a network element group type, it means that a process instance is run with the network element group as the basic unit, that is, multiple single network elements in a network element group jointly run a process instance, then the upper-level network element only needs to send a process instance to the next-level network element. Furthermore, based on the different network element relationships between the single network elements in a network element group, in one implementation method, each single network element may have a representative network element to run the process instance, that is, the upper-level network element only needs to send the process instance to the representative network element, and the representative network element is the target network element. Accordingly, a sending relationship is established between the upper-level network element and the representative network element, without establishing a sending relationship between the upper-level network element and other network elements in the next-level network element. In another implementation method, each network element may also undertake the running tasks of some instances in the process instance, so as to achieve the effect of jointly running a process instance. Therefore, the upper level network element needs to issue the corresponding part of the process instance (i.e., node process instance) for each single network element in the network element group. That is, each single network element in the network element group is a target network element, and the upper level network element needs to establish a issuing relationship with each single network element. Figure 6 The process shown in the figure determines the target network element in the network element group. The specific process is as follows:

[0073] S601: Identify the network element relationship between each single network element in the next-level network element, where the network element relationship includes a master-slave relationship and a non-master-slave relationship.

[0074] S602: If the network element relationship between the single network elements is the master-standby relationship, the target network element refers to a single network element in the next-level network elements.

[0075] S603: If the network element relationship between the single network elements is the non-active / standby relationship, the target network elements refer to all the single network elements in the next-level network elements.

[0076] A master-slave relationship means that each NE in a NE group consists of one active device and at least one standby device. Each NE runs the same process instance, and there's a usage order between the active and standby devices: the active device takes precedence over the standby. Standby devices also follow a usage order, with each standby device being used sequentially according to that order. NEs in a NE group don't operate simultaneously. Instead, a single NE serves as a representative NE, representing all NEs in the group and running the corresponding process instance. This representative NE is the target NE for the NE group, the target NE in the next-level NE.

[0077] Further, refer to Figure 7 The process shown determines the target NE in the NE group. The specific process is as follows:

[0078] S701: Obtain a usage order between each single network element in the next-level network element.

[0079] S702: Test each single network element in turn to see if it has logged in successfully according to the usage order.

[0080] S703: Determine the first single network element that successfully logs in as the target network element.

[0081] Obtain the usage order between each single network element as described above (the usage order between the main device and the backup device, and the usage order between each backup device), and test each single network element in turn to see if it has logged in successfully according to the usage order. Only the single network element that has successfully logged in can run the process instance, and the first single network element that has successfully logged in will be determined as the target network element for running the process instance. Single network elements that have not been logged in subsequently will no longer be logged in. For example, first, according to the usage order between the main device and the backup device, check whether the main device has logged in successfully. If the login is successful, the main device will be used as the target network element. If the login is unsuccessful, then according to the usage order between the backup devices, check whether each backup device has logged in successfully, and determine the first backup device that has successfully logged in as the target network element.

[0082] After determining the target network element (a single network element) in the network element group, a sending relationship is established between the upper-level network element and the target network element, without establishing a sending relationship between the upper-level network element and other single network elements in the network element group.

[0083] like Figure 8 As shown in ①, based on Figure 3 The first-level network elements and the second-level network elements shown in ②, the second-level network elements are network element group E, which consists of two single network elements (network element B and network element D), and the network element group E is identified as a network element group type. Further identify the network element relationship between the single network elements in the network element group E, and identify that network element B and network element D are in a master-slave relationship, and network element B is the master device, and network element D is the backup device. Then, according to the usage order between network element B and network element D, first check whether network element B has logged in successfully, and then check whether network element D has logged in successfully. Among them, if network element B logs in successfully, network element B is determined as the target network element of network element group E. If network element B logs in unsuccessfully, then check whether network element D has logged in successfully. If network element D has logged in successfully, then network element D is determined as the target network element of network element group E. For example, it is detected that network element B has logged in successfully, such as Figure 8As shown in ①, a sending relationship is established between network element A and network element B, but there is no need to establish a sending relationship between network element A and network element D. Therefore, when running a business process, network element A calls the second-level network element based on the calling relationship between the first-level network element and the second-level network element, that is, calls network element group E. Network element A sends the process instance originally sent to the second-level network element, such as process instance e, to network element B based on the sending relationship between network element A and network element B. In this way, the upper-level network element (network element A) accurately sends the process instance to a single network element (network element B) in the next-level network element (network element group), so that a single network element represents the network element group to normally run the process instance received by the network element group, thereby achieving the effect of the network element group normally running a process instance. This avoids the situation where multiple single network elements in the next-level network element (network element group) cannot jointly run a process instance.

[0084] A non-primary / standby relationship means that the individual NEs in a NE group are used in no particular order, and each NE runs a different portion of the same process instance. This means that each NE has a corresponding node process instance, and the node process instances corresponding to each NE combine to form the same complete process instance. This shows that in a non-primary / standby relationship, each NE is responsible for running the process instance and cannot represent one another. Therefore, each NE in a NE group is a target NE, i.e., the target NE in the next-level NE.

[0085] After determining the target network elements in the network element group (all single network elements in the network element group), a delivery relationship is established between the upper-level network element and each single network element.

[0086] Further, refer to Figure 9 The process shown determines the node process instance sent to the target network element in the network element group. The specific process is as follows:

[0087] S901: Obtain the number of single network elements of all single network elements.

[0088] S902: Split the process instance corresponding to the next-level network element into multiple node process instances according to the number of single network elements, where each node process instance corresponds to a single network element.

[0089] In order to avoid overlap between the node process instances run by each single network element in a network element group, the node process instances run by each single network element are divided. In this embodiment, the process instances can be divided according to the number of single network elements in all the single network elements in the network element group. The division is a continuous and non-overlapping division, so as to ensure that each single network element has a corresponding node process instance, and there is no duplication between the node process instances, and all the node process instances are combined together to form a complete process instance. Based on the issuing relationship between the upper-level network element and the single network elements in the network element group, the corresponding node process instance is issued to each single network element to enable each single network element to run the corresponding node process instance, thereby realizing the common operation of the process instance by all the single network elements in the network element group, so that the network element group can run the process instance normally.

[0090] like Figure 8 As shown in ②, based on Figure 3 In the first-level and second-level network elements shown in step ②, the second-level network elements are network element group E, which consists of two single network elements (network element B and network element D). Network element group E is identified as a network element group type. The network element relationships between the single network elements in network element group E are further identified, and it is determined that network element B and network element D are not in a primary-backup relationship. Therefore, a delivery relationship is established between network element A and network element B, and between network element A and network element D, respectively. Therefore, when running a service process, network element A calls the second-level network element based on the calling relationship between the first-level and second-level network elements, that is, calls network element group E. Based on the delivery relationship between network element A and network element B, and the delivery relationship between network element A and network element D, network element A splits the process instance (for example, process instance e) into two node process instances (node ​​process instance e1 and node process instance e2). Node process instance e1 is delivered to network element B, and node process instance e2 is delivered to network element D. In this way, after the upper-level network element (network element A) splits the process instance into node process instances, it accurately sends them to all single network elements (network element B and network element D) in the next-level network element (network element group). Each single network element runs a node process instance in a process instance, achieving the effect of each single network element in the network element group jointly running a process instance, so that the network element group can normally run a process instance. This avoids the situation where multiple single network elements in the next-level network element (network element group) cannot jointly run a process instance.

[0091] In some embodiments, the upper level network element calls the lower level network element based on the calling order, and the lower level network element includes several or all of the above network element types (single network element type, network element group type and the network element relationship within the network element group is the master-slave relationship, network element group type and the network element relationship within the network element group is the non-master-slave relationship), then the upper level network element can refer to the above process when establishing a issuing relationship with each type of lower level network element. Figure 10As shown, the upper-level network element (network element A) calls the lower-level network elements (network element B, network element C, network element group D, and network element group E) based on the calling order. Network element A identifies the network element type of each lower-level network element and recognizes that network element B and network element C are both single network element types. Network element A then establishes a delivery relationship with network element B and network element C, respectively, and delivers corresponding process instances, such as process instance b and process instance c, to network element B and network element C, respectively. It is recognized that network element group D and network element group E are both network element group types. It is further recognized that the network element relationship between the single network elements (network element D1 and network element D2) within network element group D is a primary-backup relationship. Furthermore, it is detected that network element D1 has successfully logged in according to the usage order. A delivery relationship is then established between network element A and network element D1, and there is no need to establish a delivery relationship between network element A and network element D2. If the process instance delivered by network element A to network element group D is process instance d, network element A delivers process instance d to single network element D1. It is further identified that the network element relationship between each single network element (network element E1 and network element E2) in network element group E is a non-master-backup relationship, and a sending relationship is established between network element A and network element E1, and network element A and network element E2 respectively. If the process instance sent by network element A to network element group E is process instance e, network element A splits process instance e into node process instance e1 and node process instance e2, and sends node process instance e1 to network element E1, and sends node process instance e2 to network element E2.

[0092] S103: Generate a business process corresponding to the business requirement based on the calling sequence of the network elements at each level, the issuing relationship between the upper-level network element and the lower-level network element, and the process instance.

[0093] Based on the calling sequence of the network elements at all levels, the issuing relationship between the upper level network element and the lower level network element, and the process instance, a business process corresponding to the business requirements can be generated, such as Figure 5 、 Figure 8 、 Figure 10 shown.

[0094] Correspondingly, to run the above business processes on network elements at all levels, you can refer to Figure 11 The specific process is as follows:

[0095] S1101. Determine the next-level network element of the current-level network element based on the calling order of the network elements at each level.

[0096] S1102: Determine a target network element in the next-level network element based on the delivery relationship.

[0097] S1103: The current-level network element sends a corresponding process instance to a target network element in the next-level network element.

[0098] S1104: Run the process instance on the target network element.

[0099] To run Figure 10 Taking the business process shown as an example, network element A obtains all process instances (process instance a, process instance b, process instance c, process instance d, process instance e). If network element A is the current-level network element, then based on the calling order of network elements at each level, network element B, network element C, network element group D, and network element group E are the next-level network elements. Network element A runs process instance a. Based on the issuing relationship between network element A and each next-level network element, network element A issues the corresponding process instance to the target network element in each next-level network element. The process of determining the target network element in the next-level network element here is similar to the process of determining the target network element in the next-level network element in the above business process creation, and will not be repeated here. Specifically, network element A sends process instance b to network element B, sends process instance c to network element C, sends process instance d1 to single network element D1 in network element group D, issues node process instance e1 to single network element E1 in network element group E, and issues node process instance e2 to single network element E2. After receiving the corresponding process instance, each single network element runs the process instance to complete the overall operation of the above business process on network elements at all levels.

[0100] The present application also provides a business process arrangement device, such as Figure 12 As shown, the device includes:

[0101] The determining unit 100 is configured to determine the calling sequence and process instances of network elements at each level based on business requirements, wherein the process instances are used to provide corresponding calling methods for the network elements at each level;

[0102] An establishing unit 200 is configured to establish a dispatching relationship between an upper-level network element and a target network element in the lower-level network element based on the network element type of the lower-level network element, wherein the target network element is a single network element, and the dispatching relationship is used to instruct the upper-level network element to send a corresponding process instance to the target network element in the lower-level network element;

[0103] The generating unit 300 is configured to generate a business process corresponding to the business requirement based on the calling sequence of the network elements at each level, the issuing relationship between the upper-level network element and the lower-level network element, and the process instance.

[0104] In one implementation, the establishment unit 200 is also used to obtain the interface parameters of the next-level network element before establishing a downlink relationship between the upper-level network element and the target network element in the next-level network element, the interface parameters including the network element type value parameter of the next-level network element, and the network element type value parameter is used to indicate the network element type of the next-level network element; based on the network element type value parameter of the next-level network element, determine the network element type of the next-level network element.

[0105] In one implementation, the establishment unit 200 is also used to determine the target network element in the next-level network element based on the network element type of the next-level network element, wherein, if the network element type of the next-level network element is a single network element type, the target network element refers to each of the next-level network elements; if the network element type of the next-level network element is a network element group type, the target network element refers to one or all single network elements in the next-level network elements.

[0106] In one implementation, if the network element type of the next-level network element is a network element group type, the establishment unit 200 is also used to identify the network element relationship between each single network element in the next-level network element, and the network element relationship includes a master-slave relationship and a non-master-slave relationship; if the network element relationship between each single network element is the master-slave relationship, then the target network element refers to a single network element in the next-level network element; if the network element relationship between each single network element is the non-master-slave relationship, then the target network element refers to all single network elements in the next-level network element.

[0107] In one implementation, if the network element relationship between the single network elements is the master-slave relationship, the establishment unit 200 is also used to obtain the usage order between the single network elements in the next-level network element; according to the usage order, test each single network element in turn to see whether it has logged in successfully; and determine the first single network element that has successfully logged in as the target network element.

[0108] In one implementation, if the network element type of the next-level network element is a single network element type, the establishment unit 200 is also used to establish a downward relationship between the upper-level network element and each of the lower-level network elements, and the downward relationship instructs the upper-level network element to send a corresponding process instance to the corresponding lower-level network element.

[0109] In one implementation, if the network element type of the next-level network element is a network element group type, and the network element relationship between each single network element in the next-level network element is a master-slave relationship, the establishment unit 200 is also used to establish a downward relationship between the upper-level network element and the target network element, and the downward relationship indicates that the upper-level network element directly sends the corresponding process instance to the target network element, and the process instance refers to a process instance corresponding to the next-level network element.

[0110] In one implementation, if the network element type of the next-level network element is a network element group type, and the network element relationship between each single network element in the next-level network element is a non-master-backup relationship, the establishment unit 200 is also used to establish a downward relationship between the next-level network element and each single network element in the next-level network element, and the downward relationship instructs the next-level network element to send a corresponding node process instance to the corresponding single network element, wherein the node process instance corresponds one-to-one to the single network element, different single network elements correspond to different node process instances, and the summary of all the node process instances is the same as a process instance corresponding to the next-level network element.

[0111] It can be seen from the above technical solutions that the process orchestration method, operation method and orchestration device provided in the embodiments of the present application, when orchestrating business processes, determine the calling order and process instances of network elements at all levels based on business needs, and further establish a sending relationship between the target network element in the upper-level network element and the lower-level network element based on the network element type of the lower-level network element. Based on the calling order of network elements at all levels, the sending relationship between the upper-level network element and the lower-level network element, and the process instance, a business process corresponding to the business need is generated. During orchestration, by directly establishing a sending relationship between the upper-level network element and a single network element in the lower-level network element, the problem that the lower-level network element is not a single network element and cannot accurately receive the process instance is avoided. This makes the orchestration not only applicable to business process types that only contain single network elements, but can also be applied to more business process types.

[0112] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0113] It should be understood that the present application is not limited to the exact structure described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A business process orchestration method, characterized in that: The method comprises: Determine the calling sequence and process instances of network elements at all levels based on business requirements, and the process instances are used to provide corresponding calling methods for network elements at all levels; Based on the network element type of the next-level network element, establishing a sending relationship between the previous-level network element and a target network element in the next-level network element, wherein the target network element is a single network element, and the sending relationship is used to instruct the previous-level network element to send a corresponding process instance to the target network element in the next-level network element; Based on the calling sequence of the network elements at each level, the issuing relationship between the upper-level network element and the lower-level network element, and the process instance, a business process corresponding to the business demand is generated.

2. The business process orchestration method according to claim 1, characterized in that: The network element type based on the next-level network element, before establishing a distribution relationship between the previous-level network element and the target network element in the next-level network element, further includes: Acquire interface parameters of the next-level network element, where the interface parameters include a network element type value parameter of the next-level network element, where the network element type value parameter is used to indicate the network element type of the next-level network element; The network element type of the next-level network element is determined based on the network element type value parameter of the next-level network element.

3. The business process orchestration method according to claim 1, wherein: The establishing of a distribution relationship between the upper-level network element and the target network element in the lower-level network element based on the network element type of the lower-level network element includes: determining a target network element in the next-level network element based on the network element type of the next-level network element, Wherein, if the network element type of the next-level network element is a single network element type, the target network element refers to each of the next-level network elements; If the network element type of the next-level network element is a network element group type, the target network element refers to one or all single network elements in the next-level network elements.

4. The business process orchestration method according to claim 3, characterized in that: If the network element type of the next-level network element is a network element group type, determining a target network element in the next-level network element based on the network element type of the next-level network element includes: Identify the network element relationship between each single network element in the next-level network element, wherein the network element relationship includes a master-slave relationship and a non-master-slave relationship; If the network element relationship between the single network elements is the master-standby relationship, the target network element refers to a single network element in the next-level network element; If the network element relationship between the single network elements is the non-active / standby relationship, the target network elements refer to all the single network elements in the next-level network elements.

5. The business process orchestration method according to claim 4, characterized in that: If the network element relationship between the single network elements is the master-standby relationship, determining the target network element in the next-level network element based on the network element type of the next-level network element includes: Obtaining a usage order between each single network element in the next-level network element; Test each network element in turn to see if it has logged in successfully according to the order of use described above; The first single network element that successfully logs in is determined as the target network element.

6. The business process orchestration method according to any one of claims 1 to 3, characterized in that: If the network element type of the next-level network element is a single network element type, establishing a delivery relationship between the previous-level network element and the target network element in the next-level network element includes: A sending relationship is established between the upper-level network element and each of the lower-level network elements respectively, and the sending relationship instructs the upper-level network element to send a corresponding process instance to the corresponding lower-level network element.

7. The business process orchestration method according to claim 4 or 5, characterized in that: If the network element type of the next-level network element is a network element group type, and the network element relationship between the single network elements in the next-level network element is a master-slave relationship, then establishing a delivery relationship between the previous-level network element and the target network element in the next-level network element includes: A sending relationship is established between the upper-level network element and the target network element, wherein the sending relationship instructs the upper-level network element to directly send a corresponding process instance to the target network element, where the process instance refers to a process instance corresponding to the lower-level network element.

8. The business process orchestration method according to claim 4, characterized in that: If the network element type of the next-level network element is a network element group type, and the network element relationship between the single network elements in the next-level network element is a non-active / standby relationship, then establishing a delivery relationship between the previous-level network element and the target network element in the next-level network element includes: A sending relationship is established between the next-level network element and each single network element in the next-level network element respectively, and the sending relationship instructs the next-level network element to send a corresponding node process instance to the corresponding single network element, wherein the node process instance corresponds one-to-one to the single network element, different single network elements correspond to different node process instances, and the summary of all the node process instances is the same as a process instance corresponding to the next-level network element.

9. A business process operation method, characterized in that: Running the service process according to any one of claims 1 to 8 on network elements at all levels, the method comprising: Determine the next level network element of the current level network element based on the calling order of the network elements at each level; Determining a target network element in the next-level network element based on the issuing relationship; The current-level network element sends the corresponding process instance to the target network element in the next-level network element; Run the process instance on the target network element.

10. A business process orchestration device, characterized in that: The device comprises: A determination unit, configured to determine a calling sequence and a process instance of network elements at each level based on business requirements, wherein the process instance is used to provide corresponding calling methods for the network elements at each level; an establishing unit, configured to establish, based on a network element type of a next-level network element, a sending relationship between an upper-level network element and a target network element in the next-level network element, wherein the target network element is a single network element, and the sending relationship is used to instruct the upper-level network element to send a corresponding process instance to the target network element in the next-level network element; A generating unit is configured to generate a business process corresponding to the business requirement based on the calling sequence of the network elements at each level, the issuing relationship between the upper-level network element and the lower-level network element, and the process instance.

Images