WO2018107442A1 - 一种业务编排方法、装置及服务器 - Google Patents

一种业务编排方法、装置及服务器 Download PDF

Info

Publication number
WO2018107442A1
WO2018107442A1 PCT/CN2016/110158 CN2016110158W WO2018107442A1 WO 2018107442 A1 WO2018107442 A1 WO 2018107442A1 CN 2016110158 W CN2016110158 W CN 2016110158W WO 2018107442 A1 WO2018107442 A1 WO 2018107442A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
operation model
logical connection
control layer
business
Prior art date
Application number
PCT/CN2016/110158
Other languages
English (en)
French (fr)
Inventor
高志江
林毅
刘欣
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CN201680069212.2A priority Critical patent/CN108432208B/zh
Priority to EP16924165.0A priority patent/EP3544260B1/en
Priority to ES16924165T priority patent/ES2898050T3/es
Priority to PCT/CN2016/110158 priority patent/WO2018107442A1/zh
Publication of WO2018107442A1 publication Critical patent/WO2018107442A1/zh
Priority to US16/442,459 priority patent/US11178233B2/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0895—Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5011—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resources being hardware resources other than CPUs, Servers and Terminals
    • 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/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5083—Techniques for rebalancing the load in a distributed system
    • G06F9/5088—Techniques for rebalancing the load in a distributed system involving task migration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/12—Discovery or management of network topologies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/40—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using virtualisation of network functions or resources, e.g. SDN or NFV entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5051—Service on demand, e.g. definition and deployment of services in real time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5041—Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
    • H04L41/5054—Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/62—Establishing a time schedule for servicing the requests
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0876—Aspects of the degree of configuration automation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer

Definitions

  • the present application relates to the field of wireless communications technologies, and in particular, to a service scheduling method, apparatus, and server.
  • SDN Software Defined Networking
  • the transport network has a centralized "brain" and direct control of physical devices through the southbound interface.
  • the industry began to gradually shift the focus of SDN from the controller south to the controller northbound interface. It is hoped that with the standardized transmission network model and the northbound API interface and open source controller, the traditional transmission network will be broken, and the ability of the transmission network will be opened through the standard northbound interface to truly open the network.
  • the embodiment of the present application provides a service scheduling method, device, and server, which are used to solve the current flexible and ever-changing service requirements in the prior art.
  • the difficulty in service scheduling and programming in the SDN is still high, and the operation and maintenance personnel cannot Technical issues for business orchestration and programming in SDN online.
  • an embodiment of the present application provides a service orchestration method, where the method includes:
  • the service flow diagram includes a plurality of operation model identifiers and a logical connection relationship between the plurality of operation model identifiers
  • the logical connection relationship is an execution order of the business process flowchart
  • the executable code for executing the service flow diagram is generated according to the corresponding scheduling parameter of each operation model identifier and the logical connection relationship.
  • the preliminary arrangement of the services to be arranged is simplified, for each operation.
  • the model identifier corresponds to the scheduling parameter set by the operation.
  • the scheduling parameter is the existing network resource that is required to perform the corresponding operation
  • the interaction with the control layer can be used to verify whether the network exists or has the right to obtain the existing network resources.
  • the online verification process is compiled into executable code when the online verification is passed, thereby realizing the online compilation of the business.
  • the multiple operation model identifiers and the logical connection relationship are graphically displayed on the user operation interface;
  • a service flow diagram consisting of the plurality of operational model identifiers and the logical connection relationship is determined.
  • the optional embodiment displays a plurality of operation model identifiers and logical connection relationships in a graphical manner on the user operation interface, and provides a graphical service programming environment for the user to quickly respond to customized business requirements. It also reduces the difficulty of business orchestration.
  • the method further includes:
  • the optional embodiment performs logical check on the business logic relationship and performs semantic syntax check on the scheduling parameters, which can initially ensure the feasibility of the business arrangement.
  • the obtaining, by the control layer, the current network status, and verifying whether the current network resource is obtained according to the obtained status of the current network including:
  • the innovation platform integrates network control, service provision and business integration development environment, and can be used for operators. It provides complete solutions from innovative design to simple development, rapid deployment, and automatic maintenance, enabling operators to quickly customize their services and cope with complex operation and maintenance requirements. Compared with the prior art, the true implementation of the application layer in the SDN architecture is completely open, and can meet the current flexible and versatile business orchestration requirements.
  • An interaction interface is created to interact with the control layer, and the interaction interface is configured to apply to the control layer for the existing network resources required to run the executable code.
  • each operation model identifier corresponds to an operation model
  • each operation model is a basic component or an enhancement component based on an open source of an SDN system architecture, and each open source basic component or enhancement component is converted into an operation when invoked.
  • the script file corresponding to the model (equivalent to a standard execution language for business processes).
  • the logical connection relationship between the operation model identifiers is a logical component based on the open source of the SDN system architecture.
  • a script file describing the logical relationship between the multiple operation models can be formed. Based on this, it is convenient to process the preliminary orchestration business process into a business process execution language and convert the business process execution language into executable code, thereby reducing the difficulty of business compilation.
  • the method further includes:
  • the interaction interface between the server and the control layer such as the NBI interface in the SDN architecture, applies for the resources required for running the programmed service, and can extend the function of the NBI interface, and apply to the SDN control layer through the interaction interface.
  • Running the resources required for the orchestration business, and running the orchestration business according to the requested resources can truly realize the business of the online operation.
  • the second aspect of the present application provides a service orchestration device, which is used to implement any one of the foregoing first aspects, and includes corresponding functional modules, which are respectively used to implement the steps in the foregoing method.
  • an embodiment of the present application provides a server, including: a processor, a transceiver, and a memory;
  • the memory is configured to store an instruction
  • the processor is configured to control an instruction stored in the memory, and control the transceiver to perform signal reception and signal transmission, when the processor executes the instruction stored in the memory,
  • the processor is operative to perform any of the methods of the first aspect above.
  • FIG. 1 is a schematic structural diagram of an exemplary SDN system according to an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a server for executing a service orchestration method according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a service scheduling method according to an embodiment of the present application.
  • FIG. 4 is a schematic diagram of a graphical representation of an operation model identifier and a logical connection relationship according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of a service flow diagram constructed by example 1 according to an embodiment of the present disclosure
  • FIG. 6 is a schematic diagram of a service flow diagram constructed by example 2 according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic diagram of a service flow diagram constructed by example 3 according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a service orchestration apparatus according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of an SDN system deployed with a service orchestration device according to an embodiment of the present disclosure.
  • FIG. 1 is a system architecture diagram of the SDN according to the embodiment of the present application, including an application layer, a control layer, and a data layer.
  • a controller is deployed on the control layer.
  • the controller integrates centralized algorithms and has centralized network-wide centralized control functions such as network planning, resource optimization, and performance evaluation.
  • An NBI interface is opened between the application layer and the control layer, that is, the NorthBound Interface, referred to as the northbound interface
  • the SBI interface is opened between the control layer and the data layer, that is, the SouthBound Interface, referred to as the southbound interface.
  • the physical layer is deployed on the data layer.
  • the physical devices are located in the south of the SDN architecture.
  • the controller communicates with these devices through the SBI to implement the devices.
  • Direct control Compared with the existing SDN architecture, the SDN architecture applicable to the embodiment of the present application adds a service orchestration device at the application layer, and the service orchestration device is located in the north direction of the SDN architecture, and communicates and interacts with the controller through the NBI.
  • the service orchestration device provides open platform development and management capabilities for end users, application developers, and administrators through the NBI interface, thereby further meeting the needs of SDN development, operation, and maintenance.
  • the service orchestration in the embodiment of the present application is based on the service orchestration performed by the SDN system architecture.
  • a service to be arranged is determined.
  • the service to be arranged is an execution process for setting and managing the transmission network according to the service requirement, and based on the determined to-be-arranged service, initially determining the service to be arranged.
  • the setting management operation here includes various types of network tasks, and can be various management tasks for network devices and network resources in the SDN architecture.
  • the execution flow of a business usually includes multiple operational steps, and the order in which the multiple operational steps are performed.
  • the execution process of the service to be arranged it is determined whether the corresponding network resource can be applied from the SDN system architecture to support the smooth execution of the to-be-arranged service. Row. Then, when it is determined that the corresponding network resource can be applied from the SDN system architecture to support the to-be-arranged service, the execution process of the orchestration service is compiled to form executable code. Finally, based on the compiled executable code, the corresponding network resources are applied from the SDN system architecture to run the compiled executable code, thereby satisfying the user's business requirements.
  • FIG. 2 exemplarily shows a schematic structural diagram of a server provided by an embodiment of the present application, where the server is used to execute a service orchestration method process in the embodiment of the present application.
  • the server includes a processor 201 and a transceiver 205, and optionally, a memory 202 and a communication interface 203, wherein the processor 201, the memory 202, the communication interface 203, and the transceiver 205 are mutually connected by a bus 204.
  • the memory may be integrated in the processor 201 or may be independent of the processor 201.
  • the bus 204 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus 204 can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 2, but it does not mean that there is only one bus or one type of bus.
  • the memory 202 may include a volatile memory such as a random-access memory (RAM); the memory may also include a non-volatile memory such as a flash memory (flash) Memory), hard disk drive (HDD) or solid-state drive (SSD); the memory 202 may also include a combination of the above types of memory.
  • RAM random-access memory
  • flash non-volatile memory
  • HDD hard disk drive
  • SSD solid-state drive
  • the communication interface 203 can be a wired communication access port, a wireless communication interface, or a combination thereof, wherein the wired communication interface can be, for example, an Ethernet interface.
  • the Ethernet interface can be an optical interface, an electrical interface, or a combination thereof.
  • the wireless communication interface can be a WLAN interface.
  • the processor 201 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and an NP.
  • CPU central processing unit
  • NP network processor
  • the processor 201 may further include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be complex A programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.
  • CPLD complex A programmable logic device
  • FPGA field-programmable gate array
  • GAL general array logic
  • the memory 202 in the embodiment of the present application is used to store instructions, and the processor 201 is configured to control the transceiver 205 to perform signal reception and signal transmission according to the instructions stored in the execution memory 202.
  • the processor 201 executes the instruction stored in the memory 202, The processor 201 is used to:
  • the service flow diagram includes a plurality of operation model identifiers and a logical connection relationship between the plurality of operation model identifiers; wherein, the logical connection relationship The order of execution of the business process diagram;
  • the corresponding execution parameters are generated according to each operation model identifier, and the logical connection relationship is generated, and executable code for executing the business flow chart is generated.
  • the processor 201 simplifies the preliminary orchestration of the to-be-arranged service by constructing a service flow diagram composed of a plurality of operation model identifiers and logical connection relationships between the plurality of operation model identifiers, and identifies each operation model identifier.
  • a service flow diagram composed of a plurality of operation model identifiers and logical connection relationships between the plurality of operation model identifiers, and identifies each operation model identifier.
  • the scheduling parameter is the existing network resource required to perform the corresponding operation
  • the execution of the arranged business flow chart compiles the arranged business flow chart into executable code when the online verification is passed, thereby realizing the online compilation of the business.
  • multiple operation model identifiers and logical connection relationships are graphically displayed on the user operation interface.
  • the processor 201 is configured to: according to the operation of the user in the user operation interface An instruction is executed to determine a plurality of operation model identifiers and logical connection relationships selected by the user, and to determine a service flow diagram composed of a plurality of operation model identifiers and logical connection relationships.
  • Graphically displaying multiple operational model identifiers and logical connection relationships on the user interface provides users with a graphical business programming environment that enables users to quickly respond to customized business needs while reducing business The difficulty of programming.
  • the processor 201 is further configured to: perform logic verification on the logical connection relationship; and perform semantic verification on the scheduling parameter.
  • the logical check of the business logic relationship and the semantic grammar check of the scheduling parameters can initially guarantee the feasibility of business orchestration.
  • the processor 201 is configured to: obtain an existing network state by using an interaction interface that interacts with the control layer, and query whether the existing network resource exists in the current network state according to the current network state; and/or, according to the current The status of the network determines whether there is permission to apply for live network resources.
  • the processor 201 can interact with a central controller of the control layer, the processor 201 can also interact with a synergy of the control layer, and the processor 201 can also interact with the network management system of the control layer.
  • the interaction interface between the processor 201 and the control layer is an NBI interface in the SDN architecture, so that the function of the NBI interface can be further extended.
  • the interaction interface with the control layer may also be a T-API standard interface defined by an Open Networking Foundation (ONF) organization.
  • ONF Open Networking Foundation
  • the interaction interface with the control layer may also be an IETF standard interface (Internet Engineering Task Force, Internet Engineering Task Force, referred to as IETF standard interface).
  • IETF standard interface Internet Engineering Task Force, Internet Engineering Task Force, referred to as IETF standard interface
  • the innovation platform integrates network control, service provision and business integration development environment, and can be used for operators. Provides complete solutions from innovative design to simple development, rapid deployment, and automated maintenance to enable operators to do business quickly Customize and calmly deal with complex operation and maintenance needs. Compared with the prior art, the true implementation of the application layer in the SDN architecture is completely open, and can meet the current flexible and versatile business orchestration requirements.
  • the processor 201 is configured to: generate, according to each operation model, a corresponding scheduling parameter, generate a script file corresponding to each operation model identifier; and identify, according to each operation model, a script file and a logical connection relationship of the corresponding operation, Generate executable code that performs all operations in the business process diagram; and create an interaction interface that interacts with the control layer, and the interaction interface is used to request the control layer for the live network resources required to run the executable code.
  • each operation model identifier corresponds to an operation model
  • each operation model is a basic component or an enhancement component based on an open source of the SDN system architecture, and each open source basic component or
  • each open source basic component or When the enhancement component is called it can be converted into a script file corresponding to the operation model (equivalent to a standard execution language of the business process).
  • the logical connection relationship between the operation model identifiers is a logical component based on the open source of the SDN system architecture.
  • a script file describing the logical relationship between the multiple operation models can be formed.
  • mapping relationship between the basic component, the enhanced component, and the operation model identifier in the service flow chart, and the mapping relationship between the logical component and the logical connection relationship between the multiple operation model identifiers are described in the method flow.
  • the processor 201 is further configured to: obtain the existing network resource that is applied for by using the interaction interface; run the executable code according to the existing network resource that is applied for;
  • the existing network resources that are accessed by the created interface help the control layer to complete the resource management tasks of the underlying resource query, the underlying resource reservation, and the notification processing of the underlying resource changes.
  • the resources required by the business, and running the programmed services according to the resources requested, can truly realize the business of the online operation.
  • FIG. 3 exemplarily shows an embodiment of the present application.
  • a method flow diagram is executed by a processor deployed on a server to perform business orchestration, as shown in FIG. 3, the method includes the following steps:
  • Step 301 Obtain a service flow diagram of the to-be-programmed service, where the to-be-arranged service is used to perform a management and control operation on the transport network; the service flow diagram includes a plurality of operation model identifiers and a logical connection relationship between the plurality of operation model identifiers; The logical connection relationship is the execution order of the business process flowchart;
  • Step 302 Acquire scheduling parameters corresponding to each operation model identifier, and obtain the current network status through the control layer when the scheduling parameter is the current network resource required to execute the service flow diagram, and check according to the obtained current network status. Can you get the live network resources you need?
  • Step 303 When the verification is passed, the executable code for executing the service flow chart is generated according to the corresponding scheduling parameter and the logical connection relationship of each operation model identifier.
  • the execution process of the to-be-arranged service includes multiple operations and the execution sequence of the multiple operations.
  • the embodiment of the present application constructs a plurality of operations to be arranged in a manner of constructing a service flow chart.
  • the constructed business process diagram is composed of a plurality of preset operation model identifiers and logical connection relationships between the plurality of operation model identifiers, and the plurality of operation model identifiers represent execution steps of multiple operations of the service to be arranged
  • the logical connection relationship between the plurality of operation model identifiers represents the execution order of the constructed business flow chart, and represents the execution order of the plurality of operations to be orchestrated.
  • the embodiment of the present application provides a graphical service programming environment, so that the user can quickly respond to customized service requirements.
  • the provided graphical business programming environment is specifically: displaying a plurality of operation model identifiers and logical connection relationships in a graphical manner on the user operation interface, where the user operation interface is a graphical business programming environment.
  • some components are open sourced to represent an operation model of various operations of the transport network service, and a logical model representing the execution order between the multiple operation models, and the open source is implemented.
  • the operational model and the logical model are both called transport network components, and the transport network components usually include basic components, enhancement components, and logical components.
  • the basic components are used for basic management and control operations on network devices or network services in the transport network.
  • the basic control operations include connection management, network element management, service model management, or OAM management.
  • These basic components are SDN transport network operation models based on the NBI interface or T-API interface of the open SDN control layer or the IETF standard interface for secondary development or encapsulation.
  • the basic component CreateService representing the creation operation represents the basic component QueryService of the query operation
  • the basic component UpdateService representing the update operation
  • the basic component DeleteService representing the deletion operation, which represents the basic component QueryTopology for querying the network topology.
  • the policy model provides users with encapsulated policies, such as the time policy component Timer, which provides timing, looping, and other common time policies.
  • the algorithm model provides basic algorithm, network optimization, business analysis and other algorithm functions.
  • Logic component the various business logic provided for basic control operations. These logic components are based on the design principles of the program and the characteristics of the transfer service. They include mechanisms such as sequence, branch, loop, and event trigger to implement basic components and enhance components. Various logical combinations. For example, Start, End, Sequential Logic, Parallel Gateway Logic, and so on.
  • the transport network component in the embodiment of the present application is not limited to the above three components, and should also include independent components designed by a third party in the future, and these independent components may have special transfer functions, which are collectively referred to in the embodiments of the present application.
  • the stand-alone component is a third-party component, and the third-party component of course includes components having the same functions as the above-described basic component, enhancement component, and logic component.
  • the operation model identifier in the embodiment of the present application is the identifier of the basic component and the enhanced component in the embodiment of the present application.
  • the logical connection relationship between the multiple operation model identifiers in the embodiment of the present application is the logic that represents the basic component and the logical combination relationship between the enhanced components in the embodiment of the present application. The identity of the component.
  • the identifiers of the basic components are: Create Service, QueryService, UpdateService, DeleteService, QueryTopology.
  • the identity of the enhanced component is Timer
  • the identity of the logical component is Start, End, Sequential Logic, Parallel Gateway Logic, and so on.
  • graphically identifying multiple operational model identifications and logical connection relationships is to graphically identify the identity of the transport network components, including basic components, enhancement components, logic components, and third-party components.
  • FIG. 4 An example of the graphical operation model identification and logical connection relationship, optionally, as shown in FIG. 4, "Create Service”, "Query Service”, “Update Service”, " Indicators such as “Timer”, “Start”, “End”, “Sequential Logic”, “Parallel Gateway Logic”, etc. are displayed in a frame on the user's operation interface.
  • the frame is available for the user to select into the business programming interface in various ways, such as copying, pasting, inserting, dragging, importing, and the like.
  • the manner of graphically designing the operation model identifier and the logical connection relationship is not limited to displaying the identifier of the transport network component in the frame, and any other manner that can realize the graphical representation of the operation model identifier and the logical connection relationship should fall. It is within the scope of protection of the embodiments of the present application.
  • the user when constructing the business flow chart of the business to be arranged, the user only needs to select multiple operation model identifiers and logical connection relationships from the user operation interface. Construct a business flow chart for the business to be arranged.
  • the logical connection relationship between the plurality of operation model identifiers selected by the user and the plurality of operation model identifiers can be determined only according to the operation instruction of the user operation interface response, and then the determination can be determined.
  • step 301 is to obtain a service flow diagram, including: determining, according to an operation instruction of the user on the user operation interface, multiple operation model identifiers and logical connection relationships selected by the user, and determining identification and logic by multiple operation models.
  • a business process diagram consisting of connection relationships.
  • the user can store the configured service flow chart as a service template, and when the subsequent service needs to be arranged, the service template of the service to be arranged can be obtained by searching or selecting the stored service template. Therefore, the obtained business flow chart can also be directly from the pre-stored business template.
  • the selected business process diagram can be directly from the pre-stored business template.
  • a plurality of operations to be arranged in a business need to be supported by some elements, which are called scheduling parameters, and each operation model identifier in the business flow chart to be orchestrated is only the identifier of the basic component or the enhanced component, and therefore, the constructed service
  • the flow chart needs to set the scheduling parameters for each operation model identifier.
  • one of the operations to be programmed is “Query the bandwidth ODU2 between the source node A and the sink node E.”
  • the operation model identifier of this operation may be only “QueryService”, and the query item supporting this query operation is “source node A”. "Site node E" and "bandwidth ODU2".
  • these query items "source node A”, "sink node E”, and "bandwidth ODU2" need to be arranged as scheduling parameters to the business process.
  • the processor performing the service orchestration it is necessary to obtain the scheduling parameters corresponding to each operation model identifier in the service flow chart.
  • the scheduling parameter corresponding to each graphical operation model identifier in the service flow diagram may be set through the user operation interface.
  • each operation model map has a plurality of parameter options available for selection, and for the selected parameter options, the scheduling parameters required for each operation of the service to be scheduled may be separately set.
  • the parameter option corresponding to each operation model identifier needs to be pre-stored, and the scheduling parameter corresponding to each parameter option is stored for the parameter setting operation performed by the user on the user operation interface.
  • step 302 the scheduling parameters corresponding to each operation model identifier are obtained, including:
  • a scheduling parameter corresponding to each operation model identifier in the service flow chart Determining, according to an operation instruction of the user on the user operation interface, a scheduling parameter corresponding to each operation model identifier in the service flow chart. Specifically, the corresponding parameter option is identified according to each operation model selected by the user, and the scheduling parameter corresponding to each operation model identifier is determined according to the parameter value input by the user for the selected parameter option.
  • the logic check mainly checks whether the logical connection relationship between the multiple operation model identifiers in the service flow chart is contradictory.
  • the semantic check of the scheduling parameters is mainly to verify whether the scheduling parameters themselves are legal.
  • the corresponding scheduling parameter is usually the set time parameter, or the algorithm parameter or the time parameter, and usually does not need to provide the existing network resources, so usually does not pass.
  • the control layer obtains the status of the live network for verification, and only needs to perform semantic verification. But it does not rule out special circumstances.
  • the corresponding scheduling parameters need to provide the live network resources in addition to the semantic check. Therefore, the control layer needs to obtain the current network status to perform the check. .
  • the SDN system architecture provided by the embodiment of the present application where the existing network resource required to be provided herein refers to the scheduling parameter corresponding to any operation model identifier in the service flow chart, needs to be scheduled from the data layer of the SDN.
  • the current network status obtained by the control layer is the full network resource view of the SDN based on the SDN system architecture. Based on the entire network resource view, the resource status and service status of any node device can be queried.
  • the scheduling parameter is the current network resource that is required to be executed by the service flow diagram
  • the status of the current network is obtained through the control layer, and according to the obtained status of the current network, whether the required current network can be obtained is verified. Resources.
  • the acquiring, by the control layer, the status of the current network, the processor that performs the service orchestration acquires the status of the existing network by using an interaction interface that interacts with the control layer.
  • the processor that performs the service orchestration interacts with the central controller of the control layer, and the processor that performs the service orchestration can also interact with the synergy of the control layer, and the processor that performs the service orchestration can also be connected with the network layer of the control layer.
  • the system interacts.
  • the invoked interface is the control layer NBI interface of the SDN system architecture provided by the embodiment of the present application.
  • the interaction interface with the control layer may also be a T-API standard interface specified by the ONF organization.
  • the interaction interface with the control layer may also be an IETF standard interface.
  • the verification can obtain the current network resource that needs to be provided, including:
  • scheduling parameters include the resources used to execute the service flow diagram, verify whether there is permission to apply for the required resources from the SDN idle resources.
  • step 303 is performed, which specifically includes:
  • the foregoing embodiment has detailed the operation model corresponding to each operation model identifier, and is a basic component or an enhancement component based on the open source of the SDN system architecture, and each open source basic component or enhancement component is called.
  • an open source description language corresponding to the operation may be formed.
  • the description language of the operations may be converted into a script file corresponding to the operation.
  • the logical connection relationship between the operation model identifiers is based on the open source logic components of the SDN system architecture. When each logic component is called, it can form a description of multiple operations.
  • An open source description language that is used to identify the logical relationships between multiple operations.
  • an XML script corresponding to each operation model identifier corresponding operation may be generated according to each operation model identifier corresponding to the scheduling parameter and the open source description language of the basic component or the enhancement component corresponding to each operation model identifier.
  • the XML script file that performs all the operations in the constructed business process flow can be converted into executable code that executes all the operations in the constructed business flow diagram.
  • a BPMN transaction processing model (Business Process Management Initiative, a transaction processing model) may be used to convert the verified business process flow into a business process execution language, and then the business process execution language. Convert to an executable program.
  • the BPMN specification can support the mapping from the created business process flow to the business process execution language, such as the Business Process Execution Language (BPEL).
  • BPEL Business Process Execution Language
  • the processor performing the business orchestration needs to create an interaction interface between the processor performing the business orchestration and the control layer when generating the executable file, and the interaction interface is used for controlling
  • the layer requests the live network resources required to run the programmed executable code.
  • the existing network resources to be provided here refer to the scheduling parameters set for the corresponding operation of any operation model when performing the executable code of the arranged business flow chart, and the resources to be scheduled from the data layer of the SDN need to be
  • the resources scheduled from the data layer of the SDN include the resources requested and/or the resources of the required query.
  • the purpose of scheduling resources from the data layer of the SDN by interacting with the control layer during the verification process is to verify whether there is a resource for the required query and whether there is permission to apply for the required application resource.
  • the purpose of scheduling resources from the data layer of the SDN by interacting with the control layer is to apply for the resources of the required query and the resources to be used.
  • the interaction interface between the processor and the control layer that performs the service orchestration created in step 303 is the control layer NBI of the SDN system architecture. interface.
  • the interaction interface between the processor and the control layer that performs the service orchestration may also be a T-API standard interface specified by the ONF organization.
  • the interaction interface between the processor and the control layer that performs the service orchestration may also be an IETF standard interface.
  • the processor performing the service orchestration also performs the following steps: obtaining the existing network resource that is applied for by the created interaction interface; and running according to the existing network resource that is applied for. Executable code.
  • the existing network resources that are applied for according to the SDN system architecture provided by the embodiment of the present application include the SDN resources required for running the executable code and the SDN resources to be used.
  • the processor performing the business orchestration can perform operation management on the designed services, and we can refer to the successfully designed executable programs as tasks, and the processor performing the business orchestration can complete the task state machine.
  • Various management tasks such as performing tasks, suspending tasks, modifying tasks, and saving tasks as templates.
  • the processor performing the business orchestration needs to perform the verification operation multiple times, and performs the running state verification on the logic of the task online through real-time interaction with the control layer to ensure that the task can be in the live network. normal operation.
  • the processor performing the service orchestration may also notify the control layer to update the status of the existing network according to the existing network resources that are requested by the created interactive interface.
  • the interactive interface interacts with the control layer to assist the control layer to query the underlying resources, reserve the underlying resources, and notify the change of the underlying resources according to the existing network resources applied for.
  • the present application is mainly applicable to an OTN (Optical Transport Network) or WDM (Wavelength Division Multiplexing) network.
  • OTN Optical Transport Network
  • WDM Widelength Division Multiplexing
  • the inventive concept of graphical service orchestration and online compilation of the present application is also applicable to other network environments such as IP.
  • the preliminary arrangement of the services to be arranged is simplified, and the corresponding operation manner is identified for each operation model.
  • Set the scheduling parameters are the existing network resources required to perform the corresponding operations, you can check whether there is or is there online by interacting with the control layer.
  • the authority obtains the existing network resources required to support the execution of the arranged business flow chart, and compiles the arranged business flow chart into executable code when the online verification is passed, thereby realizing the online compilation of the business.
  • the embodiment of the present application provides a service scheduling method that is automatically created by a timing service.
  • the service S1 is created at time t1
  • the service S1 is an ODU service, specifically, an ODU2 is created from the node A to the node E.
  • the method flow includes the following steps:
  • Step 401 Determine a operation model identifier Create Service, a Timer, and a logic composed of Start, End, and Sequential Logic according to a graphical Create Service, a graphical Timer, and a graphical Start, End, and Sequential Logic selected by the user. Connection relationship
  • Step 402 Obtain a service flow diagram formed by a logical connection relationship composed of an operation model identifier Create Service, a Timer, and Start, End, and Sequential Logic;
  • Step 403 Determine, according to input by the user, operation parameter identifiers Create Service and Timer corresponding scheduling parameters, respectively;
  • the Timer corresponding scheduling parameter is t1.
  • Step 404 performing logic verification on the business logic of the business process flowchart, and on the Create Service Corresponding scheduling parameters and Timer corresponding scheduling parameters are verified;
  • the verification process includes the following check items:
  • the scheduling parameter corresponding to the Create Service includes the resource to be queried, it is checked whether the resource of the Query is present in the SDN network resource;
  • the topology information of the network, the real-time network device information, and the available port information between the source node A and the sink node E are obtained through the control layer, and then the information obtained according to the obtained information is verified. There are normal “source node A” and “sink node E”, and there is an available port configured for ODU2. If there are normal "source node A” and “sink node E”, there is an available port configured for ODU2, and the verification result of this check is pass verification.
  • the network layer needs to obtain relevant network operation authentication information, OAM information, idle resource information, etc., and then according to the obtained information, verify whether there is permission to operate the network at time t1 (for example, from Applying resources in SDN and using the requested resources to create S1 services), and whether there are enough resources to support the creation of ODU2 services from node A to node E.
  • Step 405 in combination with the BPMN transaction processing model, processing the orchestrated business flowchart into an executable program, such as java code, according to the arranged business flow chart and the scheduling parameters corresponding to the Timer corresponding scheduling parameter t1 and Create Service in the service flow chart. Or C language code, etc.
  • an executable program such as java code
  • an interaction interface that needs to interact with the control layer for resource scheduling when executing the executable code, such as a service creation interface (where the interface type of the service creation interface may be an NBI interface, a TAPI interface, or an IETF standard) is also created. interface).
  • a service creation interface where the interface type of the service creation interface may be an NBI interface, a TAPI interface, or an IETF standard
  • Step 406 commissioning the executable executable program through the created interaction interface with the control layer.
  • the running process of the executable program is: when the t1 arrives, the service creation interface is invoked, the resources required to create the ODU2 service from the node A to the node E are acquired, and the slave node A to the node is created according to the acquired resource. E's ODU2 business.
  • control layer can also perform online interaction with the control layer to assist the control layer to complete tasks such as querying the underlying resources, reserving the underlying resources, and notifying the underlying resource changes.
  • the preliminary arrangement of the to-be-programmed service is simplified, and the scheduling parameters set for the Create Service and the Timer corresponding operation are in the scheduling parameter.
  • the control layer In order to perform the live network resources required for the corresponding operations, by interacting with the control layer, it is possible to verify whether the existence exists and whether it has the right to obtain the existing network resources to support the execution of the arranged business flow chart. When the test passes, the arranged business flow chart is compiled into executable code, thereby realizing online compilation of the business.
  • the embodiment of the present application provides a service scheduling method for automatically updating a timing service. If the service S1 is updated to the service S2 at time t2, the ODU2 service from the source node A to the sink node E is changed to the source.
  • the ODU3 service from the node A to the sink node E, the method process includes the following steps:
  • Step 501 Determine an operation model identifier Query according to a graphical Query Service selected by the user, an Update Service model identifier, a graphical Timer, and a graphical Start, End, and Sequential Logic. Service, Update Service, Timer, and logical connection relationship consisting of Start, End, and Sequential Logic;
  • Step 502 Obtain a service flow diagram formed by a logical connection relationship consisting of an operation model identifier Query Service, an Update Service, a Timer, and Start, End, and Sequential Logic;
  • Step 503 Determine, according to input by the user, operation parameter identifiers Query Service, Update Service, and Timer corresponding scheduling parameters, respectively;
  • the scheduling parameters corresponding to the Create Service are: “Source Node A”, “Sink Node E”, and “Bandwidth ODU2".
  • the scheduling parameters corresponding to the Create Service are: “Source Node A”, “Sink Node E”, and “Bandwidth ODU3".
  • the Timer corresponding scheduling parameter is t2.
  • Step 504 Perform logic verification on the service logic of the service flow chart, and verify the scheduling parameters corresponding to the Query Service, the Update Service, and the Timer respectively.
  • the verification process includes the following check items:
  • the scheduling parameters corresponding to the Query Service and the Update Service include the resources to be queried.
  • the topology information of the network, the real-time network device information, and the source node A and the sink node E are obtained through the control layer.
  • the scheduling parameters corresponding to the Update Service include the resources to be used.
  • the network operation authentication information, OAM information, and idle resource information are obtained through the control layer, and then the information is obtained according to the obtained information. Verify that there is permission to operate the network at time t2 (eg, requesting resources from SDN and using the requested resources to create S2 services), and whether there are sufficient resources to support the creation of ODU3 services from source node A to sink node E.
  • Step 505 in combination with the BPMN transaction processing model, processing the orchestrated business process flowchart into an executable program according to the arranged business flow chart and the scheduling parameter corresponding to the Timer corresponding scheduling parameter t2 and the Query Service and the Update Service in the service flow chart.
  • processing the orchestrated business process flowchart into an executable program according to the arranged business flow chart and the scheduling parameter corresponding to the Timer corresponding scheduling parameter t2 and the Query Service and the Update Service in the service flow chart.
  • Such as java code or C language code Such as java code or C language code.
  • an interaction interface that needs to interact with the control layer for resource scheduling when executing the executable code, such as a service query interface and a service update interface (where the interface type of the service query interface and the service update interface may be NBI interface, TAPI interface or IETF standard interface).
  • Step 506 commissioning the executable executable program through the created interaction interface with the control layer.
  • the running process of the executable program is: calling the service query interface to query related information of the ODU2 service from the source node A to the sink node E, and when the t2 arrives, calling the service update interface to obtain the update from the source node A
  • the resources required for the ODU3 service to the sink node E are changed from the source node A to the ODU2 service of the sink node E to the ODU3 service from the source node A to the sink node E according to the acquired resources.
  • control layer can also perform online interaction with the control layer to assist the control layer to complete tasks such as querying the underlying resources, reserving the underlying resources, and notifying the underlying resource changes.
  • the preliminary arrangement of the to-be-arranged service is simplified, and the scheduling set for the corresponding operations of the Query Service, the Timer, and the Update Service is simplified.
  • the parameter when the scheduling parameter is the existing network resource that is required to perform the corresponding operation, interacts with the control layer to verify whether the existence exists and whether it has the right to obtain the existing network resources to support the arranged business flow chart.
  • the execution of the online verification process compiles the arranged business flow chart into executable code, thereby realizing the online compilation of the business.
  • the embodiment of the present application provides a service scheduling method for timing bandwidth update.
  • the ODU1 service from the source node A to the sink node E is referred to as the service S3
  • the ODU0 service referred to as the service from the source node A to the sink node E
  • the service S5 is referred to as the service S5
  • the service to be scheduled is: the service S3 is created first, and the service S3 is changed to the service S4 in the daily T3-T4 time period, in the daily In the T5-T6 time period, the service S4 is changed to the service S5, and the method process includes the following steps:
  • Step 601 Determine an operation model identifier Create according to a graphical Create Service ID, an Update Service model identifier, a graphical Timer, and a graphical Start, End, and Sequential Logic selected by the user.
  • Service, Update Service, Timer, and logical connection relationship consisting of Start, End, Sequential Logic, Parallel Logic, and Update Service and Timer include two;
  • Step 602 Obtain a service flow diagram formed by a logical connection relationship composed of an operation model identifier Create Service, an Update Service, a Timer, and Start, End, and Sequential Logic;
  • the acquisition is sequentially connected by "Start”, “Create Service”, “Parallel Logic”, and “Parallel Logic” forms two branches, each of which is composed of " Time (Timer) and “Update Service” are sequentially connected, and each "Update Service” and “End” are sequentially connected to form a business flow chart;
  • Step 603 according to the input of the user, respectively determine an operation model identifier Create Service and an update schedule corresponding to the Update Service and the Timer in each branch;
  • the scheduling parameters corresponding to the Create Service are: “source node A”, and the sink node E “sink node E”. And "bandwidth ODU1”.
  • the scheduling parameters corresponding to the Create Service are: "source node A”, “sink node” E” and "bandwidth ODU0".
  • the Timer corresponding scheduling parameter in the first branch is the time period T3 to T4.
  • the scheduling parameters corresponding to the Create Service are: “source node A”, “sink” Node E” and "Bandwidth ODU2”.
  • the Timer corresponding scheduling parameter in the second branch is the time period T5 to T6.
  • Step 604 performing logic verification on the service logic of the service flow chart, and verifying the scheduling parameters corresponding to the Create Service, the Update Service, and the Timer respectively;
  • the verification process includes the following check items:
  • the scheduling parameters corresponding to the Create Service and the Update Service include the resources to be queried.
  • the topology information of the network, the real-time network device information, and the source node A and the sink node E are obtained through the control layer.
  • the available port information between the two, and then according to the obtained information to verify whether there is a normal "source node A" and "sink node E", “source node A”, “sink node E” support bandwidth change, whether there is Configure the available ports for ODU1, ODU0, and ODU2 respectively.
  • source node A and "sink node E"
  • they are respectively configured for ODU1, ODU0
  • the available port of the ODU2 the source node A and the sink node E support the bandwidth change, and the check result of the check is the pass verification.
  • the scheduling parameters corresponding to the Update Service include the resources to be used.
  • the network operation authentication information, OAM information, and idle resource information are obtained through the control layer, and then the information is obtained according to the obtained information.
  • the resources are changed from the service S3 to the service S4, and whether there are sufficient resources for the change from the service S4 to the service S5.
  • Step 605 Combine the BPMN transaction processing model, and process the arranged business flow chart into an executable program according to the arranged business flow chart and the Timer corresponding scheduling parameter in the service flow chart and the scheduling parameters corresponding to the Create Service and the Update Service, such as Java code or C language code, etc.
  • an interaction interface such as a service creation interface and a service update interface, that needs to interact with the control layer for resource scheduling when executing executable code is also created.
  • Step 606 commissioning the executable executable program through the created interaction interface with the control layer.
  • the running process of the executable program is: calling the service creation interface to obtain the resources required to create the service 3, and creating the ODU1 service from the source node A to the sink node E according to the acquired resource; when the T3 arrives, the call is made.
  • the service update interface acquires the resources required to change the service 3 to the service 4, and changes the ODU1 service from the source node A to the sink node E according to the acquired resource to
  • the ODU0 service from the source node A to the sink node E, and the service 4 is maintained in the time period T3 to T4; when the T5 arrives, the service update interface is invoked to acquire the resources required to change the service 4 to the service 5, according to the acquired resources.
  • the ODU0 service from the source node A to the sink node E is changed to the ODU3 service from the source node A to the sink node E, and the service 4 is maintained in the time period T5 to T6.
  • control layer can also perform online interaction with the control layer to assist the control layer to complete tasks such as querying the underlying resources, reserving the underlying resources, and notifying the underlying resource changes.
  • Parallel Logic forms two branches by constructing a connection by Start, Create Service, and Parallel Logic. Each branch is sequentially connected by Timer and Update Service, and each Update Service and End are sequentially connected to form a business flow chart.
  • the simplified scheduling of the services to be arranged is simplified, and the scheduling parameters set for the Create Service, each Timer, and the corresponding operation of each Update Service are used when the scheduling parameters are the existing network resources required to perform the corresponding operations, and the control layer is adopted.
  • the interaction can be verified online and whether there is permission to obtain the existing network resources required to support the execution of the arranged business flow chart, and the online business flow chart is compiled into executable code when the online verification is passed, and then Realized online compilation of business.
  • the embodiment of the present application further provides a service orchestration device 800.
  • the service orchestration device 800 is located in an application layer of an SDN system architecture, and a control layer of an SDN system architecture.
  • the controller 900 is deployed, and the data layer of the SDN system architecture is deployed with multiple node devices accessing the SDN, as shown in FIG. 9 , node A, node B, node C, node E, node F, and topology of these node devices.
  • the controller 900 can obtain a topology map of the data layer, and can perform resource management and service maintenance on each node device of the data layer.
  • the service orchestration device 800 includes:
  • the scheduling unit 820 is configured to obtain a service flow chart of the service to be arranged, and the to-be-arranged service is used to perform a management and control operation on the transmission network;
  • the service flow diagram includes multiple operation model identifiers and multiple operation modes.
  • Logical connection relationship between type identifiers; logical connection relationship is the execution order of the business flow chart;
  • the scheduling unit 820 is further configured to acquire scheduling parameters corresponding to each operation model identifier
  • the checking unit 840 is configured to obtain the status of the live network through the control layer when the scheduling parameter acquired by the orchestration unit is the current network resource required to execute the service flow chart, and verify whether the current network status can be obtained according to the obtained current network status.
  • Network resource
  • the compiling unit 860 is configured to generate executable code for executing the service flowchart according to the scheduling parameter corresponding to each operation model identifier acquired by the obtaining unit and the logical connection relationship when the verification passes.
  • the orchestration unit 820 is configured to:
  • the checking unit 840 is further configured to: after the scheduling unit 820 acquires the scheduling parameter corresponding to each operation model identifier,
  • the verification unit 840 is configured to:
  • the compiling unit 860 is configured to:
  • An interaction interface is created between the operation unit 880 and the controller 900 of the control layer, and the interaction interface is used to apply to the controller 900 of the control layer for the existing network resources required to run the executable code.
  • an operation unit 880 is further included, and an interaction interface between the operation unit 880 and the controller 900 of the control layer is shown in FIG. 9;
  • the running unit 880 is configured to: after the compiling unit 860 generates the executable code that executes the service flowchart, to obtain the existing network resource that is applied for by using the interaction interface;
  • the interaction layer is used to assist the control layer to complete the resource management tasks of the underlying resource query, the underlying resource reservation, and the notification processing of the underlying resource change.
  • the service orchestration device simplifies the preliminary arrangement of the to-be-arranged business by constructing a service flow diagram composed of a plurality of operation model identifiers and logical connection relationships between the plurality of operation model identifiers, and identifies each operation model identifier
  • a service flow diagram composed of a plurality of operation model identifiers and logical connection relationships between the plurality of operation model identifiers, and identifies each operation model identifier
  • online verification can be performed to verify whether the existing network resources are available or not.
  • the execution of the arranged business flow chart compiles the arranged business flow chart into executable code when the online verification is passed, thereby realizing the online compilation of the business.
  • the operation flow of the to-be-arranged business is initially arranged by programming the business flow chart, which can reduce the difficulty of business arrangement and compilation; the feasibility check of the arranged business is performed online by interacting with the controller, and further Compiling the orchestration business through feasibility check can efficiently complete the online programming and compiling of customized services.
  • online programming and compiling can be performed for different business needs, so as to meet the current flexible and varied services. demand.
  • embodiments of the present application can be provided as a method, or a computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (system), and computer program products according to embodiments of the present application.
  • the flow chart can be implemented by computer program instructions And/or a combination of the processes and/or blocks in the block diagrams, and the flowcharts and/or blocks in the flowcharts.
  • These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Computer And Data Communications (AREA)

Abstract

一种业务编排方法、装置及服务器，用于解决不能在线进行SDN中的业务编排和编程的技术问题。本申请的业务编排方法包括：获取待编排业务的业务流程图，待编排业务用于对传送网进行设定管控操作；业务流程图包括多个操作模型标识以及多个操作模型标识之间的逻辑连接关系；逻辑连接关系为业务流程图的执行顺序；获取每一操作模型标识对应的调度参数，并在调度参数为执行业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的现网状态，校验能否获取现网资源；校验通过时，根据每一操作模型标识对应的调度参数，以及逻辑连接关系，生成执行业务流程图的可执行代码。

Description

一种业务编排方法、装置及服务器 技术领域
本申请涉及无线通信技术领域，尤其涉及一种业务编排方法、装置及服务器。
背景技术
自软件定义网络(Software Defined Networking，简称SDN)技术诞生并应用于传送网络以来，T-SDN在构建下一代“软件化”传送网的方向上不断演进，SDN通过开放的编程接口来实现网络功能虚拟化、网络管理简单化以及网络部署自动化，旨在满足运营商的智能化、开放化、可创新的迫切诉求。
随着T-SDN控制器的引入，传送网有了集中控制的“大脑”，并可通过南向接口实现对物理设备的直接控制。在集中控制的基础上，业界开始将SDN的关注点逐渐由控制器南向接口转向控制器北向接口。希望借助标准化的传送网模型及北向API接口、开源化的控制器等技术，打破传统传送网络的封闭性，将传送网络的能力通过标准的北向接口开放出去，真正实现网络开放化。
运营商面对各种互联网应用的增长，必须不断地扩大自己的传送网络容量和规模，以保证有足够的带宽来应对爆炸式增长的流量需求。运营商面对不断增长的海量设备和业务，需要运营商针对不同的网络场景和业务需求进行区分运维，运维场景更加复杂。
由于与北向接口相关的功能需求，以及与SDN业务编排本身相关的功能需求尚没有被充分发掘，SDN中的业务编排和编程的难度依然很大，运维人员还无法在线进行SDN中的业务编排和编程。为了满足多变的业务需求，依旧由设备商或者第三方软件商为运营商在原有业务支撑系统或运营支撑系统的基础上开发新业务、业务更新。
例如，运营商如果存在新的运维需求或者需要新的业务，通常需要将其需求描述给设备商，由设备商进行定制化的功能开发，该开发过程往往要经过复杂漫长的过程，以瀑布模型为例，运营商开发需求到达后，需要经过分析、设计、编码、测试等活动最终才能完成交付，整个周期通常要进行数月，如果在开发中途出现需求变更的情况，则整个开发过程还需要重来一遍，整个过程非常耗时。设备商完成开发后，还需要在运营商网络中进行软件升级、配置等复杂的操作，最终才能给运营商提供所需服务。运营商的运维人员手动操作具有新业务功能的业务支撑系统或者运维支撑系统，通过南向接口实现对物理设备的运维操作。
综上，面对当前灵活多变的业务需求，SDN中的业务编排和编程的难度依然很高，运维人员还不能在线进行SDN中的业务编排和编程。
发明内容
本申请实施例提供一种业务编排方法、装置及服务器，用以解决现有技术中面对当前灵活多变的业务需求，SDN中的业务编排和编程的难度依然很高，运维人员还不能在线进行SDN中的业务编排和编程的技术问题。
第一方面，本申请实施例提供一种业务编排方法，该方法包括：
获取待编排业务的业务流程图，所述待编排业务用于对传送网进行设定管控操作；所述业务流程图包括多个操作模型标识以及所述多个操作模型标识之间的逻辑连接关系；所述逻辑连接关系为所述业务流程图的执行顺序；
获取每一操作模型标识对应的调度参数，并在所述调度参数为执行所述业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的所述现网状态，校验能否获取所述现网资源；
校验通过时，根据所述每一操作模型标识对应的调度参数，以及所述逻辑连接关系，生成执行所述业务流程图的可执行代码。
实施例中通过构建由多个操作模型标识和多个操作模型标识之间的逻辑连接关系组成的业务流程图，简化了待编排业务的初步编排，针对每个操作 模型标识对应操作所设置的调度参数，在调度参数为执行对应操作所需提供的现网资源时，通过与控制层交互，可在线校验是否存在或是否有权限获取所需提供的现网资源来支持所编排的业务流程图的执行，在线校验通过时将所编排的业务流程图编译成可执行代码，进而实现了业务的在线编译。与现有技术相比，通过编排业务流程图来初步编排待编排业务的执行流程，可降低业务编排和编译的难度；通过与控制层交互，在线进行所编排业务的可行性校验，以及进一步对通过可行性校验的编排业务进行编译，可高效的完成定制化业务的在线编排和编译，在此基础上，可针对不同的业务需求进行在线编排和编译，从而满足当前灵活多变的业务需求。
可选的，所述多个操作模型标识和所述逻辑连接关系以图形化方式显示在用户操作界面；
获取待编排业务的业务流程图，包括：
根据用户在所述用户操作界面的操作指令，确定被用户选定的多个操作模型标识和逻辑连接关系，以及
确定由所述多个操作模型标识和所述逻辑连接关系组成的业务流程图。
可选实施例将多个操作模型标识和逻辑连接关系以图形化方式显示在用户操作界面，能给用户提供一种图形化的业务编程环境，使用户能够快速的响应定制化的业务需求，同时也降低了业务编排的难度。
可选的，在获取每一操作模型标识对应的调度参数之后，所述方法还包括：
对所述逻辑连接关系进行逻辑校验；以及对所述调度参数进行语义校验。
可选实施例对业务逻辑关系进行逻辑校验，以及对调度参数进行语义语法校验，可以初步保证业务编排的可行性。
可选的，所述通过控制层获取现网状态，并根据获取的所述现网状态，校验能否获取所述现网资源，包括：
通过预先创建的与所述控制层进行交互的交互接口获取所述现网状态；
根据所述现网状态，查询所述现网状态中是否存在所述现网资源；和/或,
根据所述现网状态，判断是否有权限申请所述现网资源。
通过预先创建的与控制层进行交互的交互接口获取SDN全网资源，并根据获取的资源来校验初步编排的业务流程图的可行性，一方面可在线校验初步编排业务的可行性，另一方面，通过图形化的编程方式，可以向运营商提供便捷的业务编排创新平台，方便运营商进行业务创新，该创新平台集网络控制、业务提供、业务集成开发环境于一体，能够为运营商提供从创新设计到简单开发、快速部署、自动维护的完整解决方案，能够完成运营商快速业务定制和从容应对复杂的运维需求。与现有技术相比，真正的实现SDN架构中应用层的完全开放化，可满足当前灵活多变的业务编排需求。
可选的，根据所述每一操作模型标识对应的调度参数以及所述逻辑连接关系，生成执行所述业务流程图的可执行代码，包括：
根据所述每一操作模型标识对应的调度参数，生成每一操作模型标识对应操作的脚本文件；
根据每一操作模型标识对应操作的脚本文件和所述逻辑连接关系，生成执行所述业务流程图中所有操作的可执行代码；以及
创建与所述控制层进行交互的交互接口，所述交互接口用于向所述控制层申请运行所述可执行代码所需提供的现网资源。
实施例中，每个操作模型标识对应一个操作模型，每个操作模型是基于SDN系统架构开源化的基本组件或者增强组件，每个开源化的基本组件或者增强组件被调用时，可以转化成操作模型对应的脚本文件(相当于业务流程的一种标准执行语言)。相应的，操作模型标识之间的逻辑连接关系是基于SDN系统架构开源化的逻辑组件，每个逻辑组件被调用时，能够形成描述多个操作模型间逻辑关系的脚本文件。基于此，可方便的将初步编排好的业务流程图处理成业务流程执行语言，以及将业务流程执行语言转化成可执行代码，进而降低了业务编译的难度。
进一步的，生成执行所述业务流程图的可执行代码之后，还包括：
通过所述交互接口获取申请到的现网资源；
根据所述申请到的现网资源，运行所述可执行代码；以及
根据所述申请到的现网资源，通过创建的所述交互接口协助所述控制层完成底层资源查询、底层资源预留和底层资源变化的通告处理的资源管理任务。
实施例中通过服务器与控制层交互的交互接口，如SDN架构中的NBI接口，来申请用来运行所编排业务所需的资源，可以扩展NBI接口的功能，通过交互接口向SDN的控制层申请运行所编排业务所需的资源，并根据申请的资源来运行所编排业务可真正实现在线运行所编排业务。
第二方面本申请实施例提供一种业务编排装置，用于实现上述第一方面中的任意一种方法，包括相应的功能模块，分别用于实现以上方法中的步骤。
第三方面，本申请实施例提供一种服务器，包括：处理器、收发器和存储器；
所述存储器用于存储指令，所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述处理器用于执行上述第一方面中的任意一种方法。
附图说明
图1为本申请实施例提供的一种示意性SDN系统架构图；
图2为本申请实施例提供的一种用于执行业务编排方法流程的服务器的结构示意图；
图3为本申请实施例提供的一种业务编排方法流程示意图；
图4为本申请实施例提供的一种操作模型标识和逻辑连接关系图形化的示意图；
图5为本申请实施例提供的一种示例1构建的业务流程图的示意图；
图6为本申请实施例提供的一种示例2构建的业务流程图的示意图；
图7为本申请实施例提供的一种示例3构建的业务流程图的示意图；
图8为本申请实施例提供的一种业务编排装置的结构示意图；
图9为本申请实施例提供的一种部署有业务编排装置的SDN系统架构示意图。
具体实施方式
下面结合附图，对本申请的技术方案进行描述。
本申请实施例的业务编排方法适用于软件定义网络SDN的业务编排，图1为本申请实施例的SDN的系统架构图，包括应用层、控制层和数据层。控制层上部署有控制器，控制器集成了集中算法，具备网络规划、资源优化，性能评估等自动化的全网集中控制功能。应用层与控制层之间开放有NBI接口，即NorthBound Interface，简称北向接口，控制层与数据层之间开放有SBI接口，即SouthBound Interface，简称南向接口。
如图1所示的SDN系统架构，数据层上部署有全网内的物理设备，这些物理设备位于SDN架构的南向，控制器通过SBI与这些设备进行通讯和交互，来实现对这些设备的直接控制。与现有SDN架构相比，本申请实施例适用的SDN架构在应用层增加了业务编排装置，业务编排装置位于SDN架构的北向，与控制器通过NBI进行通信和交互。
业务编排装置作为SDN应用层与控制层的桥梁，通过NBI接口来为最终用户、应用开发者以及管理员提供开放的平台开发和管理能力，从而能够进一步满足SDN开发、运营和维护的需要。
基于图1所示的系统架构，本申请实施例中的业务编排是基于SDN系统架构所执行的业务编排。根据用户的业务需求，首先确定一个待编排业务，待编排业务是根据业务需求，确定出的一个对传送网进行设定管控操作的执行流程，基于确定的待编排业务，初步确定待编排业务的执行流程。这里的设定管控操作包括多种类型的网络任务，可以是对SDN架构中网络设备、网络资源的各种管控任务。一个业务的执行流程通常包括多个操作步骤，以及这多个操作步骤的执行顺序。其次，基于待编排业务的执行流程，判断是否能够从SDN系统架构中申请到相应的网络资源来支持该待编排业务的顺利执 行。然后，在确定可以从SDN系统架构中申请到相应的网络资源来支持待编排业务时，对待编排业务的执行流程进行编译，形成可执行代码。最后，基于编译好的可执行代码，从SDN系统架构中申请相应的网络资源来运行编译好的可执行代码，进而满足用户的业务需求。
图2示例性示意出了本申请实施例提供的一种服务器的的结构示意图，该服务器用于执行本申请实施例中的业务编排方法流程。如图2所示，该服务器包括处理器201和收发器205，可选地，还包括存储器202和通信接口203，其中，处理器201、存储器202、通信接口203和收发器205通过总线204相互连接；存储器可以集成于处理器201中，也可以独立于处理器201。
总线204可以是外设部件互连标准(peripheral component interconnect，简称PCI)总线或扩展工业标准结构(extended industry standard architecture，简称EISA)总线等。总线204可以分为地址总线、数据总线、控制总线等。为便于表示，图2中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
存储器202可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，简称RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，简称HDD)或固态硬盘(solid-state drive，简称SSD)；存储器202还可以包括上述种类的存储器的组合。
通信接口203可以为有线通信接入口，无线通信接口或其组合，其中，有线通信接口例如可以为以太网接口。以太网接口可以是光接口，电接口或其组合。无线通信接口可以为WLAN接口。
处理器201可以是中央处理器(central processing unit，简称CPU)，网络处理器(network processor，简称NP)或者CPU和NP的组合。
处理器201还可以进一步包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，简称ASIC)，可编程逻辑器件(programmable logic device，简称PLD)或其组合。上述PLD可以是复杂可 编程逻辑器件(complex programmable logic device，简称CPLD)，现场可编程逻辑门阵列(field-programmable gate array，简称FPGA)，通用阵列逻辑(generic array logic,简称GAL)或其任意组合。
本申请实施例中的存储器202用于存储指令，处理器201用于根据执行存储器202存储的指令，并控制收发器205进行信号接收和信号发送，当处理器201执行存储器202存储的指令时，处理器201用于：
获取待编排业务的业务流程图，待编排业务用于对传送网进行设定管控操作；业务流程图包括多个操作模型标识以及多个操作模型标识之间的逻辑连接关系；其中，逻辑连接关系为业务流程图的执行顺序；
获取每一操作模型标识对应的调度参数，并在调度参数为执行业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的现网状态，校验能否获取现网资源；
校验通过时，根据每一操作模型标识对应的调度参数，以及逻辑连接关系，生成执行业务流程图的可执行代码。
本申请实施例中，处理器201通过构建由多个操作模型标识和多个操作模型标识之间的逻辑连接关系组成的业务流程图，简化了待编排业务的初步编排，针对每个操作模型标识对应操作所设置的调度参数，在调度参数为执行对应操作所需提供的现网资源时，通过与控制层交互，可在线校验是否存在或是否有权限获取所需提供的现网资源来支持所编排的业务流程图的执行，在线校验通过时将所编排的业务流程图编译成可执行代码，进而实现了业务的在线编译。与现有技术相比，通过编排业务流程图来初步编排待编排业务的执行流程，可降低业务编排和编译的难度；通过与控制层交互，在线进行所编排业务的可行性校验，以及进一步对通过可行性校验的编排业务进行编译，可高效的完成定制化业务的在线编排和编译，在此基础上，可针对不同的业务需求进行在线编排和编译，从而满足当前灵活多变的业务需求。
可选地，本申请实施例中，多个操作模型标识和逻辑连接关系以图形化方式显示在用户操作界面。处理器201用于：根据用户在用户操作界面的操 作指令，确定被用户选定的多个操作模型标识和逻辑连接关系，以及确定由多个操作模型标识和逻辑连接关系组成的业务流程图。
将多个操作模型标识和逻辑连接关系以图形化方式显示在用户操作界面，能给用户提供一种图形化的业务编程环境，使用户能够快速的响应定制化的业务需求，同时也降低了业务编排的难度。
可选的，处理器201，在获取每一操作模型标识对应的调度参数之后，还用于：对逻辑连接关系进行逻辑校验；以及对调度参数进行语义校验。
对业务逻辑关系进行逻辑校验，以及对调度参数进行语义语法校验，可以初步保证业务编排的可行性。
可选的，处理器201，用于：通过预先创建的与控制层进行交互的交互接口获取现网状态；根据现网状态，查询现网状态中是否存在现网资源；和/或,根据现网状态，判断是否有权限申请现网资源。
可选的，处理器201可与控制层的中心控制器进行交互，处理器201也可与控制层的协同器进行交互，处理器201还可与控制层的网管系统进行交互。
可选的，处理器201与控制层的交互接口为SDN架构中的NBI接口，这样可以进一步扩展NBI接口的功能。
可选的，与控制层的交互接口也可以是开放式网络基金会(Open Networking Foundation，简称ONF)组织规定的T-API标准接口。
可选的，与控制层的交互接口还可以是IETF标准接口，(Internet Engineering Task Force，因特网工程任务组，简称IETF标准接口)。
通过预先创建的与控制层进行交互的交互接口获取SDN全网资源，并根据获取的资源来校验初步编排的业务流程图的可行性，一方面可在线校验初步编排业务的可行性，另一方面，通过图形化的编程方式，可以向运营商提供便捷的业务编排创新平台，方便运营商进行业务创新，该创新平台集网络控制、业务提供、业务集成开发环境于一体，能够为运营商提供从创新设计到简单开发、快速部署、自动维护的完整解决方案，能够完成运营商快速业 务定制和从容应对复杂的运维需求。与现有技术相比，真正的实现SDN架构中应用层的完全开放化，可满足当前灵活多变的业务编排需求。
可选的，处理器201，用于：根据每一操作模型标识对应的调度参数，生成每一操作模型标识对应操作的脚本文件；根据每一操作模型标识对应操作的脚本文件和逻辑连接关系，生成执行业务流程图中所有操作的可执行代码；以及创建与控制层进行交互的交互接口，交互接口用于向控制层申请运行可执行代码所需提供的现网资源。
为了降低了业务编译的难度，本申请实施例中，每个操作模型标识对应一个操作模型，每个操作模型是基于SDN系统架构开源化的基本组件或者增强组件，每个开源化的基本组件或者增强组件被调用时，可以转化成操作模型对应的脚本文件(相当于业务流程的一种标准执行语言)。相应的，操作模型标识之间的逻辑连接关系是基于SDN系统架构开源化的逻辑组件，每个逻辑组件被调用时，能够形成描述多个操作模型间逻辑关系的脚本文件。基于此，可方便的将初步编排好的业务流程图处理成业务流程执行语言，以及将业务流程执行语言转化成可执行代码，进而降低了业务编译的难度。其中，基本组件、增强组件与业务流程图中的操作模型标识的映射关系，逻辑组件与多个操作模型标识之间的逻辑连接关系的映射关系参见方法流程。
可选的，处理器201，生成执行业务流程图的可执行代码之后，还用于：通过交互接口获取申请到的现网资源；根据申请到的现网资源，运行可执行代码；以及根据申请到的现网资源，通过创建的交互接口协助控制层完成底层资源查询、底层资源预留和底层资源变化的通告处理的资源管理任务。
通过服务器与控制层交互的交互接口，如SDN架构中的NBI接口，来申请用来运行所编排业务所需的资源，可以扩展NBI接口的功能，通过交互接口向SDN的控制层申请运行所编排业务所需的资源，并根据申请的资源来运行所编排业务可真正实现在线运行所编排业务。
基于相同的发明构思，本申请实施例的业务编排方法正是基于一个待编排业务的执行流程进行的编排和编译。图3示例性示出了本申请实施例提供 的一种方法流程示意图，该方法流程由部署在服务器上执行业务编排的处理器执行，如图3所示，该方法包括以下步骤：
步骤301，获取待编排业务的业务流程图，待编排业务用于对传送网进行设定管控操作；业务流程图包括多个操作模型标识以及多个操作模型标识之间的逻辑连接关系；其中，逻辑连接关系为业务流程图的执行顺序；
步骤302，获取每一操作模型标识对应的调度参数，并在调度参数为执行业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的现网状态，校验能否获取所需提供的现网资源；
步骤303，校验通过时，根据每一操作模型标识对应的调度参数，以及逻辑连接关系，生成执行业务流程图的可执行代码。
由于待编排业务的执行流程包括多个操作以及多个操作的执行顺序，为了简化待编排业务的编排和编译，本申请实施例以构建业务流程图的方式构建一个待编排业务多个操作的执行流程，所构建的业务流程图由多个预先设定的操作模型标识和这多个操作模型标识之间的逻辑连接关系组成，而这多个操作模型标识代表待编排业务多个操作的执行步骤，这多个操作模型标识之间的逻辑连接关系代表所构建的业务流程图的执行顺序，同时代表待编排业务多个操作的执行顺序。
可选的，为了降低待编排业务的编排和编译难度，本申请实施例提供一种图形化的业务编程环境，使用户能够快速的响应定制化的业务需求。具体的，所提供的图形化的业务编程环境具体为：将多个操作模型标识和逻辑连接关系以图形化方式显示在用户操作界面，这里的用户操作界面即为图形化的业务编程环境。通过设计图形化的业务编程环境，可向运营商提供便捷的创新平台，方便运营商进行业务创新，该创新平台集网络控制、业务提供、业务集成开发环境于一体，能够为运营商提供从创新设计到简单开发、快速部署、自动维护的完整解决方案，能够完成运营商快速业务定制和从容应对复杂的运维需求。
为了更清楚的说明本申请实施例中图形化的多个操作模型标识和图形化 的逻辑连接关系，本申请进行以下示例。
首先，本申请实施例中，根据SDN传送业务的特点，开源化出一些组件来表示传送网业务的多种操作的操作模型，以及表示多种操作模型之间的执行顺序的逻辑模型，开源化的操作模型和逻辑模型都称为传送网组件，传送网组件通常包括基本组件、增强组件和逻辑组件。
其中，基本组件用于对传送网中的网络设备或网络业务进行基本管控操作，基本管控操作包括连接管控、网元管控、业务模型管控或OAM管控等。这些基本组件是基于开放的SDN控制层的NBI接口或T-API接口或IETF标准接口进行二次开发或者封装而成的SDN传送网操作模型。例如，表示创建操作的基本组件CreateService，表示查询操作的基本组件QueryService，表示更新操作的基本组件UpdateService，表示删除操作的基本组件DeleteService，表示查询网络拓扑结构的基本组件QueryTopology。
增强组件，为基本管控操作提供通用策略模型、算法模型和标准业务模型。策略模型向用户提供封装好的策略，如时间策略组件Timer，可提供定时、循环、等常用时间策略。算法模型可提供基本算路、网络优化、业务分析等算法功能。
逻辑组件，为基本管控操作提供的各种业务逻辑，这些逻辑组件参考程序设计原理和传送业务的特点构成，包含顺序、分支、循环、事件触发等机制，用来实现基本组件、增强组件间的各种逻辑组合关系。例如，Start(开始)、End(结束)、Sequential Logic(顺序)、Parallel Gateway Logic(分支)等。
当然，本申请实施例中的传送网组件并不限于上述三种组件，也应当包括将来专门由第三方设计完成的独立组件，这些独立组件可能具有特殊的传送功能，本申请实施例中统称这些独立组件为第三方组件，第三方组件当然也包括与上述基本组件、增强组件和逻辑组件具有相同功能的组件。
其次，本申请实施例中的操作模型标识，即为本申请实施例中的基本组件、增强组件的标识。本申请实施例中的多个操作模型标识之间的逻辑连接关系，即为本申请实施例中代表基本组件、增强组件之间逻辑组合关系的逻 辑组件的标识。
例如，基本组件的标识为：Create Service、QueryService、UpdateService、DeleteService、QueryTopology。例如，增强组件的标识为Timer，逻辑组件的标识为Start、End、Sequential Logic、Parallel Gateway Logic等。
再次，将多个操作模型标识和逻辑连接关系图形化，即为将传送网组件(包括基本组件、增强组件、逻辑组件和第三方组件)的标识进行图形化。
示例的出的图形化的操作模型标识和逻辑连接关系，可选的，如图4所示，将“创建(Create Service)”、“查询(QueryService)”、“变更(Update Service)”、“时间(Timer)”、“开始(Start)”、“结束(End)”、“顺序(Sequential Logic)”“并行(Parallel Gateway Logic)”等标识以图框的方式显示在用户的操作界面，这些图框可供用户以各种选取方式，如复制、粘贴、插入、拖拽、导入等，选定至业务编程界面。
本申请实施例中，将操作模型标识和逻辑连接关系图形化的方式不限于将传送网组件的标识在图框中显示，其他任何能够实现操作模型标识和逻辑连接关系图形化的方式都应落入本申请实施例的保护范围内。
基于图形化的操作模型标识和图形化的逻辑连接关系，在构建待编排业务的业务流程图时，对用户来说，只需从用户操作界面选定多个操作模型标识和逻辑连接关系就能够构建出一个待编排业务的业务流程图。对于执行业务编排的处理器来说，只需根据用户操作界面响应的操作指令，就可以确定被用户选定的多个操作模型标识和多个操作模型标识之间的逻辑连接关系，进而可以确定一个待编排业务的业务流程图。
可选的，步骤301获取一个业务流程图，包括：根据用户在用户操作界面的操作指令，确定被用户选定的多个操作模型标识和逻辑连接关系，以及确定由多个操作模型标识和逻辑连接关系组成的业务流程图。
可选的，用户可以将构建好的业务流程图存储为业务模板，待后续需要编排相似业务时，查找或选定所存储的业务模板，即可获取待编排业务的业务流程图。因此，获取的业务流程图，也可以是直接从预先存储的业务模板 中选定的业务流程图。
一个待编排业务的多个操作必然需要一些元素来支撑，这些元素称为调度参数，而待编排业务的业务流程图中每个操作模型标识只是基本组件或者增强组件的标识，因此，构建的业务流程图中需要对每一个操作模型标识进行调度参数的设置。例如待编排业务的其中一个操作为“查询源节点A到宿节点E间的带宽ODU2”，这个操作的操作模型标识可能仅为“QueryService”，支撑这个查询操作的查询项是“源节点A”、“宿节点E”，以及“带宽ODU2”，因此，在编排业务时，还需要将这些查询项“源节点A”、“宿节点E”，以及“带宽ODU2”作为调度参数编排到业务流程图中。对于执行业务编排的处理器来说，需要获取业务流程图中每一操作模型标识对应的调度参数。
本申请实施例中，对于编程人员来说，可以通过用户操作界面来设置业务流程图中每一个图形化的操作模型标识对应的调度参数。
可选的，为了不增加编程人员的设计负担，每一操作模型映射有可供选取的多个参数选项，针对被选取的参数选项，可以分别设置待编排业务每一操作所需求的调度参数。相应的，对于执行业务编排的处理器来说，需要预先存储每一操作模型标识对应的参数选项，针对用户在用户操作界面进行的参数设置操作，存储每一参数选项对应的调度参数。
可选的，步骤302中，获取每一操作模型标识对应的调度参数，包括：
根据用户在用户操作界面的操作指令，确定所述业务流程图中每一操作模型标识对应的调度参数。具体为：根据用户选定的每一操作模型标识对应的参数选项，以及根据用户针对选定的参数选项输入的参数值，确定每一操作模型标识对应的调度参数。
为了实现在线编译，在编译之前需要校验初步编排的业务流程图中每一操作模型标识对应的调度参数是否合法，业务流程图的业务逻辑是否合法，以及在调度参数为执行业务流程图所需提供的资源(如在源节点A和宿节点E之间创建带宽ODU3所需的资源)时，需要核对是否能够从SDN空闲资源中申请到所需提供的资源，或者在调度参数为执行业务流程图所需查询的资 源(如查询源节点A和宿节点E之间的带宽ODU2所需查询的资源)时，需要核对SDN全网资源中是否存在所需查询的资源。
基于此，可选的，对执行业务编排的处理器来说，在获取每一操作模型标识对应的调度参数之后，还包括以下步骤：
(1)对业务流程图中多个操作模型标识之间的逻辑连接关系进行逻辑校验；
其中，逻辑校验主要校验业务流程图中多个操作模型标识之间的逻辑连接关系是否矛盾。
(2)对业务流程图中多个操作模型标识各自对应的调度参数进行语义校验；
对调度参数进行语义校验，主要是校验调度参数本身是否合法。
(3)在调度参数为执行业务流程图所需提供的现网资源时，校验能否获取所需提供的现网资源。
值得说明的是，业务流程图中的操作模型标识为增强组件标识时，其对应的调度参数通常是设置的时间参数，或者算法参数或时间参数，通常不需要提供现网资源，因此通常不通过控制层获取现网状态进行校验，只需进行语义校验即可。但也不排除特殊情况。
而当业务流程图中的操作模型标识为基本组件标识时，其对应的调度参数除了进行语义校验之外，通常需要提供现网资源，因此需要通过控制层获取现网状态才能够进行校验。
其中，基于本申请实施例提供的SDN系统架构，此处所需提供的现网资源，是指校验业务流程图中任一操作模型标识对应的调度参数时，需要从SDN的数据层调度的资源；此处通过控制层获取的现网状态为基于SDN系统架构的SDN的数据层覆盖的全网资源视图，基于全网资源视图，可以查询任何节点设备的资源状况和业务状态。
可选的，在调度参数为执行业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的现网状态，校验能否获取所需提供的现网 资源。
其中，可选的，通过控制层获取现网状态，包括：执行业务编排的处理器通过预先创建的与所述控制层进行交互的交互接口获取所述现网状态。
可选的，执行业务编排的处理器与控制层的中心控制器进行交互，执行业务编排的处理器也可与控制层的协同器进行交互，执行业务编排的处理器还可与控制层的网管系统进行交互。
可选的，通过控制层获取现网状态校验调度参数时，所调用的交互接口为本申请实施例提供的SDN系统架构的控制层NBI接口。可选的，与控制层的交互接口也可以是ONF组织规定的T-API标准接口。可选的，与控制层的交互接口还可以是IETF标准接口。
具体的，在调度参数为执行业务流程图所需提供的现网资源时，校验能否获取所需提供的现网资源，包括：
(b)在调度参数包括执行业务流程图所需查询的资源时，检验SDN全网资源中是否存在所需查询的资源；
(a)在调度参数包括执行业务流程图所需使用的资源时，校验是否有权限从SDN空闲资源中申请到所需使用的资源。
在上述任一校验项都校验通过时，执行步骤303，具体包括：
根据每一操作模型标识对应的调度参数，生成每一操作模型标识对应操作的脚本文件；根据每一操作模型标识对应操作的脚本文件和逻辑连接关系，生成执行业务流程图中所有操作的可执行代码；并创建与控制层进行交互的交互接口，交互接口用于向控制层申请运行可执行代码所需提供的现网资源。
本申请实施例中，前述实施例已经详述了每一操作模型标识对应的操作模型，是基于SDN系统架构开源化的基本组件或者增强组件，每个开源化的基本组件或者增强组件被调用时，可根据为其设置的调度参数，形成对应操作的开源化的描述语言，基于现有技术，这些操作的描述语言可以转化成操作对应的脚本文件。相应的，操作模型标识之间的逻辑连接关系是基于SDN系统架构开源化的逻辑组件，每个逻辑组件被调用时，能够形成描述多个操 作模型标识对应的多个操作间逻辑关系的开源化的描述语言。
例如，可根据每一操作模型标识对应的调度参数，以及每一操作模型标识对应的基本组件或增强组件的开源化的描述语言，生成每一操作模型标识对应操作的XML脚本。基于生成的每一操作模型标识对应操作的XML脚本，和多个操作模型标识对应的多个操作间逻辑关系的XML脚本，就可以生成执行所构建的业务流程图中所有操作的XML脚本文件；进而可将执行所构建的业务流程图中所有操作的XML脚本文件，转化为执行所构建的业务流程图中所有操作的可执行代码。
可选的，可采用BPMN事务处理模型(Business Process Management Initiative，业务流程建模符号，简称事务处理模型)，将校验通过的业务流程图转化为业务流程执行语言，然后再将业务流程执行语言转化为可执行程序。其中，BPMN规范能够支持从创建的业务流程图到业务流程执行语言的映射，例如业务流程建模语言标准BPEL(Business Process Execution Language，简称业务流程建模语言标准)。
为了能够在线运行编译好的可执行代码，执行业务编排的处理器在生成上述可执行文件时，还需要创建执行业务编排的处理器与控制层进行交互的交互接口，这些交互接口用于向控制层申请运行所编排的可执行代码所需提供的现网资源。此处所需提供的现网资源，是指执行所编排的业务流程图的可执行代码时，针对任一操作模型标识对应操作所设置的调度参数，需要从SDN的数据层调度的资源，需要从SDN的数据层调度的资源包括所需申请的资源和/或所需查询的资源。
值得说明的是，校验过程中通过与控制层交互从SDN的数据层调度资源的目的是：校验是否存在所需查询的资源，以及是否有权限申请所需申请的资源。在运行可执行代码时，通过与控制层交互从SDN的数据层调度资源的目的是：申请所需查询的资源和所需使用的资源。
可选的，基于本申请实施例提供的SDN系统架构，步骤303所创建的执行业务编排的处理器与控制层交互的交互接口为SDN系统架构的控制层NBI 接口。
可选的，执行业务编排的处理器与控制层的交互接口也可以是ONF组织规定的T-API标准接口。
可选的，执行业务编排的处理器与控制层的交互接口还可以是IETF标准接口。
基于创建的与控制层之间的交互接口，步骤303之后，执行业务编排的处理器还执行以下步骤：通过所创建的交互接口获取申请到的现网资源；根据申请到的现网资源，运行可执行代码。其中，基于本申请实施例提供的SDN系统架构，申请到的现网资源包括运行可执行代码所需查询的SDN资源和所需使用的SDN资源。
本申请实施例中，执行业务编排的处理器能够对所设计的这些业务进行运行管理，我们可以将这些设计成功的可执行程序称为任务，则执行业务编排的处理器可以完成任务状态机的各种管理，如执行任务、暂停任务、修改任务、保存任务为模板等任务管理操作。特别地，在整个任务管理过程中，执行业务编排的处理器需要多次进行校验操作，通过与控制层的实时交互在线地对任务的逻辑进行运行态校验，保证任务能够在现网中正常运行。
此外，执行业务编排的处理器在运行可执行代码过程中，还可以通过创建的交互接口，通知控制层根据申请到的现网资源更新现网状态。例如，通过交互接口与控制层进行在线交互，协助控制层根据申请到的现网资源，完成查询底层资源，预留底层资源，底层资源变化的通告处理等。
值得说明的是，本申请主要适用于OTN(光传送网)或者WDM(波分复用)网络，本申请的图形化业务编排和在线编译的发明构思也同样适用于IP等其他网络环境。
本申请实施例中，通过构建由多个操作模型标识和多个操作模型标识之间的逻辑连接关系组成的业务流程图，简化了待编排业务的初步编排，针对每个操作模型标识对应操作所设置的调度参数，在调度参数为执行对应操作所需提供的现网资源时，通过与控制层交互，可在线校验是否存在或是否有 权限获取所需提供的现网资源来支持所编排的业务流程图的执行，在线校验通过时将所编排的业务流程图编译成可执行代码，进而实现了业务的在线编译。与现有技术相比，通过编排业务流程图来初步编排待编排业务的执行流程，可降低业务编排和编译的难度；通过与控制层交互，在线进行所编排业务的可行性校验，以及进一步对通过可行性校验的编排业务进行编译，可高效的完成定制化业务的在线编排和编译，在此基础上，可针对不同的业务需求进行在线编排和编译，从而满足当前灵活多变的业务需求。
示例1
基于上述方法流程，本申请实施例提供一种定时业务自动创建的业务编排方法流程，具体是在t1时刻创建业务S1，业务S1为ODU业务，具体为创建从节点A到节点E的ODU2，该方法流程包括如下步骤：
步骤401，根据用户选定的图形化的Create Service，图形化的Timer，以及图形化的Start、End、Sequential Logic，确定操作模型标识Create Service、Timer，以及由Start、End、Sequential Logic组成的逻辑连接关系；
步骤402，获取由操作模型标识Create Service、Timer以及Start、End、Sequential Logic组成的逻辑连接关系所构成的业务流程图；
参照图5，获取由“开始(Start)”、“时间(Timer)”、“创建(Create Service)”、“结束(End)”顺序连接所构成的业务流程图；
步骤403，根据用户的输入，分别确定操作模型标识Create Service和Timer对应调度参数；
具体的，根据用户选择的Create Service对应的三个参数项：“源节点”、“宿节点”和“带宽”，以及用户在三个参数项分别输入的参数“节点A”、“节点E”和“ODU2”，确定Create Service对应的调度参数为：“源节点A”，“宿节点E”和“带宽ODU2”；
根据用户选择的Timer对应的参数项输入的t1，确定Timer对应调度参数为t1。
步骤404，对业务流程图的业务逻辑进行逻辑校验，以及对Create Service 对应的调度参数和Timer对应调度参数进行校验；
可选的，校验过程包括以下校验项：
其一，校验业务逻辑的语义是否合法，例如校验该业务逻辑是否跟其他逻辑冲突等；
其二，校验Timer对应调度参数t1的语义是否合法，t1只能为将来的时间，不能为过去的时间。
其三，校验Create Service对应的调度参数“源节点A”、“宿节点E”和“带宽ODU2”等数据格式、数据类型是否合法和正确；
其四，校验Create Service对应的调度参数包括所需查询的资源时，检验SDN全网资源中是否存在所需查询的资源；
在校验之前，需要通过控制层获取网络的拓扑结构信息，实时网络设备信息，以及“源节点A”与“宿节点E”之间的可用端口信息，进而根据获取的这些信息来校验否存在正常的“源节点A”和“宿节点E”，是否存在配置给ODU2的可用端口。若存在正常的“源节点A”和“宿节点E”，存在配置给ODU2的可用端口，则该项校验的校验结果为通过校验。
其五，校验Create Service对应的调度参数包括所需使用的资源时，校验是否有权限从SDN空闲资源中申请到所需使用的资源；
在此项校验之间，需要通过控制层获取相关的网络操作鉴权信息、OAM信息、空闲资源信息等，进而根据获取的信息，校验是否有权限在时间t1对网络进行操作(如从SDN中申请资源以及使用所申请资源创建S1业务)，以及是否有足够的资源来支持创建从节点A到节点E的ODU2业务。
若有权限在在时间t1对网络进行操作，存在足够的资源来创建从节点A到节点E的ODU2业务，则此项校验通过。
如果上述任一校验项的校验不通过，则提示结束此次业务编排任务，以便编程人员重新设置业务流程图中每个操作模型标识的调度参数。
如果上述任一校验项均通过校验，则校验结果为通过校验，此时可继续下一步骤。
步骤405，结合BPMN事务处理模型，根据编排好的业务流程图以及业务流程图中Timer对应调度参数t1和Create Service对应的调度参数，将编排好的业务流程图处理成可执行程序，如java代码或C语言代码等。
在生成可执行代码时，还创建在执行可执行代码时需要与控制层交互进行资源调度的交互接口，如业务创建接口(其中，业务创建接口的接口类型可以是NBI接口，TAPI接口或者IETF标准接口)。
步骤406，通过创建的与控制层的交互接口，试运行编排好的可执行程序。
基于创建的交互接口，可执行程序的运行过程为：在t1到来时，调用业务创建接口，获取创建从节点A到节点E的ODU2业务所需的资源，根据获取的资源创建从节点A到节点E的ODU2业务。
可执行程序的运行过程中，还可以与控制层进行在线交互，协助控制层完成查询底层资源，预留底层资源，底层资源变化的通告处理等任务。
上述具体实例中，通过构建由Create Service、Timer以及Start、End、Sequential Logic组成的业务流程图，简化了待编排业务的初步编排，针对Create Service、Timer对应操作所设置的调度参数，在调度参数为执行对应操作所需提供的现网资源时，通过与控制层交互，可在线校验是否存在以及是否有权限获取所需提供的现网资源来支持所编排的业务流程图的执行，在线校验通过时将所编排的业务流程图编译成可执行代码，进而实现了业务的在线编译。与现有技术相比，通过编排业务流程图来初步编排待编排业务的执行流程，可降低业务编排和编译的难度；通过与控制层交互，在线进行所编排业务的可行性校验，以及进一步对通过可行性校验的编排业务进行编译，可高效的完成定制化业务的在线编排和编译。
示例2
基于上述方法流程，本申请实施例提供一种定时业务自动更新的业务编排方法流程，如在t2时刻将业务S1更新为业务S2，即将从源节点A到宿节点E的ODU2业务变更为从源节点A到宿节点E的ODU3业务，该方法流程包括如下步骤：
步骤501，根据用户选定的图形化的Query Service(查询操作模型标识)、Update Service(更新操作模型标识)，图形化的Timer，以及图形化的Start、End、Sequential Logic，确定操作模型标识Query Service、Update Service、Timer，以及由Start、End、Sequential Logic组成的逻辑连接关系；
步骤502，获取由操作模型标识Query Service、Update Service、Timer以及Start、End、Sequential Logic组成的逻辑连接关系所构成的业务流程图；
参照图6，获取由“开始(Start)”、“查询(Query Service)”、“时间(Timer)”、“变更(Update Service)”、“结束(End)”顺序连接所构成的业务流程图；
步骤503，根据用户的输入，分别确定操作模型标识Query Service、Update Service和Timer对应调度参数；
具体的，根据用户选择的Query Service对应的三个参数项：“源节点”、“宿节点”和“带宽”，以及用户在三个参数项分别输入的参数“节点A”、“节点E”和“ODU2”，获取Create Service对应的调度参数为：“源节点A”，“宿节点E”和“带宽ODU2”。
根据用户选择的Update Service对应的三个参数项：“源节点”、“宿节点”和“带宽”，以及用户在三个参数项分别输入的参数“节点A”、“节点E”和“ODU3”，获取Create Service对应的调度参数为：“源节点A”，“宿节点E”和“带宽ODU3”。
根据用户选择的Timer对应的参数项输入的t2，确定Timer对应调度参数为t2。
步骤504，对业务流程图的业务逻辑进行逻辑校验，以及对Query Service、Update Service和Timer分别对应的调度参数进行校验；
可选的，校验过程包括以下校验项：
其一，校验业务逻辑的语义是否合法，例如校验该业务逻辑是否跟其他逻辑冲突等；
其二，校验Timer对应调度参数t2的语义是否合法，t2只能为将来的时 间，不能为过去的时间。
其三，校验Query Service对应的调度参数“源节点A”、“宿节点E”和“带宽ODU2”等数据格式、数据类型是否合法和正确；校验Update Service对应的调度参数“源节点A”、“宿节点E”和“带宽ODU3”等数据格式、数据类型是否合法和正确；
其四，检验SDN全网资源中是否存在校验Query Service、Update Service对应的调度参数所需查询的资源；
因Query Service、Update Service对应的调度参数包括所需查询的资源，在校验之前，需要通过控制层获取网络的拓扑结构信息，实时网络设备信息，以及“源节点A”与“宿节点E”之间的可用端口信息，进而根据获取的这些信息来校验是否存在正常的“源节点A”和“宿节点E”，源节点A，宿节点E是否支持带宽变更，是否存在从源节点A到宿节点E的ODU2业务端口，是否存在配置给ODU3的可用端口。若存在正常的“源节点A”和“宿节点E”，存在从源节点A到宿节点E的ODU2业务端口，存在配置给ODU3的可用端口，源节点A和宿节点E支持带宽变更，则该项校验的校验结果为通过校验。
其五，校验是否有权限从SDN空闲资源中申请到所需使用的资源；
因Update Service对应的调度参数包括所需使用的资源，在此项校验之间，需要通过控制层获取相关的网络操作鉴权信息、OAM信息、空闲资源信息等，进而根据获取的信息，校验是否有权限在时间t2对网络进行操作(如从SDN中申请资源以及使用所申请资源创建S2业务)，以及是否有足够的资源来支持创建从源节点A到宿节点E的ODU3业务。
若有权限在在时间t2对网络进行操作，存在足够的资源来创建源节点A到宿节点E的ODU3业务，则此项校验通过。
如果上述任一校验项的校验不通过，则提示结束此次业务编排任务，以便编程人员重新设置业务流程图中每个操作模型标识的调度参数。
如果上述任一校验项均通过校验，则校验结果为通过校验，此时可继续下一步骤。
步骤505，结合BPMN事务处理模型，根据编排好的业务流程图以及业务流程图中Timer对应调度参数t2和Query Service、Update Service对应的调度参数，将编排好的业务流程图处理成可执行程序，如java代码或C语言代码等。
在生成可执行代码时，还创建在执行可执行代码时需要与控制层交互进行资源调度的交互接口，如业务查询接口和业务更新接口(其中，业务查询接口和业务更新接口的接口类型可以是NBI接口，TAPI接口或者IETF标准接口)。
步骤506，通过创建的与控制层的交互接口，试运行编排好的可执行程序。
基于创建的交互接口，可执行程序的运行过程为：调用业务查询接口查询从源节点A到宿节点E的ODU2业务的相关信息，在t2到来时，调用业务更新接口，获取更新从源节点A到宿节点E的ODU3业务所需的资源，根据获取的资源将从源节点A到宿节点E的ODU2业务变更为从源节点A到宿节点E的ODU3业务。
可执行程序的运行过程中，还可以与控制层进行在线交互，协助控制层完成查询底层资源，预留底层资源，底层资源变化的通告处理等任务。
本申请实施例中的可选地一些其它特征与上述方法实施例中的相同，可参见上述方法实施例中的论述，在此不再赘述。
上述具体实例中，通过构建由Start、Query Service、Timer、Update Service、End顺序连接组成的业务流程图，简化了待编排业务的初步编排，针对Query Service、Timer、Update Service对应操作所设置的调度参数，在调度参数为执行对应操作所需提供的现网资源时，通过与控制层交互，可在线校验是否存在以及是否有权限获取所需提供的现网资源来支持所编排的业务流程图的执行，在线校验通过时将所编排的业务流程图编译成可执行代码，进而实现了业务的在线编译。与现有技术相比，通过编排业务流程图来初步编排待编排业务的执行流程，可降低业务编排和编译的难度；通过与控制层交互，在线进行所编排业务的可行性校验，以及进一步对通过可行性校验的编排业务进 行编译，可高效的完成定制化业务的在线编排和编译。
示例3
基于上述方法流程，本申请实施例提供一种定时带宽更新的业务编排方法流程，假如从源节点A到宿节点E的ODU1业务简称业务S3，从源节点A到宿节点E的ODU0业务简称业务S4；从源节点A到宿节点E的ODU2业务简称业务S5；若所要编排的业务为：先创建业务S3，并且在每日的T3-T4时间段将业务S3变更为业务S4，在每日的T5-T6时间段将业务S4变更为业务S5，该方法流程包括如下步骤：
步骤601，根据用户选定的图形化的Create Service(创建操作模型标识)、Update Service(更新操作模型标识)，图形化的Timer，以及图形化的Start、End、Sequential Logic，确定操作模型标识Create Service、Update Service、Timer，以及由Start、End、Sequential Logic(顺序)、Parallel Logic(并行)组成的逻辑连接关系，其中，Update Service和Timer都包括两个；
步骤602，获取由操作模型标识Create Service、Update Service、Timer以及Start、End、Sequential Logic组成的逻辑连接关系所构成的业务流程图；
参照图7，获取由“开始(Start)”、“创建(Create Service)”、“顺序，(Parallel Logic)”顺序连接，“并行(Parallel Logic)”处形成两个分支，每个分支由“时间(Timer)”和“变更(Update Service)”顺序连接，每个“变更(Update Service)”与“结束(End)”顺序连接，所构成的业务流程图；
步骤603，根据用户的输入，分别确定操作模型标识Create Service和每个分支中的Update Service和Timer对应调度参数；
具体的，根据用户在Create Service对应的参数项输入的“节点A”、“节点E”和“ODU1”，获取Create Service对应的调度参数为：“源节点A”，宿节点E“宿节点E”和“带宽ODU1”。
根据用户选择的第1个分支中Update Service对应的参数项输入的参数“节点A”、“节点E”和“ODU0”，获取Create Service对应的调度参数为：“源节点A”，“宿节点E”和“带宽ODU0”。
根据用户选择的第1个分支中Timer对应的参数项输入的时间段T3～T4，确定第1个分支中Timer对应调度参数为时间段T3～T4。
根据用户选择的第2个分支中Update Service对应的参数项分别输入的参数“节点A”、“节点E”和“ODU2”，获取Create Service对应的调度参数为：“源节点A”，“宿节点E”和“带宽ODU2”。
根据用户选择的第2个分支中Timer对应的参数项输入的时间段T5～T6，确定第2个分支中Timer对应调度参数为时间段T5～T6。
步骤604，对业务流程图的业务逻辑进行逻辑校验，以及对Create Service、Update Service和Timer分别对应的调度参数进行校验；
可选的，校验过程包括以下校验项：
其一，校验业务逻辑的语义是否合法，例如校验该业务逻辑是否跟其他逻辑冲突等；
其二，校验Timer对应调度参数时间段T3～T4以及时间段T5～T6的语义是否合法，以及校验时间段T3～T4与时间段T5～T6有没有重复。
其三，校验Create Service对应的调度参数“源节点A”、“宿节点E”和“带宽ODU1”等数据格式、数据类型是否合法和正确；校验Update Service对应的调度参数“源节点A”、“宿节点E”和“带宽ODU0”以及“带宽ODU2”等数据格式、数据类型是否合法和正确；
其四，检验SDN全网资源中是否存在校验Create Service、Update Service对应的调度参数所需查询的资源；
因Create Service、Update Service对应的调度参数包括所需查询的资源，在校验之前，需要通过控制层获取网络的拓扑结构信息，实时网络设备信息，以及“源节点A”与“宿节点E”之间的可用端口信息，进而根据获取的这些信息来校验是否存在正常的“源节点A”和“宿节点E”，“源节点A”，“宿节点E”是否支持带宽变更，是否存在分别配置给ODU1，ODU0，ODU2的可用端口。
若存在正常的“源节点A”和“宿节点E”，存在分别配置给ODU1，ODU0， ODU2的可用端口，源节点A和宿节点E支持带宽变更，则该项校验的校验结果为通过校验。
其五，校验是否有权限从SDN空闲资源中申请到所需使用的资源；
因Update Service对应的调度参数包括所需使用的资源，在此项校验之间，需要通过控制层获取相关的网络操作鉴权信息、OAM信息、空闲资源信息等，进而根据获取的信息，校验是否有权限在时间段T3～T4以及在时间段T5～T6对网络进行操作，以及是否有足够的资源创建从源节点A到宿节点E的ODU1业务(即业务3)，以及是否有足够的资源进行业务S3到业务S4的变更，以及是否有足够的资源进行业务S4到业务S5的变更。
若有权限在时间段T3～T4以及在时间段T5～T6对网络进行操作，存在足够的资源来创建源业务3，进行业务S3到业务S4的变更，进行业务S4到业务S5的变更，则此项校验通过。
如果上述任一校验项的校验不通过，则提示结束此次业务编排任务，以便编程人员重新设置业务流程图中每个操作模型标识的调度参数。
如果上述任一校验项均通过校验，则校验结果为通过校验，此时可继续下一步骤。
步骤605，结合BPMN事务处理模型，根据编排好的业务流程图以及业务流程图中Timer对应调度参数和Create Service、Update Service对应的调度参数，将编排好的业务流程图处理成可执行程序，如java代码或C语言代码等。
在生成可执行代码时，还创建在执行可执行代码时需要与控制层交互进行资源调度的交互接口，如业务创建接口和业务更新接口。
步骤606，通过创建的与控制层的交互接口，试运行编排好的可执行程序。
基于创建的交互接口，可执行程序的运行过程为：调用业务创建接口获取创建业务3所需的资源，根据获取的资源创建从源节点A到宿节点E的ODU1业务；在T3到来时，调用业务更新接口，获取将业务3变更为业务4所需的资源，根据获取的资源将从源节点A到宿节点E的ODU1业务变更为 从源节点A到宿节点E的ODU0业务，并在时间段T3～T4保持业务4；在T5到来时，调用业务更新接口，获取将业务4变更为业务5所需的资源，根据获取的资源将从源节点A到宿节点E的ODU0业务变更为从源节点A到宿节点E的ODU3业务，并在时间段T5～T6保持业务4。
可执行程序的运行过程中，还可以与控制层进行在线交互，协助控制层完成查询底层资源，预留底层资源，底层资源变化的通告处理等任务。
上述具体实例中，通过构建由Start、Create Service、Parallel Logic顺序连接，Parallel Logic处形成两个分支，每个分支由Timer和Update Service顺序连接，每个Update Service与End顺序连接组成的业务流程图，简化了待编排业务的初步编排，针对Create Service、每个Timer、每个Update Service对应操作所设置的调度参数，在调度参数为执行对应操作所需提供的现网资源时，通过与控制层交互，可在线校验是否存在以及是否有权限获取所需提供的现网资源来支持所编排的业务流程图的执行，在线校验通过时将所编排的业务流程图编译成可执行代码，进而实现了业务的在线编译。与现有技术相比，通过编排业务流程图来初步编排待编排业务的执行流程，可降低业务编排和编译的难度；通过与控制层交互，在线进行所编排业务的可行性校验，以及进一步对通过可行性校验的编排业务进行编译，可高效的完成定制化业务的在线编排和编译。
基于相同的发明构思，如图8所示，本申请实施例还提供一种业务编排装置800，如图9所示，该业务编排装置800位于SDN系统架构应用层中，SDN系统架构的控制层部署有控制器900，SDN系统架构的数据层部署有接入SDN的多个节点设备，如图9中示意的节点A，节点B，节点C，节点E，节点F，这些节点设备的拓扑结构图参见图9，控制器900可以获取数据层的拓扑结构图，还能对数据层的各个节点设备进行资源管理和业务维护，在此系统架构下，业务编排装置800包括：
编排单元820，用于获取待编排业务的业务流程图，待编排业务用于对传送网进行设定管控操作；业务流程图包括多个操作模型标识以及多个操作模 型标识之间的逻辑连接关系；逻辑连接关系为业务流程图的执行顺序；
编排单元820，还用于获取每一操作模型标识对应的调度参数；
校验单元840，用于在编排单元获取的调度参数为执行业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的现网状态，校验能否获取现网资源；
编译单元860，用于在校验通过时，根据获取单元获取的每一操作模型标识对应的调度参数，以及逻辑连接关系，生成执行业务流程图的可执行代码。
可选的，多个操作模型标识和逻辑连接关系以图形化方式显示在用户操作界面；编排单元820，用于：
根据用户在用户操作界面的操作指令，确定被用户选定的多个操作模型标识和逻辑连接关系，以及
确定由多个操作模型标识和逻辑连接关系组成的业务流程图。
可选的，校验单元840，在编排单元820获取每一操作模型标识对应的调度参数之后，还用于：
对逻辑连接关系进行逻辑校验；以及对调度参数进行语义校验。
可选的，检验单元840用于：
通过预先创建的与控制层的控制器900之间进行交互的交互接口获取现网状态；其中，控制层的控制器900与检验单元840的交互接口参见图9；
根据现网状态，查询现网状态中是否存在现网资源；和/或,
根据现网状态，判断是否有权限申请现网资源。
可选的，编译单元860用于：
根据每一操作模型标识对应的调度参数，生成每一操作模型标识对应操作的脚本文件；
根据每一操作模型标识对应操作的脚本文件和逻辑连接关系，生成执行业务流程图中所有操作的可执行代码；以及
创建运行单元880与控制层的控制器900进行交互的交互接口，交互接口用于向控制层的控制器900申请运行可执行代码所需提供的现网资源。
可选的，还包括运行单元880，运行单元880和控制层的控制器900之间的交互接口参见图9；
运行单元880，在编译单元860生成执行业务流程图的可执行代码之后，用于通过交互接口获取申请到的现网资源；
根据申请到的现网资源，运行可执行代码；以及
根据申请到的现网资源，通过交互接口协助控制层完成底层资源查询、底层资源预留和底层资源变化的通告处理的资源管理任务。
本申请实施例中，业务编排装置通过构建由多个操作模型标识和多个操作模型标识之间的逻辑连接关系组成的业务流程图，简化了待编排业务的初步编排，针对每个操作模型标识对应操作所设置的调度参数，在调度参数为执行对应操作所需提供的现网资源时，通过与控制器交互，可在线校验是否存在或是否有权限获取所需提供的现网资源来支持所编排的业务流程图的执行，在线校验通过时将所编排的业务流程图编译成可执行代码，进而实现了业务的在线编译。与现有技术相比，通过编排业务流程图来初步编排待编排业务的执行流程，可降低业务编排和编译的难度；通过与控制器交互，在线进行所编排业务的可行性校验，以及进一步对通过可行性校验的编排业务进行编译，可高效的完成定制化业务的在线编排和编译，在此基础上，可针对不同的业务需求进行在线编排和编译，从而满足当前灵活多变的业务需求。
本申请实施例中的可选地一些其它特征与上述方法实施例中的相同，可参见上述方法实施例中的论述，在此不再赘述。
本领域内的技术人员应明白，本申请的实施例可提供为方法、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图 和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本申请的可选实施例，但本领域内的技术人员一旦得知了基本创造性概念，则可对这些实施例作出另外的变更和修改。所以，所附权利要求意欲解释为包括优选实施例以及落入本申请范围的所有变更和修改。
显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (18)

  1. 一种业务编排方法，其特征在于，所述方法包括：
    获取待编排业务的业务流程图，所述待编排业务用于对传送网进行设定管控操作；所述业务流程图包括多个操作模型标识以及所述多个操作模型标识之间的逻辑连接关系；所述逻辑连接关系为所述业务流程图的执行顺序；
    获取每一操作模型标识对应的调度参数，并在所述调度参数为执行所述业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的所述现网状态，校验能否获取所述现网资源；
    校验通过时，根据所述每一操作模型标识对应的调度参数，以及所述逻辑连接关系，生成执行所述业务流程图的可执行代码。
  2. 如权利要求1所述的方法，其特征在于，所述多个操作模型标识和所述逻辑连接关系以图形化方式显示在用户操作界面；
    获取待编排业务的业务流程图，包括：
    根据用户在所述用户操作界面的操作指令，确定被用户选定的多个操作模型标识和逻辑连接关系，以及
    确定由所述多个操作模型标识和所述逻辑连接关系组成的业务流程图。
  3. 如权利要求2所述的方法，其特征在于，在获取每一操作模型标识对应的调度参数之后，所述方法还包括：
    对所述逻辑连接关系进行逻辑校验；以及
    对所述调度参数进行语义校验。
  4. 如权利要求3所述的方法，其特征在于，所述通过控制层获取现网状态，并根据获取的所述现网状态，校验能否获取所述现网资源，包括：
    通过预先创建的与所述控制层进行交互的交互接口获取所述现网状态；
    根据所述现网状态，查询所述现网状态中是否存在所述现网资源；和/或,
    根据所述现网状态，判断是否有权限申请所述现网资源。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，根据所述每一 操作模型标识对应的调度参数以及所述逻辑连接关系，生成执行所述业务流程图的可执行代码，包括：
    根据所述每一操作模型标识对应的调度参数，生成每一操作模型标识对应操作的脚本文件；
    根据每一操作模型标识对应操作的脚本文件和所述逻辑连接关系，生成执行所述业务流程图中所有操作的可执行代码；以及
    创建与所述控制层进行交互的交互接口，所述交互接口用于向所述控制层申请运行所述可执行代码所需提供的现网资源。
  6. 如权利要求5所述的方法，其特征在于，生成执行所述业务流程图的可执行代码之后，还包括：
    通过所述交互接口获取申请到的现网资源；
    根据所述申请到的现网资源，运行所述可执行代码；以及
    根据所述申请到的现网资源，通过创建的所述交互接口协助所述控制层完成底层资源查询、底层资源预留和底层资源变化的通告处理的资源管理任务。
  7. 一种业务编排装置，其特征在于，包括：
    编排单元，用于获取待编排业务的业务流程图，所述待编排业务用于对传送网进行设定管控操作；所述业务流程图包括多个操作模型标识以及所述多个操作模型标识之间的逻辑连接关系；所述逻辑连接关系为所述业务流程图的执行顺序；
    所述编排单元，还用于获取每一操作模型标识对应的调度参数；
    校验单元，用于在所述编排单元获取的所述调度参数为执行所述业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的所述现网状态，校验能否获取所述现网资源；
    编译单元，用于在校验通过时，根据所述获取单元获取的所述每一操作模型标识对应的调度参数，以及所述逻辑连接关系，生成执行所述业务流程图的可执行代码。
  8. 如权利要求7所述的装置，其特征在于，所述多个操作模型标识和所述逻辑连接关系以图形化方式显示在用户操作界面；所述编排单元，用于：
    根据用户在所述用户操作界面的操作指令，确定被用户选定的多个操作模型标识和逻辑连接关系，以及
    确定由所述多个操作模型标识和所述逻辑连接关系组成的业务流程图。
  9. 如权利要求8所述的装置，其特征在于，所述校验单元，在所述编排单元获取每一操作模型标识对应的调度参数之后，还用于：
    对所述逻辑连接关系进行逻辑校验；以及对所述调度参数进行语义校验。
  10. 如权利要求9所述的装置，其特征在于，所述检验单元用于：
    通过预先创建的与所述控制层进行交互的交互接口获取所述现网状态；
    根据所述现网状态，查询所述现网状态中是否存在所述现网资源；和/或,
    根据所述现网状态，判断是否有权限申请所述现网资源。
  11. 如权利要求7至10中任一项所述的装置，其特征在于，所述编译单元用于：
    根据所述每一操作模型标识对应的调度参数，生成每一操作模型标识对应操作的脚本文件；
    根据每一操作模型标识对应操作的脚本文件和所述逻辑连接关系，生成执行所述业务流程图中所有操作的可执行代码；以及
    创建与所述控制层进行交互的交互接口，所述交互接口用于向所述控制层申请运行所述可执行代码所需提供的现网资源。
  12. 如权利要求11所述的装置，其特征在于，还包括运行单元；
    所述运行单元，在所述编译单元生成执行所述业务流程图的可执行代码之后，用于通过所述交互接口获取申请到的现网资源；
    根据所述申请到的现网资源，运行所述可执行代码；以及
    根据所述申请到的现网资源，通过所述交互接口协助所述控制层完成底层资源查询、底层资源预留和底层资源变化的通告处理的资源管理任务。
  13. 一种服务器，其特征在于，包括：处理器、收发器和存储器；
    所述存储器用于存储指令，所述处理器用于根据执行所述存储器存储的指令，并控制所述收发器进行信号接收和信号发送，当所述处理器执行所述存储器存储的指令时，所述处理器用于：
    获取待编排业务的业务流程图，所述待编排业务用于对传送网进行设定管控操作；所述业务流程图包括多个操作模型标识以及所述多个操作模型标识之间的逻辑连接关系；所述逻辑连接关系为所述业务流程图的执行顺序；
    获取每一操作模型标识对应的调度参数，并在所述调度参数为执行所述业务流程图所需提供的现网资源时，通过控制层获取现网状态，并根据获取的所述现网状态，校验能否获取所述现网资源；
    校验通过时，根据所述每一操作模型标识对应的调度参数，以及所述逻辑连接关系，生成执行所述业务流程图的可执行代码。
  14. 如权利要求13所述的服务器，其特征在于，所述多个操作模型标识和所述逻辑连接关系以图形化方式显示在用户操作界面；所述处理器用于：
    根据用户在所述用户操作界面的操作指令，确定被用户选定的多个操作模型标识和逻辑连接关系，以及
    确定由所述多个操作模型标识和所述逻辑连接关系组成的业务流程图。
  15. 如权利要求14所述的服务器，其特征在于，所述处理器，在获取每一操作模型标识对应的调度参数之后，还用于：
    对所述逻辑连接关系进行逻辑校验；以及对所述调度参数进行语义校验。
  16. 如权利要求15所述的服务器，其特征在于，所述处理器，用于：
    通过预先创建的与所述控制层进行交互的交互接口获取所述现网状态；
    根据所述现网状态，查询所述现网状态中是否存在所述现网资源；和/或,
    根据所述现网状态，判断是否有权限申请所述现网资源。
  17. 如权利要求13至16中任一项所述的服务器，其特征在于，所述处理器，用于：
    根据所述每一操作模型标识对应的调度参数，生成每一操作模型标识对应操作的脚本文件；
    根据每一操作模型标识对应操作的脚本文件和所述逻辑连接关系，生成执行所述业务流程图中所有操作的可执行代码；以及
    创建与所述控制层进行交互的交互接口，所述交互接口用于向所述控制层申请运行所述可执行代码所需提供的现网资源。
  18. 如权利要求17所述的服务器，其特征在于，所述处理器，生成执行所述业务流程图的可执行代码之后，还用于：
    通过所述交互接口获取申请到的现网资源；
    根据申请到的所述现网资源，运行所述可执行代码；以及
    根据所述申请到的现网资源，通过所述交互接口协助所述控制层完成底层资源查询、底层资源预留和底层资源变化的通告处理的资源管理任务。
PCT/CN2016/110158 2016-12-15 2016-12-15 一种业务编排方法、装置及服务器 WO2018107442A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
CN201680069212.2A CN108432208B (zh) 2016-12-15 2016-12-15 一种业务编排方法、装置及服务器
EP16924165.0A EP3544260B1 (en) 2016-12-15 2016-12-15 Service layout method and device, and server
ES16924165T ES2898050T3 (es) 2016-12-15 2016-12-15 Método y dispositivo de disposición de servicios, y servidor
PCT/CN2016/110158 WO2018107442A1 (zh) 2016-12-15 2016-12-15 一种业务编排方法、装置及服务器
US16/442,459 US11178233B2 (en) 2016-12-15 2019-06-15 Service orchestration method and apparatus, and server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/110158 WO2018107442A1 (zh) 2016-12-15 2016-12-15 一种业务编排方法、装置及服务器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/442,459 Continuation US11178233B2 (en) 2016-12-15 2019-06-15 Service orchestration method and apparatus, and server

Publications (1)

Publication Number Publication Date
WO2018107442A1 true WO2018107442A1 (zh) 2018-06-21

Family

ID=62557894

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/110158 WO2018107442A1 (zh) 2016-12-15 2016-12-15 一种业务编排方法、装置及服务器

Country Status (5)

Country Link
US (1) US11178233B2 (zh)
EP (1) EP3544260B1 (zh)
CN (1) CN108432208B (zh)
ES (1) ES2898050T3 (zh)
WO (1) WO2018107442A1 (zh)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109104297A (zh) * 2018-07-09 2018-12-28 中国银行股份有限公司 一种业务流程的处理方法及装置
CN111083722A (zh) * 2019-04-15 2020-04-28 中兴通讯股份有限公司 模型的推送、模型的请求方法及装置、存储介质
WO2020094045A1 (en) * 2018-11-08 2020-05-14 Huawei Technologies Co., Ltd. Method for enhancing status communications in a sdn-based communication system
CN111429127A (zh) * 2020-03-20 2020-07-17 中国建设银行股份有限公司 一种应用于缴费的业务管理方法和装置
CN113094167A (zh) * 2020-01-08 2021-07-09 顺丰科技有限公司 一种云计算资源处理方法、装置、设备及存储介质
CN113435846A (zh) * 2021-06-30 2021-09-24 深圳平安智汇企业信息管理有限公司 业务流程编排方法、装置、计算机设备及存储介质
CN117611094A (zh) * 2023-12-06 2024-02-27 阿帕数字科技有限公司 基于业务流程编排实现供应链体系设计方法及系统
CN117611094B (zh) * 2023-12-06 2024-06-07 阿帕数字科技有限公司 基于业务流程编排实现供应链体系设计方法及系统

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109408112B (zh) * 2018-09-25 2024-01-16 平安科技（深圳）有限公司 在线开发文档生成方法、装置、终端及可读存储介质
CN111061723B (zh) * 2018-10-16 2023-05-09 中国移动通信有限公司研究院 工作流实现方法及装置
CN109933315A (zh) * 2019-02-26 2019-06-25 广州衡昊数据科技有限公司 一种图形化的业务处理系统和方法
CN112084827B (zh) * 2019-06-14 2024-02-23 杭州海康威视数字技术股份有限公司 数据处理方法及装置
CN110413267B (zh) * 2019-08-08 2023-05-26 四川爱创科技有限公司 基于业务规则的自适应业务流程建模方法
CN111404738B (zh) * 2020-03-10 2023-05-30 中国电信集团工会上海市委员会 一种网络控制器的流表和配置的热修改方法
CN111949338A (zh) * 2020-08-10 2020-11-17 上海熙菱信息技术有限公司 一种基于微服务的服务编排方法
CN111966334B (zh) * 2020-08-17 2023-06-27 支付宝(杭州)信息技术有限公司 一种业务处理方法、装置及设备
CN112099848B (zh) * 2020-09-11 2024-03-05 杭州海康威视数字技术股份有限公司 一种业务处理方法、装置及设备
CN112379884B (zh) * 2020-11-13 2024-01-12 李斌 基于Spark和并行内存计算的流程引擎实现方法及系统
CN114527962A (zh) * 2020-11-23 2022-05-24 中国移动通信集团重庆有限公司 流程自动化处理装置、方法及计算设备
CN113469647A (zh) * 2021-06-23 2021-10-01 广州鲁邦通智能科技有限公司 一种企业信息集成系统和业务处理方法
CN113553159A (zh) * 2021-07-29 2021-10-26 共达地创新技术(深圳)有限公司 基于可视化的模型调度方法、设备和存储介质
CN113934416B (zh) * 2021-10-26 2022-08-19 山东同圆数字科技有限公司 基于图形化语义策略编程的运维管理方法及系统
CN114679495B (zh) * 2022-02-08 2024-01-05 阿里云计算有限公司 一种资源服务操作请求的调度编排方法和调度执行方法
CN114691233A (zh) * 2022-03-16 2022-07-01 中国电子科技集团公司第五十四研究所 一种基于工作流引擎的遥感数据处理插件分布式调度方法
WO2024065191A1 (en) * 2022-09-27 2024-04-04 Siemens Aktiengesellschaft Method, apparatus, electronic device, and readable storage medium for orchestrating microservices
CN115564322B (zh) * 2022-12-06 2023-09-19 连连（杭州）信息技术有限公司 一种业务处理方法、装置、电子设备及存储介质
CN116132513B (zh) * 2023-02-24 2024-04-19 重庆长安汽车股份有限公司 服务编排的参数更新方法、装置、设备及存储介质
CN115955409B (zh) * 2023-03-09 2023-05-30 花瓣云科技有限公司 一种变更编排方法及相关装置
CN117472552B (zh) * 2023-12-28 2024-05-28 中电数据产业有限公司 服务场景智能编排及动态调度方法、装置、设备及介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104978172A (zh) * 2014-04-04 2015-10-14 中兴通讯股份有限公司 Sdn应用集成管理和控制的方法、系统及设备
CN105207798A (zh) * 2014-06-26 2015-12-30 中兴通讯股份有限公司 软件定义网络中的业务编排方法及装置
US20160294643A1 (en) * 2015-04-03 2016-10-06 Electronics And Telecommunications Research Institute System and method for service orchestration in distributed cloud environment

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE69808633T2 (de) * 1997-07-25 2003-06-12 British Telecomm Ablaufsteuerung für ein softwaresystem
US7117500B2 (en) * 2001-12-20 2006-10-03 Cadence Design Systems, Inc. Mechanism for managing execution of interdependent aggregated processes
US7596416B1 (en) * 2004-08-25 2009-09-29 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Project management tool
GB0427133D0 (en) * 2004-12-10 2005-01-12 British Telecomm Workflow scheduler
CN101729588A (zh) * 2008-10-17 2010-06-09 华为技术有限公司 一种业务编排的方法及装置
US8887163B2 (en) * 2010-06-25 2014-11-11 Ebay Inc. Task scheduling based on dependencies and resources
US20140032255A1 (en) * 2011-03-21 2014-01-30 Tarek Mohamed Mohamed HEGAZI System and method for schedule optimization
CN103513976B (zh) 2012-06-29 2018-06-12 中兴通讯股份有限公司 业务流程建模方法及装置
US9588822B1 (en) * 2012-12-18 2017-03-07 Amazon Technologies, Inc. Scheduler for data pipeline
CN104811326A (zh) 2014-01-24 2015-07-29 中兴通讯股份有限公司 一种管理业务链的方法、系统及装置
US9798596B2 (en) * 2014-02-27 2017-10-24 Commvault Systems, Inc. Automatic alert escalation for an information management system
CN104360842B (zh) 2014-10-23 2017-09-26 桂林电子科技大学 一种基于jbpm的服务动态流程编排方法
US10403399B2 (en) * 2014-11-20 2019-09-03 Netspective Communications Llc Tasks scheduling based on triggering event and work lists management
US9886311B2 (en) * 2015-04-24 2018-02-06 International Business Machines Corporation Job scheduling management
US9916177B2 (en) * 2015-08-19 2018-03-13 International Business Machines Corporation Predictive workload scheduling with integrated analytics
CN106209875A (zh) * 2016-07-19 2016-12-07 青岛海信传媒网络技术有限公司 基于多业务服务器的业务处理方法及业务服务器

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104978172A (zh) * 2014-04-04 2015-10-14 中兴通讯股份有限公司 Sdn应用集成管理和控制的方法、系统及设备
CN105207798A (zh) * 2014-06-26 2015-12-30 中兴通讯股份有限公司 软件定义网络中的业务编排方法及装置
US20160294643A1 (en) * 2015-04-03 2016-10-06 Electronics And Telecommunications Research Institute System and method for service orchestration in distributed cloud environment

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MARTINI, B. ET AL: "An SDN Orchestrator for resources chaining in cloud data centers", EUROPEAN CONFERENCE ON NETWORKS AND COMMUNICATIONS (EU CNC), 23 June 2014 (2014-06-23) - 26 June 2014 (2014-06-26), pages 1 - 5, XP032629326, DOI: 10.1109/EuCNC.2014.6882628 *
See also references of EP3544260A4 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109104297A (zh) * 2018-07-09 2018-12-28 中国银行股份有限公司 一种业务流程的处理方法及装置
CN109104297B (zh) * 2018-07-09 2022-01-21 中国银行股份有限公司 一种业务流程的处理方法及装置
WO2020094045A1 (en) * 2018-11-08 2020-05-14 Huawei Technologies Co., Ltd. Method for enhancing status communications in a sdn-based communication system
CN111083722A (zh) * 2019-04-15 2020-04-28 中兴通讯股份有限公司 模型的推送、模型的请求方法及装置、存储介质
CN111083722B (zh) * 2019-04-15 2024-06-07 中兴通讯股份有限公司 模型的推送、模型的请求方法及装置、存储介质
CN113094167A (zh) * 2020-01-08 2021-07-09 顺丰科技有限公司 一种云计算资源处理方法、装置、设备及存储介质
CN111429127A (zh) * 2020-03-20 2020-07-17 中国建设银行股份有限公司 一种应用于缴费的业务管理方法和装置
CN113435846A (zh) * 2021-06-30 2021-09-24 深圳平安智汇企业信息管理有限公司 业务流程编排方法、装置、计算机设备及存储介质
CN117611094A (zh) * 2023-12-06 2024-02-27 阿帕数字科技有限公司 基于业务流程编排实现供应链体系设计方法及系统
CN117611094B (zh) * 2023-12-06 2024-06-07 阿帕数字科技有限公司 基于业务流程编排实现供应链体系设计方法及系统

Also Published As

Publication number Publication date
ES2898050T3 (es) 2022-03-03
CN108432208B (zh) 2020-02-21
US20190306256A1 (en) 2019-10-03
EP3544260A1 (en) 2019-09-25
EP3544260A4 (en) 2019-11-06
CN108432208A (zh) 2018-08-21
US11178233B2 (en) 2021-11-16
EP3544260B1 (en) 2021-09-22

Similar Documents

Publication Publication Date Title
WO2018107442A1 (zh) 一种业务编排方法、装置及服务器
US10877813B2 (en) Resource control stack based system for multiple domain presentation of cloud computing resource control
US11316758B2 (en) Network service design and deployment process for NFV systems
US11294655B2 (en) Computer-automated software release and deployment architecture
US10862733B2 (en) Standardized microservices for controlling components of distinct applications in multi-tenant clouds
EP3455728B1 (en) Orchestrator for a virtual network platform as a service (vnpaas)
US11698780B2 (en) Deployment and configuration of an edge site based on declarative intents indicative of a use case
US9537717B2 (en) Policy enforcement point provisioning
US11157253B1 (en) Computer-automated software release and deployment architecture
US20170207968A1 (en) Systems and methods for cloud-deployments with imperatives
US10732969B2 (en) Method and apparatus for creating and managing controller based remote solutions
US9634900B2 (en) Declarative approach to virtual network creation and operation
WO2017071266A1 (zh) 一种业务和资源编排的系统、方法及装置
CN108810164A (zh) 一种支持SaaS应用流程按需定制及运行的装置
Thanh et al. Embedding security and privacy into the development and operation of cloud applications and services
Brabra et al. Toward higher-level abstractions based on state machine for cloud resources elasticity
Képes et al. Integrating IoT Devices Based on Automatically Generated Scale-Out Plans
JP2011513842A (ja) コードレスプロビジョニング
US10417051B2 (en) Synchronizing shared resources in an order processing environment using a synchronization component
CA3127714A1 (en) Availability factor (afactor) based automation system
Conțu et al. An automation platform for slice creation using open source MANO
CN115242871B (zh) 业务网关的服务方法及装置、存储介质及电子设备
Smirnov et al. D5. 5–Report on second cycle development
Sowoidnich Concept for executing management operations on components of application instances
Tamburri et al. Deployment Abstractions-Final Version

Legal Events

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

Ref document number: 16924165

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2016924165

Country of ref document: EP

Effective date: 20190612