Network element traffic management method, device and system based on layered architecture

Abstract

The present disclosure provides a network element traffic management method, device and system based on a layered architecture, which relates to the field of network communication technology. The layered architecture includes a control layer and a data layer; the method includes: the control layer responds to the management request of the network element microservice, performs lifecycle management on the data layer, so as to establish a communication connection between the data layer and the network element microservice; when the data layer receives the traffic transmission request initiated by the network element microservice, it performs traffic management on the communication traffic of the network element microservice. The present disclosure uses the control layer and data layer of the service grid agent to manage the communication traffic of the network element microservice, which can shorten the forwarding path of the communication traffic, reduce network latency, and thereby enhance the service grid's management capabilities for the network element microservice.

Description

Technical Field

[0001] The present disclosure relates to the field of network communication technology, and in particular, to a network element traffic management method based on a layered architecture, a network element traffic management device based on a layered architecture, and a network element traffic management system based on a layered architecture. Background Art

[0002] With the rapid development of microservices and cloud technologies, a large number of microservices have dramatically increased the difficulty of their operation and maintenance, such as microservice connection, management, and monitoring. Therefore, a dedicated microservice system such as service grid is needed to be responsible for communication, current limiting, circuit breaking, and monitoring between microservices.

[0003] At present, when cloud-native network elements introduce service mesh to govern microservices, it is usually based on the sidecar proxy mode. The sidecar proxy takes over the communication traffic of the network element microservices and processes it, thereby realizing the communication carrying, monitoring, and security capabilities of the cloud-native network elements.

[0004] However, when using a service mesh based on the sidecar proxy mode to directly proxy the communication traffic of cloud-native network elements, the communication traffic of the network element microservices needs to be redirected to the service mesh proxy, which makes the network forwarding path longer, increases network latency, and reduces the service performance of the service mesh proxy, thereby reducing the service mesh's governance capabilities for the network element microservices.

[0005] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0006] The present invention provides a network element traffic management method based on a layered architecture, a network element traffic management device based on a layered architecture, and a network element traffic management system based on a layered architecture, thereby overcoming the problem of low management capability of the service grid for network element microservices in related technologies at least to a certain extent.

[0007] According to a first aspect of the present disclosure, a network element traffic management method based on a layered architecture is provided, wherein the layered architecture includes a control layer and a data layer; the method includes:

[0008] The control layer responds to the governance request of the network element microservice and performs lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice;

[0009] When the data layer receives the traffic transmission request initiated by the network element microservice, it performs traffic management on the communication traffic of the network element microservice.

[0010] In an exemplary embodiment of the present disclosure, the control layer includes a network element microservice governance interface and parsing function, a data layer deployment function, a data layer configuration function and a data layer management function; the data layer includes one or more data layer functions of a socket layer function, a transport layer function, a network layer function and a media access control layer function.

[0011] In an exemplary embodiment of the present disclosure, the control layer responds to a governance request of a network element microservice and performs lifecycle management on the data layer, including:

[0012] The control layer receives the governance request of the network element microservice through the network element microservice governance interface, and parses the governance request of the network element microservice to determine the function of the data layer;

[0013] The control layer performs lifecycle management on the data layer according to the function of the data layer.

[0014] In an exemplary embodiment of the present disclosure, the network element microservice governance interface includes at least network namespace information of the network element microservice and function information of the data layer;

[0015] The parsing of the governance request of the network element microservice to determine the data layer function includes:

[0016] Determine the network namespace of the network element microservice according to the network namespace information of the network element microservice;

[0017] The data layer function in the network namespace of the network element microservice is determined according to the function information of the data layer.

[0018] In an exemplary embodiment of the present disclosure, the control layer performs lifecycle management on the data layer according to the function of the data layer, including:

[0019] The control layer deploys, configures and manages the data layer according to the functions of the data layer.

[0020] In an exemplary embodiment of the present disclosure, the control layer deploys the data layer according to the function of the data layer, including:

[0021] The control layer deploys the data layer at a corresponding network protocol layer on a network protocol stack of a network namespace of the network element microservice according to a function of the data layer.

[0022] In an exemplary embodiment of the present disclosure, the traffic transmission request is a system call of a network protocol stack of a network namespace, and the system call includes at least the communication traffic of the network element microservice;

[0023] When the data layer receives the traffic transmission request initiated by the network element microservice, traffic management is performed on the communication traffic of the network element microservice, including:

[0024] When the data layer receives the system call, it determines the network protocol stack of the network namespace of the network element microservice according to the system call;

[0025] When the communication traffic of the network element microservice enters the network protocol stack, the function of the data layer of the network protocol layer deployed on the network protocol stack is triggered to perform traffic management on the communication traffic.

[0026] In an exemplary embodiment of the present disclosure, the corresponding triggering of the function of the data layer of the network protocol layer deployed on the network protocol stack to perform traffic management on the communication traffic includes:

[0027] The communication traffic is subjected to one or more of socket layer processing, transport layer processing, network layer processing, and media access control layer processing through the function of the data layer.

[0028] According to a second aspect of the present disclosure, a network element traffic management device based on a layered architecture is provided, wherein the layered architecture includes a control layer and a data layer; the device includes:

[0029] A lifecycle management module, used for the control layer to respond to the governance request of the network element microservice, perform lifecycle management on the data layer, so as to establish a communication connection between the data layer and the network element microservice;

[0030] The communication traffic management module is used to manage the communication traffic of the network element microservice when the data layer receives a traffic transmission request initiated by the network element microservice.

[0031] According to a third aspect of the present disclosure, a network element traffic management system based on a layered architecture is provided, wherein the layered architecture includes a control layer and a data layer, and the system includes:

[0032] A network element microservice, used to send a governance request to the control layer and a traffic transmission request to the data layer;

[0033] The control layer is used to respond to the governance request of the network element microservice and perform lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice;

[0034] The data layer is used to perform traffic management on the communication traffic of the network element microservice when receiving a traffic transmission request initiated by the network element microservice.

[0035] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, it implements any one of the above-mentioned network element traffic management methods based on a layered architecture.

[0036] According to a fifth aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned network element traffic management methods based on a layered architecture by executing the executable instructions.

[0037] The exemplary embodiments of the present disclosure may have some or all of the following beneficial effects:

[0038] In the network element traffic management method based on the layered architecture provided in the example implementation mode of the present disclosure, the layered architecture includes a control layer and a data layer, wherein the control layer responds to the management request of the network element microservice and performs lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice; when the data layer receives the traffic transmission request initiated by the network element microservice, it performs traffic management on the communication traffic of the network element microservice. The present disclosure uses the control layer and the data layer of the service grid agent to manage the communication traffic of the network element microservice, and can flexibly load the data layer according to the type of the network element microservice, and take over the communication traffic of the network element microservice through the data layer, without the need to detour the communication traffic, shortening the forwarding path of the communication traffic, reducing network latency, and improving the service performance of the service grid agent, thereby improving the management capability of the service grid for the network element microservice.

[0039] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative work.

[0041] Figure 1 A schematic diagram of the architecture of a network element traffic management system based on a layered architecture in an embodiment of the present disclosure is shown;

[0042] Figure 2 A schematic diagram of the architecture of a service grid based on a sidecar proxy in an embodiment of the present disclosure is shown;

[0043] Figure 3A flow chart of a network element traffic management method based on a layered architecture in an embodiment of the present disclosure is shown;

[0044] Figure 4 A schematic diagram of the architecture of another network element traffic management system in an embodiment of the present disclosure is shown;

[0045] Figure 5 A schematic diagram of the architecture of another network element traffic management system in an embodiment of the present disclosure is shown;

[0046] Figure 6 A block diagram of a network element traffic management device based on a layered architecture in an embodiment of the present disclosure is schematically shown;

[0047] Figure 7 A schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0048] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0049] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0050] The technical solution of the embodiment of the present disclosure is described in detail below:

[0051] Figure 1 FIG. 1 shows a schematic diagram of the architecture of a network element traffic management system based on a layered architecture. Figure 1As shown, the system architecture 100 includes a network element microservice 110 and a service grid agent, and the service grid agent can be separated into a control layer 120 and a data layer 130. Among them, the network element microservice 110 can send a governance request to the control layer 120, and the control layer 120 responds to the governance request of the network element microservice 110 and performs life cycle management on the data layer 130 to establish a communication connection between the data layer 130 and the network element microservice 110. The network element microservice 110 can also send a traffic transmission request to the data layer 130, and when the data layer 130 receives the traffic transmission request initiated by the network element microservice 110, it performs traffic management on the communication traffic of the network element microservice 110. In addition, the control layer 120 can also be used to create corresponding data layers 130 for different types of network element microservices 110, and dynamically load the corresponding data layer 130 according to the type of the network element microservice and the governance requirements of the network element microservice.

[0052] The technical solution of the embodiment of the present disclosure is described in detail below:

[0053] At present, when cloud-native network elements introduce service mesh to govern microservices, it is usually based on the sidecar proxy mode. The sidecar proxy takes over the communication traffic of the network element microservices and processes it, thereby realizing the communication carrying, monitoring, and security capabilities of the cloud-native network elements.

[0054] refer to Figure 2 As shown, a service grid architecture diagram based on the sidecar proxy is given. Specifically, the operating system user state 210 deploys a service grid proxy 202 for each network element microservice in the cloud native network element 201, wherein the cloud native network element 201 may include interface network element microservices, business network element microservices, and other types of network element microservices such as management and control. Taking the interface network element microservice as an example, the communication traffic of the interface network element microservice can be first sent to the interface network element microservice network namespace 203. After the communication traffic of the interface network element microservice is captured by the service grid proxy network namespace 204 of the operating system kernel state 220, it is forwarded to the service grid proxy 202 of the operating system user state 210, and the communication traffic of the interface network element microservice is processed by the service grid proxy 202. Then, the processed communication traffic is sent back to the network protocol stack of the service grid proxy network namespace 204. The network protocol stack includes multiple network protocol layers, such as Socket (socket layer) 205, TCP (Transmission Control Protocol, transmission control protocol layer) / IP (Internet Protocol, Internet Protocol layer) 206 and network card driver layer 207. Finally, the communication traffic can enter other network element microservice network namespaces or leave the operating system node through the network card 208.

[0055] It can be seen that when using a service mesh based on the sidecar proxy mode to directly proxy the communication traffic of cloud-native network elements, the communication traffic of the network element microservices needs to be redirected to the service mesh proxy, which makes the network forwarding path longer, increases network latency, and reduces the service performance of the service mesh proxy, thereby reducing the service mesh's governance capabilities for the network element microservices.

[0056] Based on the above problems, this example implementation provides a network element traffic management method based on a layered architecture. The layered architecture refers to separating the service network agent into a control layer and a data layer, and using the control layer and the data layer to manage the traffic of microservice communication traffic. Figure 3 As shown, the method may include the following steps S310 and S320:

[0057] Step S310. The control layer responds to the governance request of the network element microservice and performs lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice;

[0058] Step S320: When the data layer receives the traffic transmission request initiated by the network element microservice, it performs traffic management on the communication traffic of the network element microservice.

[0059] In the network element traffic management method based on the layered architecture provided in the example implementation mode of the present disclosure, the layered architecture includes a control layer and a data layer, wherein the control layer responds to the management request of the network element microservice and performs lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice; when the data layer receives the traffic transmission request initiated by the network element microservice, it performs traffic management on the communication traffic of the network element microservice. The present disclosure uses the control layer and the data layer of the service grid agent to manage the communication traffic of the network element microservice, and can flexibly load the data layer according to the type of the network element microservice, and take over the communication traffic of the network element microservice through the data layer, without the need to detour the communication traffic, shortening the forwarding path of the communication traffic, reducing network latency, and improving the service performance of the service grid agent, thereby improving the management capability of the service grid for the network element microservice.

[0060] Next, the above steps of this exemplary embodiment are described in more detail.

[0061] In step S310, the control layer responds to the governance request of the network element microservice and performs lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice.

[0062] In the example implementation of the present disclosure, the cloud native network element can be split into multiple highly cohesive network element microservices, which are loosely coupled and communicate through service-oriented interfaces. For example, the IPU component of the 5G (5th generation mobile networks, fifth generation mobile communication network) core network control plane network element can be split into different types of network element microservices, such as interface network element microservices, business network element microservices, etc. Therefore, the network element microservice can be an interface network element microservice, a business network element microservice, or other types of network element microservices, and the present disclosure does not make specific limitations on this.

[0063] It should be noted that the present disclosure separates the service grid agent in the service grid into a control layer and a data layer, and the control layer and the data layer can be used to manage the communication traffic of different types of network element microservices. Exemplarily, a control layer can be deployed in the user state of the operating system, and the control layer can include a network element microservice governance interface and a parsing module, a data layer loading module, and a data layer management and control module. Correspondingly, the control layer can include a network element microservice governance interface and a parsing function, a data layer deployment function, a data layer configuration function, and a data layer management function. The cloud-native network element can call the network element microservice governance interface of the control layer according to the type of each network element microservice, and create a data layer corresponding to each network element microservice in the kernel state of the operating system through the network element microservice governance interface. For example, for an interface-type network element microservice, a data layer corresponding to the network element microservice can be created.

[0064] In an example implementation, the control layer may receive a governance request for a network element microservice through a network element microservice governance interface, and parse the governance request for the network element microservice to determine the data layer function. The network element microservice governance interface defines the network namespace bound to the network element microservice and the functional information of the required data layer. Specifically, when parsing the governance request for the network element microservice, the network namespace of the network element microservice may be determined based on the network namespace information of the network element microservice, and the data layer function in the network namespace of the network element microservice may be determined based on the functional information of the data layer. Then, the data layer may be lifecycle managed based on the data layer function, such as deploying, configuring, and managing the data layer.

[0065] After determining the data layer function in the network namespace of the network element microservice, the data layer can be deployed on the corresponding network protocol layer on the network protocol stack of the network namespace of the network element microservice according to the data layer function to establish a communication connection between the data layer and the network element microservice. Among them, the network namespace provides a new isolated network protocol stack for all processes in the namespace. The network protocol stack refers to the sum of the protocols at each layer in the network, reflecting the process of file transfer in the network, from the upper layer protocol to the underlying protocol, and then from the underlying protocol to the upper layer protocol. Exemplarily, the network protocol stack may include multiple network protocol layers, such as the Socket layer, the TCP / IP layer, and the network card driver layer.

[0066] Exemplarily, according to different network element microservice governance requirements, the data layer may include one or more of a socket layer data layer, a transport layer data layer, a network layer data layer, and a media access control (MAC) layer data layer. Specifically, each data layer in the data layer may be deployed in a corresponding network protocol layer in a network protocol stack. For example, the socket layer data layer may be hooked in the Socket layer, the transport layer data layer may be hooked in the TCP / UDP (User Datagram Protocol) / SCTP (Stream Control Transmission Protocol) layer, the network layer data layer may be hooked in the IP layer, and the MAC layer data layer may be hooked in the network card driver layer. Correspondingly, the data layer may include one or more data layer functions of the socket layer function, the transport layer function, the network layer function, and the media access control layer function. In this example, different types of data layer hooks are in different network protocol stack layers to process different types of network element microservice communication traffic. For example, Socket tracking is applied in the Socket layer, direct high-performance forwarding is in the network card driver layer, and the data layer opens corresponding interfaces for direct calls by network element microservices.

[0067] refer to Figure 4As shown, the cloud native network element 201 includes interface network element microservices, business network element microservices, and other types of network element microservices. The operating system user state 210 deploys a control layer 401, and the data layer 402 runs in the operating system kernel state 220. The control layer 401 and the data layer 402 constitute a service grid agent. The cloud native network element 201 calls the network element microservice governance interface of the control layer 401 according to the type of each network element microservice, and creates a data layer 402 corresponding to each network element microservice in the operating system kernel state 220 through the network element microservice governance interface. For example, for an interface network element microservice, a data layer 402 corresponding to the network element microservice can be created. The data layer 402 may include multiple data layers, namely data layer 1...data layer N. Each data layer hooks the corresponding network protocol layer in the interface network element microservice network namespace, including Socket205, TCP / IP206, and network card driver 207.

[0068] The present disclosure reconstructs the service mesh agent into two components, a control layer and a data layer. Only one control layer needs to be deployed in the operating system user state, and the data layer is hooked to the network protocol stack of the network namespace of the network element microservice. Compared with the related art of deploying the service mesh agent in the operating system user state, the operating system resource overhead is reduced. In particular, the data layer in the present disclosure runs in the operating system kernel state in bytecode, which is lighter and more efficient.

[0069] In step S320, when the data layer receives the traffic transmission request initiated by the network element microservice, it performs traffic management on the communication traffic of the network element microservice.

[0070] Among them, the traffic transmission request initiated by the network element microservice is a system call of the network protocol stack of the network namespace, and the system call at least includes the communication traffic of the network element microservice. Exemplarily, when the data layer receives the system call, the network protocol stack of the network namespace of the network element microservice can be determined according to the system call. Since the data layer is hooked on the network protocol layer, when the communication traffic of the network element microservice enters the network protocol stack, the function of the data layer of the network protocol layer deployed on the network protocol stack is triggered to process the communication traffic.

[0071] by Figure 4Taking the interface-type network element microservice in as an example, when processing the communication traffic of the network element microservice, the communication traffic of the interface-type network element microservice can be sent to the network protocol stack of the interface-type network element microservice network namespace 203. If the required data layer function information is a network layer function, the IP layer can take over the communication traffic of the interface-type network element microservice and perform network layer processing on the communication traffic of the interface-type network element microservice. Correspondingly, the processed communication traffic can enter other network element microservice network namespaces or leave the operating system node through the network card. It can be understood that the present disclosure can perform one or more of socket layer processing, transport layer processing, network layer processing, and media access control layer processing on the communication traffic through the functions of the data layer according to the governance requirements of different network element microservices.

[0072] The present disclosure can dynamically start the corresponding service grid function according to the type of network element microservice, improve the service performance of the service grid agent, and further enhance the governance capability of the service grid for the network element microservice.

[0073] In one example implementation, reference is made to Figure 5 As shown, the cloud native network element 201 includes network element microservice 1 and network element microservice N. The operating system user state 210 deploys a control layer 401, and the control layer 401 may include a network element microservice governance interface and parsing module, a data layer loading module, and a data layer management and control module. Taking network element microservice 1 as an example, the cloud native network element 201 can call the network element microservice governance interface of the control layer 401 to create a corresponding data layer 402, including a socket layer data layer, a transport layer data layer, a network layer data layer, and a MAC layer data layer. The data layer 402 runs in the operating system kernel state 220. The control layer 401 parses the data layer system call 501 through the network element microservice governance interface and parsing module, and hooks the required data layer 402 to the corresponding network protocol layer in the network namespace 502 of the network element microservice 1 through the data layer loading module. For example, the Socket layer data layer is hooked to Socket 205, the transport layer data layer is hooked to TCP / UDP / SCTP 206, the network layer data layer is hooked to IP 206, the MAC layer data layer is hooked to the network card driver 207, and the data layer 402 is configured and managed through the data layer control module.

[0074] The cloud-native network element 201 initiates a data layer system call 501 to transmit the communication message to be processed according to the governance requirements of the network element microservice 1, and the communication message includes the communication traffic of the microservice 1 network element microservice. The communication traffic of the network element microservice 1 enters the network protocol layer in the network element micro1 service namespace 502 and triggers the data layer corresponding to the network protocol layer to perform microservice governance. Among them, the data layer system call 501 includes the socket layer data layer call, the transport layer data layer call, the network layer data layer call and the MAC layer data layer call. For example, when the governance requirement of microservice 1 is to only manage the transport layer traffic, it is sufficient to call the transport layer data layer interface. Finally, the communication traffic of the managed network element microservice 1 can enter the network element microservice N network namespace 503 or leave the operating system node through the network card 208. By Figure 5 It can be seen that the data layer 403 is hooked to the network protocol stack in the network namespace 503 of the network element microservice N, and at the same time realizes the dynamic loading of the data layer 409 according to the type of the network element microservice and the governance requirements of the network element microservice. The data layer 409 includes data layer 1... and other data layers.

[0075] In the network element traffic management method based on the layered architecture provided in the example implementation mode of the present disclosure, the layered architecture includes a control layer and a data layer, wherein the control layer responds to the management request of the network element microservice and performs lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice; when the data layer receives the traffic transmission request initiated by the network element microservice, it performs traffic management on the communication traffic of the network element microservice. The present disclosure uses the control layer and the data layer of the service grid agent to manage the communication traffic of the network element microservice, and can flexibly load the data layer according to the type of the network element microservice, and take over the communication traffic of the network element microservice through the data layer, without the need to detour the communication traffic, shortening the forwarding path of the communication traffic, reducing network latency, and improving the service performance of the service grid agent, thereby improving the management capability of the service grid for the network element microservice.

[0076] It should be noted that although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0077] Furthermore, in this exemplary embodiment, a network element traffic management device based on a layered architecture is also provided, wherein the layered architecture includes a control layer and a data layer. Figure 6As shown, the network element traffic management device 600 based on the layered architecture may include a lifecycle management module 610 and a communication traffic management module 620, wherein:

[0078] The lifecycle management module 610 is used for the control layer to respond to the governance request of the network element microservice and perform lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice;

[0079] The communication traffic management module 620 is used to manage the communication traffic of the network element microservice when the data layer receives a traffic transmission request initiated by the network element microservice.

[0080] In an optional embodiment, the control layer includes a network element microservice governance interface and parsing function, a data layer deployment function, a data layer configuration function and a data layer management function; the data layer includes one or more data layer functions of a socket layer function, a transport layer function, a network layer function and a media access control layer function.

[0081] In an optional implementation, the lifecycle management module 610 includes:

[0082] A request parsing submodule, used for the control layer to receive the governance request of the network element microservice through the network element microservice governance interface, and parse the governance request of the network element microservice to determine the data layer function;

[0083] The cycle management submodule is used for the control layer to perform life cycle management on the data layer according to the function of the data layer.

[0084] In an optional implementation, the network element microservice governance interface includes at least network namespace information of the network element microservice and function information of the data layer; the request parsing submodule includes:

[0085] A network namespace determining unit, configured to determine a network namespace of the network element microservice according to the network namespace information of the network element microservice;

[0086] A data layer function determination unit is used to determine the data layer function in the network namespace of the network element microservice according to the function information of the data layer.

[0087] In an optional implementation, the period management submodule is configured to be used by the control layer to deploy, configure and manage the data layer according to the function of the data layer.

[0088] In an optional implementation, the cycle management submodule is configured to be used by the control layer to deploy the data layer at a corresponding network protocol layer on a network protocol stack of a network namespace of the network element microservice according to the data layer function.

[0089] In an optional implementation, the traffic transmission request is a system call of a network protocol stack of a network namespace, and the system call includes at least the communication traffic of the network element microservice; the communication traffic management module 620 includes:

[0090] A network protocol stack determination submodule, configured to determine, when the data layer receives the system call, the network protocol stack of the network namespace of the network element microservice according to the system call;

[0091] The communication traffic management submodule is used to trigger the function of the data layer of the network protocol layer deployed on the network protocol stack to perform traffic management on the communication traffic when the communication traffic of the network element microservice enters the network protocol stack.

[0092] In an optional embodiment, the communication traffic management submodule is configured to perform one or more of socket layer processing, transport layer processing, network layer processing, and media access control layer processing on the communication traffic through the functions of the data layer.

[0093] The specific details of each module in the above-mentioned network element traffic management device based on layered architecture have been described in detail in the corresponding network element traffic management method based on layered architecture, so they will not be repeated here.

[0094] The exemplary embodiments of the present disclosure also provide a computer-readable storage medium on which a program product capable of implementing the above-mentioned method of this specification is stored. In some possible embodiments, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on an electronic device, the program code is used to cause the electronic device to perform the steps according to various exemplary embodiments of the present disclosure described in the above-mentioned "exemplary method" section of this specification. The program product may adopt a portable compact disk read-only memory (CD-ROM) and include program code, and may be run on an electronic device, such as a personal computer. However, the program product of the present disclosure is not limited thereto, and in this document, a readable storage medium may be any tangible medium containing or storing a program, which may be used by an instruction execution system, an apparatus or a device or used in combination with it.

[0095] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0096] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0097] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0098] Program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0099] The exemplary embodiment of the present disclosure also provides an electronic device capable of implementing the above method. Figure 7 hereinafter, an electronic device 700 according to this exemplary embodiment of the present disclosure is described. Figure 7 The electronic device 700 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0100] like Figure 7 As shown, the electronic device 700 may be in the form of a general-purpose computing device. The components of the electronic device 700 may include, but are not limited to: at least one processing unit 710, at least one storage unit 720, a bus 730 connecting different system components (including the storage unit 720 and the processing unit 710), and a display unit 740.

[0101] The storage unit 720 stores program codes, which can be executed by the processing unit 710, so that the processing unit 710 executes the steps according to various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of this specification. For example, the processing unit 710 can execute Figure 3 The method steps in .

[0102] The storage unit 720 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 721 and / or a cache memory unit 722 , and may further include a read-only memory unit (ROM) 723 .

[0103] The storage unit 720 may also include a program / utility 724 having a set (at least one) of program modules 725, such program modules 725 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0104] Bus 730 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0105] The electronic device 700 may also communicate with one or more external devices 800 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 700, and / or communicate with any device that enables the electronic device 700 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 750. Furthermore, the electronic device 700 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 760. As shown, the network adapter 760 communicates with other modules of the electronic device 700 via a bus 730. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 700, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0106] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the exemplary implementation of the present disclosure.

[0107] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to the exemplary embodiment of the present disclosure, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0108] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0109] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A network element traffic management method based on a layered architecture, characterized in that: The layered architecture includes a control layer and a data layer; the method includes: The control layer responds to the governance request of the network element microservice, performs lifecycle management on the data layer, so as to establish a communication connection between the data layer and the network element microservice, the control layer includes a network element microservice governance interface, the data layer includes data layer functions, and the network element microservice governance interface includes at least network namespace information of the network element microservice and function information of the data layer; When the data layer receives the traffic transmission request initiated by the network element microservice, it performs traffic management on the communication traffic of the network element microservice; The control layer responds to the governance request of the network element microservice and performs lifecycle management on the data layer, and further includes: determining the network namespace of the network element microservice according to the network namespace information of the network element microservice; The data layer function in the network namespace of the network element microservice is determined according to the function information of the data layer.

2. The network element traffic management method according to claim 1, characterized in that: The control layer includes a network element microservice governance interface and parsing function, a data layer deployment function, a data layer configuration function, and a data layer management function; the data layer includes one or more data layer functions of a socket layer function, a transport layer function, a network layer function, and a media access control layer function.

3. The network element traffic management method according to claim 2, characterized in that: The control layer responds to the governance request of the network element microservice and performs lifecycle management on the data layer, including: The control layer receives the governance request of the network element microservice through the network element microservice governance interface, and parses the governance request of the network element microservice to determine the function of the data layer; The control layer performs lifecycle management on the data layer according to the function of the data layer.

4. The network element traffic management method according to claim 1, characterized in that: The control layer performs lifecycle management on the data layer according to the function of the data layer, including: The control layer deploys, configures and manages the data layer according to the functions of the data layer.

5. The network element traffic management method according to claim 4, characterized in that: The control layer deploys the data layer according to the function of the data layer, including: The control layer deploys the data layer at a corresponding network protocol layer on a network protocol stack of a network namespace of the network element microservice according to a function of the data layer.

6. The network element traffic management method according to claim 1, characterized in that: The traffic transmission request is a system call of a network protocol stack of a network namespace, and the system call includes at least the communication traffic of the network element microservice; When the data layer receives the traffic transmission request initiated by the network element microservice, traffic management is performed on the communication traffic of the network element microservice, including: When the data layer receives the system call, it determines the network protocol stack of the network namespace of the network element microservice according to the system call; When the communication traffic of the network element microservice enters the network protocol stack, the function of the data layer of the corresponding network protocol layer deployed on the network protocol stack is triggered to perform traffic management on the communication traffic.

7. The network element traffic management method according to claim 6, characterized in that: The corresponding triggering of the data layer function of the network protocol layer deployed on the network protocol stack to perform traffic management on the communication traffic includes: The communication traffic is subjected to one or more of socket layer processing, transport layer processing, network layer processing, and media access control layer processing through the function of the data layer.

8. A network element traffic management device based on a layered architecture, characterized in that: The layered architecture includes a control layer and a data layer; the device includes: A lifecycle management module, used for the control layer to respond to the governance request of the network element microservice, perform lifecycle management on the data layer, so as to establish a communication connection between the data layer and the network element microservice, the control layer includes a network element microservice governance interface, the data layer includes data layer functions, and the network element microservice governance interface includes at least network namespace information of the network element microservice and function information of the data layer; A communication traffic management module, used for managing the communication traffic of the network element microservice when the data layer receives a traffic transmission request initiated by the network element microservice; The lifecycle management module is further used to determine the network namespace of the network element microservice according to the network namespace information of the network element microservice; and determine the data layer function in the network namespace of the network element microservice according to the function information of the data layer.

9. A network element traffic management system based on a layered architecture, characterized in that: The layered architecture includes a control layer and a data layer, and the system includes: A network element microservice is used to send a governance request to the control layer and a traffic transmission request to the data layer, wherein the control layer includes a network element microservice governance interface, the data layer includes data layer functions, and the network element microservice governance interface includes at least network namespace information of the network element microservice and function information of the data layer; The control layer is used to respond to the governance request of the network element microservice and perform lifecycle management on the data layer to establish a communication connection between the data layer and the network element microservice; The data layer is used to perform traffic management on the communication traffic of the network element microservice when receiving the traffic transmission request initiated by the network element microservice; The control layer is further used to determine the network namespace of the network element microservice according to the network namespace information of the network element microservice; and determine the data layer function in the network namespace of the network element microservice according to the function information of the data layer.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

11. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to perform the method of any one of claims 1 to 7 by executing the executable instructions.

Images