CN114615213B - Method and system for implementing multi-network link interface based on message queue - Google Patents
Method and system for implementing multi-network link interface based on message queue Download PDFInfo
- Publication number
- CN114615213B CN114615213B CN202210091531.0A CN202210091531A CN114615213B CN 114615213 B CN114615213 B CN 114615213B CN 202210091531 A CN202210091531 A CN 202210091531A CN 114615213 B CN114615213 B CN 114615213B
- Authority
- CN
- China
- Prior art keywords
- link
- management object
- physical
- link management
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 30
- 239000011159 matrix material Substances 0.000 claims abstract description 50
- 238000003860 storage Methods 0.000 claims abstract description 7
- 238000004590 computer program Methods 0.000 claims description 11
- 230000005856 abnormality Effects 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 3
- 230000001174 ascending effect Effects 0.000 claims 1
- 238000011161 development Methods 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000004075 alteration Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000006855 networking Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 238000011144 upstream manufacturing Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000005304 joining Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000026676 system process Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/62—Queue scheduling characterised by scheduling criteria
- H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
- H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to a method, a system and a storage medium for realizing a multi-network link interface based on a message queue, wherein the method comprises the following steps: enabling a plurality of physical interfaces and respectively connecting the physical interfaces to a message queue component; starting a link management object corresponding to each physical interface; registering the link management object with the message queue component; sending a corresponding event to the corresponding link management object, and configuring the corresponding physical interface according to the event through the corresponding link management object, wherein the event comprises an enabling event; and constructing a link decision matrix according to the working state of the physical interface, and when uplink application data is transmitted, transmitting the uplink application data of the link management objects from a plurality of corresponding link decision matrices. And uplink application data are sent from a plurality of corresponding link management objects through the link decision matrix, so that network links are managed in a layered manner, and the development speed of the system is greatly improved.
Description
Technical Field
The invention relates to the field of network links, in particular to a method and a system for realizing a multi-network link interface based on a message queue.
Background
In modern computer networks, the connection is bi-directional. For a connection to an uplink port, the same cable or wireless link may transmit data between devices at either end and the other, the uplink being used to upload data.
In the traditional network switching mode, a plurality of global variables, signals and the like are often used for realizing network switching, and a plurality of interfaces cannot be simultaneously optimized along with system load change, because of the complexity of the system, a plurality of unavoidable competition states are often brought in the use of the global variables, each physical interface has a corresponding global variable, the complexity of interface combination switching is exponentially increased due to more and more variables, the use of resources is abnormal, and the system is unstable during multi-link uplink.
How to stabilize and fast network interfaces among multiple uplink data interfaces according to each network interface and application load is a problem that each multi-link uplink device primarily solves. The conventional uplink supports a plurality of physical interfaces, but cannot use a plurality of physical interfaces at the same time, and only one of the interfaces can be used even if a plurality of physical interfaces are available, or only a certain number of interfaces can be used at the same time, and there is no way to aggregate data according to the system load requirements. Meanwhile, conventional uplink network handover often causes errors of handover logic when facing multiple input sources, such as a user suddenly needs to switch to uplink B when using uplink a networking; for example, in the uplink A networking process, a certain IO signal is input to require that the uplink A is re-enabled; due to incorrect operation of global variables or semaphores, there is a high probability that the overall link state will be inconsistent, leading to uplink state handoff failure.
The invention aims at solving the problems existing in the prior art and designs a method and a system for realizing a multi-network link interface based on a message queue.
Disclosure of Invention
Aiming at the problems in the prior art, the invention aims to provide a method and a system for realizing a multi-network link interface based on a message queue, which can effectively solve the problems in the prior art.
The technical scheme of the invention is as follows:
a method for realizing a multi-network link interface based on a message queue comprises the following steps:
enabling a plurality of physical interfaces and respectively connecting the physical interfaces to a message queue component;
starting a link management object corresponding to each physical interface;
registering the link management object with the message queue component;
sending a corresponding event to the corresponding link management object, and configuring the corresponding physical interface according to the event through the corresponding link management object, wherein the event comprises an enabling event;
and constructing a link decision matrix according to the working state of the physical interface, and when uplink application data is transmitted, transmitting the uplink application data of the link management objects from a plurality of corresponding link decision matrices.
Further, constructing a link decision matrix according to the working state of the physical interface, and before uplink application data of a plurality of corresponding link management objects through the link decision matrix, comprising the following steps:
acquiring a connection state and an enabling state of each physical interface, judging and outputting the physical interface which can work currently;
acquiring and outputting the connection priority of each physical interface;
the working state at least comprises the connection state, the starting state and the connection priority, and a link decision matrix is constructed according to the connection state, the starting state and the connection priority.
Further, the uplink application data from a plurality of corresponding link management objects through the link decision matrix comprises the following steps:
if the number of the physical interfaces which can work currently is one, transmitting the application data to the physical interfaces which can work currently, judging whether the link management object corresponding to the physical interfaces which can work currently is effective or not, and if so, uploading the application data through the corresponding link management object.
Further, the uplink application data from a plurality of corresponding link management objects through the link decision matrix comprises the following steps:
if the number of the physical interfaces which can work currently is a plurality of, transmitting the application data to any one of the physical interfaces which can work currently, judging whether the link management object corresponding to the physical interfaces which can work currently is effective or not, and uploading the application data through the interface which is effective by the link management object.
Further, if the number of the interfaces which are effective by the link management object is a plurality of interfaces, and the flow required by the application data is greater than a first threshold, the application data is simultaneously uplink through the interfaces which are effective by the link management object;
and if the number of the effective interfaces of the link management object is a plurality of interfaces and the flow required by the application data is smaller than a first threshold value, the application data is time-sharing uplink through the effective interfaces of the link management object.
Further, a virtual physical interface is included that is configured to be deferrable and/or bootable on demand.
Further, in response to the event and/or the user operation, joining the virtual physical interface, registering a link management object corresponding to the virtual physical interface to the message queue component, registering the virtual physical interface to a system, and uploading the application data together through the link management object corresponding to the virtual physical interface and the link management object corresponding to the physical interface.
Further, the method comprises the following steps:
and in response to the physical interface abnormality, notifying the message queue component through the link management object, restarting the corresponding physical interface and/or starting other physical interfaces through the event.
A system for implementing a multiple network link interface based on message queues, comprising the following modules:
the physical interface starting module is used for starting a plurality of physical interfaces and respectively connecting the physical interfaces to the message queue component;
the link management object starting module is used for starting the link management object corresponding to each physical interface;
a registration module for registering the link management object with the message queue component;
the configuration module is used for sending corresponding events to the corresponding link management objects, and configuring the corresponding physical interfaces according to the events through the corresponding link management objects;
and the decision module is used for constructing a link decision matrix according to the working state of the physical interface, and when uplink application data is transmitted, the link decision matrix is used for managing the object uplink application data from a plurality of corresponding links.
A computer readable storage medium storing a computer program which when executed by a processor implements the method for implementing a message queue based multi-network link interface.
Accordingly, the present invention provides the following effects and/or advantages:
the invention constructs the link decision matrix for the working states of a plurality of physical interfaces, and uplink application data is sent from a plurality of corresponding link management objects through the link decision matrix, so that network links are managed in a layered manner, and the development speed of the system is greatly improved.
By introducing the decision matrix, the complexity of the system is greatly reduced, the expandability is increased, and the introduction of errors is reduced.
The invention can realize the parallel online of a plurality of physical ports and simplify the software operation. Meanwhile, the invention can register to the system when the virtual physical interface is needed/accessed through processing the virtual physical interface, and the system processes the virtual physical interface as a physical interface, and adds the virtual physical interface into a cluster of the physical interface to perform parallel uplink.
It is to be understood that both the foregoing general description and the following detailed description of the present invention are exemplary and explanatory and are intended to provide further explanation of the invention as claimed.
Drawings
Fig. 1 is a schematic diagram of a prior art framework.
FIG. 2 is a flow chart of the present invention.
Fig. 3 is a schematic diagram of the framework of the present invention.
Detailed Description
For the purpose of facilitating understanding to those skilled in the art, the present invention will now be described in further detail with reference to the accompanying drawings: it should be understood that, in this embodiment, the steps mentioned in this embodiment, unless specifically stated otherwise, may be performed in any order, simultaneously or partially simultaneously,
referring to fig. 2-3, a method for implementing a multi-network link interface based on message queues includes the steps of:
s1, a plurality of physical interfaces are started, and the physical interfaces are respectively connected to a message queue component.
In this step, the physical interface refers to a device such as a wired interface or a wireless interface, and is a hardware interface between different devices and components in the system. Meanwhile, before this step, a link Manager (also referred to as a link management Manager) is started, and then a physical interface is started according to system configuration through the link Manager. The link manager is a self-defined module used for starting each physical interface. The message queue component commonly used, such as redis/moquitto, can be essentially considered a first-in, first-out queue for outputting messages in a first-in, first-out order. The link manager of this step may subscribe to a topic and receive a message if it arrives, which may be equivalent to an event. In this embodiment, physical interface a and physical interface B are started.
S2, starting the link management object corresponding to each physical interface.
And starting a link management object corresponding to the physical interface according to the started physical interface. According to the result of S1, the present embodiment starts the link management object AgentA and the link management object AgentB corresponding to the physical interface a and the physical interface B. The link management object is used to receive the data that the physical interface needs to upload.
And S3, registering the link management object to the message queue component.
In this step, after registration, the link object can only acquire and/or send data from the message queue component. The present embodiment registers the link management object AgentA and the link management object AgentB to the message queue component.
S4, sending a corresponding event to the corresponding link management object, and configuring the corresponding physical interface according to the event through the corresponding link management object, wherein the event comprises an enabling event.
In this step, the event includes an enabling event, and a common event format may have protocols such as jsonrpc. The event of the interface has different events according to different interfaces, for example, the embodiment is an ethernet, when the configuration is static IP, and the network cable is just accessed, an interface enabling event can be generated, because the static state is configured in advance, a protocol enabling event can be continuously generated, and when the interface can be connected to the external network, an online enabling event can be generated.
S4.1, acquiring the connection state and the starting state of each physical interface, judging and outputting the physical interface which can work currently.
This step obtains whether the physical interface is connected with hardware and whether the physical interface is enabled, e.g. has access to ethernet or is wirelessly connected with a network, while the network interface is enabled. And then outputs the physical interface that can currently operate. The physical interfaces currently accessing the network and which can operate are, for example, physical interface a and physical interface B. Then subsequent data will be upstream from the physical interface currently accessing the network and being operational.
And S4.2, acquiring and outputting the connection priority of each physical interface.
This step outputs the priority of the physical interface, e.g. the priority of physical interface a is greater than the priority of physical interface B. Then subsequent data will be upstream from the higher priority physical interface.
And S4.3, the working state at least comprises the connection state, the starting state and the connection priority, and a link decision matrix is constructed according to the connection state, the starting state and the connection priority. The link decision matrix may be represented, for example, by the following matrix:
s5, constructing a link decision matrix according to the working state of the physical interface, and when uplink application data is transmitted, uplink application data of a plurality of corresponding link management objects are transmitted through the link decision matrix.
The present step is a core step of the present invention, in the step S4.3, a link decision matrix is established, when data is required to be uploaded, the data is judged by a first column element included in the link decision matrix, one or more physical interfaces are selected to be optimal, then the data is judged by a second column element included in the link decision matrix, one or more physical interfaces … which continuously meet the condition are selected, and finally the data is judged by an nth column element included in the link decision matrix, and one or more physical interfaces which are all met are selected to be uplink data.
The following describes in detail a number of specific processing steps for uplink application data from a number of corresponding link management objects via the link decision matrix. As shown in fig. 3.
Further, the uplink application data from a plurality of corresponding link management objects through the link decision matrix comprises the following steps:
s5.1, if the number of the physical interfaces which can work currently is one, transmitting the application data to the physical interfaces which can work currently, judging whether the link management object corresponding to the physical interfaces which can work currently is effective or not, and if yes, uploading the application data through the corresponding link management object.
This step is used to handle the situation when only one physical interface is operational. In this embodiment, only the physical interface a can work for example, as shown by the graph represented by only the physical interface a in fig. 3, SA, SB, SC in fig. 3 respectively represent each determination condition in the link decision matrix, the application data will first pass through SA, the SA interface will determine whether the physical interface a is valid according to the data provided by AgentA, and when a is valid, the link decision matrix will continuously confirm whether AgentB is valid, and if not, it will continue. Eventually only a can be used, and the data link is up only from a.
And S5.2, if the number of the physical interfaces which can work currently is a plurality of, transmitting the application data to any one of the physical interfaces which can work currently, judging whether the link management object corresponding to the physical interfaces which can work currently is effective, and uploading the application data through the interface which is effective by the link management object.
This step is used to handle the case interfaces when the physical interface has multiple physical interfaces that can operate. For example, physical interfaces a and B may be operational, as shown by the graph represented by the aggregate uplink for a/B in fig. 3. The application data in the link decision matrix passes through SA firstly, the SA interface judges whether A is effective or not according to the data provided by AgentA, and when A is effective, the link decision matrix continuously confirms whether AgentB is effective or not, B is effective, and the link decision matrix advances rightwards. Eventually, an A/B can be used, and the data link can be simultaneously uplink from the A/B.
Further, s5.2.1, if the number of interfaces for which the link management object is effective is plural, and the flow required by the application data is greater than the first threshold, uplink the application data through the interfaces for which the link management object is effective at the same time;
and if the number of the effective interfaces of the link management object is a plurality of interfaces and the flow required by the application data is smaller than a first threshold value, the application data is time-sharing uplink through the effective interfaces of the link management object.
Further, a virtual physical interface is included that is configured to be deferrable and/or bootable on demand. And responding to the event and/or user operation to join the virtual physical interface, registering a link management object corresponding to the virtual physical interface to the message queue component, registering the virtual physical interface to a system, and uploading the application data through the link management object corresponding to the virtual physical interface and the link management object corresponding to the physical interface.
In this step, the virtual physical interface may be considered as VPN or PPPOE, etc., when the user joins the virtual network actively or passively, or the virtual physical interface accessed actively initiates an enabling event, such as dialing a number of telecommunication accounts. Thus, the virtual physical interface is configured to be re-enabled when needed for use or after a delay of a certain time. The method comprises the steps of registering a link management object corresponding to the virtual physical interface to the message queue component, registering the virtual physical interface to a system, judging the virtual physical interface to be consistent with the physical interface, adding the virtual physical interface in a physical interface mode through the method, and integrating the virtual physical interface into establishment and subsequent judgment of a link decision matrix. In this embodiment, the interface C is a virtual physical interface.
Further, the method comprises the following steps:
s6, responding to the abnormality of the physical interface, notifying the message queue component through the link management object, restarting the corresponding physical interface and/or starting other physical interfaces through the event.
Example two
A system for implementing a multiple network link interface based on message queues, comprising the following modules:
the physical interface starting module is used for starting a plurality of physical interfaces and respectively connecting the physical interfaces to the message queue component;
the link management object starting module is used for starting the link management object corresponding to each physical interface;
a registration module for registering the link management object with the message queue component;
the configuration module is used for sending corresponding events to the corresponding link management objects, and configuring the corresponding physical interfaces according to the events through the corresponding link management objects;
and the decision module is used for constructing a link decision matrix according to the working state of the physical interface, and when uplink application data is transmitted, the link decision matrix is used for managing the object uplink application data from a plurality of corresponding links.
The working principle and the using method of the embodiment are basically the same as those of the first embodiment, and are not repeated.
Example III
A computer readable storage medium storing a computer program which when executed by a processor implements a method for implementing a message queue based multiple network link interface according to embodiment one.
The working principle and the using method of the embodiment are basically the same as those of the first embodiment, and are not repeated.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It should be noted that in the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
In the description of the present invention, it should be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present invention, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.
In the present invention, unless explicitly specified and limited otherwise, the terms "mounted," "connected," "secured," and the like are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally formed; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communicated with the inside of two elements or the interaction relationship of the two elements. The specific meaning of the above terms in the present invention can be understood by those of ordinary skill in the art according to the specific circumstances.
In the present invention, unless expressly stated or limited otherwise, a first feature "up" or "down" a second feature may be the first and second features in direct contact, or the first and second features in indirect contact via an intervening medium. Moreover, a first feature being "above," "over" and "on" a second feature may be a first feature being directly above or obliquely above the second feature, or simply indicating that the first feature is level higher than the second feature. The first feature being "under", "below" and "beneath" the second feature may be the first feature being directly under or obliquely below the second feature, or simply indicating that the first feature is less level than the second feature.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms should not be understood as necessarily being directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.
Claims (9)
1. A method for realizing a multi-network link interface based on a message queue is characterized in that: comprises the following steps:
enabling a plurality of physical interfaces and respectively connecting the physical interfaces to a message queue component;
starting a link management object corresponding to each physical interface;
registering the link management object with the message queue component;
sending a corresponding event to the corresponding link management object, and configuring the corresponding physical interface according to the event through the corresponding link management object, wherein the event comprises an enabling event;
constructing a link decision matrix according to the working state of the physical interfaces, acquiring the connection state and the starting state of each physical interface when uplink application data are transmitted, judging and outputting the physical interfaces which can work currently; acquiring and outputting the connection priority of each physical interface; the working state at least comprises the connection state, the starting state and the connection priority, and a link decision matrix is constructed according to the connection state, the starting state and the connection priority, wherein the link decision matrix is expressed as:
when the link decision matrix is established, the data is judged through a first column element contained in the link decision matrix, the best one or more physical interfaces are selected, then the data is judged through a second column element contained in the link decision matrix, one or more physical interfaces … which continuously meet the condition are selected, and finally the data is judged through an N column element contained in the link decision matrix, and the all met one or more physical interfaces are selected for uplink data;
and uploading application data from a plurality of corresponding link management objects through the link decision matrix.
2. The method for implementing a multi-network link interface based on a message queue according to claim 1, wherein: the uplink application data from a plurality of corresponding link management objects through the link decision matrix comprises the following steps:
if the number of the physical interfaces which can work currently is one, transmitting the application data to the physical interfaces which can work currently, judging whether the link management object corresponding to the physical interfaces which can work currently is effective or not, and if so, uploading the application data through the corresponding link management object.
3. The method for implementing a multi-network link interface based on a message queue according to claim 1, wherein: the uplink application data from a plurality of corresponding link management objects through the link decision matrix comprises the following steps:
if the number of the physical interfaces which can work currently is a plurality of, transmitting the application data to any one of the physical interfaces which can work currently, judging whether the link management object corresponding to the physical interfaces which can work currently is effective or not, and uploading the application data through the interface which is effective by the link management object.
4. The method for implementing a multi-network link interface based on a message queue according to claim 1, wherein: if the number of the effective interfaces of the link management object is a plurality of, and the flow required by the application data is larger than a first threshold, simultaneously ascending the application data through the effective interfaces of the link management object;
and if the number of the effective interfaces of the link management object is a plurality of interfaces and the flow required by the application data is smaller than a first threshold value, the application data is time-sharing uplink through the effective interfaces of the link management object.
5. The method for implementing a multi-network link interface based on a message queue according to claim 1, wherein: a virtual physical interface is included that is configured to be deferrable and/or bootable on demand.
6. The method for implementing a multi-network link interface based on a message queue according to claim 5, wherein: and responding to the event and/or user operation to join the virtual physical interface, registering a link management object corresponding to the virtual physical interface to the message queue component, registering the virtual physical interface to a system, and uploading the application data through the link management object corresponding to the virtual physical interface and the link management object corresponding to the physical interface.
7. The method for implementing a multi-network link interface based on a message queue according to claim 1, wherein: the method comprises the following steps:
and in response to the physical interface abnormality, notifying the message queue component through the link management object, restarting the corresponding physical interface and/or starting other physical interfaces through the event.
8. A multi-network link interface realizing system based on message queue is characterized in that: comprises the following modules:
the physical interface starting module is used for starting a plurality of physical interfaces and respectively connecting the physical interfaces to the message queue component;
the link management object starting module is used for starting the link management object corresponding to each physical interface;
a registration module for registering the link management object with the message queue component;
the configuration module is used for sending a corresponding event to the corresponding link management object, configuring the corresponding physical interface according to the event through the corresponding link management object, acquiring the connection state and the starting state of each physical interface, judging and outputting the physical interface which can work currently; acquiring and outputting the connection priority of each physical interface; the working state at least comprises the connection state, the starting state and the connection priority, and a link decision matrix is constructed according to the connection state, the starting state and the connection priority, wherein the link decision matrix is expressed as follows:
when the link decision matrix is established, the data is judged through a first column element contained in the link decision matrix, the best one or more physical interfaces are selected, then the data is judged through a second column element contained in the link decision matrix, one or more physical interfaces … which continuously meet the condition are selected, and finally the data is judged through an N column element contained in the link decision matrix, and the all met one or more physical interfaces are selected for uplink data;
and the decision module is used for constructing a link decision matrix according to the working state of the physical interface, and when uplink application data is transmitted, the link decision matrix is used for managing the object uplink application data from a plurality of corresponding links.
9. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements a message queue based multi-network link interface implementation method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210091531.0A CN114615213B (en) | 2022-01-26 | 2022-01-26 | Method and system for implementing multi-network link interface based on message queue |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210091531.0A CN114615213B (en) | 2022-01-26 | 2022-01-26 | Method and system for implementing multi-network link interface based on message queue |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114615213A CN114615213A (en) | 2022-06-10 |
| CN114615213B true CN114615213B (en) | 2024-04-12 |
Family
ID=81857431
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210091531.0A Active CN114615213B (en) | 2022-01-26 | 2022-01-26 | Method and system for implementing multi-network link interface based on message queue |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114615213B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102045776A (en) * | 2011-01-11 | 2011-05-04 | 中国科学院计算技术研究所 | Adaptive traffic stream switching method for communication network system and corresponding server |
| CN103677844A (en) * | 2013-12-20 | 2014-03-26 | 国云科技股份有限公司 | Lightweight class data processing frame based on message chain |
| CN110430112A (en) * | 2019-06-26 | 2019-11-08 | 苏州浪潮智能科技有限公司 | A kind of method and apparatus for realizing virtual machine network IO priority |
| CN113973058A (en) * | 2020-07-23 | 2022-01-25 | 华为技术有限公司 | Link management method and communication device |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB2337414A (en) * | 1998-05-14 | 1999-11-17 | Fujitsu Ltd | Soft handoff in cellular communications networks |
| DE10130749A1 (en) * | 2001-06-26 | 2003-01-02 | Philips Corp Intellectual Pty | Packet switching device with feedback coupling for allocation unit has port controller for storing, arranging packets in queues, generating queue state feedback information units for allocation unit |
| US10778809B2 (en) * | 2016-02-26 | 2020-09-15 | Arista Networks, Inc. | Per-input port, per-control plane network data traffic class control plane policing |
| US10341463B2 (en) * | 2017-05-03 | 2019-07-02 | International Business Machines Corporation | System and method for message queue configuration in a network |
| US11122599B2 (en) * | 2017-09-01 | 2021-09-14 | Qualcomm Incorporated | Acknowledgement mechanisms for uplink low latency communications |
-
2022
- 2022-01-26 CN CN202210091531.0A patent/CN114615213B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102045776A (en) * | 2011-01-11 | 2011-05-04 | 中国科学院计算技术研究所 | Adaptive traffic stream switching method for communication network system and corresponding server |
| CN103677844A (en) * | 2013-12-20 | 2014-03-26 | 国云科技股份有限公司 | Lightweight class data processing frame based on message chain |
| CN110430112A (en) * | 2019-06-26 | 2019-11-08 | 苏州浪潮智能科技有限公司 | A kind of method and apparatus for realizing virtual machine network IO priority |
| CN113973058A (en) * | 2020-07-23 | 2022-01-25 | 华为技术有限公司 | Link management method and communication device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114615213A (en) | 2022-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3316555B1 (en) | Mac address synchronization method, device and system | |
| CN109194585B (en) | Message forwarding method and network equipment | |
| JP6004079B2 (en) | Switches and programs | |
| US9998298B2 (en) | Data transmission method, apparatus, and computer storage medium | |
| US9906412B2 (en) | Collaboration method and system in distributed resilient network interconnect system | |
| CN109861925B (en) | Data transmission method, related device and network | |
| US10803004B2 (en) | Modular UPS system and data transmission method for power device | |
| CN105743816B (en) | A kind of link aggregation method and device | |
| CN108092922B (en) | Method and device for transmitting message by interface board | |
| US20130148512A1 (en) | Distributed control plane for link aggregation | |
| CN104158683A (en) | Cross-device aggregation group rapid convergence method, and cross-device aggregation group rapid convergence device | |
| CN107360012B (en) | Link state processing method and network node equipment | |
| CN114615213B (en) | Method and system for implementing multi-network link interface based on message queue | |
| CN105553765A (en) | FC-AV protocol processing chip network communication robustness testing method | |
| CN104394075A (en) | Message transmission method and equipment | |
| EP3537671B1 (en) | Protection switching method and system, and nodes | |
| KR102087874B1 (en) | Pilot setup method and device | |
| US11522762B2 (en) | Coordination device and method for providing control applications via a communication network for transmitting time-critical data | |
| CN113055832B (en) | Method for uniformly managing and sending Beidou short messages of multiple same Beidou devices | |
| JP2003348107A (en) | Two-way linked network, route selecting method used therefor, and program thereof | |
| US10985944B2 (en) | Routing gateway and method for automotive vehicle | |
| CN108616375B (en) | Method and circuit for transmitting data in specified period based on AS5643 protocol | |
| KR100670801B1 (en) | System for testing multiprotocol on next generation network | |
| CN117915048A (en) | Equipment management method and device, vehicle-mounted terminal equipment and storage medium | |
| US9112602B2 (en) | Method of automatically determining link speed for a multispeed fiber link module |
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 |