CN110896407B - NFVO component configuration management, request forwarding method and request processing device - Google Patents

NFVO component configuration management, request forwarding method and request processing device Download PDF

Info

Publication number
CN110896407B
CN110896407B CN201811069365.4A CN201811069365A CN110896407B CN 110896407 B CN110896407 B CN 110896407B CN 201811069365 A CN201811069365 A CN 201811069365A CN 110896407 B CN110896407 B CN 110896407B
Authority
CN
China
Prior art keywords
component
request
forwarding
components
interface
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
Application number
CN201811069365.4A
Other languages
Chinese (zh)
Other versions
CN110896407A (en
Inventor
李薛林
高建军
张凤桥
康宁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bright Oceans Inter Telecom Co Ltd
Original Assignee
Bright Oceans Inter Telecom Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bright Oceans Inter Telecom Co Ltd filed Critical Bright Oceans Inter Telecom Co Ltd
Priority to CN201811069365.4A priority Critical patent/CN110896407B/en
Publication of CN110896407A publication Critical patent/CN110896407A/en
Application granted granted Critical
Publication of CN110896407B publication Critical patent/CN110896407B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/70Software maintenance or management
    • G06F8/71Version control; Configuration management
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0893Assignment of logical groups to network elements
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/60Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a configuration management method of an NFVO component, which comprises the following steps: defining a component template and defining a component connection rule; performing attribute parameter configuration on the component template according to the NFVO request forwarding service requirement to obtain each component, wherein each component comprises a monitoring component, a branch component, a response component, a forwarding component and a processing flow component; and connecting and storing the obtained components according to the service requirements and the connection rules. The invention also discloses an NFVO request forwarding method and a request processing device. By the method and the device, the NFVO request processing flow can be decoupled into the components, the purposes of flexibly configuring the flow and quickly adding and deleting the flow are achieved, and the NFVO request processing efficiency is greatly improved.

Description

NFVO component configuration management, request forwarding method and request processing device
Technical Field
The invention relates to the field of software, in particular to a technology for processing and forwarding NFVO (network function virtualization) requests.
Background
NFV, i.e., network function virtualization, carries very many functions of software processing through generic hardware such as X86 and virtualization technologies, thereby reducing the expensive equipment cost of the network. The functions of the network equipment can be independent of special hardware through software and hardware decoupling and function abstraction, resources can be shared fully and flexibly, rapid development and deployment of new services are achieved, and automatic deployment, elastic expansion, fault isolation, self-healing and the like are carried out based on actual service requirements. NFVO is the network function virtualization coordinator.
For a traditional service, a received data type is single, if a data type is newly added, a source code of an existing system needs to be modified and upgraded to complete a requirement, an NFV system can process different data types from applications due to its own advantages, and if a traditional method for receiving a single data type is adopted to be interfaced with the NFV system to complete NFVO request processing and forwarding, the efficiency of the system is reduced.
Therefore, a request forwarding technology based on NFVO is urgently needed.
Disclosure of Invention
The invention discloses a configuration management method of an NFVO component, which comprises the following steps:
defining a component template and defining a component connection rule;
according to NFVO request forwarding service requirements, attribute parameter configuration is carried out on the component template to obtain each component, and each component comprises a monitoring component, a branch component, a response component, a forwarding component and a processing flow component;
and connecting and storing the obtained components according to the service requirements and the connection rules.
In particular, the method comprises the following steps of,
the definition component template is attribute information, interface information, connection information and individual parameters of each component of the definition component;
the attribute information of the defined component is defined component labels and component types, and the component types are resident components and non-resident components;
the definition of the component connection rule is to define the connection relation among the components, and the connection relation is data connection, control connection and component information at two ends of the connection.
Preferably:
determining the component type according to the use frequency of the components and the data processing sequence among the components;
the resident component independently occupies a thread, and the components are connected with one another through data;
and a plurality of the non-resident components occupy one thread, and the components are connected through control.
The invention also discloses a request forwarding method based on the NFVO component, which comprises the following steps:
the monitoring component monitors the corresponding NFVO interface according to the attribute parameter configuration information of the monitoring component and sends a request obtained by monitoring to the connected branch component;
the branch component receives each interface request sent by the monitoring component, matches each interface request to corresponding processing logic according to attribute parameter configuration information of the branch component, and sends the interface requests to a forwarding component;
the response component responds to the result of the branch component processing logic according to the attribute parameter configuration information of the response component;
the forwarding component forwards each interface request to a corresponding processing flow component according to the attribute parameter configuration information of the forwarding component;
and the processing flow component processes the interface requests according to preset processing flows and attribute parameter configuration information and then sends the processed interface requests to corresponding upper-layer application.
Preferably, the following components:
and adding a protocol handle in the request, and ensuring that the requests processed by all the components are consistent according to the protocol handle.
Preferably:
the attribute parameter configuration information of the monitoring component comprises monitoring interface information thereof;
the attribute parameter configuration information of the branch component comprises corresponding monitoring interface information and processing logic corresponding to the monitoring interface;
the attribute parameter configuration information of the response component comprises a response code and a response message body thereof;
the attribute parameter configuration information of the forwarding component comprises the address and interface information of the corresponding processing flow component;
the attribute parameter configuration information of the processing flow comprises corresponding upper-layer application interface information.
Preferably:
the monitoring component and the forwarding component are resident components;
the branching component and the responding component are non-resident components.
The invention also discloses a request forwarding device based on the NFVO component, which comprises:
the component configuration management unit is used for defining a component template, configuring the components according to the component template and storing the configured components;
a request receiving and forwarding unit, configured to receive, by using the component configured by the component configuration management unit, a request of the NFVO, and perform response and forwarding after performing logic processing on the request by using the component configured by the component configuration management unit;
and the data processing unit is used for receiving the request of the request receiving and forwarding unit, processing the request according to the component configured by the component configuration management unit and then sending the processed request to the corresponding upper-layer application.
In detail, the component configuration management unit further includes:
the component definition module is used for defining a component template and defining a component connection rule;
the component configuration module is used for carrying out attribute parameter configuration on the component template defined by the component definition unit according to the NFVO request forwarding service requirement to obtain each component, and each component comprises a monitoring component, a branch component, a response component, a forwarding component and a processing flow component;
and the component storage module is used for connecting and storing the obtained components according to the service requirements and the connection rules.
In detail, the request receiving and forwarding unit further comprises:
the monitoring component is used for monitoring the corresponding NFVO interface according to the attribute parameter configuration information of the monitoring component and sending a request obtained by monitoring to the connected branch component;
the branch component is used for receiving each interface request sent by the monitoring component, matching each interface request to corresponding processing logic according to attribute parameter configuration information of the branch component, and sending the interface request to the forwarding component;
the response component is used for responding to the result of the branch component processing logic according to the attribute parameter configuration information of the response component;
and the forwarding component is used for forwarding the interface requests to the corresponding processing flow components according to the attribute parameter configuration information.
In detail, the data processing unit further comprises:
and the processing flow component is used for processing each interface request according to the preset processing flow and attribute parameter configuration information and then sending the processed interface request to the corresponding upper-layer application.
The invention firstly provides a configuration management method of an NFVO request processing assembly, which is used for defining and configuring various request processing assemblies based on the NFVO, completing each flow step of NFVO request forwarding, decomposing each step of request forwarding, and facilitating calling and combining to form a flexible forwarding flow; the invention also provides a request forwarding method based on the NFVO request processing component, which is characterized in that each component is used to configure, combine and connect the components into a simple and easy-to-use and flexible-increase/decrease request forwarding flow, and the method can be used for different data types, different service types and different upper-layer applications, and really realizes flexible and rapid processing of big data. Compared with the traditional server, when a new data type, a service type and an upper application occur, only a new configuration component technology is needed to be added, and a source code of an existing system is not needed to be modified; meanwhile, the invention separates the request receiving and processing, and the receiving is not influenced by untimely processing, thereby improving the overall performance and accuracy of the system.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a method for managing configuration of an NFVO component according to an embodiment of the present application;
fig. 2 is a schematic flowchart of a request forwarding method based on an NFVO component according to a second embodiment of the present application;
FIG. 3 is a logic diagram of a method provided in a third embodiment of the present application;
FIG. 4 is a logic diagram of a method according to a fourth embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a request forwarding device based on an NFVO component according to a fifth embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art based on the embodiments of the present invention without inventive step, are within the scope of the present invention.
Referring to fig. 1, fig. 1 is a method for managing configuration of an NFVO device according to an embodiment of the present application, where the method includes:
step S101: defining a component template, and defining a component connection rule.
The definition component template is attribute information, interface information, connection information and individual parameters of each component of the definition component.
The attribute information of the defined component is a defined component label and a component type, and the component type is a resident component and a non-resident component. And determining the component type according to the use frequency of the components and the data processing sequence among the components.
The resident component independently occupies a thread, and the components are connected with one another through data.
And a plurality of the non-resident components occupy one thread, and the components are connected through control.
The definition of the component connection rule is to define the connection relation among the components, and the connection relation is data connection, control connection and component information at two ends of the connection.
It should be noted that, the resident component may be used frequently, and the data processing sequence thereof is prior, if the data processing sequence must be passed through the component to process data and obtain data result before triggering the next component to process data, then the component should be the resident component, whereas the resident component may be used frequently, and the execution of the component is controlled by the previous component, then the resident component is the non-resident component.
Preferably, as a simplified connection relationship between components, the connection lines between the components can be expressed by lines of different styles, and the relationship between the components can also be described by different languages, that is, the connection relationship between the components is a data connection and a control connection.
The data connection is that the two components use the processing result of the data as the connection relation, and the data processing result of the previous component can trigger the execution of the next component;
the control connection is that the two components use the execution condition as the connection relation, and whether the previous component finishes normal execution can trigger the execution of the next component.
Step S102: and configuring attribute parameters of the component template according to the NFVO request forwarding service requirement to obtain each component, wherein each component comprises a monitoring component, a branch component, a response component, a forwarding component and a processing flow component.
Configuring attribute parameters for a component template according to service requirements to obtain each component, wherein the attribute parameters include but are not limited to the type of the component, interface information corresponding to the component, information of a response port required by the component, address information of a component acquisition request, heartbeat information of the component, associated report information, a component processing step, a component executing step and the like, each component configuration can select one or more attribute parameters according to actual service requirements, and when new parameters appear, the attribute parameters can be updated to the component template.
The monitoring component is a resident component, monitors a request sent by the NFVO side according to interface information configured by the component, and forwards the request to a next connected component according to attribute parameters configured by the component once the request is monitored to be sent;
the branch component is a non-resident component, judges a branch to be taken by the request according to the request sent by the monitoring component and the information configured by the component, and carries out corresponding processing.
The response component is a non-resident component and responds to the corresponding interface according to the request sent by the branch component and the response information of the component configuration.
The forwarding component is a resident component that forwards the request according to the logic in the branching component, i.e. some parameters in the request are sent to the process flow component also in the manner of Rest.
The process flow component may process the received request according to a preset processing step, and send a processing result to a pre-configured upper application.
Step S103: and connecting and storing the obtained components according to the service requirements and the connection rules.
The components configured with specific parameters are connected with each other to form a complete processing flow, the configuration information of the flow can be recorded after the flow is stored, the recording can be carried out in different forms, such as xml files which are commonly used, different connection relations are distinguished through the types of the connection nodes in the files, the starting node and the ending node of each connection relation are recorded, and the components and the connection relations thereof are connected through unique identification of the components and the connection relations of the components.
The complete processing flows are stored, and the stored complete processing flows can be directly called when the same data is processed or information is sent to the same upper-layer application at one time. The time for configuration can be greatly saved, and the efficiency is improved.
It should be noted that the components can be flexibly configured, and one or more components to be used are selected according to different configurations of the processing flow.
The components configured according to the component template include, but are not limited to, a listening component, a branching component, a responding component, a forwarding component, a processing flow component, and may also include business components related to specific businesses, such as: a filter component,
Therefore, each step of NFVO request forwarding is disassembled into different types of assemblies, the purpose of flexibly configuring the process is achieved, the assemblies are divided into two different types, the execution sequence and the number of occupied threads are determined according to the types of the assemblies, resources are intelligently allocated, the processing efficiency is improved, a plurality of resident assemblies connected through control can occupy one thread, a complex function can be made into a plurality of small assemblies to facilitate maintenance, a resident assembly connected through data occupies one thread, the working of the assembly is guaranteed not to be influenced if the efficiency of a subsequent assembly is low, and therefore better processing efficiency can be obtained through the combined configuration of the assemblies of different types.
Based on the NFVO request processing component configuration management method, the present invention also discloses a request forwarding method based on the NFVO component, and a second embodiment of the present invention is given below, as shown in fig. 2.
Under normal conditions, the NFVO side sends a request to the OSS side in a Rest manner, and after the OSS side monitors the request through a monitoring component, the OSS side receives, forwards, and processes the request and then sends valid data to an upper application, and the method specifically includes the following steps:
step S201: and the monitoring component monitors the corresponding NFVO interface according to the attribute parameter configuration information of the monitoring component and sends a request obtained by monitoring to the connected branch component.
The attribute parameter configuration information of the monitoring component comprises monitoring interface information thereof.
The listening component is a resident component.
Step S202: and the branch component receives each interface request sent by the monitoring component, matches each interface request to corresponding processing logic according to the attribute parameter configuration information of the branch component, and sends the interface request to the forwarding component.
The attribute parameter configuration information of the branch component comprises corresponding monitoring interface information and processing logic corresponding to the monitoring interface.
The branching component is a non-resident component.
Step S203: and the response component responds to the result of the branch component processing logic according to the attribute parameter configuration information.
The attribute parameter configuration information of the response component comprises a response code and a response message body thereof.
The response component is a non-resident component.
Step S204: and the forwarding component forwards each interface request to the corresponding processing flow component according to the attribute parameter configuration information of the forwarding component.
The attribute parameter configuration information of the forwarding component comprises the address and interface information of the corresponding processing flow component.
The forwarding component is a resident component.
Step S205: and the processing flow component processes the interface requests according to preset processing flows and attribute parameter configuration information and then sends the processed interface requests to corresponding upper-layer application.
The attribute parameter configuration information of the processing flow comprises corresponding upper-layer application interface information.
In the whole request forwarding process, a protocol handle is added in a request, the consistency of requests processed by all components is ensured according to the handle, and a new handle is adopted in the next request forwarding.
I.e., to ensure that the entire flow is processing the same request from snoop to response, in accordance with passing the http change handle.
The branch component and the response component are non-resident components and are positioned in one thread, the functions of the branch component and the response component are decoupled, the maintenance is convenient, the monitoring component and the forwarding component are resident components and occupy one thread respectively, and the response to the request cannot be influenced due to untimely monitoring and forwarding.
To better illustrate the present invention, a logical schematic of the components is given, as shown in FIG. 3.
And the monitoring component configures the attribute of the login interface, continuously scans and judges whether a request of the interface exists, and if the request is received, the monitoring component adds httpexchang handle and transmits the httpexchang handle to the branch component.
The branch component receives the data transmitted from the monitoring component, acquires the URL attribute from the data, compares the URL attribute with the self-configured data and finds the branch to be taken by the request; if a response is required, a response is made by the response component.
And after responding to the NFVO through the corresponding response component, sending the request to the corresponding forwarding component according to the configured forwarding information, sending the request to a response processing flow through the forwarding component, and sending the request to the corresponding upper-layer application after the processing flow processes the request according to the pre-configured steps.
When a new flow needs to be added, only the response component needs to be added.
For better illustration of the present invention, a fourth embodiment of the present invention is further illustrated by referring to the example shown in fig. 4.
The HttpListener is responsible for monitoring the request from the NFVO side;
ttpUrlBranch is responsible for branch determination of these requests;
response is used for responding to the NFVO side request;
the Request is used for requesting to forward;
loginaandupdatetoken, htpchannelregister and httphannellogout are the first branches, realtimealarmhttpsggetter is the second branch in the overall logic diagram, and syncbyallsmargetgetter and syncbyfilehttpsggetter are the third branches.
The fifth embodiment of the present invention further discloses a request forwarding device based on the NFVO component, as shown in fig. 5.
The component configuration management unit 1 is used for defining a component template, configuring the components according to the component template, and storing the configured components.
The component configuration management unit further includes:
the component definition module 11 is used for defining a component template and defining a component connection rule;
the component configuration module 12 is configured to perform attribute parameter configuration on the component template defined by the component definition unit according to the NFVO request forwarding service requirement to obtain each component, where each component includes a monitoring component, a branch component, a response component, a forwarding component, and a processing flow component;
and the component storage module 13 is configured to connect and store the obtained components according to the service requirements and the connection rules.
A request receiving and forwarding unit 2, configured to receive the request of the NFVO by using the component configured by the component configuration management unit, and perform response and forwarding after performing logic processing on the request by using the component configured by the component configuration management unit.
The request receiving and forwarding unit further comprises:
the monitoring component 21 is configured to monitor a corresponding NFVO interface according to the monitoring component attribute parameter configuration information, and send a request obtained by monitoring to a connected branch component;
the branch component 22 is configured to receive each interface request sent by the monitoring component, match each interface request to corresponding processing logic according to attribute parameter configuration information of the branch component, and send the interface request to the forwarding component;
a response component 23, configured to respond to the result of the branch component processing logic according to the attribute parameter configuration information of the response component;
and the forwarding component 24 is configured to forward each interface request to the corresponding processing flow component according to the attribute parameter configuration information.
And the data processing unit 3 is configured to receive the request of the request receiving and forwarding unit, process the request according to the component configured by the component configuration management unit, and send the processed request to the corresponding upper-layer application.
The data processing unit further comprises:
and the processing flow component 31 is configured to process each interface request according to a preset processing flow and attribute parameter configuration information, and then send the processed interface request to a corresponding upper layer application.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific corresponding working processes of the foregoing systems, modules and units described above may refer to method steps, which are not described herein again.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A method for managing configuration of an NFVO component, the method comprising:
defining a component template and defining a component connection rule; the definition component template is attribute information, interface information, connection information and individual parameters of each component of the definition component; the attribute information of the defined component is defined component labels and component types, and the component types are resident components and non-resident components; the definition of the connection rule of the components is to define the connection relation among the components, and the connection relation is data connection, control connection and component information positioned at two ends of the connection;
performing attribute parameter configuration on the component template according to the NFVO request forwarding service requirement to obtain each component, wherein each component comprises a monitoring component, a branch component, a response component, a forwarding component and a processing flow component;
and connecting and storing the obtained components according to the service requirements and the connection rules.
2. The method of claim 1, wherein:
determining the component type according to the use frequency of the components and the data processing sequence among the components;
the resident component independently occupies a thread, and the components are connected with one another through data;
and a plurality of the non-resident components occupy one thread, and the components are connected through control.
3. A request forwarding method based on an NFVO component is characterized by comprising the following steps:
the monitoring component monitors the corresponding NFVO interface according to the attribute parameter configuration information of the monitoring component and sends a request obtained by monitoring to the connected branch component;
the branch component receives each interface request sent by the monitoring component, matches each interface request to corresponding processing logic according to attribute parameter configuration information of the branch component, and sends the interface requests to a forwarding component;
the response component responds to the result of the branch component processing logic according to the attribute parameter configuration information of the response component;
the forwarding component forwards each interface request to a corresponding processing flow component according to the attribute parameter configuration information of the forwarding component;
and the processing flow component processes each interface request according to preset processing flow and attribute parameter configuration information and then sends the interface request to corresponding upper-layer application.
4. The method of claim 3, wherein:
and adding a protocol handle in the request, and ensuring that the requests processed by all the components are consistent according to the protocol handle.
5. The method of claim 4, wherein:
the attribute parameter configuration information of the monitoring component comprises monitoring interface information thereof;
the attribute parameter configuration information of the branch component comprises corresponding monitoring interface information and processing logic corresponding to the monitoring interface;
the attribute parameter configuration information of the response component comprises a response code and a response message body thereof;
the attribute parameter configuration information of the forwarding component comprises the address and interface information of the corresponding processing flow component;
the attribute parameter configuration information of the processing flow comprises corresponding upper layer application interface information.
6. The method of claim 5, wherein:
the monitoring component and the forwarding component are resident components;
the branching component and the responding component are non-resident components.
7. A NFVO component-based request forwarding apparatus, comprising:
the component configuration management unit is used for defining a component template, configuring components according to the component template and storing the configured components;
a request receiving and forwarding unit, configured to receive, by using the component configured by the component configuration management unit, a request of the NFVO, and perform response and forwarding after performing logic processing on the request by using the component configured by the component configuration management unit;
and the data processing unit is used for receiving the request of the request receiving and forwarding unit, processing the request according to the component configured by the component configuration management unit and then sending the processed request to the corresponding upper-layer application.
8. The apparatus of claim 7, wherein the component configuration management unit further comprises:
the component definition module is used for defining a component template and defining a component connection rule; the definition component template is attribute information, interface information, connection information and individual parameters of each component of the definition component; the attribute information of the defined component is defined component labels and component types, and the component types are resident components and non-resident components; the definition of the connection rule of the components is to define the connection relation among the components, and the connection relation is data connection, control connection and component information positioned at two ends of the connection;
the component configuration module is used for carrying out attribute parameter configuration on the component template defined by the component definition unit according to the NFVO request forwarding service requirement to obtain each component, and each component comprises a monitoring component, a branch component, a response component, a forwarding component and a processing flow component;
and the component storage module is used for connecting and storing the obtained components according to the service requirements and the connection rules.
9. The apparatus of claim 8, wherein the request receiving and forwarding unit further comprises:
the monitoring component is used for monitoring the corresponding NFVO interface according to the attribute parameter configuration information of the monitoring component and sending a request obtained by monitoring to the connected branch component;
the branch component is used for receiving each interface request sent by the monitoring component, matching each interface request to corresponding processing logic according to attribute parameter configuration information of the branch component, and sending the interface request to the forwarding component;
the response component is used for responding to the result of the branch component processing logic according to the attribute parameter configuration information of the response component;
and the forwarding component is used for forwarding the interface requests to the corresponding processing flow components according to the attribute parameter configuration information.
10. The apparatus of claim 9, wherein the data processing unit further comprises:
and the processing flow component is used for processing each interface request according to the preset processing flow and attribute parameter configuration information and then sending the processed interface request to the corresponding upper layer application.
CN201811069365.4A 2018-09-13 2018-09-13 NFVO component configuration management, request forwarding method and request processing device Active CN110896407B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201811069365.4A CN110896407B (en) 2018-09-13 2018-09-13 NFVO component configuration management, request forwarding method and request processing device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201811069365.4A CN110896407B (en) 2018-09-13 2018-09-13 NFVO component configuration management, request forwarding method and request processing device

Publications (2)

Publication Number Publication Date
CN110896407A CN110896407A (en) 2020-03-20
CN110896407B true CN110896407B (en) 2023-03-10

Family

ID=69785503

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201811069365.4A Active CN110896407B (en) 2018-09-13 2018-09-13 NFVO component configuration management, request forwarding method and request processing device

Country Status (1)

Country Link
CN (1) CN110896407B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1637706A (en) * 2003-12-18 2005-07-13 东芝解决方案株式会社 Component processing system and component processing method
CN105282195A (en) * 2014-06-27 2016-01-27 中兴通讯股份有限公司 Network service providing, strategy rule evaluating and service component selecting method and device
CN107678745A (en) * 2017-09-25 2018-02-09 南京中新赛克科技有限责任公司 System and method based on page assembly
CN108207008A (en) * 2016-12-19 2018-06-26 中兴通讯股份有限公司 A kind of management method and device for virtualizing network element

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1637706A (en) * 2003-12-18 2005-07-13 东芝解决方案株式会社 Component processing system and component processing method
CN105282195A (en) * 2014-06-27 2016-01-27 中兴通讯股份有限公司 Network service providing, strategy rule evaluating and service component selecting method and device
CN108207008A (en) * 2016-12-19 2018-06-26 中兴通讯股份有限公司 A kind of management method and device for virtualizing network element
CN107678745A (en) * 2017-09-25 2018-02-09 南京中新赛克科技有限责任公司 System and method based on page assembly

Also Published As

Publication number Publication date
CN110896407A (en) 2020-03-20

Similar Documents

Publication Publication Date Title
CN110324164B (en) Network slice deployment method and device
EP3291499B1 (en) Method and apparatus for network service capacity expansion
CN108370341B (en) Resource allocation method, virtual network function manager and network element management system
CN108712332B (en) Communication method, system and device
CN111371627A (en) Method for setting multiple IP (Internet protocol) in Pod in Kubernetes
US9331870B2 (en) Switch, information processing apparatus, and information processing system
CN109375933B (en) Method and equipment for upgrading client
CN109151025B (en) Load balancing method and device based on URL, computer storage medium and equipment
CN108304267B (en) Multi-source data leading method with high reliability and low resource overhead
CN116260725A (en) Bandwidth allocation method and device of server, electronic equipment and storage medium
CN114296909B (en) Automatic capacity expansion and contraction method and system for nodes according to kubernetes events
CN109120680B (en) Control system, method and related equipment
CN114710549A (en) Dynamic management method, system and service node of network card in container platform
CN111209125B (en) Multi-process command line implementation method
US20130036216A1 (en) System and method for optimized event monitoring in a management environment
CN110798358B (en) Distributed service identification method and device, computer readable medium and electronic equipment
CN110896407B (en) NFVO component configuration management, request forwarding method and request processing device
CN113760522A (en) Task processing method and device
CN112073499A (en) Dynamic service method of multi-machine type cloud physical server
CN115426258B (en) Information configuration method, device, switch and readable storage medium
CN114584629B (en) Transaction message processing method and device
US20150244780A1 (en) System, method and computing apparatus to manage process in cloud infrastructure
CN112448854B (en) Kubernetes complex network policy system and implementation method thereof
CN115918116A (en) Information processing method, device and storage medium
CN109286513B (en) Resource deployment method and device

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