CN108572957A - A kind of dispatching method and device of operation NE database - Google Patents
A kind of dispatching method and device of operation NE database Download PDFInfo
- Publication number
- CN108572957A CN108572957A CN201710132639.9A CN201710132639A CN108572957A CN 108572957 A CN108572957 A CN 108572957A CN 201710132639 A CN201710132639 A CN 201710132639A CN 108572957 A CN108572957 A CN 108572957A
- Authority
- CN
- China
- Prior art keywords
- configuration protocol
- protocol session
- network element
- priority
- configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000010586 diagram Methods 0.000 description 14
- 238000004590 computer program Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 5
- 230000004048 modification Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses it is a kind of operation NE database dispatching method and device, the method includes：Obtain the type of each configuration protocol session of operation NE database and the object run priority of each configuration protocol session；According to the type of each configuration protocol session and the object run priority of each configuration protocol session, by the default operator precedence grade for determining strategy and determining each configuration protocol session；When the configuration protocol session application operates the NE database, the operation of each configuration protocol session is dispatched according to the application time point or operator precedence grade of the state of the NE database and each configuration protocol session.
Description
Technical Field
The invention relates to a Software Defined Network (SDN) technology, in particular to a scheduling method and device of an operation Network metadata base.
Background
The SDN is a novel network architecture provided by Stanford university in America, realizes flexible control of network flow by separating a control plane and a data plane of network equipment, and provides a good platform for innovation of a network.
The SDN Controller (SDN Controller) may simultaneously implement Configuration and control on a Network Element, and the SDN Controller including a Configuration Application (Configuration Application) configures a Network Element (Network Element) located at an opposite end of a Session through a Configuration protocol Session (Configuration protocol Session).
In SDN, a Network Configuration Protocol (Network Configuration Protocol) is a common Protocol used for an SDN controller to configure a Network element, and other protocols that can be used for configuring a Network element further include a Simple Network Management Protocol (SNMP) and a Command Line Interface (CLI).
The NETCONF protocol is defined by RFC 6241 issued by the International standards organization Internet Engineering Task Force (IETF) in 2011, wherein four layers of the NETCONF protocol are specified; fig. 1 is a schematic diagram of a NETCONF protocol layer, as shown in fig. 1, the NETCONF protocol includes a Secure Transport layer (Secure Transport), a message layer (Messages), an operation layer (Operations), and a Content layer (Content), wherein the operation layer defines a series of Operations that an SDN controller can perform on a network element, including nine Operations of get configuration < get-config >, edit configuration < edit-config >, copy configuration < copy-config >, delete configuration < delete-config >, lock < lock >, unlock < unlock >, get information < get >, close session < close-session > and force close session < kill-session >, wherein the lock < lock > operation is used for the SDN controller to lock a certain database (data) of the network element, and only the controller performing the lock operation can perform the lock session of the SDN protocol by the SDN controller during the time when the certain database of the network element is locked, modifications to the locked network element database are not possible for other SDN controllers and other configuration protocols, such as SNMP, CLI, to make any modifications to the locked network element database.
Of course, in practical applications, other configuration protocols such as SNMP and CLI may also perform a lock operation on the network element database, and similarly, once the lock operation is performed on the network element database by SNMP or CLI, only the SDN controller performing the lock operation may modify the locked network element database through the SNMP session or CLI session performing the lock operation, and no modification can be performed on the locked network element database by other SDN controllers and other configuration protocols. However, this may cause a configuration protocol or a configuration protocol session to lock a network metadata base for a long time, which may affect the operation efficiency of the entire network.
Although the SDN controller wants to lock a network metadata base that is locked by other configuration protocol sessions, it may force to close the configuration protocol session that is locked by the network metadata base by performing a forced close session < kill-session > operation, and then perform a lock < lock > operation on the network metadata base, but in this way, the forced close configuration protocol session is completely cleared, and a session needs to be re-established next time, which wastes time for establishing a session, increases network overhead, and risks losing instructions and data.
Disclosure of Invention
In order to solve the existing technical problem, embodiments of the present invention desirably provide a scheduling method and apparatus for operating a network element database, which can avoid that the network element database is operated by a configuration protocol or a configuration protocol session for a long time, and can not increase network overhead and eliminate the problem of losing instructions and data.
The technical scheme of the embodiment of the invention is realized as follows:
the embodiment of the invention provides a scheduling method of an operation network metadata base, which comprises the following steps:
acquiring the type of each configuration protocol session of an operation network metadata base and the target operation priority of each configuration protocol session;
determining the operation priority of each configuration protocol session according to a preset determination strategy according to the type of each configuration protocol session and the target operation priority of each configuration protocol session;
and when the configuration protocol session applies for operating the network element database, scheduling the operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session.
Preferably, before the obtaining the type of the configuration protocol session of the operation network metadata base and the target operation priority of each configuration protocol session, the method further includes:
sending information that the network element database supports a preemptive scheduling mode based on operation priority to configuration applications of each configuration protocol session opposite terminal;
and instructing the configuration application of each opposite terminal of the configuration protocol session to send information containing the target operation priority of each configuration protocol session to the network element where the network element database is located.
Preferably, the determining the operation priority of each configuration protocol session according to the preset determination policy includes:
and determining the operation priority of each configuration protocol session according to the type of each configuration protocol session and/or according to the target operation priority of each configuration protocol session.
Preferably, the scheduling operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session includes:
when the state of the network element database is idle, scheduling the operation of each configuration protocol session according to the application time point of each configuration protocol session in sequence; or
And when the state of the network element database is that exclusive operation of the configuration protocol session exists, scheduling the operation of each configuration protocol session according to the operation priority of the first configuration protocol session which is exclusively operated and the second configuration protocol session which applies for operation.
Preferably, the scheduling operation of each configuration protocol session according to the operation priority of the configuration protocol session which is exclusively operating and the configuration protocol session which applies for operation includes:
when the operation priority of the first configuration protocol session is smaller than that of the second configuration protocol session, preemptively operating the network element database by the second configuration protocol session; otherwise, the original operation state is maintained.
Preferably, the method further comprises:
when the operation priority of the first configuration protocol session is greater than or equal to the operation priority of the second configuration protocol session, the configuration application of the opposite end of the second configuration protocol session applies to the network element for obtaining the operation priority greater than the operation priority of the first configuration protocol session.
The embodiment of the invention also provides a scheduling device of the operation network metadata base, which comprises an acquisition module, a determination module and a scheduling module; wherein,
the acquisition module is used for acquiring the type of each configuration protocol session of the operation network metadata base and the target operation priority of each configuration protocol session;
the determining module is used for determining the operation priority of each configuration protocol session according to a preset determining strategy according to the type of each configuration protocol session and the target operation priority of each configuration protocol session;
the scheduling module is used for scheduling the operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session when the configuration protocol session applies for operating the network element database.
Preferably, the apparatus further comprises a sending module, configured to:
sending information that the network element database supports a preemptive scheduling mode based on operation priority to configuration applications of each configuration protocol session opposite terminal;
and instructing the configuration application of each opposite terminal of the configuration protocol session to send information containing the target operation priority of each configuration protocol session to the network element where the network element database is located.
Preferably, the determining module is specifically configured to:
and determining the operation priority of each configuration protocol session according to the type of each configuration protocol session and/or according to the target operation priority of each configuration protocol session.
Preferably, the scheduling module is specifically configured to:
when the state of the network element database is idle, scheduling the operation of each configuration protocol session according to the application time point of each configuration protocol session in sequence; or
And when the state of the network element database is that exclusive operation of the configuration protocol session exists, scheduling the operation of each configuration protocol session according to the operation priority of the first configuration protocol session which is exclusively operated and the second configuration protocol session which applies for operation.
Preferably, the scheduling module is further configured to:
when the operation priority of the first configuration protocol session is smaller than that of the second configuration protocol session, preemptively operating the network element database by the second configuration protocol session;
otherwise, the original operation state is maintained.
Preferably, the scheduling module is further configured to:
when the operation priority of the first configuration protocol session is greater than or equal to the operation priority of the second configuration protocol session, the configuration application of the opposite end of the second configuration protocol session applies to the network element for obtaining the operation priority greater than the operation priority of the first configuration protocol session.
The scheduling method and device for the metadata base of the operation network provided by the embodiment of the invention are used for acquiring the types of all configuration protocol sessions of the metadata base of the operation network and the target operation priority of all configuration protocol sessions; determining the operation priority of each configuration protocol session according to a preset determination strategy according to the type of each configuration protocol session and the target operation priority of each configuration protocol session; when the network element database is applied for operation by the configuration protocol session, scheduling the operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session; therefore, the embodiment of the invention determines the operation priority of each configuration protocol session according to the type of each configuration protocol session and the target operation priority of each configuration protocol session, and reasonably schedules the operation of each configuration protocol session on the network element database according to the operation priority of each configuration protocol session, so that the network element database can be prevented from being locked by one configuration protocol or configuration protocol session for a long time, the time for newly establishing the session can be reduced, the network overhead can not be increased, and the problem of instruction and data loss can be solved.
Drawings
Fig. 1 is a schematic diagram of NETCONF protocol layering;
fig. 2 is a schematic flow chart illustrating an implementation of a scheduling method for an operation network metadata base according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram illustrating a component structure of a scheduling apparatus for operating a network element database according to an embodiment of the present invention;
fig. 4 is a schematic flow chart illustrating an implementation of a scheduling method for a running configuration database of a lock network element according to an embodiment of the present invention;
fig. 5 is a schematic flow chart illustrating an implementation of a scheduling method for a candidate configuration database of a secondary locking network element according to an embodiment of the present invention.
Detailed Description
So that the manner in which the features and aspects of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings.
Fig. 2 is a schematic diagram of an implementation flow of a scheduling method for an operation network metadata database according to an embodiment of the present invention, in the embodiment of the present invention, a main body of the operation network metadata database is a configuration application of a configuration protocol session peer, which is generally an application capable of running a configuration protocol session, such as an SDN controller or a network management application, and the method may be implemented by a network element, as shown in fig. 2, the method includes:
step 101: acquiring the type of each configuration protocol session of an operation network metadata base and the target operation priority of each configuration protocol session;
here, the network element is composed of one or more machine disks or machine frames, the network element is a network element capable of independently performing a certain transmission and/or forwarding function, and the network element is generally the smallest unit that can be monitored and managed in network management.
The configuration protocol session is a session established for a configuration application at one end of the configuration protocol session to configure a network element at the other end of the session.
The type of the configuration protocol session can be classified according to the protocol adopted by the configuration application to configure the network element, such as the configuration protocol session of the NETCONF protocol, the configuration protocol session of the SNMP and the configuration protocol session of the CLI;
the network element may obtain the type of the configuration protocol session by a signal sent to the network element when the configuration application establishes the configuration protocol session.
In addition, supporting a preemptive scheduling mode based on an operation priority is one capability of a network element, but some network elements do not support the preemptive scheduling mode based on the operation priority; therefore, before the network element obtains the type of the configuration protocol session of the operation network metadata base and the target operation priority of each configuration protocol session, the step further includes: a network element sends information that a network element database of the network element database supports a preemptive scheduling mode based on operation priority to a configuration application of each configuration protocol session opposite terminal;
meanwhile, in order to obtain the target operation priority of each configuration protocol session, the network element also instructs the configuration application of each configuration protocol session opposite end to send information containing the target operation priority of each configuration protocol session to the network element;
in the embodiment of the present invention, only if the network element database of the network element itself supports the preemptive scheduling method based on the operation priority, the corresponding information can be sent to the configuration application of each configuration protocol session opposite end and the configuration application of each configuration protocol session opposite end is instructed to send the corresponding information to itself, which is also a precondition for adopting the scheduling method of the embodiment of the present invention.
The target operation priority is an operation priority determined by the configuration application according to the expectation of the configuration protocol session, the configuration application of the opposite end of the configuration protocol session can determine the target operation priority corresponding to the configuration application according to the operation requirement of the configuration application, and sends information containing the target operation priority to the network element;
specifically, the operation priority may be represented by a binary number, and the larger the number of the operation priority is, the more priority the operation is; the number of levels of the operation priority depends on the number of bits of binary digits representing the operation priority, and if the number of bits is two, the number of levels of the operation priority is 4, and if the number of bits is three, the number of levels of the operation priority is 8; in practical applications, the operation priority is generally represented as a binary number of three bits, but in the embodiment of the present invention, for simplicity, the operation priority is represented as a natural decimal number, which may be 1 at the lowest level and 8 at the highest level.
Step 102: determining the operation priority of each configuration protocol session according to a preset determination strategy according to the type of each configuration protocol session and the target operation priority of each configuration protocol session;
here, the preset determination policy includes: determining the operation priority of each configuration protocol session according to the type of each configuration protocol session, and/or determining the operation priority of each configuration protocol session according to the target operation priority of each configuration protocol session;
specifically, the network element may determine the operation priority of each configuration protocol session only according to the type of each configuration protocol session or only according to the target operation priority of each configuration protocol session; or determining the operation priority of each configuration protocol session by combining the type of each configuration protocol session and the target operation priority of each configuration protocol session;
the method for the network element to determine the operation priority of each configuration protocol session only according to the type of each configuration protocol session may be: the network element determines a higher operation priority for the configuration protocol session executing the NETCONF protocol, determines a medium operation priority for the configuration protocol session executing the SNMP, and determines a lower operation priority for the configuration protocol session executing the CLI;
the network element only determines the operation priority of each configuration protocol session according to the target operation priority of each configuration protocol session, which is relatively simple, and can directly determine the operation priority of each configuration protocol session according to the target operation priority of each configuration protocol session, and the method is generally applicable to the condition that each configuration protocol session is of the same type;
the method for determining the operation priority of each configuration protocol session by the network element in combination with the type of each configuration protocol session and the target operation priority of each configuration protocol session may be: determining a priority coefficient for each type of configuration protocol session, for example, the priority coefficient of the configuration protocol session of the NETCONF protocol may be 3, the priority coefficient of the configuration protocol session of the SNMP may be 2, and the priority coefficient of the configuration protocol session of the CLI may be 1; then multiplying the priority coefficient of each configuration protocol session with the target operation priority of each configuration protocol session, and determining the operation priority according to the magnitude sequence of the obtained products;
and if the products of two or more than two are the same, determining the operation priority of each configuration protocol session according to the type of each configuration protocol session.
Step 103: and when the configuration protocol session applies for operating the network element database, scheduling the operation of each configuration protocol session according to the state of the network element database and the application time or the operation priority of each configuration protocol session.
Specifically, when the state of the network element database is idle, the network element schedules the operation of each configuration protocol session in sequence according to the application time point of each configuration protocol session;
and when the state of the network element database is that exclusive operation of the configuration protocol session exists, the network element schedules the operation of each configuration protocol session according to the operation priority of the first configuration protocol session which is exclusively operated and the second configuration protocol session which applies for operation.
More specifically, when the state of the network metadata base is idle, the configuration protocol session which is applied for operation first is operated first, that is, the configuration protocol session which is applied for operation first is operated first, so that the time utilization rate of the network metadata base is higher;
when the state of the network element database is exclusive operation of the configuration protocol session, the operation of each configuration protocol session needs to be scheduled according to the operation priority of the configuration protocol session which is exclusively operated and the configuration protocol session which applies for operation.
The scheduling method of the embodiment of the invention is mainly used for exclusive operation of the network element database, and the problem that one configuration protocol or configuration protocol session locks one network element database for a long time can be avoided by adopting the uniform scheduling of the embodiment of the invention; in the NETCONF protocol, the exclusive operation is locking, namely the network metadata database is firstly locked, and then the database data is modified; if the operation is a non-exclusive operation, for example, the operations of acquiring configuration < get-config >, copying configuration < copy-config > and the like in the NETCONF protocol are not the scope discussed in the embodiments of the present invention.
More specifically, when the operation priority of the first configuration protocol session is smaller than the operation priority of the second configuration protocol session, the second configuration protocol session preemptively operates the network metadata base; otherwise, the network element maintains the original operation state.
When the second configuration protocol session preemptively operates the network metadata database, the first configuration protocol session only suspends exclusive operation and is not cleared; after the second configuration protocol session releases the exclusive operation, the first configuration protocol session can continue to perform the exclusive operation according to the original progress; therefore, the whole network has higher efficiency, the network overhead is not increased, and the problem of losing instructions and data does not exist.
Further, when the operation priority of the first configuration protocol session is greater than the operation priority of the second configuration protocol session, the configuration application of the opposite end of the second configuration protocol session applies to the network element for obtaining the operation priority greater than the operation priority of the first configuration protocol session.
Therefore, when the configuration protocol session with lower operation priority has very urgent tasks to operate the network element database, the network element can be applied for obtaining the operation priority which is greater than the operation priority of the currently operated configuration protocol session again, and then the preemptive operation is carried out;
after obtaining the request of reapplication of the operation priority level for the configuration protocol session with lower operation priority level, the network element can determine whether to be determined again according to the transaction emergency degree and the operation time of the currently operating configuration protocol session;
the degree of urgency of the transaction can be generally expressed by a specific code contained in information sent by a configuration application at the opposite end of the configuration protocol session;
the operation time of the currently operating configurator protocol session may indicate whether the currently operating configurator protocol session exclusively operates the network element for a long time, because if one configurator protocol session exclusively operates one network element for a long time, it indicates that other applications which need to operate the network element may be affected, and the operation efficiency of the whole network may be affected.
Fig. 3 is a schematic structural diagram of a scheduling apparatus for operating a network element database according to an embodiment of the present invention, and as shown in fig. 3, the apparatus includes an obtaining module 31, a determining module 32, and a scheduling module 33; wherein,
the acquiring module 31 is configured to acquire the type of each configuration protocol session in the operation network metadata base and the target operation priority of each configuration protocol session;
the determining module 32 is configured to determine, according to the type of each configuration protocol session and the target operation priority of each configuration protocol session, the operation priority of each configuration protocol session according to a preset determining policy;
the scheduling module 33 is configured to schedule the operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session when the configuration protocol session applies for operating the network element database.
For clarity of description, the following will respectively describe each module in detail:
the acquiring module 31 is configured to acquire the type of each configuration protocol session in the operation network metadata base and the target operation priority of each configuration protocol session;
supporting a preemptive scheduling mode based on an operation priority is one capability of a network element, but some network elements do not support the preemptive scheduling mode based on the operation priority; therefore, the apparatus further comprises a sending module 34, wherein the sending module 34 is configured to:
transmitting information that a network metadata base supports a preemptive scheduling mode based on operation priority to a configuration application of each configuration protocol session opposite terminal;
meanwhile, in order to obtain the target operation priority of each configuration protocol session, the sending module 34 is further configured to:
instruct the configuration application of each opposite end of the configuration protocol session to send information containing the target operation priority of each configuration protocol session to the obtaining module 31.
The determining module 32 is configured to determine, according to the type of each configuration protocol session and the target operation priority of each configuration protocol session, the operation priority of each configuration protocol session according to a preset determining policy;
here, the preset determination policy includes: determining the operation priority of each configuration protocol session according to the type of each configuration protocol session, and/or determining the operation priority of each configuration protocol session according to the target operation priority of each configuration protocol session;
specifically, the determining module 32 may determine the operation priority of each configuration protocol session only according to the type of each configuration protocol session or only according to the target operation priority of each configuration protocol session; the operation priority of each configuration protocol session may also be determined in combination with the type of each configuration protocol session and the target operation priority of each configuration protocol session.
The determining module 32 may determine the operation priority of each configuration protocol session only according to the type of each configuration protocol session by: the determining module 32 determines a higher operation priority for the configuration protocol session executing the NETCONF protocol, a medium operation priority for the configuration protocol session executing the SNMP, and a lower operation priority for the configuration protocol session executing the CLI;
the determining module 32 determines the operation priority of each configuration protocol session only according to the target operation priority of each configuration protocol session, which is relatively simple, and can directly determine the operation priority of each configuration protocol session according to the target operation priority of each configuration protocol session, and the method is generally applicable to the condition that each configuration protocol session is of the same type;
the determining module 32, in combination with the type of each configuration protocol session and the target operation priority of each configuration protocol session, may determine the operation priority of each configuration protocol session by: determining a priority coefficient for each type of configuration protocol session, for example, the priority coefficient of the configuration protocol session of the NETCONF protocol may be 3, the priority coefficient of the configuration protocol session of the SNMP may be 2, and the priority coefficient of the configuration protocol session of the CLI may be 1; then multiplying the priority coefficient of each configuration protocol session with the target operation priority of each configuration protocol session, and determining the operation priority according to the magnitude sequence of the obtained products;
and if the products of two or more than two are the same, determining the operation priority of each configuration protocol session according to the type of each configuration protocol session.
The scheduling module 33 is configured to schedule the operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session when the configuration protocol session applies for operating the network element database.
When the state of the network element database is idle, the scheduling module 33 schedules the operation of each configuration protocol session in sequence according to the application time point of each configuration protocol session;
when the state of the network element database is that exclusive operation of the configuration protocol session exists, the scheduling module 33 schedules the operation of each configuration protocol session according to the operation priority of the first configuration protocol session which is exclusively operated and the second configuration protocol session which applies for operation.
The scheduling method of the embodiment of the invention is mainly used for exclusive operation of the network element database, and the problem that one configuration protocol or configuration protocol session locks one network element database for a long time can be avoided by adopting the uniform scheduling of the embodiment of the invention; in the NETCONF protocol, the exclusive operation is locking, namely the network metadata database is firstly locked, and then the database data is modified; if the operation is a non-exclusive operation, for example, the operations of acquiring configuration < get-config >, copying configuration < copy-config > and the like in the NETCONF protocol are not the scope discussed in the embodiments of the present invention.
More specifically, when the operation priority of the first configuration protocol session is smaller than the operation priority of the second configuration protocol session, the second configuration protocol session preemptively operates the network metadata base; otherwise, the scheduling module 33 maintains the original operation state.
When the second configuration protocol session preemptively operates the network metadata database, the first configuration protocol session only suspends exclusive operation and is not cleared; after the second configuration protocol session releases the exclusive operation, the configuration protocol session of the first configuration protocol session can continue to perform the exclusive operation following the original progress; therefore, the whole network has higher efficiency, the network overhead is not increased, and the problem of losing instructions and data does not exist.
Further, when the operation priority of the first configuration protocol session is greater than the operation priority of the second configuration protocol session, the configuration application of the opposite end of the second configuration protocol session applies to the network element for obtaining the operation priority greater than the operation priority of the first configuration protocol session.
Therefore, when the configuration protocol session with lower operation priority has very urgent tasks to operate the network element database, the network element can be applied for obtaining the operation priority which is greater than the operation priority of the currently operated configuration protocol session again, and then the preemptive operation is carried out;
after obtaining the request of reapplication of the operation priority level for the configuration protocol session with lower operation priority level, the network element can determine whether to be determined again according to the transaction emergency degree and the operation time of the currently operating configuration protocol session;
the degree of urgency of the transaction can be generally expressed by a specific code contained in information sent by a configuration application at the opposite end of the configuration protocol session;
the operation time of the currently operating configurator protocol session may indicate whether the currently operating configurator protocol session exclusively operates the network element for a long time, because if one configurator protocol session exclusively operates one network element for a long time, it indicates that other applications which need to operate the network element may be affected, and the operation efficiency of the whole network may be affected.
In the embodiment of the present invention, the obtaining module 31, the determining module 32, the scheduling module 33, and the sending module 34 may be implemented by a Central Processing Unit (CPU), a Microprocessor (MPU), a Digital Signal Processor (DSP), or a Field Programmable Gate Array (FPGA) located in a network element.
In order to more clearly describe the embodiments of the present invention, the following explains the embodiments of the present invention by taking a real application scenario as an example.
Example one
In this embodiment, each configuration protocol session executes a NETCONF protocol, and belongs to the same type of configuration protocol session, so that the network element only needs to determine an operation priority according to a target operation priority of each controller. For brevity, the operation priority is simply referred to as priority.
Fig. 4 is a schematic flowchart of an implementation process of a scheduling method for a running configuration database of a lock network element according to an embodiment of the present invention, as shown in fig. 4, the process includes:
step 401: the network element 1 informs the controller 1, the controller 2 and the controller 3 that the preemptive locking based on priority is supported;
in this embodiment, the controller 1, the controller 2, and the controller 3 are all configuration applications of a configuration protocol session opposite terminal, and are generally SDN controllers, which are controllers for short;
the lock is a lock < lock > operation in the configuration protocol, which is an exclusive operation used to modify the database.
Step 402: each controller advertises its target priority to network element 1;
specifically, the target priority of the controller 1 is 1, the target priority of the controller 2 is 2, and the target priority of the controller 3 is 3.
Step 403: the network element 1 determines the priority for each configuration protocol session according to the received target priority sent by the controller and informs the controller of the priority;
since the controllers are of the same type, the network element 1 determines the priority according to the target priority of each controller, that is, the priority of the controller 1 is 1, the priority of the controller 2 is 2, and the priority of the controller 3 is 3.
Step 404: the controller 1 locks the running configuration database of the network element 1;
here, it is assumed that the time at which the controller 1 applies for locking the running configuration database of the network element 1 is the earliest, and therefore the running configuration database of the network element 1 is locked by the controller 1.
Step 405: the operation configuration database of the network element 1 is locked by the session 1, the network element 1 informs the controller 2 and the controller 3 that the operation configuration database of the network element 1 is in a locked state by the session 1, and the priority of the currently locked session 1 is 1;
the session 1 is a configuration protocol session established between the controller 1 and the network element 1, and so on, and the session 2 is a configuration protocol session established between the controller 2 and the network element 1; session 3 is a configuration protocol session established by controller 3 with network element 1.
Step 406: when the controller 2 applies for locking the operation configuration database of the network element 1, the priority 1 of the currently locked session 1 is lower than the priority 2 of the session 2 between the controller 2 and the network element 1, and the controller 2 executes preemptive locking;
it is assumed here that the controller 2 requests to lock the running configuration database of the network element 1 later than the controller 1 but earlier than the controller 3.
Step 407: preemptively locking the running configuration database of the network element 1 by the session 2, informing the controller 1 and the controller 3 that the running configuration database of the network element 1 is in a preemptively locked state by the session 2 by the network element 1, and setting the priority of the session 2 of the current preemptively locking to be 2;
then, the controller 3 may also execute preemptive locking by determining the priority of the currently locked session, which is not described in detail herein.
Example two
In this embodiment, the configuration protocol sessions executed by the controller 4 are of different types; the preset determination strategy is that the network element determines the operation priority of each configuration protocol session only according to the type of each configuration protocol session. For brevity, the operation priority is simply referred to as priority.
Fig. 5 is a schematic diagram of an implementation flow of a scheduling method for a candidate configuration database of a secondary locked network element according to an embodiment of the present invention, and as shown in fig. 5, the flow includes:
step 501: the network element 2 informs the controllers 4, 5 and 6 that the preemptive locking based on the priority is supported;
here, the controller 4, the controller 5, and the controller 6 are all configuration applications of a configuration protocol session opposite terminal, and are generally SDN controllers, which are controllers for short;
in this embodiment, the controller 4 is an SDN controller that executes an SNMP, and the controller 5 and the controller 6 are SDN controllers that execute a NETCONF protocol;
the lock is a lock < lock > operation in the configuration protocol, which is an exclusive operation used to modify the database.
Step 502: each controller advertises its target priority to network element 2;
specifically, the target priority of the controller 4 is 4, the target priority of the controller 5 is 2, and the target priority of the controller 6 is 3.
Step 503: the network element 2 determines the priority for each configuration protocol session according to the protocol type of the configuration protocol session and the received target priority sent by the controller and informs the controller of the priority;
since the priority of executing the configuration protocol session of the SNMP is generally lower than the priority of executing the configuration protocol session of the NETCONF protocol, the network element 2 determines a lower priority to the controller 4 and a higher priority to the controller 5 and the controller 6;
specifically, the priority of the controller 4 is 1, the priority of the controller 5 is 2, and the priority of the controller 6 is 3.
Step 504: the controller 4 locks the candidate configuration database of the network element 2;
here, it is assumed that the time at which the controller 4 applies for locking the candidate configuration database of the network element 2 is the earliest, and therefore the candidate configuration database of the network element 2 is locked by the controller 4.
Step 505: the candidate configuration database of the network element 2 is locked by the session 1, the network element 2 informs the controller 5 and the controller 6 that the candidate configuration database of the network element 2 is in a locked state by the session 1, and the priority of the currently locked session 1 is 1;
the session 1 is a configuration protocol session established between the controller 4 and the network element 2, and so on, and the session 2 is a configuration protocol session established between the controller 5 and the network element 2; session 3 is a configuration protocol session established by controller 6 with network element 2.
Step 506: when the controller 5 applies for locking the candidate configuration database of the network element 2, the priority 1 of the currently locked session 1 is lower than the priority 2 of the session 2 between the controller 5 and the network element, and the controller 5 executes preemptive locking;
it is assumed here that the controller 5 applies for locking the candidate configuration database of the network element 2 later than the controller 4 but earlier than the controller 6.
Step 507: the candidate configuration database of the network element 2 is preemptively locked by the session 2, the network element 2 informs the controller 4 and the controller 6 that the candidate configuration database of the network element 2 is in a preemptively locked state by the session 2, and the priority of the session 2 which is subjected to the current preemptive locking is 2;
then, the controller 6 may also execute preemptive locking by determining the priority of the currently locked session, which is not described in detail herein.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.
Claims (12)
1. A scheduling method for an operation network metadata base is characterized by comprising the following steps:
acquiring the type of each configuration protocol session of an operation network metadata base and the target operation priority of each configuration protocol session;
determining the operation priority of each configuration protocol session according to a preset determination strategy according to the type of each configuration protocol session and the target operation priority of each configuration protocol session;
and when the configuration protocol session applies for operating the network element database, scheduling the operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session.
2. The method of claim 1, wherein before the obtaining the type of the configuration protocol session of the operation network metadata base and the target operation priority of each configuration protocol session, the method further comprises:
sending information that the network element database supports a preemptive scheduling mode based on operation priority to configuration applications of each configuration protocol session opposite terminal;
and instructing the configuration application of each opposite terminal of the configuration protocol session to send information containing the target operation priority of each configuration protocol session to the network element where the network element database is located.
3. The method according to claim 1 or 2, wherein the determining the operation priority of each configuration protocol session according to a preset determination policy comprises:
and determining the operation priority of each configuration protocol session according to the type of each configuration protocol session and/or according to the target operation priority of each configuration protocol session.
4. The method according to claim 1 or 2, wherein the scheduling the operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session comprises:
when the state of the network element database is idle, scheduling the operation of each configuration protocol session according to the application time point of each configuration protocol session in sequence; or
And when the state of the network element database is that exclusive operation of the configuration protocol session exists, scheduling the operation of each configuration protocol session according to the operation priority of the first configuration protocol session which is exclusively operated and the second configuration protocol session which applies for operation.
5. The method of claim 4, wherein scheduling the operation of each configuration protocol session according to the operation priority of the configuration protocol session that is exclusively operating and the configuration protocol session that applies for operation comprises:
when the operation priority of the first configuration protocol session is smaller than that of the second configuration protocol session, preemptively operating the network element database by the second configuration protocol session; otherwise, the original operation state is maintained.
6. The method of claim 5, further comprising:
when the operation priority of the first configuration protocol session is greater than or equal to the operation priority of the second configuration protocol session, the configuration application of the opposite end of the second configuration protocol session applies to the network element for obtaining the operation priority greater than the operation priority of the first configuration protocol session.
7. The scheduling device of the operation network metadata base is characterized by comprising an acquisition module, a determination module and a scheduling module; wherein,
the acquisition module is used for acquiring the type of each configuration protocol session of the operation network metadata base and the target operation priority of each configuration protocol session;
the determining module is used for determining the operation priority of each configuration protocol session according to a preset determining strategy according to the type of each configuration protocol session and the target operation priority of each configuration protocol session;
the scheduling module is used for scheduling the operation of each configuration protocol session according to the state of the network element database and the application time point or the operation priority of each configuration protocol session when the configuration protocol session applies for operating the network element database.
8. The apparatus of claim 7, further comprising a sending module configured to:
sending information that the network element database supports a preemptive scheduling mode based on operation priority to configuration applications of each configuration protocol session opposite terminal;
and instructing the configuration application of each opposite terminal of the configuration protocol session to send information containing the target operation priority of each configuration protocol session to the network element where the network element database is located.
9. The apparatus according to claim 7 or 8, wherein the determining module is specifically configured to:
and determining the operation priority of each configuration protocol session according to the type of each configuration protocol session and/or according to the target operation priority of each configuration protocol session.
10. The apparatus according to claim 7 or 8, wherein the scheduling module is specifically configured to:
when the state of the network element database is idle, scheduling the operation of each configuration protocol session according to the application time point of each configuration protocol session in sequence; or
And when the state of the network element database is that exclusive operation of the configuration protocol session exists, scheduling the operation of each configuration protocol session according to the operation priority of the first configuration protocol session which is exclusively operated and the second configuration protocol session which applies for operation.
11. The apparatus of claim 10, wherein the scheduling module is further configured to:
when the operation priority of the first configuration protocol session is smaller than that of the second configuration protocol session, preemptively operating the network element database by the second configuration protocol session;
otherwise, the original operation state is maintained.
12. The apparatus of claim 11, wherein the scheduling module is further configured to:
when the operation priority of the first configuration protocol session is greater than or equal to the operation priority of the second configuration protocol session, the configuration application of the opposite end of the second configuration protocol session applies to the network element for obtaining the operation priority greater than the operation priority of the first configuration protocol session.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710132639.9A CN108572957B (en) | 2017-03-07 | 2017-03-07 | Scheduling method and device for metadata base of operation network |
| PCT/CN2018/077528 WO2018161828A1 (en) | 2017-03-07 | 2018-02-28 | Scheduling method and device for operating network element database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710132639.9A CN108572957B (en) | 2017-03-07 | 2017-03-07 | Scheduling method and device for metadata base of operation network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108572957A true CN108572957A (en) | 2018-09-25 |
| CN108572957B CN108572957B (en) | 2022-04-01 |
Family
ID=63448041
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710132639.9A Active CN108572957B (en) | 2017-03-07 | 2017-03-07 | Scheduling method and device for metadata base of operation network |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN108572957B (en) |
| WO (1) | WO2018161828A1 (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060050683A1 (en) * | 2004-09-09 | 2006-03-09 | Nextel Communications, Inc. | Prioritization of service requests received at a session initiation protocol (SIP) server |
| CN1968195A (en) * | 2006-05-29 | 2007-05-23 | 华为技术有限公司 | Communication system scheduling method |
| CN103888351A (en) * | 2012-12-20 | 2014-06-25 | 国际商业机器公司 | Method and device used for managing multiple conversations in network based on multi-path routing |
| CN104079436A (en) * | 2014-07-14 | 2014-10-01 | 武汉大学 | Cross-device and cross-protocol EPON element management system |
| CN104883267A (en) * | 2014-02-28 | 2015-09-02 | 杭州华三通信技术有限公司 | Network configuration accessing method and device thereof |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101610173B (en) * | 2009-07-14 | 2012-09-05 | 中兴通讯股份有限公司 | Method and network management server for implementing data collocation on multi-network elements |
| CN103312667B (en) * | 2012-03-09 | 2016-09-14 | 华为技术有限公司 | A kind of methods, devices and systems of information updating |
| GB2541461B (en) * | 2015-08-21 | 2021-04-28 | Metaswitch Networks Ltd | Prioritising SIP messages |
-
2017
- 2017-03-07 CN CN201710132639.9A patent/CN108572957B/en active Active
-
2018
- 2018-02-28 WO PCT/CN2018/077528 patent/WO2018161828A1/en active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060050683A1 (en) * | 2004-09-09 | 2006-03-09 | Nextel Communications, Inc. | Prioritization of service requests received at a session initiation protocol (SIP) server |
| CN1968195A (en) * | 2006-05-29 | 2007-05-23 | 华为技术有限公司 | Communication system scheduling method |
| CN103888351A (en) * | 2012-12-20 | 2014-06-25 | 国际商业机器公司 | Method and device used for managing multiple conversations in network based on multi-path routing |
| CN104883267A (en) * | 2014-02-28 | 2015-09-02 | 杭州华三通信技术有限公司 | Network configuration accessing method and device thereof |
| CN104079436A (en) * | 2014-07-14 | 2014-10-01 | 武汉大学 | Cross-device and cross-protocol EPON element management system |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2018161828A1 (en) | 2018-09-13 |
| CN108572957B (en) | 2022-04-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2016131172A1 (en) | Method and device for updating network service descriptor | |
| US20200213937A1 (en) | Network Slice Instance Processing Method and Apparatus, and System | |
| US8127041B2 (en) | Datacasting system with automatic delivery of service mangement capability | |
| US11314545B2 (en) | Predicting transaction outcome based on artifacts in a transaction processing environment | |
| CN108713309A (en) | SD-WAN system, use method of SD-WAN system and related device | |
| JP6974587B2 (en) | Quality of service implementation to separate user planes | |
| CN110730478A (en) | Slice association method, device, end-to-end slice organizer and storage medium | |
| CN106851799B (en) | Method and device for sending heartbeat packet in long connection | |
| WO2022016969A1 (en) | Data processing method and device | |
| WO2021147880A1 (en) | Cell switching method, apparatus and device, and storage medium | |
| JP2017168074A (en) | Method and apparatus for controlling data transmission | |
| CN110768840A (en) | Control method, device, equipment and storage medium of communication equipment | |
| CN113556359A (en) | Communication protocol conversion method, device, system and gateway device | |
| WO2015096632A1 (en) | Data download method and device | |
| CN110875945B (en) | Method, apparatus and medium for task processing on a generic service entity | |
| CN108572957B (en) | Scheduling method and device for metadata base of operation network | |
| CN102833158A (en) | Network data sending method and device and network data system | |
| CN111427704B (en) | Remote monitoring method, device, equipment and storage medium for configuration instruction | |
| CN115865643B (en) | SDN network forwarding strategy determination method, SDN network forwarding strategy determination system, SDN network forwarding strategy controller and SDN network forwarding strategy determination device | |
| CN113553194B (en) | Hardware resource management method, device and storage medium | |
| CN108234092B (en) | Signaling configuration method, RRC entity and PDCP entity | |
| EP3616371B1 (en) | Methods and apparatus for scheduling of services in a traffic-engineering network | |
| CN113556793B (en) | non-GBR data transmission control method, system, SMF and user terminal | |
| CN112995311A (en) | Service providing method, device and storage medium | |
| CN110392017B (en) | Method and related device for processing RPC message |
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 |