CN107800550B - Policy execution method and orchestrator - Google Patents
Policy execution method and orchestrator Download PDFInfo
- Publication number
- CN107800550B CN107800550B CN201610791285.4A CN201610791285A CN107800550B CN 107800550 B CN107800550 B CN 107800550B CN 201610791285 A CN201610791285 A CN 201610791285A CN 107800550 B CN107800550 B CN 107800550B
- Authority
- CN
- China
- Prior art keywords
- message
- strategy
- controller
- execution
- receiving
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 24
- 230000002159 abnormal effect Effects 0.000 claims description 23
- 230000003213 activating effect Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 7
- 238000010200 validation analysis Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/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/12—Discovery or management of network topologies
-
- 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/38—Flow based routing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a strategy execution method and a orchestrator, and relates to the technical field of networks. The policy execution method comprises the following steps: the orchestrator sends the strategy message to the controller; if receiving a successful receiving message from the controller, sending execution state query information to the controller; execution state information is received from the controller. In the method, the orchestrator can inquire the execution state of the strategy from the controller after successfully sending the strategy message to the controller, so that the execution state of the strategy can be grasped in time, and the coordination capability to the network is improved.
Description
Technical Field
The invention relates to the technical field of networks, in particular to a strategy execution method and a orchestrator.
Background
A hierarchical model is introduced into an SDN (Software Defined Network), and an SDN system is generally divided into an arrangement layer, a control layer and a forwarding layer when applied to an operator Network at present, wherein the arrangement layer mainly implements arrangement of services and cooperation of the Network, the control layer mainly implements control of devices and the Network, and the forwarding layer mainly implements high-speed forwarding of data streams.
At present, after an SDN orchestrator issues an instruction, a controller feeds back a result of whether the instruction is received, and if the feedback information is not received, the orchestrator determines that the instruction is not received and can re-issue the instruction to the controller, so as to ensure that the instruction can reach the controller.
Disclosure of Invention
It is an object of the invention to propose a solution that improves the network coordination capability of the orchestrator.
According to an aspect of the present invention, a policy enforcement method is provided, including: the orchestrator sends the strategy message to the controller; if receiving the successful receiving message from the controller, sending execution state query information to the controller; execution state information is received from the controller.
Further, after receiving the reception success message from the controller, the sending the execution state query information to the controller includes: starting timing after receiving a receiving success message from the controller; when the predetermined validation time is reached, the controller is queried for the status of the policy's execution.
Further, the policy message includes a predetermined effective time of the policy message; the policy enforcement method further comprises: and acquiring the preset effective time of the strategy message.
Further, if the execution status is unsuccessful, the execution status information includes failure reason information.
Further, still include: and determining the abnormal state according to the failure reason information.
In the method, the orchestrator can inquire the execution state of the strategy from the controller after successfully sending the strategy message to the controller, so that the execution state of the strategy can be grasped in time, and the coordination capability to the network is improved.
According to another aspect of the invention, there is provided an orchestrator comprising: the strategy issuing module is used for sending the strategy message to the controller; a receiving status message receiving module for receiving a receiving success message from the controller; the execution state query module is used for sending execution state query information to the controller after the receiving state message receiving module receives the successful receiving message from the controller; and the execution state message receiving module is used for receiving the execution state information from the controller.
Further, the execution status query module comprises: the timer is used for starting timing after receiving the receiving success message from the controller, and activating the query unit when the preset effective time is reached; and the query unit is used for querying the execution state of the strategy to the controller.
Further, the policy message includes a predetermined effective time of the policy message; the orchestrator further comprises: and the effective time determining module is used for acquiring the preset effective time of the strategy message.
Further, if the execution status is unsuccessful, the execution status information includes failure reason information.
Further, still include: and the abnormal state analysis module is used for determining the abnormal state according to the failure reason information.
After the strategy message is successfully sent to the controller, the orchestrator can inquire the execution state of the strategy from the controller, so that the execution state of the strategy can be grasped in time, and the coordination capability of the network is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flow chart of one embodiment of a policy enforcement method of the present invention.
FIG. 2 is a flow chart of another embodiment of a policy enforcement method of the present invention.
FIG. 3 is a flow chart of another embodiment of a policy enforcement method of the present invention.
FIG. 4 is a schematic diagram of one embodiment of an organizer of the present invention.
FIG. 5 is a diagram illustrating one embodiment of an execution status query module in an orchestrator according to the present invention.
FIG. 6 is a schematic view of another embodiment of an organizer of the present invention.
FIG. 7 is a schematic view of yet another embodiment of an organizer of the present invention.
Detailed Description
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
A flow diagram of one embodiment of a policy enforcement method of the present invention is shown in fig. 1.
In step 101, the orchestrator sends a policy message to the controller. In one embodiment, the orchestrator may formulate and issue policies based on node needs or user configuration.
In step 102, it is determined whether a reception success message is received from the controller. If the receiving success message is received, step 103 is executed. If the successful receiving message is not received, the strategy message can be retransmitted or formulated again.
In step 103, execution status query information is sent to the controller.
In step 104, execution status information is received from the controller. The execution status information may include a success flag, or a failure flag. In one embodiment, when the execution fails, the execution state information further includes failure cause information.
In the method, the orchestrator can inquire the execution state of the strategy from the controller after successfully sending the strategy message to the controller, so that the execution state of the strategy can be grasped in time, and the coordination capability to the network is improved.
In one embodiment, since the policy needs a certain time to be executed, or the policy is not executed immediately, and the policy needs to be executed only at a certain time, after the policy is issued, the orchestrator needs to perform a timing operation. The method considers the actual situation in the strategy execution process, and can obtain more accurate execution state information from the controller.
A flow chart of another embodiment of the policy enforcement method of the present invention is shown in fig. 2.
In step 201, the orchestrator generates a policy message.
In step 202, the orchestrator sends a policy message to the controller.
In step 203, it is determined whether a reception success message is received from the controller. If the receiving success message is received, step 204 is executed. If the receiving success message is not received, the step 201 is executed back.
In step 204, the policy message is queried for a predetermined validation time at the controller.
In step 205, a timer is started to start timing.
In step 206, it is determined whether a predetermined validation time has been reached. If the predetermined effective time is reached, go to step 207; if the preset effective time is not reached, timing is continued until the preset effective time is reached.
In step 207, execution status query information is sent to the controller.
In step 208, execution state information is received from the controller. The execution status information may include a success flag, or a failure flag. In one embodiment, when the execution fails, the execution state information further includes failure cause information.
In the method, the delay of the effective strategy can be fully considered, and asynchronous query is carried out aiming at the preset effective time of the strategy message, so that the orchestrator can timely and accurately acquire the execution state of the strategy, and the coordination capability of the orchestrator on the network is improved.
A flow chart of yet another embodiment of the policy enforcement method of the present invention is shown in fig. 3.
In step 301, the orchestrator sends a policy message to the controller. In one embodiment, the orchestrator may formulate and issue policies based on node needs or user configuration.
In step 302, it is determined whether a reception success message is received from the controller. If the receiving success message is received, step 303 is executed. If the successful receiving message is not received, the strategy message can be retransmitted or formulated again.
In step 303, execution status query information is sent to the controller.
In step 304, execution state information is received from the controller. The execution status information may include a success flag, or a failure flag.
In step 305, it is determined whether the execution is successful according to the execution status information. If the execution is not successful, go to step 306.
In step 306, the abnormal state of the node, link, controller, etc. is analyzed according to the failure cause information in the execution state information. In one embodiment, the abnormal state may be fed back to the user, and abnormal nodes and links may be avoided in the subsequent policy generation, so as to improve the probability of successful policy execution.
In the method, the orchestrator can analyze the fault node in the network according to the failure reason information or judge the fault of the controller, so that the fault state can be grasped in time; furthermore, through network abnormal state marking, a strategy which is more consistent with the current network state can be generated, and the success rate of strategy execution is improved.
A schematic diagram of one embodiment of the orchestrator of the present invention is shown in fig. 4. The policy issuing module 401 is configured to send a policy message to the controller. In one embodiment, the orchestrator may formulate and issue policies based on node needs or user configuration. The receiving status message receiving module 402 is configured to receive a receiving success message from the controller, and activate the execution status query module 403 if the receiving success message is received. The execution status query module 403 is used to send the execution status query information to the controller. The execution status message receiving module 404 is used to receive execution status information from the controller. The execution status information may include a success flag, or a failure flag. In one embodiment, when the execution fails, the execution state information further includes failure cause information.
After the strategy message is successfully sent to the controller, the orchestrator can inquire the execution state of the strategy from the controller, so that the execution state of the strategy can be grasped in time, and the coordination capability of the network is improved.
In one embodiment, since the execution of the policy requires a certain time, or the policy is not executed immediately, and the execution needs to be started at a certain time, the orchestrator needs to perform a timing operation after issuing the policy. A schematic diagram of one embodiment of an execution status query module in the orchestrator of the present invention is shown in fig. 5. Wherein the timer 501 is capable of starting timing after receiving a receiving success message from the controller, and activating the query unit when a predetermined validation time is reached. The querying unit 502 is used for querying the execution state of the policy to the controller.
The orchestrator considers the actual situation in the policy execution process, and can execute the query operation in the preset effective time, so that more accurate execution state information can be obtained.
A schematic diagram of another embodiment of the organizer of the present invention is shown in fig. 6. The structure and function of the policy issuing module 601, the receiving status message receiving module 602, the executing status querying module 603, and the executing status message receiving module 604 are similar to those in the embodiment of fig. 4. The orchestrator further comprises an validation time determination module 605 capable of obtaining predetermined validation time information of the policy message and sending the predetermined validation time information to the execution status query module 603. The execution status query module 603 issues the execution status query information at the predetermined effective time according to the predetermined effective time information.
Because the preset effective time of different strategy messages is different, the orchestrator can carry out asynchronous query more pertinently according to the preset effective time of the strategy messages, so that the orchestrator can timely and accurately acquire the execution state of the strategy, and the network coordination capability of the orchestrator is improved.
A schematic diagram of yet another embodiment of the orchestrator of the present invention is shown in fig. 7. The structure and function of the policy issuing module 701, the received status message receiving module 702, the execution status querying module 703 and the execution status message receiving module 704 are similar to those in the embodiments of fig. 4 and fig. 6. The orchestrator further comprises an abnormal state analysis module 705 capable of analyzing abnormal states of nodes, links, controllers, etc. according to the failure reason information in case that the received execution state message comprises the execution unsuccessful flag and the failure reason information. In one embodiment, the orchestrator may feed back the abnormal state to the user, and may avoid the abnormal node and link in the subsequent policy generation, so as to improve the probability of successful policy execution.
The orchestrator can analyze the fault node in the network according to the failure reason information or judge the controller fault, so that the fault state can be grasped in time; furthermore, through network abnormal state marking, a strategy which is more consistent with the current network state can be generated, and the success rate of strategy execution is improved.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention and not to limit it; although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art will understand that: modifications to the specific embodiments of the invention or equivalent substitutions for parts of the technical features may be made; without departing from the spirit of the present invention, it is intended to cover all aspects of the invention as defined by the appended claims.
Claims (3)
1. A method for policy enforcement, comprising:
acquiring preset effective time of a policy message, wherein the preset effective time is generated according to the time length required by the execution of the policy and the appointed execution time of the policy;
the method comprises the steps that a composer sends a strategy message to a controller, wherein the strategy message comprises preset effective time of the strategy message;
if receiving a successful receiving message from the controller, timing, and sending execution state query information to the controller when the preset effective time corresponding to the strategy message is reached;
receiving execution state information from the controller, wherein if the execution state is unsuccessful, the execution state information comprises failure reason information;
determining an abnormal state according to the failure reason information;
and feeding back the abnormal state to the user, and avoiding the nodes and links with abnormal states in the subsequent strategy generation.
2. The method of claim 1,
the abnormal states include abnormal states of nodes, links, and controllers.
3. An organizer, comprising:
the effective time determining module is used for acquiring the preset effective time of the strategy message;
the system comprises a strategy issuing module, a strategy receiving module and a strategy sending module, wherein the strategy issuing module is used for sending a strategy message to a controller, and the strategy message comprises the preset effective time of the strategy message;
a receiving status message receiving module for receiving a receiving success message from the controller;
an execution state query module, configured to send execution state query information to the controller after the reception state message receiving module receives a reception success message from the controller, where the execution state query module includes:
the timer is used for starting timing after receiving the successful receiving message from the controller, and activating the query unit when the preset effective time corresponding to the strategy message is reached;
the query unit is used for querying the execution state of the strategy to the controller;
an execution status message receiving module, configured to receive execution status information from the controller, where the execution status information includes failure cause information if the execution status is unsuccessful;
and the abnormal state analysis module is used for determining abnormal states according to the failure reason information, wherein the abnormal states comprise abnormal states of nodes, links and controllers so as to feed back the abnormal states to a user, and the nodes and links with abnormal states are avoided in the subsequent strategy generation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610791285.4A CN107800550B (en) | 2016-08-31 | 2016-08-31 | Policy execution method and orchestrator |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610791285.4A CN107800550B (en) | 2016-08-31 | 2016-08-31 | Policy execution method and orchestrator |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107800550A CN107800550A (en) | 2018-03-13 |
| CN107800550B true CN107800550B (en) | 2021-04-30 |
Family
ID=61528744
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610791285.4A Active CN107800550B (en) | 2016-08-31 | 2016-08-31 | Policy execution method and orchestrator |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107800550B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104219235A (en) * | 2014-08-28 | 2014-12-17 | 福建新大陆软件工程有限公司 | Distributed transaction requesting method and device |
| CN105871576A (en) * | 2015-01-21 | 2016-08-17 | 杭州华三通信技术有限公司 | Strategy management method and strategy management device based on SDN (Software Defined Network) |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101369909A (en) * | 2007-08-15 | 2009-02-18 | 华为技术有限公司 | Method, network communicating system and device for reporting policy execution result |
| CN101355807B (en) * | 2008-08-20 | 2016-08-03 | 中兴通讯股份有限公司 | A kind of feedback method during failure of policy installation |
| CN101355808B (en) * | 2008-08-20 | 2013-01-16 | 中兴通讯股份有限公司 | Method for reporting failure of policy installation |
| CN105392149A (en) * | 2014-09-05 | 2016-03-09 | 中兴通讯股份有限公司 | Strategy adjusting trigger and strategy adjusting method and device, and strategy adjusting system |
| CN104539457B (en) * | 2014-12-30 | 2018-09-18 | 北京邮电大学 | Equipment based on software definition technology unifies the methods, devices and systems of management and control |
-
2016
- 2016-08-31 CN CN201610791285.4A patent/CN107800550B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104219235A (en) * | 2014-08-28 | 2014-12-17 | 福建新大陆软件工程有限公司 | Distributed transaction requesting method and device |
| CN105871576A (en) * | 2015-01-21 | 2016-08-17 | 杭州华三通信技术有限公司 | Strategy management method and strategy management device based on SDN (Software Defined Network) |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107800550A (en) | 2018-03-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3197237A1 (en) | Intelligent home terminal and control method therefor | |
| US20080168127A1 (en) | System and Method For Scheduling Device Management | |
| US9282422B2 (en) | Method and system for parameter configuration of mobile terminal | |
| EP4047882A1 (en) | Operation control method and device, household electrical appliance, and storage medium | |
| CN112492023B (en) | Device control method, device, storage medium, and electronic apparatus | |
| CN110493075B (en) | Method, device and system for monitoring online duration of equipment | |
| CN112099968A (en) | Equipment control method, device, system, storage medium and electronic device | |
| CN101009649A (en) | Queue management in a network processor | |
| KR20080024480A (en) | A processing method, terminal, equipment management server and system for subscribing task in the equipment management | |
| US9836958B2 (en) | Device control method, server, system and computer storage medium | |
| US20180115474A1 (en) | Flow entry aging method, switch, and controller | |
| WO2010031304A1 (en) | Method, device and system for multicasting upgrade files | |
| CN112466303B (en) | Device discovery method, device, storage medium, and electronic apparatus | |
| CN112423322B (en) | Model information sending method, device, storage medium and electronic device | |
| CN111934956B (en) | Equipment configuration method and device, storage medium and electronic device | |
| CN106878178B (en) | Flow table issuance method, system and controller | |
| CN106327143B (en) | Method and apparatus for nodes in a flow | |
| CN107800550B (en) | Policy execution method and orchestrator | |
| CN104796874B (en) | Information binding method and device | |
| KR102017631B1 (en) | Terminal apparatus and method for transmitting and receiving data | |
| US8332498B2 (en) | Synchronized relay messaging and coordinated network processing using SNMP | |
| CN116319729A (en) | Robot control method, device, server, system and storage medium | |
| WO2014177096A1 (en) | Method and device for querying and notifying scheduler supporting ability | |
| JP5276461B2 (en) | Network system | |
| CN114390436B (en) | Equipment control method and device, storage medium and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| EE01 | Entry into force of recordation of patent licensing contract |
Application publication date: 20180313 Assignee: China Telecom Digital Intelligence Technology Co.,Ltd. Assignor: CHINA TELECOM Corp.,Ltd. Contract record no.: X2024110000005 Denomination of invention: Strategy execution methods and orchestrators Granted publication date: 20210430 License type: Common License Record date: 20240226 |
|
| EE01 | Entry into force of recordation of patent licensing contract |