CN112235203A - Flow distribution method and device - Google Patents
Flow distribution method and device Download PDFInfo
- Publication number
- CN112235203A CN112235203A CN202011113861.2A CN202011113861A CN112235203A CN 112235203 A CN112235203 A CN 112235203A CN 202011113861 A CN202011113861 A CN 202011113861A CN 112235203 A CN112235203 A CN 112235203A
- Authority
- CN
- China
- Prior art keywords
- setting
- micro service
- target
- request
- traffic
- 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.)
- Withdrawn
Links
Images
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/10—Flow control; Congestion control
- H04L47/20—Traffic policing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/63—Routing a service request depending on the request content or context
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The application relates to the technical field of communication networks, in particular to a traffic distribution method and a traffic distribution device. The method comprises the following steps: receiving a setting instruction for setting a flow distribution strategy; and setting the flow distribution strategy according to the setting instruction, wherein the flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and the flow distribution strategy is used for routing an access request to the corresponding micro service when the request end requests to access the micro service. The flow of the user can be accurately controlled, and customized flow control service is realized; the problem of can't accurate control user flow among the prior art is solved.
Description
Technical Field
The present application relates to the field of communications network technologies, and in particular, to a method and an apparatus for allocating traffic.
Background
In complex systems consisting of multiple microservices, the traffic accessing the system is increasingly presenting a trend of complexity, "meshing". How to accurately identify the traffic from a specific user in the complex and complicated traffic and accurately control the version and behavior of accessing each node in the user traffic link has become a problem that needs to be solved in the future.
Disclosure of Invention
In view of this, embodiments of the present application provide a method and an apparatus for allocating traffic to solve the problems in the prior art.
According to a first aspect, an embodiment of the present application provides a traffic distribution method, including:
receiving a setting instruction for setting a flow distribution strategy;
and setting the flow distribution strategy according to the setting instruction, wherein the flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and the flow distribution strategy is used for routing an access request to the corresponding micro service when the request end requests to access the micro service.
Optionally, the setting the flow distribution policy according to the setting instruction includes:
and when the setting instruction is an instruction for setting a first request end for accessing the first micro service for the first micro service, setting an association relation between the first micro service and the request end identification of the first request end according to the setting instruction.
Optionally, the setting the flow distribution policy according to the setting instruction includes:
and when the setting instruction is an instruction for setting a second request end for sending a target access request to access a second micro service, setting an association relation between the second request end and the second micro service according to the setting instruction, wherein the target access request is a request carrying a target identifier.
Optionally, the method includes:
receiving a flow access request sent by a target request end;
acquiring the flow distribution strategy;
determining a target micro service which is requested to be accessed from at least two micro services according to the flow access request and the flow distribution strategy;
routing the traffic access request to the target microservice.
Optionally, the determining, according to the traffic access request and the traffic distribution policy, a target microservice that is requested to be accessed from at least two microservices includes:
and after receiving the flow access request, determining the target micro service corresponding to the request end identification according to the request end identification of the target request end and the flow distribution strategy.
Optionally, the determining, according to the traffic access request and the traffic distribution policy, a target microservice that is requested to be accessed from at least two microservices includes:
when the access request carries a target identifier, determining a target micro-service corresponding to the target identifier according to the flow distribution strategy; the target identification is used for characterizing the target micro-service to be accessed.
Optionally, the routing the traffic access request to the target microservice includes:
routing the traffic access request to an istio-ingressgateway ingress gateway through an api-gateway to the target microservice.
Optionally, the method further includes:
and if the micro service requested to be accessed cannot be determined according to the flow access request and the flow distribution strategy, routing the flow access request to the general micro service.
In a second aspect, there is provided a flow distribution device, the device comprising:
the receiving module is used for receiving a setting instruction for setting a flow distribution strategy;
and the setting module is used for setting the flow distribution strategy according to the setting instruction received by the receiving module, the flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and the flow distribution strategy is used for routing an access request to the corresponding micro service when the request end requests to access the micro service.
In a third aspect, a traffic distribution apparatus is provided, which includes a memory and a processor, wherein the memory stores at least one program instruction, and the processor loads and executes the at least one program instruction to implement the method of the first aspect.
In a fourth aspect, there is provided a computer storage medium having stored therein at least one program instruction for loading and execution by a processor to perform the method of the first aspect.
By receiving a setting instruction for setting a traffic distribution policy; setting the flow distribution strategy according to the setting instruction, wherein the flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and the flow distribution strategy is used for routing an access request to the corresponding micro service when the request end requests to access the micro service; the flow distribution request of each user can be accurately routed according to the flow distribution strategy, so that the flow of the user can be accurately controlled, and customized flow control service is realized; the problem of can't accurate control user flow among the prior art is solved.
The foregoing description is only an overview of the technical solutions of the present invention, and in order to make the technical solutions of the present invention more clearly understood and to implement them in accordance with the contents of the description, the following detailed description is given with reference to the preferred embodiments of the present invention and the accompanying drawings.
Drawings
Fig. 1 is a flowchart of a method of allocating traffic according to an embodiment of the present invention;
FIG. 2 is a flow chart of an implementation of setting a flow allocation measurement according to an embodiment of the present invention;
fig. 3 is a flowchart of a method of allocating traffic according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a flow distribution device according to an embodiment of the present invention.
Detailed Description
The technical solutions of the present invention will be described clearly and completely with reference to the accompanying drawings, and it should be understood that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the description of the present invention, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inner", "outer", etc., indicate orientations or positional relationships based on the orientations or positional relationships shown in the drawings, and are only for convenience of description and simplicity of description, but do not indicate or imply that the device or element being referred to must have a particular orientation, be constructed and operated in a particular orientation, and thus, should not be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
In the description of the present invention, it should be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; can be mechanically or electrically connected; they may be connected directly or indirectly through intervening media, or they may be interconnected between two elements. The specific meanings of the above terms in the present invention can be understood in specific cases to those skilled in the art.
In addition, the technical features involved in the different embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
For the sake of understanding, first, the terms related to the following embodiments of the present application will be briefly described.
Micro-service: is a cloud-native architecture approach in which a single application is composed of many loosely-coupled and independently deployable smaller components or services. The service described herein may refer to an application program, and the application program may deploy multiple versions according to different use requirements, and the micro service described herein is an application program of different versions.
And step sto, constructing a service grid for the micro-service, and controlling the flow of the service.
Service mesh is a service mesh.
Kubernetes: a cluster orchestration engine.
And Crd: the customresourcedention personalized resource definitions (in kubernets).
B/S architecture (Browser/Server ): browser and server architecture modes.
The methods described in the examples below can all be used and are exemplified in the sio, unless otherwise specified.
Referring to fig. 1, a flowchart of a method of a traffic distribution method according to an embodiment of the present application is shown, where as shown in fig. 1, the method includes:
in order to promote the service, the service test may be provided with a plurality of versions, and a specified user may be set to access a certain version according to a requirement, or a certain version may be set for a certain user group to access, that is, a manager may set a traffic distribution policy for accessing the microservice.
In practical implementation, a manager may set a UI (user interface) interface implemented by the B/S framework, that is, set the traffic distribution policy in the browser, so that the manager can quickly configure a corresponding traffic distribution policy according to a service requirement.
In a possible implementation manner, when a certain user needs to be specified to access the first micro service, a setting instruction for setting the first request end of the user to access the first micro service can be applied. For example, the user finds a first microservice in the UI interface and enters a requestor id of the first requestor in a column of the service user. Accordingly, the browser can receive the setting instruction. The identifier of the request end may be at least one of a mobile phone number, an IP (internet protocol) address, a MAC (media access control address), a session, a cookie, and a token, and in actual implementation, the identifier may be any identifier capable of uniquely identifying the request end, which is not limited in this embodiment. Assuming that the service has two versions, namely, grey-a and grey-B, in addition to the general version, the mobile phone user B can be set to access the grey-B version.
In another possible embodiment, when a certain user group needs to be specified to access the second micro service, in order to improve the setting efficiency and avoid the problem of complex operation when users increase each user in the user group one by one, when the users in the user group use a request end to request traffic, a target identifier may be carried in a traffic access request, where the target identifier is used to indicate that the second micro service is requested to be accessed. Optionally, a field may be added to the header of the traffic access request, and the target identifier is carried in the field. For example, token _ nya may be added to the header of the traffic access request, and optionally, the trafficlabel may be set as token _ nya, thereby indicating that the request end carrying token _ nya in the sent traffic access request requests access to the grey-a version. Accordingly, the browser may receive the setting instruction.
And 102, setting the flow distribution strategy according to the setting instruction.
And after receiving the setting instruction, setting a corresponding flow distribution strategy according to the setting instruction.
Wherein, this step includes two possible implementation manners:
the first method comprises the following steps: and when the setting instruction is an instruction for setting a first request end for accessing the first micro service for the first micro service, setting an association relation between the first micro service and the request end identification of the first request end according to the setting instruction.
And the second method comprises the following steps: and when the setting instruction is an instruction for setting a second request end for sending a target access request to access a second micro service, setting an association relation between the second request end and the second micro service according to the setting instruction, wherein the target access request is a request carrying a target identifier.
The flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and is used for routing an access request to the corresponding micro service when the request end requests to access the micro service.
After the steps, the rule execution engine corresponding to the micro-service of different versions can be constructed and realized, all the flow distribution strategies of the same service are integrated and unified by using task scheduling management, and finally, multiple multi-type application models are converted into corresponding flow models to be configured and issued.
That is, after the traffic allocation policy is set, the traffic allocation may be performed according to the traffic allocation policy. Optionally, various versions of a certain service, that is, various types of traffic allocation policies are integrated, and subsequently, after receiving a traffic access request for accessing the service, traffic routing may be performed according to the integrated traffic allocation policies. In practical implementation, Kubernetes (k8s) was constructed for istio's main crd: the Destinationrule is used as a target set to control the route of each flow access request to which application model, and a routing rule is defined for each k8s service; and if the traffic is routed to the corresponding application model by using the VirtualService as a routing rule control flow, defining a routing rule for each domain name expected to be exposed to the outside.
In a possible embodiment, please refer to fig. 2, which shows a schematic diagram of a specific implementation of the setting of the traffic distribution policy in the present application, as shown in fig. 2, a user may apply a setting instruction at a user interaction unit; converting various strategies set by a front-end user into corresponding application measuring and calculating unit models according to rule types, such as flow strategies in a self-defined header mode, a user mobile phone number mode, a user specified userid mode and the like, and carrying out persistence in the system; and aiming at different application models, establishing and realizing corresponding rule execution engines, using task scheduling management to integrate and unify all flow distribution strategies of the same service, and finally converting various multi-type application models into corresponding flow distribution models for configuration and issuing. And realizing a flow decision unit. Main crd to construct idio of Kubernetes (k8 s): destinationrule as a destination set to control where traffic needs, defining routing rules for each k8s service; VirtualService controls how and where traffic goes as routing rules, which are defined for each domain name that is expected to be exposed to the outside.
In summary, by receiving a setting instruction for setting a traffic distribution policy; setting the flow distribution strategy according to the setting instruction, wherein the flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and the flow distribution strategy is used for routing an access request to the corresponding micro service when the request end requests to access the micro service; the flow distribution request of each user can be accurately routed according to the flow distribution strategy, so that the flow of the user can be accurately controlled, and customized flow control service is realized; the problem of can't accurate control user flow among the prior art is solved.
Referring to fig. 3, a flowchart of a method for allocating traffic according to another embodiment of the present application is shown, where as shown in fig. 3, the method includes:
when a user needs to request access to a microservice, a traffic access request may be sent out, and correspondingly, the server may receive the traffic access request.
Optionally, when the target request end is a preset request end for accessing a user group of a certain specified micro service, the traffic access request may carry a target identifier, where the target identifier is used to indicate that the target micro service is requested to be accessed. In addition, in general, in order to identify itself, the traffic access request may carry a request end identifier of a target request end, where the request end identifier may be at least one of a mobile phone number, an IP address, an MAC address, a session, a cookie, and a token, and in actual implementation, the request end identifier may be any identifier capable of uniquely identifying the request end, which is not limited in this embodiment.
In actual implementation, the traffic access request further includes a service identifier of the service requested to be accessed. For example, when requesting to access the service 1, the traffic access request may carry the service identifier of the service 1. Wherein the service includes a plurality of versions.
after receiving the traffic access request, the service requesting access may obtain each traffic allocation policy corresponding to the service. Optionally, each traffic distribution policy corresponding to the service may be obtained according to the service identifier. The number of the obtained traffic distribution policies is-1, for example, if a certain service includes a general version, and grey-a and grey-b versions, the traffic distribution policy may include 2 traffic distribution policies corresponding to the grey-a and the grey-b.
then, the target micro service which is requested to be accessed currently is determined from the at least two micro services according to the received flow access request and the obtained flow distribution strategies.
In a possible implementation manner, when the traffic access request carries the target identifier, the service to be accessed currently is determined to be the second microservice according to the traffic allocation policy.
In another possible implementation manner, when the traffic access request does not carry the target identifier, whether a traffic allocation policy corresponding to the request identifier of the target request end exists is queried, and if so, the micro service corresponding to the traffic allocation policy is determined to be the target micro service.
In yet another possible implementation, if there is no corresponding micro service in the traffic allocation policy, the general micro service is determined as the target micro service.
After the target micro-service is determined to be obtained, the traffic access request can be routed to the determined target micro-service. Optionally, as illustrated by taking the determined target micro service as a grey-a, the traffic access request may first reach an istio-ingress gateway, then pass through an api-gateway, and finally reach a service test, and perform traffic policing through an already injected sidecar agent istio-proxy, and finally route the request to the test-grey-a.
In summary, a traffic access request sent by a target request end is received; acquiring a flow distribution strategy; determining a target micro service which is requested to be accessed from at least two micro services according to the flow access request and the flow distribution strategy; routing the traffic access request to the target microservice. The problem of can't accurate control user flow among the prior art is solved. And then the flow of the user can be accurately controlled, and the effect of customized flow control service is realized.
By using the scheme, a small-scale target group can obtain product experience in advance, a supplier can obtain user feedback of the target group in advance, and a product strategy is updated and adjusted; in the development process, tests with different functional characteristics are not interfered with each other, and testers can test a new characteristic independently, so that agile and efficient development is achieved.
It should be noted that the methods shown in fig. 1 and fig. 3 may be applied to the same execution main body, or may be separately executed in different devices, and when the methods are applied to the same execution main body, the step of obtaining the traffic distribution policy in step 302 is an exclusive preset traffic distribution policy, and is not described herein again.
Referring to fig. 4, a schematic structural diagram of a flow distribution device according to an embodiment of the present application is shown, and as shown in fig. 4, the flow distribution device includes:
a receiving module 510, configured to receive a setting instruction for setting a traffic distribution policy;
a setting module 520, configured to set the traffic distribution policy according to the setting instruction received by the receiving module 510, where the traffic distribution policy includes an association relationship between a micro service and a request end requesting to access the micro service, and the traffic distribution policy is used to route an access request to a corresponding micro service when the request end requests to access the micro service.
In summary, by receiving a setting instruction for setting a traffic distribution policy; setting the flow distribution strategy according to the setting instruction, wherein the flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and the flow distribution strategy is used for routing an access request to the corresponding micro service when the request end requests to access the micro service; the flow distribution request of each user can be accurately routed according to the flow distribution strategy, so that the flow of the user can be accurately controlled, and customized flow control service is realized; the problem of can't accurate control user flow among the prior art is solved.
The present embodiment also provides a flow distribution device, which includes a memory and a processor, where the memory stores at least one program instruction, and the processor implements the method according to the foregoing embodiment by loading and executing the at least one program instruction.
The present embodiment also provides a computer storage medium, in which at least one program instruction is stored, and the at least one program instruction is used for being loaded and executed by a processor to implement the method of the above embodiment.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (9)
1. A method of traffic distribution, the method comprising:
receiving a setting instruction for setting a flow distribution strategy;
and setting the flow distribution strategy according to the setting instruction, wherein the flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and the flow distribution strategy is used for routing an access request to the corresponding micro service when the request end requests to access the micro service.
2. The method of claim 1, wherein the setting the traffic distribution policy according to the setting instruction comprises:
and when the setting instruction is an instruction for setting a first request end for accessing the first micro service for the first micro service, setting an association relation between the first micro service and the request end identification of the first request end according to the setting instruction.
3. The method of claim 1, wherein the setting the traffic distribution policy according to the setting instruction comprises:
and when the setting instruction is an instruction for setting a second request end for sending a target access request to access a second micro service, setting an association relation between the second request end and the second micro service according to the setting instruction, wherein the target access request is a request carrying a target identifier.
4. The method of claim 1, further comprising:
receiving a flow access request sent by a target request end;
acquiring the flow distribution strategy;
determining a target micro service which is requested to be accessed from at least two micro services according to the flow access request and the flow distribution strategy;
routing the traffic access request to the target microservice.
5. The method of claim 4, wherein determining a target microservice for access request from at least two microservices according to the traffic access request and the traffic distribution policy comprises:
and after receiving the flow access request, determining the target micro service corresponding to the request end identification according to the request end identification of the target request end and the flow distribution strategy.
6. The method of claim 4, wherein determining a target microservice for access request from at least two microservices according to the traffic access request and the traffic distribution policy comprises:
when the access request carries a target identifier, determining a target micro-service corresponding to the target identifier according to the flow distribution strategy; the target identification is used for characterizing the target micro-service to be accessed.
7. The method of any of claims 4 to 6, wherein said routing said traffic access request to said target microservice comprises:
routing the traffic access request to an istio-ingressgateway ingress gateway through an api-gateway to the target microservice.
8. The method according to any one of claims 4 to 6, further comprising:
and if the micro service requested to be accessed cannot be determined according to the flow access request and the flow distribution strategy, routing the flow access request to the general micro service.
9. A flow distribution device, the device comprising:
the receiving module is used for receiving a setting instruction for setting a flow distribution strategy;
and the setting module is used for setting the flow distribution strategy according to the setting instruction received by the receiving module, the flow distribution strategy comprises an incidence relation between the micro service and a request end requesting to access the micro service, and the flow distribution strategy is used for routing an access request to the corresponding micro service when the request end requests to access the micro service.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011113861.2A CN112235203A (en) | 2020-10-17 | 2020-10-17 | Flow distribution method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011113861.2A CN112235203A (en) | 2020-10-17 | 2020-10-17 | Flow distribution method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112235203A true CN112235203A (en) | 2021-01-15 |
Family
ID=74118890
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011113861.2A Withdrawn CN112235203A (en) | 2020-10-17 | 2020-10-17 | Flow distribution method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112235203A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115250267A (en) * | 2022-07-21 | 2022-10-28 | 平安科技（深圳）有限公司 | Microservice session management method, microservice session management device, computer equipment and storage medium |
-
2020
- 2020-10-17 CN CN202011113861.2A patent/CN112235203A/en not_active Withdrawn
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115250267A (en) * | 2022-07-21 | 2022-10-28 | 平安科技（深圳）有限公司 | Microservice session management method, microservice session management device, computer equipment and storage medium |
| CN115250267B (en) * | 2022-07-21 | 2024-03-01 | 平安科技（深圳）有限公司 | Micro-service session management method, micro-service session management device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108370341B (en) | Resource allocation method, virtual network function manager and network element management system | |
| CN115442423A (en) | Method for discovering services provided by a network repository function | |
| US9397922B1 (en) | Automated network testing platform | |
| CN117793952A (en) | Communication method and device | |
| CN110447208A (en) | A kind of management method, unit and the system of network slice | |
| CN111356207A (en) | Service slice selection method and device | |
| CN109417492B (en) | Network function NF management method and NF management equipment | |
| US8850030B2 (en) | Method and apparatus for providing network resources to content providers | |
| WO2015096680A1 (en) | Node distribution method and control center | |
| CN113572689A (en) | Microservice gateway management method, system, device, readable storage medium and product | |
| US10050823B2 (en) | System and method for providing device management service to electronic device having no broadband communication module | |
| CN109417501B (en) | Method and equipment for arranging network resources | |
| CN114398176A (en) | Service access method, device, electronic equipment and storage medium | |
| CN114302429B (en) | NWDAF network element determination method, device, equipment and storage medium | |
| US8135837B2 (en) | UPnP QoS network system and method for reserving path and resource | |
| US20170359231A1 (en) | System for generating a virtualized network function | |
| JP2016511451A (en) | System and method for opening network functions and associated network elements | |
| EP3470983A1 (en) | Method, system and computer readable medium to allocate resources to at least one application | |
| CN108093036A (en) | A kind of method and device for obtaining resource | |
| CN112235203A (en) | Flow distribution method and device | |
| US20130143524A1 (en) | Mediation Server, Control Method Therefor, Communication Device, Control Method Therefor, Communication System, and Computer Program | |
| CN114205280A (en) | Application publishing method and flow routing method based on container cloud and service grid | |
| CN110557303B (en) | Network multi-outlet test platform system and test method | |
| CN113472853B (en) | Application program network fragment selection method, application server and UDR | |
| EP1895417A1 (en) | Data storage system and method for testing new applications |
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 | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210115 |
|
| WW01 | Invention patent application withdrawn after publication |