CN113938422A - Flow distribution method and device and electronic equipment - Google Patents
Flow distribution method and device and electronic equipment Download PDFInfo
- Publication number
- CN113938422A CN113938422A CN202111185219.XA CN202111185219A CN113938422A CN 113938422 A CN113938422 A CN 113938422A CN 202111185219 A CN202111185219 A CN 202111185219A CN 113938422 A CN113938422 A CN 113938422A
- Authority
- CN
- China
- Prior art keywords
- traffic
- label
- provider
- request
- flow
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/38—Flow based routing
Abstract
An embodiment of the present specification provides a traffic allocation method, which provides a tag customization interface, performs tag setting on a traffic requester through the tag customization interface, configures a routing rule, determines a type of the tag, performs matching from tags of method traffic providers if the tag is a method tag, performs matching from tags of service traffic providers if the tag is a service tag, allocates a traffic request to a matched traffic provider, performs degradation processing on the traffic request to a traffic provider without a tag if the tag is not a service tag, and provides traffic for the traffic request after traffic routing. The routing is carried out in a mode of label self-matching without redevelopment every time, thereby improving the flexibility.
Description
Technical Field
The present application relates to the field of computers, and in particular, to a method and an apparatus for allocating traffic and an electronic device.
Background
The transmission of data forms traffic, and when providing services, it is often necessary to distribute traffic, which is actually to match traffic demanders with traffic providers.
In many conventional matching methods, a traffic provider is defined in advance by software definition, a routing script is developed, and when a traffic is distributed, the routing script is executed to distribute the traffic. However, this approach requires new scripts to be developed each time, and is less flexible. This is because the routing script actually uses the traffic provider's identification directly, requiring re-development whenever routing to a new traffic provider is required.
Therefore, there is a need to provide a new traffic distribution method.
Disclosure of Invention
The embodiment of the specification provides a flow distribution method, a flow distribution device and electronic equipment, which are used for improving flexibility.
An embodiment of the present specification further provides a traffic distribution method, including:
providing a label self-defining interface, and setting a label for a flow requester and configuring a routing rule through the label self-defining interface;
determining the type of the label, and if the label is a method type label, matching from the labels of the method type flow providers;
if the label is a service label, matching from the labels of the service flow providers;
distributing the traffic request to a matched traffic provider, and if the traffic request is not matched with the traffic provider, distributing the traffic request degradation processing to a traffic provider without a label;
after traffic routing, the traffic provider provides traffic to the traffic request.
Optionally, the method further comprises:
determining the matched traffic common provider of the same group of traffic providers;
the traffic provider provides traffic to the traffic request, further comprising:
distributing the traffic request to the matched traffic co-provider, which provides traffic for the traffic request.
Optionally, the allocating the traffic request to the matched traffic common provider includes:
and when the matched running state of the flow provider meets a preset load condition, triggering a flow circulation task: and distributing the traffic request to the matched traffic common provider.
Optionally, the method further comprises:
grading the method type flow providers;
the matching from the label of the method class traffic provider comprises:
and matching the labels according to the priority order of the method class traffic providers.
Optionally, the method further comprises:
and decomposing the flow request to obtain a plurality of subtasks, and distributing the plurality of subtasks to a plurality of method type flow providers respectively to perform distributed flow supply.
Optionally, the method further comprises:
and generating and sending a flow request to the server in response to the task operation of the client user.
Optionally, the traffic request comprises a request to obtain third party data.
An embodiment of the present specification further provides a flow distribution device, including:
the interface module is used for providing a label self-defining interface, performing label setting on a flow requester through the label self-defining interface and configuring a routing rule;
the label matching module is used for determining the type of the label, and if the label is a method type label, matching is carried out from the labels of the method type flow provider;
if the label is a service label, matching from the labels of the service flow providers;
the routing module is used for distributing the traffic request to the matched traffic provider, and if the traffic request is not matched with the traffic provider, the traffic request degradation processing is distributed to the traffic provider without a label;
after traffic routing, the traffic provider provides traffic to the traffic request.
An embodiment of the present specification further provides an electronic device, where the electronic device includes:
a processor; and the number of the first and second groups,
a memory storing a computer executable program which, when executed, causes the processor to perform any of the methods described above.
The present specification also provides a computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement any of the above methods.
In various technical solutions provided in the embodiments of the present specification, a tag is set for a traffic requester through the tag custom interface and a routing rule is configured, a type of the tag is determined, if the tag is a method-class tag, matching is performed from tags of method-class traffic providers, if the tag is a service-class tag, matching is performed from tags of service-class traffic providers, the traffic request is distributed to a matched traffic provider, if the tag is not matched to a traffic provider, the traffic request is distributed to a traffic provider without a tag through a degradation process, and after traffic routing is performed, the traffic provider provides traffic for the traffic request. The routing is carried out in a mode of label self-matching without redevelopment every time, thereby improving the flexibility.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a schematic diagram illustrating a flow distribution method according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a flow distribution device provided in an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure;
fig. 4 is a schematic diagram of a computer-readable medium provided in an embodiment of the present specification.
Detailed Description
Exemplary embodiments of the present invention will now be described more fully with reference to the accompanying drawings. The exemplary embodiments, however, may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these exemplary embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the invention to those skilled in the art. The same reference numerals denote the same or similar elements, components, or parts in the drawings, and thus their repetitive description will be omitted.
Features, structures, characteristics or other details described in a particular embodiment do not preclude the fact that the features, structures, characteristics or other details may be combined in a suitable manner in one or more other embodiments in accordance with the technical idea of the invention.
In describing particular embodiments, the present invention has been described with reference to features, structures, characteristics or other details that are within the purview of one skilled in the art to provide a thorough understanding of the embodiments. One skilled in the relevant art will recognize, however, that the invention may be practiced without one or more of the specific features, structures, characteristics, or other details.
The flow charts shown in the drawings are merely illustrative and do not necessarily include all of the contents and operations/steps, nor do they necessarily have to be performed in the order described. For example, some operations/steps may be decomposed, and some operations/steps may be combined or partially combined, so that the actual execution sequence may be changed according to the actual situation.
The block diagrams shown in the figures are functional entities only and do not necessarily correspond to physically separate entities. I.e. these functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor means and/or microcontroller means.
The term "and/or" and/or "includes all combinations of any one or more of the associated listed items.
Fig. 1 is a schematic diagram of a flow distribution method provided in an embodiment of the present disclosure, where the flow distribution method may include:
s101: and providing a label self-defining interface, and setting a label for the flow requester and configuring a routing rule through the label self-defining interface.
The tag self-defining interface is an interface for a user to set tags, the user can define and generate the tags in an abstract mode, and then the tags can be configured for a traffic requester (a consumer initiating a traffic request) by utilizing the pre-abstracted tags.
Of course, an abstract setting of the tag may be made on-the-spot for a traffic requester.
In embodiments of the present specification, the traffic provider may also be configured with a tag.
Through providing the user-defined interface of the tags, the tags can be abstracted by the user according to the required dimensionality of the user, and the tag mining method is favorable for the tag mining.
In an embodiment of the present specification, the method may further include:
and generating and sending a flow request to the server in response to the task operation of the client user.
In an embodiment of the present specification, the traffic request includes a request to obtain third party data.
In the embodiment of the specification, a tag customization system which can be configured through operation can be provided, and a tag customization interface is accessed.
In this way, the user can perform the definition of the completion tag by operation.
In the label self-defining system, an editing component can be configured for a user to edit a label, and a marking component can be configured for setting the label of a flow provider by using the label generated by editing.
The routing rule may be a rule that matches a traffic provider for a traffic requester by means of label matching.
S102: determining the type of the label, and if the label is a method type label, matching from the labels of the method type flow providers;
and if the label is the service class label, matching from the labels of the service class flow providers.
Considering that the multiple labels need to be traversed when directly matching among the multiple labels, and the difference between the traffic providers cannot be reflected, in practical application, the traffic providers often have a priority order, so in order to improve matching efficiency and meet the priority requirement, we can classify the traffic providers, preferentially match the traffic providers at certain levels, and if the matching is unsuccessful, perform degraded matching.
Thus, the matching efficiency can be improved, and the traffic can be provided according to the priority.
The classification mode of the labels can have different dimensions, and a category can be determined under each dimension.
For example, in one case, the tags may be classified into method class tags or service class tags, in another case, the classes of the tags may also be classified according to different service providers of the tags, the tags may also be classified into different classes, each class represents a class, and specific ways of classifying the classes of the tags are not specifically set forth and limited herein.
Therefore, in the embodiment of the present specification, the traffic providers can be classified into method class traffic providers and service class traffic providers, and we can match the method class traffic providers for the traffic requests, and if not, downgrade the traffic providers to the service class traffic providers to perform matching.
In specific implementation, the type of the tag may be determined according to information carried in the traffic request, for example, a traffic requester identifier carried in the traffic request, and the traffic requester queries the tag that the traffic requester has, and determines whether the traffic requester has a method type tag.
And if the traffic requester has the method class label, matching according to the labels of a plurality of method class traffic providers, and determining the method class traffic provider matched with the traffic requester.
If the traffic requester does not have a method class label, it is matched to the service class traffic provider, and if it is not matched, it is matched to the traffic provider from among the traffic providers without labels.
Thus, in embodiments of the present description, the method may comprise:
and if the method class traffic provider is not matched, matching from the label of the service class traffic provider.
Considering that even there are differences between method class traffic providers, we can also prioritize and then match according to this priority within the method class traffic providers.
Therefore, in the embodiment of the present specification, the method may further include:
grading the method type flow providers;
the matching from the label of the method class traffic provider comprises:
and matching the labels according to the priority order of the method class traffic providers.
In this way, tag match filtering for providers can be implemented.
Specifically, the method-class traffic provider may be classified according to the load of the method-class traffic provider, so that the traffic provider with a small load can provide traffic preferentially to implement load balancing.
Of course, the classification may also be performed according to the reliability of the traffic provider, and the traffic provider with high reliability is preferentially allowed to provide the traffic, which is not described in detail herein.
S103: distributing the traffic request to a matched traffic provider, and if the traffic request is not matched with the traffic provider, distributing the traffic request degradation processing to a traffic provider without a label;
after traffic routing, the traffic provider provides traffic to the traffic request.
And performing label setting and routing rule configuration on a traffic requester through the label custom interface, determining the type of the label, matching from the labels of the method traffic providers if the label is the method label, matching from the labels of the service traffic providers if the label is the service label, distributing the traffic request to the matched traffic providers, performing degradation processing on the traffic request to the traffic providers without labels if the label is not the service label, and providing traffic for the traffic request by the traffic providers after traffic routing. The routing is carried out in a mode of label self-matching without redevelopment every time, thereby improving the flexibility.
In this embodiment, it is considered that the demanded quantity and the offered quantity of the traffic may not match, because we may let multiple traffic providers provide the traffic for the same traffic request, the traffic request may be circulated between different traffic providers according to a time sequence, or the traffic may be provided by multiple traffic providers at the same time.
In a specific implementation, the plurality of traffic providers may be divided into a same group, and a common provider of traffic in the same group may provide traffic for the traffic request.
Therefore, in the embodiment of the present specification, the method may further include:
determining the matched traffic common provider of the same group of traffic providers;
the traffic provider provides traffic to the traffic request, further comprising:
distributing the traffic request to the matched traffic co-provider, which provides traffic for the traffic request.
And flow isolation is realized by restricting the flow to flow only in the preset packet.
In consideration of practical application, the flow can be set under conditions, when the conditions are met, the flow is circulated, and when the conditions are not met, the flow only needs to be provided by one matched flow provider.
In this embodiment, the allocating the traffic request to the matched traffic common provider includes:
and when the matched running state of the flow provider meets a preset load condition, triggering a flow circulation task: and distributing the traffic request to the matched traffic common provider.
Considering the practical application, the traffic request may be a complex request, which may have multiple nodes or multiple branches, and we may decompose it, and then provide the traffic in a distributed manner.
In an embodiment of the present specification, the method may further include:
and decomposing the flow request to obtain a plurality of subtasks, and distributing the plurality of subtasks to a plurality of method type flow providers respectively to perform distributed flow supply.
In this embodiment of the present specification, parallel nodes in an execution link of a traffic request may be decomposed into subtasks for distributed traffic provision, so that the execution of the subtasks may be performed synchronously, thereby reducing the execution time of the entire traffic request and increasing the response speed, or certainly, the traffic request may be decomposed in segments, which is not described in detail herein.
Fig. 2 is a schematic structural diagram of a flow distribution device provided in an embodiment of the present disclosure, where the flow distribution device may include:
the interface module 201 is configured to provide a tag custom interface, perform tag setting on a traffic requester through the tag custom interface, and configure a routing rule;
the tag matching module 202 is configured to determine the type of the tag, and if the tag is a method type tag, perform matching from tags of a method type traffic provider;
if the label is a service label, matching from the labels of the service flow providers;
the routing module 203 allocates the traffic request to the matched traffic provider, and if the traffic request is not matched with the traffic provider, allocates the traffic request degradation processing to the traffic provider without a label;
after traffic routing, the traffic provider provides traffic to the traffic request.
In an embodiment of the present specification, the apparatus may further include:
and the response module is used for responding to the task operation of the client user and generating and sending the flow request to the server.
Optionally, the traffic request comprises a request to obtain third party data.
In this embodiment, it is considered that the demanded quantity and the offered quantity of the traffic may not match, because we may let multiple traffic providers provide the traffic for the same traffic request, the traffic request may be circulated between different traffic providers according to a time sequence, or the traffic may be provided by multiple traffic providers at the same time.
In a specific implementation, the plurality of traffic providers may be divided into a same group, and a common provider of traffic in the same group may provide traffic for the traffic request.
In an embodiment of the present specification, the apparatus may further include:
the same group constraint module is used for determining the matched flow common providers of the same group of flow providers;
the traffic provider provides traffic to the traffic request, further comprising:
distributing the traffic request to the matched traffic co-provider, which provides traffic for the traffic request.
The condition for the peer constraint module to trigger traffic requests to circulate in the peer may be that the load of the traffic provider currently providing traffic support exceeds a threshold.
Therefore, in this embodiment of the present specification, the allocating the traffic request to the matched common traffic provider may specifically include:
and when the matched running state of the flow provider meets a preset load condition, triggering a flow circulation task: and distributing the traffic request to the matched traffic common provider.
In an embodiment of the present specification, the apparatus may further include:
the level division module is used for carrying out level division on the method type flow provider;
the matching from the label of the method class traffic provider comprises:
and matching the labels according to the priority order of the method class traffic providers.
In an embodiment of the present specification, the apparatus may further include:
the task decomposition module is used for decomposing the flow request to obtain a plurality of subtasks;
in this way, the routing module 203 is further configured to distribute the plurality of sub-requests to the plurality of method traffic providers, respectively, to perform distributed traffic provision.
The specific decomposition mode may be to decompose parallel nodes in an execution link of the traffic request into subtasks, so that the execution of the subtasks can be performed synchronously, thereby shortening the execution time of the entire traffic request and increasing the response speed.
Or the flow request can be segmented and decomposed.
The device sets a label for a flow requester through the label custom interface and configures a routing rule, determines the type of the label, matches the label from a label of a method type flow provider if the label is a method type label, matches the label from the label of a service type flow provider if the label is a service type label, distributes the flow request to the matched flow provider, distributes the flow request to the flow provider without the label if the label is not matched with the flow provider, and provides flow for the flow request by the flow provider after flow routing. The routing is carried out in a mode of label self-matching without redevelopment every time, thereby improving the flexibility.
Based on the same inventive concept, the embodiment of the specification further provides the electronic equipment.
In the following, embodiments of the electronic device of the present invention are described, which may be regarded as specific physical implementations for the above-described embodiments of the method and apparatus of the present invention. Details described in the embodiments of the electronic device of the invention should be considered supplementary to the embodiments of the method or apparatus described above; for details which are not disclosed in embodiments of the electronic device of the invention, reference may be made to the above-described embodiments of the method or the apparatus.
Fig. 3 is a schematic structural diagram of an electronic device provided in an embodiment of the present disclosure. An electronic device 300 according to this embodiment of the invention is described below with reference to fig. 3. The electronic device 300 shown in fig. 3 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 3, electronic device 300 is embodied in the form of a general purpose computing device. The components of electronic device 300 may include, but are not limited to: at least one processing unit 310, at least one memory unit 320, a bus 330 connecting the various system components (including the memory unit 320 and the processing unit 310), a display unit 340, and the like.
Wherein the storage unit stores program code executable by the processing unit 310 to cause the processing unit 310 to perform the steps according to various exemplary embodiments of the present invention described in the above-mentioned processing method section of the present specification. For example, the processing unit 310 may perform the steps as shown in fig. 1.
The storage unit 320 may include readable media in the form of volatile storage units, such as a random access memory unit (RAM)3201 and/or a cache storage unit 3202, and may further include a read only memory unit (ROM) 3203.
The storage unit 320 may also include a program/utility 3204 having a set (at least one) of program modules 3205, such program modules 3205 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 thereof, may comprise an implementation of a network environment.
The electronic device 300 may also communicate with one or more external devices 400 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 300, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 300 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 350. Also, the electronic device 300 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 360. Network adapter 360 may communicate with other modules of electronic device 300 via bus 330. It should be appreciated that although not shown in FIG. 3, other hardware and/or software modules may be used in conjunction with electronic device 300, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments of the present invention described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiment of the present invention can be embodied in the form of a software product, which can be stored in a computer-readable storage medium (which can be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to make a computing device (which can be a personal computer, a server, or a network device, etc.) execute the above-mentioned method according to the present invention. The computer program, when executed by a data processing apparatus, enables the computer readable medium to implement the above-described method of the invention, namely: such as the method shown in fig. 1.
Fig. 4 is a schematic diagram of a computer-readable medium provided in an embodiment of the present specification.
A computer program implementing the method shown in fig. 1 may be stored on one or more computer readable media. The computer readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable storage medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable storage medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind 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).
In summary, the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that some or all of the functionality of some or all of the components in embodiments in accordance with the invention may be implemented in practice using a general purpose data processing device such as a microprocessor or a Digital Signal Processor (DSP). The present invention may also be embodied as apparatus or device programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
While the foregoing embodiments have described the objects, aspects and advantages of the present invention in further detail, it should be understood that the present invention is not inherently related to any particular computer, virtual machine or electronic device, and various general-purpose machines may be used to implement the present invention. The invention is not to be considered as limited to the specific embodiments thereof, but is to be understood as being modified in all respects, all changes and equivalents that come within the spirit and scope of the invention.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments.
The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for allocating traffic, comprising:
providing a label self-defining interface, and setting a label for the flow requester and configuring a routing rule through the label self-defining interface;
determining the type of the label, and if the label is a method type label, matching from the labels of the method type flow providers;
if the label is a service label, matching from the labels of the service flow providers;
distributing the traffic request to a matched traffic provider, and if the traffic request is not matched with the traffic provider, distributing the traffic request degradation processing to a traffic provider without a label;
after traffic routing, the traffic provider provides traffic to the traffic request.
2. The method of claim 1, further comprising:
the matched traffic provider is determined to be a same group of traffic common providers;
the traffic provider provides traffic to the traffic request, further comprising:
distributing the traffic request to the matched traffic co-provider, which provides traffic for the traffic request.
3. The method according to any of claims 1-2, wherein said distributing the traffic requests to the matched traffic co-providers comprises:
and when the matched running state of the flow provider meets a preset load condition, triggering a flow circulation task: and distributing the traffic request to the matched traffic common provider.
4. The method according to any one of claims 1-3, further comprising:
grading the method type flow providers;
the matching from the label of the method class traffic provider comprises:
and matching the labels according to the priority order of the method class traffic providers.
5. The method according to any one of claims 1-4, further comprising:
and decomposing the flow request to obtain a plurality of subtasks, and distributing the plurality of subtasks to a plurality of method type flow providers respectively to perform distributed flow supply.
6. The method according to any one of claims 1-5, further comprising:
and generating and sending a flow request to the server in response to the task operation of the client user.
7. The method of any of claims 1-6, wherein the traffic request comprises a request to obtain third party data.
8. A flow distribution device, comprising:
the interface module is used for providing a label self-defining interface, performing label setting on a flow requester through the label self-defining interface and configuring a routing rule;
the label matching module is used for determining the type of the label, and if the label is a method type label, matching is carried out from the labels of the method type flow provider;
if the label is a service label, matching from the labels of the service flow providers;
the routing module is used for distributing the traffic request to the matched traffic provider, and if the traffic request is not matched with the traffic provider, the traffic request degradation processing is distributed to the traffic provider without a label;
after traffic routing, the traffic provider provides traffic to the traffic request.
9. An electronic device, wherein the electronic device comprises:
a processor; and the number of the first and second groups,
a memory storing computer-executable instructions that, when executed, cause the processor to perform the method of any of claims 1-7.
10. A computer readable storage medium, wherein the computer readable storage medium stores one or more programs which, when executed by a processor, implement the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111185219.XA CN113938422B (en) | 2021-10-12 | 2021-10-12 | Flow distribution method and device and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111185219.XA CN113938422B (en) | 2021-10-12 | 2021-10-12 | Flow distribution method and device and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113938422A true CN113938422A (en) | 2022-01-14 |
| CN113938422B CN113938422B (en) | 2023-02-24 |
Family
ID=79278683
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111185219.XA Active CN113938422B (en) | 2021-10-12 | 2021-10-12 | Flow distribution method and device and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113938422B (en) |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080002697A1 (en) * | 2006-07-03 | 2008-01-03 | Anantharamaiah Prasanna | Method, appratus, and system for capturing traffic statistics between two sites of mpls based vpn |
| US7512702B1 (en) * | 2002-03-19 | 2009-03-31 | Cisco Technology, Inc. | Method and apparatus providing highly scalable server load balancing |
| US20090259736A1 (en) * | 2008-04-15 | 2009-10-15 | Juniper Networks, Inc. | Label-based target host configuration for a server load balancer |
| WO2011073460A1 (en) * | 2009-12-15 | 2011-06-23 | Telefonica, S.A. | System and method for generating trust among data network users |
| US20110271007A1 (en) * | 2010-04-28 | 2011-11-03 | Futurewei Technologies, Inc. | System and Method for a Context Layer Switch |
| WO2016156249A1 (en) * | 2015-03-31 | 2016-10-06 | British Telecommunications Public Limited Company | Content playback management |
| CN109242235A (en) * | 2018-07-04 | 2019-01-18 | 江苏寓见旅行社有限公司 | Data processing method and system based on interpersonal relationships |
| US10187289B1 (en) * | 2015-12-28 | 2019-01-22 | Amazon Technologies, Inc. | Route advertisement management using tags in directly connected networks |
| CN111177093A (en) * | 2019-12-31 | 2020-05-19 | 山东蚁动网络科技有限公司 | Method, device and medium for sharing scientific and technological resources |
| CN111626796A (en) * | 2020-07-29 | 2020-09-04 | 北京搜狐新媒体信息技术有限公司 | Flow estimation method and device |
| CN112381563A (en) * | 2020-11-02 | 2021-02-19 | 上海淇玥信息技术有限公司 | Automatic label generation method and device and electronic equipment |
-
2021
- 2021-10-12 CN CN202111185219.XA patent/CN113938422B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7512702B1 (en) * | 2002-03-19 | 2009-03-31 | Cisco Technology, Inc. | Method and apparatus providing highly scalable server load balancing |
| US20080002697A1 (en) * | 2006-07-03 | 2008-01-03 | Anantharamaiah Prasanna | Method, appratus, and system for capturing traffic statistics between two sites of mpls based vpn |
| US20090259736A1 (en) * | 2008-04-15 | 2009-10-15 | Juniper Networks, Inc. | Label-based target host configuration for a server load balancer |
| WO2011073460A1 (en) * | 2009-12-15 | 2011-06-23 | Telefonica, S.A. | System and method for generating trust among data network users |
| US20110271007A1 (en) * | 2010-04-28 | 2011-11-03 | Futurewei Technologies, Inc. | System and Method for a Context Layer Switch |
| WO2016156249A1 (en) * | 2015-03-31 | 2016-10-06 | British Telecommunications Public Limited Company | Content playback management |
| US10187289B1 (en) * | 2015-12-28 | 2019-01-22 | Amazon Technologies, Inc. | Route advertisement management using tags in directly connected networks |
| CN109242235A (en) * | 2018-07-04 | 2019-01-18 | 江苏寓见旅行社有限公司 | Data processing method and system based on interpersonal relationships |
| CN111177093A (en) * | 2019-12-31 | 2020-05-19 | 山东蚁动网络科技有限公司 | Method, device and medium for sharing scientific and technological resources |
| CN111626796A (en) * | 2020-07-29 | 2020-09-04 | 北京搜狐新媒体信息技术有限公司 | Flow estimation method and device |
| CN112381563A (en) * | 2020-11-02 | 2021-02-19 | 上海淇玥信息技术有限公司 | Automatic label generation method and device and electronic equipment |
Non-Patent Citations (4)
| Title |
|---|
| 刘志坚等: "多运营商宽带接入方案", 《江苏通信》 * |
| 吕庆聪等: "一种普适计算环境下基于语义的服务匹配算法", 《计算机应用》 * |
| 彭薇: "一种改进的语义Web服务匹配算法", 《现代图书情报技术》 * |
| 梁咏等: "一种基于语义的Web服务匹配算法", 《微型电脑应用》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113938422B (en) | 2023-02-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109274731B (en) | Method and device for deploying and calling web service based on multi-tenant technology | |
| US20190097942A1 (en) | Orchestrating computing resources between different computing environments | |
| CN107431651B (en) | Life cycle management method and equipment for network service | |
| US10264059B2 (en) | Determining server level availability and resource allocations based on workload level availability requirements | |
| CN110688096B (en) | Method and device for constructing application program containing plug-in, medium and electronic equipment | |
| CN109032751B (en) | Virtual machine deployment method and OMM virtual machine | |
| CN103631636A (en) | Enabling multi-tenancy for a commerce server | |
| CN110795315A (en) | Method and device for monitoring service | |
| CN110888639A (en) | Business code compiling and packaging method and device | |
| CN111381899A (en) | Method and apparatus for developing target system | |
| CN112817562A (en) | Service processing method and device | |
| CN113779004A (en) | Data verification method and device | |
| CN113938422B (en) | Flow distribution method and device and electronic equipment | |
| CN111211998A (en) | Resource allocation method and device capable of elastically expanding capacity and electronic equipment | |
| CN112232856A (en) | Traffic processing method and device based on diversion and electronic equipment | |
| CN111612501A (en) | Information generation method and device based on policy reuse and electronic equipment | |
| CN115629853A (en) | Task scheduling method and device | |
| CN111681093B (en) | Method and device for displaying resource page and electronic equipment | |
| TW202315360A (en) | Microservice allocation method, electronic equipment, and storage medium | |
| CN113568623A (en) | Application deployment method and device and electronic equipment | |
| CN113312900A (en) | Data verification method and device | |
| CN113806225A (en) | Method and device for identifying service abnormal node and electronic equipment | |
| CN111953581B (en) | Method and device for managing template message task and electronic equipment | |
| US10417055B2 (en) | Runtime movement of microprocess components | |
| CN113157341B (en) | Resource environment self-adaptive processing method and device of object and electronic equipment |
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 |