CN109327321B - Network model service execution method and device, SDN controller and readable storage medium - Google Patents
Network model service execution method and device, SDN controller and readable storage medium Download PDFInfo
- Publication number
- CN109327321B CN109327321B CN201710645947.1A CN201710645947A CN109327321B CN 109327321 B CN109327321 B CN 109327321B CN 201710645947 A CN201710645947 A CN 201710645947A CN 109327321 B CN109327321 B CN 109327321B
- Authority
- CN
- China
- Prior art keywords
- service
- sub
- configuration file
- network model
- execution
- 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
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/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The embodiment of the invention provides a network model service execution method and device, an SDN controller and a readable storage medium, wherein a network model service is configured into a corresponding service configuration file in advance and stored in a service configuration file library, the obtained service configuration file comprises an identification mark of the network model service, and the service configuration file can be called and executed to realize the function of the corresponding network model service; in the service operation process, the identification mark of the current network model service to be executed is obtained, and then the service configuration file corresponding to the network model service to be executed can be found in the service configuration file library according to the obtained identification mark and then the operation is carried out. The scheme provided by the invention can be suitable for the requirements of different network model services, and can be compatible with different network model services, so that different network model services can be better integrated into various network structures.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a method and an apparatus for executing a Network model service, an SDN (Software Defined Network, Software Defined Network in Network architecture) controller, and a readable storage medium.
Background
Under the push of technologies such as cloud computing, distributed data storage and computing, network architectures are changing and gradually updated from the former decentralized mode to the centralized mode, and software defined networks are most dazzlingly represented in the centralized network architecture, and in the SDN centralized network architecture, various network model services need to be integrated into an SDN. In order to meet the requirements, a network model service execution method needs to be developed, and the method needs to adapt to the execution requirements of different network model services, so that various network model services can be operated under the action of a workflow engine.
Disclosure of Invention
The embodiment of the invention provides a network model service execution method and device, an SDN controller and a readable storage medium, and mainly solves the technical problem of providing a network model service execution scheme suitable for different network model services.
To solve the foregoing technical problem, an embodiment of the present invention provides a method for executing a network model service, including:
acquiring an identification mark of a network model service to be executed;
searching a service configuration file corresponding to the network model service to be executed in a service configuration file library according to the identification mark; the service configuration file library stores at least one service configuration file of the network model service, and the service configuration file comprises an identification mark of the network model service;
and executing the searched service configuration file.
An embodiment of the present invention further provides a network model service execution apparatus, including:
the task acquisition module is used for acquiring the identification mark of the network model service to be executed;
the task matching module is used for searching a service configuration file corresponding to the network model service to be executed in a service configuration file library according to the identification mark; the service configuration file library stores at least one service configuration file of the network model service, and the service configuration file comprises an identification mark of the network model service and sub-service configuration files of each sub-business forming the network model service;
and the task execution module is used for executing the sub-service configuration files in the searched service configuration files.
The embodiment of the invention also provides a software defined network controller, which comprises a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the steps of the network model service execution method as described above.
Embodiments of the present invention also provide a computer-readable storage medium, which stores one or more programs that are executable by one or more processors to implement the steps of the network model service execution method as described above.
The invention has the beneficial effects that:
according to the network model service execution method and device, the SDN controller and the readable storage medium provided by the embodiment of the invention, the network model service is configured into the corresponding service configuration file in advance and stored in the service configuration file library, the obtained service configuration file comprises the identification mark of the network model service, and the service configuration file can be called and executed to realize the function of the corresponding network model service; in the service operation process, the identification mark of the current network model service to be executed is obtained, and then the service configuration file corresponding to the network model service to be executed can be found in the service configuration file library according to the obtained identification mark and then the operation is carried out. The scheme provided by the invention can be suitable for the requirements of different network model services, can be compatible with the different network model services, and can enable the different network model services to be better integrated into various network structures (such as SDN).
Additional features and corresponding advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention.
Drawings
Fig. 1 is a schematic flow chart of a network model service execution method according to a first embodiment of the present invention;
fig. 2 is a schematic flow chart illustrating a process of executing a found service profile according to a first embodiment of the present invention;
fig. 3 is a schematic flow chart illustrating a process of determining a next sub-service profile to be executed according to a first embodiment of the present invention;
fig. 4 is a schematic flow chart of executing a sub-service configuration file according to a first embodiment of the present invention;
fig. 5 is a schematic diagram of serial execution of network model services according to a second embodiment of the present invention;
fig. 6 is a schematic diagram illustrating the execution of a network model service branch according to a second embodiment of the present invention;
fig. 7 is a schematic diagram illustrating merging and execution of network model services according to a second embodiment of the present invention;
fig. 8 is a schematic structural diagram of a network model service execution device according to a third embodiment of the present invention;
fig. 9 is a schematic structural diagram of a software-defined network controller according to a fourth embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, embodiments of the present invention are described in detail below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
The first embodiment is as follows:
in order to meet the execution requirements of various network model services, this embodiment provides a network model service execution method, where a network model service is configured in advance into a corresponding service configuration file, and the corresponding service configuration file is stored in a service configuration file library, and the service configuration file corresponding to the network model service to be executed is found from the service configuration file library according to an identification identifier of the current network model service to be executed during a service operation process, so as to perform operation. In order to facilitate a better understanding of the invention, the following exemplary description will be developed.
Referring to fig. 1, the method for executing a network model service in the present embodiment includes:
s101: and acquiring the identification mark of the network model service to be executed.
This step obtains the identification identifier of the network model service to be executed currently, and it should be understood that there may be only one or a plurality of network model services to be executed currently. The condition for triggering and acquiring the current network model service to be executed may be that a corresponding service execution instruction issued by the user is received, or may be that an instruction for triggering and executing the associated network model service is executed in the running process of other services or after the running is finished. In addition, it should be understood that the identification identifier of the network model service in this embodiment may be any identification information that can uniquely identify each network model service, and may be information that can be uniquely identified of the network model service itself, or may be identification information that can be uniquely identified additionally added thereto.
S102: and searching a service configuration file corresponding to the network model service to be executed in a service configuration file library according to the acquired identification mark.
As described above, in this embodiment, the service profile library stores at least one service profile of the network model service in advance, and the generation process of the service profile of each network model service can be flexibly determined according to the content, structure and other factors included in the specific service profile. In this embodiment, the service profile of each network model service includes an identification identifier of the network model service, so as to facilitate accurate identification of the service profile. It should be understood that, in this embodiment, the identification identifier included in the service profile may be an identification identifier directly identical to the corresponding network model service, or may be an identification identifier uniquely corresponding to the service profile but different in content, and at this time, the configuration profile corresponding to each network model service may be directly matched according to the corresponding relationship, or may be matched.
S103: and executing the searched service configuration file.
In this embodiment, the specific process of executing the service configuration file may be flexibly controlled according to the currently executed network model service.
As can be seen from the above process, in the embodiment, for various network model services, corresponding configuration files may be generated in advance for storage, and then when executing the network model service, only the corresponding network model service needs to be called for execution.
It should be understood that, in this embodiment, the specific structure of the service profile corresponding to the network model service may be flexibly set according to specific requirements. In an example of this embodiment, the service profile of a network model service further includes at least one service profile of a business that constitutes the network model service; that is, one network model service is decomposed into a plurality of relatively independent sub-services, and one sub-task corresponds to one sub-service configuration file. The structure is convenient for flexibly selecting the part to be executed when the network model service is executed, compared with the condition that the whole network model service can only be upgraded when the existing network model service is upgraded, the upgrading efficiency is low and the resource utilization rate is caused.
In this embodiment, the generated sub-service configuration file includes a sub-service index packet and a sub-service execution packet; the sub-service index packet comprises a sub-task index identifier and lower-level sub-service selection information, and the lower-level sub-service selection information of the sub-service index packet of at least one sub-service configuration file comprises a lower-level sub-service index identifier; the lower sub-service index identifier included in the lower sub-service selection information in this embodiment refers to a lower sub-service that is executed in association with the current sub-service after the current sub-service is executed, and the lower sub-service may be one or multiple sub-services, and for some sub-services, the lower sub-service may be empty. The lower level sub-service related to the sub-service in this embodiment may be a sub-task in the same network model service, or may be a sub-task in other network model services.
In one example, the sub-service profile includes a service execution package that mainly refers to information required for executing the sub-service, including, but not limited to, implementation interfaces and execution bodies, for example. In this embodiment, the sub-services may involve information transfer, so that there may be corresponding interfaces between the sub-services to implement information transfer, and in this embodiment, an interface common to each sub-service may be used for the interface between the sub-services, or an interface common to each sub-service may be used as much as possible.
In an example, a service profile of a network model service may be implemented by a multi-level tag, for example, defining a first-level tag as an identification corresponding to an identification of a network model service; defining a second-level label as a sub-service (i.e. a sub-service index packet), where the second-level label may have one or more labels, and the label may further define two attributes corresponding to the plurality of sub-services after the network model service is decomposed: the first is a name, that is, the name of the sub-service (i.e., sub-task index identifier) and a selector (i.e., lower-level sub-service selection information), that is, the next sub-service to be executed is selected according to the sub-service execution result; and defining a third-level tag as a service execution package action, corresponding to an implementation interface and an execution main body (namely an actual execution unit) of a sub-service.
Based on the structure of the configuration file in the above example, the service configuration file searched in S103 is shown in fig. 2, and includes:
s201: and extracting the sub-service configuration files to be executed currently from the matched service configuration files.
In this embodiment, when a service configuration file corresponding to a network model service is executed, a first sub-service configuration file included in the service configuration file may be directly executed, and the order of the sub-service configuration files included in the service configuration file in this embodiment may be determined well when the service configuration file is generated. Of course, the sub-service configuration file specified by the instruction in the service configuration file may also be executed according to a corresponding instruction, where the instruction may be an instruction issued by a user or a related instruction issued in the process of executing other network model services.
S202: and extracting a sub-service execution packet in the sub-service configuration file to execute the sub-service, sending an execution result to the sub-service configuration file corresponding to the subordinate sub-service index identifier when judging that the subordinate sub-service selection information comprises the subordinate sub-service index identifier, and taking the sub-service configuration file corresponding to the subordinate sub-service index identifier as a next sub-service configuration file to be executed.
In this embodiment, the determination of whether the lower-level sub-service selection information includes the lower-level sub-service index identifier may be performed after the sub-service is executed according to the sub-service execution packet in the sub-service configuration file, may also be performed in parallel with the sub-service before the sub-service is executed, may even be performed before the sub-service is executed according to needs, and may specifically be flexibly set according to a specific service execution scenario. For example, for a service execution scenario where all lower level subtasks have only one or none, it may be determined whether the lower level sub service selection information includes a lower level sub service index identifier after the sub service is executed according to the sub service execution packet in the sub service configuration file.
In this embodiment, when each sub-service profile of the network model service is executed, the execution may be performed through a sub-task execution queue, but it should be understood that the execution may also be performed without the sub-task execution queue. The subtask execution queue in this embodiment may be specifically implemented by a stack. When the sub-task execution queue is used, in this embodiment, after obtaining the current sub-service configuration file to be executed from the service configuration file, before extracting the sub-service execution packet in the sub-service configuration file, the method further includes: adding the sub-service index packet of the current sub-service configuration file to be executed into a sub-task execution queue; and then, after the sub-service index packet of the sub-service configuration file is taken out from the sub-task execution queue according to a preset sub-task taking-out rule (such as a first-in first-out rule), the sub-service execution packet is extracted from the current sub-service configuration file to be executed according to the sub-task index identifier in the sub-service index packet to execute the sub-service until the sub-task to be executed in the sub-task execution queue is empty.
In this embodiment, when the lower-level sub-service selection information of a certain sub-task configuration file includes at least two sub-service index identifiers, this case is called a case where there is a branch execution in the network model service, and a specific execution process is called a branch execution flow algorithm. At this time, after the subtask configuration file is executed to obtain the execution result, the result is sent to the sub service configuration file corresponding to the lower sub service index identifier, and the sub service configuration file corresponding to the lower sub service index identifier is used as the next sub service configuration file to be executed, as shown in fig. 3, including:
s301: and respectively issuing the obtained execution result to the sub-service configuration file corresponding to each sub-service index identifier.
For example, assuming that the lower-level sub-service selection information of the sub-service profile of the sub-service 1 includes two sub-service index identifiers, namely, sub-service 2 and sub-service 3, the execution result of the sub-service 1 is sent to the sub-service 2 and the sub-service 3 through the communication interface between the sub-services.
S302: and adding the sub-service index packets of the sub-service configuration file corresponding to each sub-service index identifier into the sub-task execution queue respectively.
In this step, when adding the sub-service index packets of the sub-service configuration file (hereinafter referred to as the sub-service configuration file of the lower-level sub-task) corresponding to each sub-service index identifier to the sub-task execution queue, the adding sequence may be added randomly, or according to the priority of each lower-level sub-task, and may be selected flexibly according to specific requirements.
After the sub service index packets of the sub service configuration file corresponding to each sub service index identifier are respectively added to the sub task execution queue through the process shown in fig. 3, executing the sub service configuration file corresponding to each sub service index identifier is shown in fig. 4, and includes:
s401: and taking out a sub-service index packet of a sub-service configuration file from the sub-task execution queue. Specifically, the sub-task execution queue can be fetched from the sub-task execution queue by a first-in first-out principle.
S402: and extracting a sub-service execution packet from the corresponding current sub-service configuration file to be executed according to the sub-task index identifier in the currently extracted sub-service index packet to execute the sub-service.
S403: before the sub-service is executed, extracting the lower-level sub-service selection information of the sub-service index packet to judge whether the lower-level sub-service index identifier is included, namely, the method is carried out in an asynchronous parallel mode, and if the lower-level sub-service index identifier is included, the step is switched to S404; otherwise, go to S405.
S404: and adding the sub-service configuration file corresponding to the lower-level sub-service index identifier as the next sub-service configuration file to be executed into the sub-task execution queue, and turning to S405.
S405: and taking out the sub-service index packet of the next sub-service configuration file from the sub-task execution queue.
In this embodiment, at least one sub-service configuration file further includes a merging processing identifier, where the merging processing identifier includes indication information of a sub-service to be merged; in this embodiment, the case that the currently executed sub-service configuration file includes the merge processing identifier is referred to as a merge execution case, and the corresponding execution process is a merge execution flow algorithm. When the merged execution flow algorithm judges that the subordinate sub-service selection information includes the subordinate sub-service index identifier to be executed, after extracting the sub-service execution packet in the sub-service configuration file to execute the sub-service and obtaining the execution result, the merged execution flow algorithm also includes the following steps that:
judging whether the sub-service configuration file comprises a merging processing identifier or not, if not, directly sending an execution result to the sub-service configuration file corresponding to the sub-service index identifier of the lower level; if so, acquiring an execution result of the subtask to be merged, which is indicated by the indication information of the merging processing identifier, as an execution result to be merged, merging the execution result and the execution result to be merged, and then sending the merged execution result and the execution result to the sub-service configuration file corresponding to the lower-level sub-service index identifier. It should be understood that the merging process of the execution results in this embodiment may be various merging processes, which are not described herein again.
The network model service execution method provided by the embodiment of the invention at least has the following advantages:
1. the method is suitable for various network model services, has good universality and compatibility, and is more beneficial to integration of various network model services into various network architectures.
2. The network model service is decomposed into at least one relatively independent service, and the sub-services can be called and upgraded in the calling process and the upgrading process by taking the sub-services as units, so that the method is more flexible, and the upgrading efficiency and the resource utilization rate are higher.
3. The services can be executed in an asynchronous and parallel mode, and the requirement of parallel execution of various services can be further met.
Example two:
on the basis of the first embodiment, the present embodiment is exemplified by a service profile with a specific structure and three cases of flow algorithms.
In this embodiment, the processing of the network model service includes the following three processes:
decomposition of network model services
Definition of network model services
Execution of network model services
The decomposition process of the network model service comprises the following steps:
each network model service is decomposed into sub-services with moderate granularity, the interfaces between the sub-services can adopt a universal interface, and the information between the sub-services is transmitted through messages. In order to decompose the network model services, it is necessary to master each network model service, to clearly understand each processing flow of each network model service, and then to refine, decompose, and combine all the processing flows.
The definition process of the network model service comprises the following steps:
all sub-services of each network model service are defined in a pre-formatted (e.g., XML-formatted) configuration file. In the document, a first-level tag is defined as a procedure (identification mark) and corresponds to a network model service; defining a second-level label as actioncell (i.e. sub-service index packet), where there are multiple second-level labels, and the second-level label defines two attributes in the label corresponding to multiple sub-services after the network model service is decomposed: (i.e. subtask index identifier) and a selector (i.e. lower level sub-service selection information), i.e. selecting the next sub-service to be executed according to the sub-service execution result; and defining a third-level tag as an action (service execution packet) corresponding to an implementation interface and an actual execution unit of a sub-service. Specifically shown below:
the execution process of the network model service comprises the following steps:
when a certain network model service is executed, a first sub-service configuration file in a service configuration file corresponding to the network model service is searched in a configuration file library, after the first sub-service configuration file is executed, one or more next executed sub-service configuration files are determined according to an execution result and an execution rule defined in the sub-service configuration file, then the next one or more sub-service configuration files are executed, and the like are repeated until all the sub-service configuration files are executed. These execution flows are driven by the workflow engine provided.
The terminology commonly used in workflow engines:
procedure: the identification mark of a network model service is represented, and the embodiment is characterized by a name;
ActionCell: representing a sub-service in a network model service, which comprises a sub-task index identification;
and (4) Action: representing the execution of a sub-service;
a Selector: the selection of the sub-service is expressed, the sub-service of the network model service can be selected, and the sub-services of other network model services can also be selected;
ActionCellStack: representing a stack of data structures holding the sub-services, i.e. a sub-task execution queue.
As analyzed above, depending on the characteristics of the network model service, the workflow engine can be designed in three ways:
the method comprises the steps of network model service serial execution, network model service branch execution and network model service merging execution.
The process of the network model service serial execution algorithm is as follows:
when a network model service needs to be executed, a first sub-service ActionCell of a service configuration file of the network model service is searched in a configuration file library according to the name of the network model service;
taking out an Action from the first sub-service ActionCell for execution, taking out a Selector from the sub-service ActionCell after execution, checking the next sub-service of the first sub-service ActionCell in the Selector, and sending the information of the first sub-service ActionCell to the next sub-service through a message;
and taking out the Action from the next sub-service ActionCell for execution, taking out the Selector from the sub-service ActionCell after the execution is finished, checking the next sub-service of the sub-service ActionCell in the Selector, sending the information of the sub-service ActionCell to the next sub-service through the message, and repeating the steps until the next sub-service cannot be found in the Selector, thus finishing the execution of the network model service flow. For example, referring to fig. 5, fig. 5 is a serial execution example of a network model service, and a certain network model service is divided into 7 steps, which includes:
and executing the sub-service 1 in the network model service, and selecting the next sub-service 2 in the serial flow according to the selector of the sub-service 1 after the execution.
And executing the sub-service 2 in the network model service, and selecting the next sub-service 3 in the serial flow according to the selector of the sub-service 2 after the execution.
And executing the sub-service 3 in the network model service, and selecting the next sub-service 4 in the serial flow according to the selector of the sub-service 3 after the execution.
And executing the sub-service 4 in the network model service, and selecting the next sub-service 5 in the serial flow according to the selector of the sub-service 4 after the execution.
And executing the sub-service 5 in the network model service, and selecting the next sub-service 6 in the serial flow according to the selector of the sub-service 5 after the execution.
And executing the sub-service 6 in the network model service, and selecting the next sub-service 7 in the serial flow according to the selector of the sub-service 6 after the execution.
And after the sub-service 7 is executed in the network model service, the selector of the sub-service 7 can know that the whole network model service is executed.
The sequence of the network model service execution is only one:
1- - >2- - >3- - >4- - >5- - >6- - > 7. It can be seen that the execution process may not employ a stack, but may be executed by using a stack.
The algorithm of the branch execution flow in the network model service comprises the following steps:
when a network model service needs to be executed, the first sub-service ActionCell of the network model service is found in a configuration file according to the name of the network model service, and then the sub-service ActionCell is pressed (i.e. added) into a stack ActionCellStack.
Judging whether the stack ActionCellStack has a sub-service ActionCell, if not, ending the execution of the network model service; if the sub-service ActionCell exists, popping up (namely taking out) the sub-service ActionCell at the top of the stack;
and after popping the sub-service ActionCell from the stack top, taking out the Action from the sub-service ActionCell for execution, taking out a Selector from the sub-service ActionCell after execution, checking how many sub-services which need to be executed in parallel behind the sub-service are in the Selector, and sending information in the sub-service ActionCell to one or more sub-services which need to be executed in parallel behind by messages.
If the Selector checks that only one sub-service is behind the sub-service ActionCell, the following sub-service ActionCell is pressed into a stack ActionCell Stack, then whether one sub-service ActionCell exists in the stack ActionCell Stack or not is judged, at this moment, one sub-service is definitely existed, then the sub-service ActionCell at the top of the stack is popped up, the Action is taken out from the popped sub-service ActionCell for execution, the Selector is taken out from the sub-service ActionCell after the execution is finished, then the Selector checks how many sub-services which need to be executed in parallel behind the sub-service are found, and the information in the sub-service ActionCell is sent to one or a plurality of sub-services which need to be executed in parallel behind through messages. This step is similar to the serial flow except that there are more sub-service ActionCell operations pushed onto and popped from the stack ActionCellStack.
If a plurality of sub-services behind the sub-service ActionCell are found in the Selector, the plurality of sub-service ActionCells behind the sub-service ActionCell are all pressed into a stack ActionCell State, then whether the sub-service ActionCell exists in the stack ActionCell Stack or not is judged, at the moment, the plurality of sub-service ActionCells exist in the stack, the sub-service ActionCell at the top of the stack is popped up and then is directly used in an asynchronous parallel mode (such as, but not limited to, the CompleteFuture technology of Java 8) to asynchronously and concurrently execute the ActionCell and the Selector in the sub-service ActionCell, the sub-service ActionCell at the top of the stack is not judged to have the sub-service ActionCell after the sub-service ActionCell at the top of the stack is popped, if any, the sub-service ActionCells at the bottom are pressed into the stack, and the sub-service and the sub-services and the asynchronous service and the Selector can be executed asynchronously and concurrently executed in the same level.
When the execution of the Action in the sub-service ActionCell of a certain branch on the same level is finished, one or more sub-service ActionCells which need to be executed behind the sub-service ActionCell are searched in a Selector in the sub-service ActionCell immediately, all the sub-service ActionCells are pressed into a stack ActionCellStack, then whether the sub-service ActionCell exists in the stack ActionCellStack or not is judged, if the sub-service ActionCell does not exist, the branch flow is finished, if the sub-service ActionCell exists, the sub-service ActionCell at the top of the stack is popped up, the Action and the Selector are extracted, the execution is carried out in a concurrent asynchronous mode, the execution of the sub-service ActionCells of other branches is not required to be finished, and the analogy is carried out in sequence, so that the sub-service ActionCells on a certain branch and the sub-service ActionCells on other branches can also be executed in a concurrent asynchronous mode.
When there are no more ActionCells in the stack ActionCellStack, all branch flows of the network model service are executed.
For example, as shown in fig. 6, fig. 6 is a network model service branch execution example, and a certain network model service is divided into 9 steps, which includes the following steps:
and executing the sub-service 1 in the network model service, and selecting the next sub-service 2 according to the selector of the sub-service 1 after the execution.
Executing the sub-service 2 in the network model service, selecting 3 sub-services to be executed according to a selector of the sub-service 2 after the execution, wherein the 3 sub-services are respectively the sub-service 3, the sub-service 4 and the sub-service 5, pressing the 3 sub-services (3, 4 and 5) into a sub-service stack according to an algorithm, then taking out the sub-services from the stack top one by one and respectively executing, wherein the 3 sub-services are executed according to concurrence without waiting for each other, and any one of the 3 sub-services may be finished first according to the time length of a sub-service processing flow.
After the execution of the sub-service 5 in the network model service, the selector executing the sub-service 5 can know that the execution of the branch of the network model service is completed.
And executing the sub-service 4 in the network model service, and selecting the next sub-service 7 according to the selector of the sub-service 4 after the execution.
And executing the sub-service 3 in the network model service, and selecting the next sub-service 6 according to the selector of the sub-service 3 after the execution.
The execution of the sub-service 7 in the network model service, after the execution, 2 sub-services which need to be executed are selected according to a selector of the sub-service 7, wherein the sub-services are respectively the sub-service 8 and the sub-service 9, the 2 sub-services (8 and 9) are all pressed into a sub-service stack according to an algorithm, then the sub-services are taken out from the stack top one by one and are respectively executed, the 2 sub-services are executed according to concurrence, the sub-services do not need to wait for each other, and according to the time length of a sub-service processing flow, the 2 sub-services can be finished first.
After the execution of the sub-service 6 in the network model service, the selector that executes the sub-service 6 can know that the branch of the network model service is executed.
After the execution of the sub-service 8 in the network model service, the selector executing the sub-service 8 can know that the execution of the branch of the network model service is completed.
After the execution of the sub-service 9 in the network model service, the selector that executes the sub-service 9 can know that the execution of the branch of the network model service is completed.
The order in which the network model service branches are executed may be various, such as, but not limited to, the following:
1-->2-->5-->4-->3-->7-->9-->8-->6
1-->2-->5-->4-->3-->7-->6-->9-->8
1-->2-->5-->4-->3-->7-->9-->6-->8
1-->2-->5-->4-->3-->6-->7-->9-->8
the method for combining and executing the flow algorithm in the network model service comprises the following steps:
the prior branches are definitely merged, so all the steps of merging execution flows in the network model service are similar to the branch flows, and the only difference is as follows:
when a network model service executes to a sub-service (such as ActionCell1) on a branch flow, judging that the sub-service needs to be merged with a certain sub-service (such as Actioncell8) on other branch flows according to the characteristics of the sub-service, at this time, it is observed from the Selector in the sub-service ActionCell1 that the sub-service that needs to be executed later cannot be executed immediately, but after the Action cell8 extracts the Action and finishes executing, the execution results of the two actions are merged, then extracts the Selector in ActionCell1 and ActionCell8 (both should be the same, should be merged), the Selector checks how many of the sub-services after it is needed to execute the sub-service ActionCell, and the merged result is transmitted to the following sub-services ActionCells through messages, and all the sub-services ActionCells are pressed into a stack ActionCellStack, judging whether the stack ActionCellStack has a sub-service ActionCell, if not, ending the network model service process; if yes, popping up the sub-service ActionCell, and then continuing to execute according to the steps of the branch flow and the merging flow until no sub-service ActionCell exists in the stack ActionCellStack, and ending the network model service flow.
As shown in fig. 7, fig. 7 is a case of merging and executing network model services in this embodiment, and divides a certain network model service into 11 steps, which includes the following steps:
and executing the sub-service 1 in the network model service, and selecting the next sub-service 2 according to the selector of the sub-service 1 after the execution.
Executing the sub-service 2 in the network model service, selecting 4 sub-services to be executed according to a selector of the sub-service 2 after the execution, wherein the 4 sub-services are respectively the sub-service 3, the sub-service 4, the sub-service 5 and the sub-service 6, pressing the 4 sub-services (3, 4, 5 and 6) into a sub-service stack according to an algorithm, then taking the sub-services out from the stack top one by one and respectively executing, and the 4 sub-services are executed according to concurrence without waiting for each other, wherein according to the time length of a sub-service processing flow, any one of the 4 sub-services can be finished first.
After the execution of the sub-service 6 in the network model service, the selector that executes the sub-service 6 can know that the branch of the network model service is executed.
And executing the sub-service 5 in the network model service, and selecting the next sub-service 9 according to the selector of the sub-service 5 after the execution.
And executing the sub-service 4 in the network model service, and selecting the next sub-service 8 according to the selector of the sub-service 4 after the execution.
And executing the sub-service 3 in the network model service, and selecting the next sub-service 7 according to the selector of the sub-service 3 after the execution.
And executing the sub-service 3 in the network model service, and selecting the next sub-service 7 according to the selector of the sub-service 3 after the execution.
The execution of the sub-service 9 in the network model service is completed by selecting the next sub-service 11 according to the selector of the sub-service 9, but the sub-service 11 cannot be executed at this time because the sub-service 9 needs to be merged with the sub-service 10 to execute the sub-service 11.
The execution of the sub-service 8 in the network model service is completed by selecting the next sub-service 10 according to the selector of the sub-service 8, but the sub-service 10 cannot be executed at this time because the sub-service 8 needs to be merged with the sub-service 7 to execute the sub-service 10.
The execution of the sub-service 7 in the network model service is finished, the next sub-service 10 is selected according to the selector of the sub-service 7, and the sub-service 10 can be executed only by being combined with the sub-service 8, and at this time, the sub-service 8 is already executed, so that the sub-service 10 can be executed.
The execution of the sub-service 10 in the network model service is finished, the next sub-service 11 is selected according to the selector of the sub-service 10, and the sub-service 11 needs to be merged with the sub-service 9 to be executed, and at this time, the sub-service 9 is already executed, so that the sub-service 11 can be executed.
After the execution of the sub-service 11 in the network model service, the selector executing the sub-service 11 can know that the execution of the branch of the network model service is completed.
The order in which the network model service merge is performed may be various, including but not limited to the following:
1-->2-->6-->5-->4-->3-->9-->8-->7-->10-->11
1-->2-->6-->5-->9-->4-->8-->3-->7-->10-->11
1-->2-->6-->5-->9-->4-->3-->8-->7-->10-->11
1-->2-->6-->5-->4-->8-->3-->7-->9-->10-->11
the network model service execution method provided by this embodiment decomposes the network model service at first, so that a certain sub-service of the network model service can be updated and updated independently, each branch flow of a certain network model service can be executed in a multi-thread concurrent manner, and a certain sub-service of a certain network model service can jump to a certain sub-service of other network model services to be executed after the execution of the certain sub-service is completed. And the network model service execution is more efficient and flexible.
Example three:
the present embodiment provides a network model service execution apparatus, as shown in fig. 8, including:
a task obtaining module 801, configured to obtain an identifier of a network model service to be executed.
The task obtaining module 801 obtains the identifier of the network model service to be executed currently, and it should be understood that there may be only one or a plurality of network model services to be executed currently.
And the task matching module 802 is configured to search a service configuration file corresponding to the network model service to be executed in a service configuration file library according to the identification mark.
In this embodiment, the service profile library stores at least one service profile of the network model service in advance, and a generation process of the service profile of each network model service can be flexibly determined according to factors such as content and structure included in a specific service profile. In this embodiment, the service profile of each network model service includes an identification identifier of the network model service, so as to facilitate accurate identification of the service profile. It should be understood that, in this embodiment, the identification identifier included in the service profile may be an identification identifier directly identical to the corresponding network model service, or may be an identification identifier uniquely corresponding to the service profile but different in content, and at this time, the configuration profile corresponding to each network model service may be directly matched according to the corresponding relationship, or may be matched.
And the task execution module 803 is configured to execute the sub-service configuration file in the searched service configuration file.
It should be understood that the functions of the above modules in this embodiment may be implemented by a processor.
Through the above process, the network model service execution device of this embodiment may generate and store corresponding configuration files for various network model services in advance, and then only needs to call the corresponding network model service to execute the network model service when executing the network model service.
It should be understood that, in this embodiment, the specific structure of the service profile corresponding to the network model service may be flexibly set according to specific requirements. In an example of this embodiment, the service profile of a network model service further includes at least one service profile of a business that constitutes the network model service; that is, one network model service is decomposed into a plurality of relatively independent sub-services, and one sub-task corresponds to one sub-service configuration file. The structure is convenient for flexibly selecting the part to be executed when the network model service is executed, and can only correspondingly upgrade the sub-service to be upgraded or the related sub-service when the service is required to be upgraded without upgrading the whole network model service, thereby improving the flexibility of the upgrading process and the upgrading efficiency and the resource utilization rate.
In this embodiment, the generated sub-service configuration file includes a sub-service index packet and a sub-service execution packet; the sub-service index packet comprises a sub-task index identifier and lower-level sub-service selection information, and the lower-level sub-service selection information of the sub-service index packet of at least one sub-service configuration file comprises a lower-level sub-service index identifier; the lower sub-service index identifier included in the lower sub-service selection information in this embodiment refers to a lower sub-service that is executed in association with the current sub-service after the current sub-service is executed, and the lower sub-service may be one or multiple sub-services, and for some sub-services, the lower sub-service may be empty. The lower level sub-service related to the sub-service in this embodiment may be a sub-task in the same network model service, or may be a sub-task in other network model services.
In one example, the sub-service profile includes a service execution package that mainly refers to information required for executing the sub-service, including, but not limited to, implementation interfaces and execution bodies, for example.
The task execution module 803 executes the found service configuration file, including:
the task execution module 803 extracts a sub-service profile to be currently executed from the matched service profiles.
The task execution module 803 extracts a sub-service execution packet in the sub-service configuration file to execute the sub-service, and when it is determined that the lower-level sub-service selection information includes a lower-level sub-service index identifier, sends an execution result to the sub-service configuration file corresponding to the lower-level sub-service index identifier, and takes the sub-service configuration file corresponding to the lower-level sub-service index identifier as a sub-service configuration file to be executed next.
In this embodiment, the task execution module 803 determines whether the lower level sub-service selection information includes a lower level sub-service index identifier, which may be performed after the sub-service is executed according to the sub-service execution packet in the sub-service configuration file, or may be performed in parallel with the sub-service before the sub-service is executed, or may be performed before the sub-service is executed according to a requirement, and specifically, may be flexibly set according to a specific service execution scenario.
In this embodiment, when the task execution module 803 executes each sub-service profile of the network model service, it may execute through a sub-task execution queue, but it should be understood that it may not execute through the sub-task execution queue. The subtask execution queue in this embodiment may be specifically implemented by a stack. When the task is executed through the subtask execution queue, the task execution module 803 acquires the current sub-service configuration file to be executed from the service configuration file, and adds the sub-service index packet of the current sub-service configuration file to be executed to the subtask execution queue before extracting the sub-service execution packet in the sub-service configuration file; and then, after the sub-service index packet of the sub-service configuration file is taken out from the sub-task execution queue according to a preset sub-task taking-out rule (such as a first-in first-out rule), the sub-service execution packet is extracted from the current sub-service configuration file to be executed according to the sub-task index identifier in the sub-service index packet to execute the sub-service until the sub-task to be executed in the sub-task execution queue is empty.
In this embodiment, when the lower-level sub-service selection information of a certain sub-task configuration file includes at least two sub-service index identifiers, this case is called a case where there is a branch execution in the network model service, and a specific execution process is called a branch execution flow algorithm. At this time, the task execution module 803 sends the obtained execution result to the sub-service configuration file corresponding to each sub-service index identifier, and adds the sub-service index packet of the sub-service configuration file corresponding to each sub-service index identifier to the sub-task execution queue.
When the task execution module 803 adds the sub-service index packets of the sub-service configuration file (hereinafter referred to as the sub-service configuration file of the lower-level sub-task) corresponding to each sub-service index identifier to the sub-task execution queue, the adding sequence may be added randomly, or according to the priority of each lower-level sub-task, and may be selected flexibly according to specific requirements.
At this time, the task execution module 803 executes the sub-service configuration file corresponding to each sub-service index identifier, including:
the task execution module 803 fetches a sub-service index packet of a sub-service profile from the sub-task execution queue. Specifically, the sub-task execution queue can be fetched from the sub-task execution queue by a first-in first-out principle.
The task execution module 803 extracts a sub-service execution packet from the corresponding current sub-service configuration file to be executed according to the sub-task index identifier in the currently extracted sub-service index packet to execute the sub-service.
Before the sub-service is executed, the task execution module 803 extracts the sub-service selection information of the sub-service index packet to determine whether the sub-service index packet includes a sub-service index identifier, that is, the sub-service selection information is processed in an asynchronous parallel manner, for example, the sub-service configuration file corresponding to the sub-service index identifier is added to a sub-task execution queue as a sub-service configuration file to be executed next, and the sub-service index packet of the next sub-service configuration file is taken out from the sub-task execution queue; and if not, directly taking out the sub-service index packet of the next sub-service configuration file from the sub-task execution queue.
In this embodiment, at least one sub-service configuration file further includes a merging processing identifier, where the merging processing identifier includes indication information of a sub-service to be merged; in this embodiment, the case that the currently executed sub-service configuration file includes the merge processing identifier is referred to as a merge execution case, and the corresponding execution process is a merge execution flow algorithm. When judging that the lower-level sub-service selection information includes a lower-level sub-service index identifier to be executed, the task execution module 803 extracts a sub-service execution packet in the sub-service configuration file to execute the sub-service to obtain an execution result, and judges whether the sub-service configuration file includes a merging processing identifier or not before sending the execution result to the sub-service configuration file corresponding to the lower-level sub-service index identifier, and if not, directly sends the execution result to the sub-service configuration file corresponding to the lower-level sub-service index identifier; if so, acquiring an execution result of the subtask to be merged, which is indicated by the indication information of the merging processing identifier, as an execution result to be merged, merging the execution result and the execution result to be merged, and then sending the merged execution result and the execution result to the sub-service configuration file corresponding to the lower-level sub-service index identifier. It should be understood that the merging process of the execution results in this embodiment may be various merging processes, which are not described herein again.
The network model service execution device provided by the embodiment of the invention is suitable for various different network model services, has good universality and compatibility, and is more beneficial to integrating various network model services into various network architectures. The method decomposes the network model service into at least one relatively independent service, and can call and upgrade sub-services in the calling process and the upgrading process as a unit, so that the method is more flexible, and the upgrading efficiency and the resource utilization rate are higher. And it can execute each business in asynchronous and parallel mode, and can further meet the requirement of parallel execution of various businesses.
Example four:
the present embodiments also provide a Software Defined Network (SDN) controller, which may be implemented by various servers. Referring to fig. 9, the terminal in the present embodiment includes a processor 901, a memory 902, and a communication bus 903;
the communication bus 903 is used for realizing connection communication between the processor 901 and the memory 902;
the processor 901 is configured to execute one or more programs stored in the memory 902 to implement at least the steps of the network model service execution method shown in the first and second embodiments.
The present embodiment also provides a computer-readable storage medium storing one or more programs, which are executable by one or more processors to implement at least the steps of the network model service execution method as described in the first and second embodiments. It should be understood that the computer-readable storage medium in the present embodiment is applicable to various terminals or servers.
The computer-readable storage medium and the software defined network controller provided by the embodiment can decompose the network model service, so that a certain sub-service of the network model service can be updated and updated independently, each branch flow of the certain network model service can be executed in a multi-thread concurrent manner, and a certain sub-service of the certain network model service can be skipped to a certain sub-service of other network model services for execution after the execution of the certain sub-service is finished. And the network model service execution is more efficient and flexible.
It will be apparent to those skilled in the art that the modules or steps of the embodiments of the invention described above may be implemented in a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented in program code executable by a computing device, such that they may be stored on a computer storage medium (ROM/RAM, magnetic disk, optical disk) and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The foregoing is a more detailed description of embodiments of the present invention, and the present invention is not to be considered limited to such descriptions. For those skilled in the art to which the invention pertains, several simple deductions or substitutions can be made without departing from the spirit of the invention, and all shall be considered as belonging to the protection scope of the invention.
Claims (9)
1. A network model service execution method, comprising:
acquiring an identification mark of a network model service to be executed;
searching a service configuration file corresponding to the network model service to be executed in a service configuration file library according to the identification mark; the service configuration file library stores at least one service configuration file of the network model service, and the service configuration file comprises: the identification mark of the network model service, at least one sub-service configuration file forming the network model service; the sub-service configuration file comprises a sub-service index packet and a sub-service execution packet; the sub-service index packet comprises a sub-service index identifier and lower-level sub-service selection information, and the lower-level sub-service selection information of the sub-service index packet of at least one sub-service configuration file comprises a lower-level sub-service index identifier; the executing the searched service configuration file comprises:
extracting a sub-service configuration file to be executed currently from the service configuration file;
extracting a sub-service execution packet in the sub-service configuration file to execute the sub-service, and when judging that the subordinate sub-service selection information comprises a subordinate sub-service index identifier, sending an execution result to the sub-service configuration file corresponding to the subordinate sub-service index identifier, and taking the sub-service configuration file corresponding to the subordinate sub-service index identifier as a sub-service configuration file to be executed next;
and executing the searched service configuration file.
2. The method for executing network model service according to claim 1, wherein after obtaining the sub-service configuration file to be executed currently from the service configuration file, before extracting the sub-service execution package in the sub-service configuration file, the method further comprises:
adding the sub-service index packet of the current sub-service configuration file to be executed into a sub-task execution queue;
and after the sub-service index packet of the sub-service configuration file is taken out from the sub-task execution queue according to a preset sub-task taking-out rule, extracting a sub-service execution packet from the current sub-service configuration file to be executed according to the sub-task index identifier in the sub-service index packet so as to execute the sub-service.
3. The method for performing network model services according to claim 2, wherein when the lower sub-service selection information includes at least two sub-service index identifiers, the step of sending the execution result to the sub-service profile corresponding to the lower sub-service index identifier, and using the sub-service profile corresponding to the lower sub-service index identifier as the next sub-service profile to be executed includes:
respectively issuing the execution result to the sub-service configuration file corresponding to each sub-service index mark;
and adding the sub-service index packets of the sub-service configuration files corresponding to the sub-service index identifications into the sub-task execution queue respectively.
4. The method for executing network model service according to claim 3, wherein the step of executing the sub-service configuration file corresponding to each sub-service index identifier after adding the sub-service index packet of the sub-service configuration file corresponding to each sub-service index identifier to the sub-task execution queue comprises:
taking out a sub-service index packet of a sub-service configuration file from the sub-task execution queue;
and after extracting a sub-service execution packet from the corresponding current sub-service configuration file to be executed according to the sub-task index identifier in the currently extracted sub-service index packet, before the sub-service is executed, extracting subordinate sub-service selection information of the sub-service index packet to judge whether the subordinate sub-service index identifier is included, if so, taking the sub-service configuration file corresponding to the subordinate sub-service index identifier as the next sub-service configuration file to be executed, and then taking the sub-service index packet of the next sub-service configuration file from the sub-task execution queue, and if not, directly taking the sub-service index packet of the next sub-service configuration file from the sub-task execution queue.
5. The network model service execution method of any of claims 2-4, wherein at least one of the sub-service profiles further comprises a merging process identifier, the merging process identifier comprising indication information of sub-services to be merged; when it is determined that the lower level sub service selection information includes a lower level sub service index identifier to be executed, after extracting a sub service execution packet in the sub service configuration file to execute a sub service and obtaining an execution result, sending the execution result to a front side of a sub service configuration file corresponding to the lower level sub service index identifier, the method further includes:
judging whether the sub-service configuration file comprises a merging processing identifier or not, if not, directly sending the execution result to the sub-service configuration file corresponding to the subordinate sub-service index identifier; if so, acquiring an execution result of the subtask to be merged, indicated by the indication information of the merging processing identifier, as an execution result to be merged, merging the execution result and the execution result to be merged, and then sending the merged execution result and the execution result to the sub-service configuration file corresponding to the lower-level sub-service index identifier.
6. The network model service execution method of any of claims 2-4, wherein the sub-service execution package comprises a sub-service implementation interface and a sub-service execution unit.
7. A network model service execution apparatus, comprising:
the task acquisition module is used for acquiring the identification mark of the network model service to be executed;
the task matching module is used for searching a service configuration file corresponding to the network model service to be executed in a service configuration file library according to the identification mark; the service configuration file library stores at least one service configuration file of the network model service, and the service configuration file comprises an identification mark of the network model service and a sub-service configuration file of each sub-service forming the network model service; the sub-service configuration file comprises a sub-service index packet and a sub-service execution packet; the sub-service index packet comprises a sub-service index identifier and lower-level sub-service selection information, and the lower-level sub-service selection information of the sub-service index packet of at least one sub-service configuration file comprises a lower-level sub-service index identifier; the executing the searched service configuration file comprises:
extracting a sub-service configuration file to be executed currently from the service configuration file;
extracting a sub-service execution packet in the sub-service configuration file to execute the sub-service, and when judging that the subordinate sub-service selection information comprises a subordinate sub-service index identifier, sending an execution result to the sub-service configuration file corresponding to the subordinate sub-service index identifier, and taking the sub-service configuration file corresponding to the subordinate sub-service index identifier as a sub-service configuration file to be executed next;
and the task execution module is used for executing the sub-service configuration files in the searched service configuration files.
8. A software defined network controller comprises a processor, a memory and a communication bus;
the communication bus is used for realizing connection communication between the processor and the memory;
the processor is configured to execute one or more programs stored in the memory to implement the steps of the network model service execution method of any of claims 1 to 6.
9. A computer readable storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the steps of the network model service execution method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710645947.1A CN109327321B (en) | 2017-08-01 | 2017-08-01 | Network model service execution method and device, SDN controller and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710645947.1A CN109327321B (en) | 2017-08-01 | 2017-08-01 | Network model service execution method and device, SDN controller and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109327321A CN109327321A (en) | 2019-02-12 |
| CN109327321B true CN109327321B (en) | 2021-10-15 |
Family
ID=65245085
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710645947.1A Active CN109327321B (en) | 2017-08-01 | 2017-08-01 | Network model service execution method and device, SDN controller and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109327321B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110022360A (en) * | 2019-03-27 | 2019-07-16 | 宁波大学 | A kind of industrial Internet of things system based on software defined network framework |
| CN110457490B (en) * | 2019-08-15 | 2021-06-18 | 桂林电子科技大学 | Semantic workflow index construction and retrieval method based on domain ontology |
| CN113052496A (en) * | 2021-04-23 | 2021-06-29 | 深圳壹账通智能科技有限公司 | Method and device for generating business processing flow, electronic equipment and medium |
| CN114461309A (en) * | 2022-01-27 | 2022-05-10 | 联信弘方(北京)科技股份有限公司 | Automatic instruction arranging and issuing method |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105516099A (en) * | 2015-11-30 | 2016-04-20 | 北京奇艺世纪科技有限公司 | Business side access method and device, and business side access rule configuration method and device |
| CN105988996A (en) * | 2015-01-27 | 2016-10-05 | 腾讯科技（深圳）有限公司 | Index file generation method and device |
| CN106169979A (en) * | 2015-05-19 | 2016-11-30 | 阿里巴巴集团控股有限公司 | A kind of method for processing business and equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20120035030A (en) * | 2010-10-04 | 2012-04-13 | 한국전자통신연구원 | System and method for providing service search |
-
2017
- 2017-08-01 CN CN201710645947.1A patent/CN109327321B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105988996A (en) * | 2015-01-27 | 2016-10-05 | 腾讯科技（深圳）有限公司 | Index file generation method and device |
| CN106169979A (en) * | 2015-05-19 | 2016-11-30 | 阿里巴巴集团控股有限公司 | A kind of method for processing business and equipment |
| CN105516099A (en) * | 2015-11-30 | 2016-04-20 | 北京奇艺世纪科技有限公司 | Business side access method and device, and business side access rule configuration method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109327321A (en) | 2019-02-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109327321B (en) | Network model service execution method and device, SDN controller and readable storage medium | |
| CN103197968B (en) | A kind of thread pool disposal route and system merging synchronous asynchronous feature | |
| CN113243005A (en) | Performance-based hardware emulation in on-demand network code execution systems | |
| CN108023908B (en) | Data updating method, device and system | |
| US20170329643A1 (en) | Distributed node intra-group task scheduling method and system | |
| CN110958281B (en) | Data transmission method and communication device based on Internet of things | |
| CN104462370A (en) | Distributed task scheduling system and method | |
| CN110569252B (en) | Data processing system and method | |
| CN110825535A (en) | Job scheduling method and system | |
| EP2933726B1 (en) | Apparatus, system and method for application log data processing | |
| CN112929210B (en) | Method and system for gateway routing application plug-in built on WebFlux framework and application of gateway routing application plug-in | |
| CN102801737A (en) | Asynchronous network communication method and device | |
| CN110636124A (en) | VPP cluster management method and device, electronic equipment and storage medium | |
| CN111858083A (en) | Remote service calling method and device, electronic equipment and storage medium | |
| CN115118784A (en) | Computing resource scheduling method, device and system | |
| CN113986534A (en) | Task scheduling method and device, computer equipment and computer readable storage medium | |
| CN112104679A (en) | Method, apparatus, device and medium for processing hypertext transfer protocol request | |
| CN115665231A (en) | Service creation method, device and computer-readable storage medium | |
| CN111274017B (en) | Resource processing method and device, electronic equipment and storage medium | |
| CN101320443A (en) | Electronic work order processing method and device | |
| CN114301980A (en) | Method, device and system for scheduling container cluster and computer readable medium | |
| CN114020453A (en) | Service bus message processing method, service bus system, electronic device, and medium | |
| CN111309467A (en) | Task distribution method and device, electronic equipment and storage medium | |
| CN111866159A (en) | Method, system, device and storage medium for calling artificial intelligence service | |
| CN113254143A (en) | Virtual network function network element arranging and scheduling method, device and system |
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 |