CN111431818A - Cross-domain request traffic distribution method and device, storage medium and computer equipment - Google Patents
Cross-domain request traffic distribution method and device, storage medium and computer equipment Download PDFInfo
- Publication number
- CN111431818A CN111431818A CN202010127860.7A CN202010127860A CN111431818A CN 111431818 A CN111431818 A CN 111431818A CN 202010127860 A CN202010127860 A CN 202010127860A CN 111431818 A CN111431818 A CN 111431818A
- Authority
- CN
- China
- Prior art keywords
- service
- service request
- domain
- network domain
- 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.)
- Granted
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/24—Traffic characterised by specific attributes, e.g. priority or QoS
-
- 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/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a cross-domain request traffic distribution method, a cross-domain request traffic distribution device, a storage medium and computer equipment, and relates to the technical field of cross-domain access. The method comprises the following steps: acquiring a service request sent by a requester network domain, wherein the service request carries a service code and a name identifier of the requester network domain; acquiring a service type corresponding to the service request according to the service code; acquiring flow ratio information corresponding to the service request according to the name identifier of the requester network domain and the service category corresponding to the service request; and distributing the service request to a service unit of the target network domain according to a preset proportion for processing according to the flow ratio information corresponding to the service request. The method can avoid all cross-domain accesses from being concentrated in one or more service units, reduces the processing load of the target network domain on the cross-domain service request, effectively shortens the access time of the cross-domain service request, and enhances the stability of the requester network domain and the target network domain in the cross-domain access.
Description
Technical Field
The present invention relates to the field of cross-domain access technologies, and in particular, to a method and an apparatus for allocating a flow of a cross-domain request, a storage medium, and a computer device.
Background
Cross-domain access, also referred to as cross-network domain access, refers to the manner in which resources of one domain are requested from another domain. Generally, services between different network types cannot realize self-discovery and access, and therefore, cross-domain access is implemented by means of third-party tools or services, and generally, the cross-domain access is mainly realized by means of application layer gateways.
On the other hand, many service systems tend to adopt a unit deployment mode at present, and in the unit deployment mode, each service unit can independently complete the operation of all services in a certain partition.
In the prior art, when performing cross-domain access to a network domain deployed in a unitized manner, a requester gateway generally selects one or more service units to perform service invocation according to a given or random manner, regardless of unit splitting logic of a target network domain, which may cause all service requests to be concentrated on one or more service units, and this cross-domain access manner may increase access time of the service requests, and may also cause the service units of the target network domain to generate overload operation pressure, which may aggravate processing load of the service requests of the target network domain, and may even cause a serious result of breakdown and paralysis of the target network domain.
Disclosure of Invention
In view of this, the present application provides a method, a system, a storage medium, and a computer device for cross-domain request traffic distribution, and mainly aims to solve the technical problems in the prior art that the cross-domain request access time is long and the service unit load of the target network domain is heavy.
According to a first aspect of the present invention, there is provided a cross-domain requested traffic distribution method, including:
acquiring a service request sent by a requester network domain, wherein the service request carries a service code and a name identifier of the requester network domain;
acquiring a service type corresponding to the service request according to the service code;
acquiring flow ratio information corresponding to the service request according to the name identifier of the requester network domain and the service category corresponding to the service request;
and distributing the service request to a service unit of the target network domain according to a preset proportion for processing according to the flow ratio information corresponding to the service request.
In one embodiment, the method further comprises: and acquiring the traffic ratio information of each name identifier of the requester network domain under each service category according to the current time and a preset traffic configuration plan.
In one embodiment, acquiring traffic proportioning information of each name identifier of a requester network domain under each service category according to a current time and a preset traffic configuration plan includes: when the current time is the same as the time node in the flow configuration plan, acquiring a flow configuration file corresponding to the time node in the database; and analyzing the flow configuration file to obtain the flow ratio information of each name identifier of the requester network domain under each service type.
In an embodiment, before obtaining a service class corresponding to a service request according to a service code, the method further includes: acquiring configuration information of each service code in a database; then, according to the service code, obtaining a service category corresponding to the service request, including: and acquiring the service type corresponding to the service request in the configuration information of each service code according to the service code.
In one embodiment, acquiring traffic matching information corresponding to a service request according to a name identifier of a requester network domain and a service type corresponding to the service request includes: generating a flow ratio identifier according to the name identifier of the requester network domain and the service type corresponding to the service request; and acquiring the traffic ratio information corresponding to the service request from the traffic ratio information of each name identifier of the requester network domain under each service class according to the traffic ratio identifier.
In one embodiment, distributing a service request to a service unit of a target network domain according to traffic matching information corresponding to the service request includes: obtaining the name and the distribution proportion of a service unit of a target network domain to be distributed according to the flow ratio information corresponding to the service request; and sending the service request to the service unit of the target network domain under the name according to the name and the distribution ratio of the service unit of the target network domain to be distributed.
In one embodiment, the method further comprises: and receiving a service processing result of the service request sent by the service unit of the target network domain.
According to a second aspect of the present invention, there is provided a cross-domain requested traffic distribution apparatus, the apparatus comprising:
the service request acquisition module is used for acquiring a service request sent by a requester network domain, wherein the service request carries a service code and a name identifier of the requester network domain;
the request information extraction module is used for acquiring the service type corresponding to the service request according to the service code;
the flow ratio obtaining module is used for obtaining flow ratio information corresponding to the service request according to the name identifier of the requester network domain and the service category corresponding to the service request;
and the service request distribution module is used for distributing the service request to the service unit of the target network domain according to the preset proportion for processing according to the flow ratio information corresponding to the service request.
In an embodiment, the apparatus further includes a traffic ratio update module, where the traffic ratio update module is configured to obtain traffic ratio information of each name identifier of the requester domain under each service category according to a current time and a preset traffic configuration plan.
In one embodiment, the traffic matching update module is specifically configured to, when the current time is the same as a time node in the traffic configuration plan, obtain a traffic configuration file corresponding to the time node in the database; and analyzing the flow configuration file to obtain the flow ratio information of each name identifier of the requester network domain under each service type.
In one embodiment, the apparatus further includes a configuration information obtaining module, where the configuration information obtaining module is configured to obtain configuration information of each service code in a database; and the request information extraction module is specifically used for acquiring the service type corresponding to the service request in the configuration information of each service code according to the service code.
In one embodiment, the traffic matching information obtaining module is specifically configured to generate a traffic matching identifier according to a name identifier of a requester network domain and a service category corresponding to the service request; and acquiring the traffic ratio information corresponding to the service request from the traffic ratio information of each name identifier of the requester network domain under each service class according to the traffic ratio identifier.
In one embodiment, the service request distribution module is specifically configured to obtain, according to traffic matching information corresponding to a service request, a name and a distribution ratio of a service unit of a target network domain to be distributed; and sending the service request to the service unit of the target network domain under the name according to the name and the distribution ratio of the service unit of the target network domain to be distributed.
In an embodiment, the apparatus further includes a processing result receiving module, where the processing result receiving module is configured to receive a service processing result of the service request sent by the service unit of the target network domain.
According to a third aspect of the present invention, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, implements the above-described cross-domain requested traffic allocation method.
According to a fourth aspect of the present invention, there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the above-mentioned cross-domain requested traffic allocation method when executing the program.
The invention provides a cross-domain request traffic distribution method, a device, a storage medium and computer equipment, which are characterized in that a service request carrying a service code sent by a requester domain is firstly obtained, then a name identifier and a service type of the service request are obtained according to the service code, then traffic proportioning information corresponding to the service request is obtained by utilizing the name identifier and the service type, and finally the service request is distributed to a service unit of a target domain according to the traffic proportioning information according to a preset proportion, so that the cross-domain access traffic distribution from the requester domain to the target domain is realized. The method can distribute the service requests with different name identifications and service types to the service units of different target network domains according to the service characteristics of the service requests according to the preset proportion, avoids all cross-domain accesses from being concentrated into one or more service units, reduces the processing burden of the target network domains on the cross-domain service requests, effectively shortens the access time of the cross-domain service requests, and enhances the stability of the requester network domain and the target network domain in the cross-domain access.
The foregoing description is only an overview of the technical solutions of the present application, and the present application can be implemented according to the content of the description in order to make the technical means of the present application more clearly understood, and the following detailed description of the present application is given in order to make the above and other objects, features, and advantages of the present application more clearly understandable.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a schematic flowchart illustrating a cross-domain requested traffic distribution method according to an embodiment of the present invention;
fig. 2 is a schematic flow chart illustrating another cross-domain requested traffic distribution method according to an embodiment of the present invention;
fig. 3 is a schematic view illustrating a scenario of a cross-domain requested traffic distribution method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram illustrating a cross-domain requested traffic distribution apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram illustrating another cross-domain requested traffic distribution apparatus according to an embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
In an embodiment, as shown in fig. 1, a cross-domain requested traffic distribution method is provided, which is described by taking an example that the method is applied to a domain gateway of a requester, and includes the following steps:
101. and acquiring a service request sent by the requester network domain, wherein the service request carries a service code and a name identifier of the requester network domain.
Specifically, the service request refers to a request message from the front end to the server, and the server may respond to the request of the front end according to the request message, that is, the server may execute the call of multiple applications according to the request message and return corresponding call results. In this embodiment, the service request sent by the requester domain refers to a cross-domain service request from a front end of the requester domain to a target domain server, where the cross-domain service request carries a service code, and when performing cross-domain access, a requester domain gateway deployed in an application layer acquires the service request and extracts the service code corresponding to the service request, and meanwhile, the requester domain gateway may also extract a name identifier of the requester domain in the service request.
102. And acquiring the service type corresponding to the service request according to the service code.
Specifically, each type of service request has a unique service code, and the service type corresponding to the service request can be obtained through the service code, wherein the service request of one type refers to a service request in which the requested application and the requested interface are the same. Before the service request is obtained, the requester domain gateway may obtain configuration information of all the service codes in the database, and then search a service category corresponding to the service request in the configuration information of each service code according to the service code carried in the service request.
103. And acquiring the flow ratio information corresponding to the service request according to the name identifier of the requester network domain and the service type corresponding to the service request.
Specifically, the requester domain gateway may generate a traffic matching identifier according to the name identifier of the requester domain and the service category corresponding to the service request, and then obtain traffic matching information corresponding to the service request from traffic matching information locally cached in the requester domain gateway according to the traffic matching identifier, where in the traffic matching information, the name and allocation proportion of a unit that the service request is sent to the target domain are recorded.
104. And distributing the service request to a service unit of the target network domain according to a preset proportion for processing according to the flow ratio information corresponding to the service request.
Specifically, the requester network domain gateway may obtain, according to the traffic matching information corresponding to the service request, a name and a distribution ratio of a service unit of the target network domain to be distributed, and then send, according to the name and the distribution ratio of the service unit of the target network domain to be distributed, the service request to the service unit of the target network domain under the corresponding name according to a preset distribution ratio.
The method for allocating traffic of a cross-domain request according to this embodiment includes first obtaining a service request carrying a service code sent by a requester domain, then obtaining a name identifier and a service type of the service request according to the service code, then obtaining traffic matching information corresponding to the service request by using the name identifier and the service type, and finally distributing the service request to a service unit of a target domain according to a preset proportion according to the traffic matching information, so as to implement cross-domain access from the requester domain to the target domain. The method can distribute the service requests with different name identifications and service types to the service units of different target network domains according to the service characteristics of the service requests according to the preset proportion, avoids all cross-domain accesses from being concentrated into one or more service units, reduces the processing burden of the target network domains on the cross-domain service requests, effectively shortens the access time of the cross-domain service requests, and enhances the stability of the requester network domain and the target network domain in the cross-domain access.
Further, as a refinement and an extension of the specific implementation of the foregoing embodiment, in order to fully illustrate the implementation process of the present embodiment, a method for allocating traffic across domain requests is provided, as shown in fig. 2, the method includes the following steps:
201. and acquiring the traffic ratio information of each name identifier of the requester network domain under each service category according to the current time and a preset traffic configuration plan.
Specifically, when the current time of the requester domain gateway is the same as a certain time node in the traffic configuration plan, the requester domain gateway may obtain a traffic configuration file corresponding to the time node in the database, and then analyze the traffic configuration file to obtain traffic matching information of each name identifier of the requester domain under each service category.
For example, in the scenario shown in fig. 3, both the requester network domain and the target network domain are deployed in a unitized manner, where A, B both have machine rooms in the requester network domain, each of the two machine rooms has a plurality of service units for respectively performing business operations in different partitions, and the number of service requests received by A, B two machine rooms is different because of the different numbers of servers in the two machine rooms, for example, a site may receive a total amount of 60% of the service requests, and a B site may receive a total amount of 40% of the service requests, in this embodiment, the name identifier of the requester network domain may be a unit name of the service unit of the requester network domain, such as unit 1a, unit 2a, unit 3a, unit 1B, or unit 2B, and the business category of the service request may be four categories, namely ratio1, ratio2, and ratio 3.
Correspondingly, the traffic matching information of each name identifier of the requester network domain under each service category may include the following: service requests of the unit 1a, the unit 2a and the unit 3a under four service categories of ratio, ratio1, ratio2 and ratio3 are all distributed to the unit 1c of the machine room of the target network domain A, the service requests of unit 1b and unit 2b under the traffic class of ratio are distributed to unit 1c of a-site room, service requests of unit 1b under the traffic class of ratio1 are distributed to unit 1C of the a-site room and unit 1d of the C-site room in a ratio of 1:1, the service request of unit 2b under the traffic class of ratio2 is distributed to unit 2d and unit 3d of the C-site room in a ratio of 2:3, the service requests of unit 1b and unit 2b under the traffic class of ratio3 are all distributed to unit 3d of the C-site room and so on, as shown in figure 3, in a time range, the flow ratio of the service requests sent from the requester network domain to each service unit of the target network domain is 1: 2: 1: 2.
in this embodiment, according to the change of the time node, the traffic matching information is also adjusted accordingly, so as to balance the traffic processing pressure of each service unit in the target network domain. It will be appreciated that in other scenarios, the requesting network domain may also be deployed non-componentially, in which case the name identifier of the requesting network domain may be the name and code number of the requesting network domain itself.
202. And acquiring the configuration information of each service code in a database.
Specifically, the requesting domain gateway may obtain configuration information of each service code in the database, record a service category corresponding to each service code in the configuration information, and when the configuration information of the service code is changed, the requesting domain gateway may obtain the configuration information of each service code again and replace the previous configuration information.
203. And acquiring a service request sent by the requester network domain, wherein the service request carries a service code and a name identifier of the requester network domain.
Specifically, when cross-domain access is performed, a requester domain gateway deployed in an application layer may obtain a service request sent by a requester domain, extract a service code corresponding to the service request, and meanwhile, the requester domain gateway may further extract a name identifier of the requester domain from the service request.
204. And acquiring the service type corresponding to the service request according to the service code.
Each type of service request has a unique service code, and the service type corresponding to the service request can be obtained through the service code. Specifically, the requester domain gateway may search, according to the service code carried in the service request, a service category corresponding to the service request in the configuration information of each service code.
205. And acquiring the flow ratio information corresponding to the service request according to the name identifier of the requester network domain and the service type corresponding to the service request.
Specifically, the requester domain gateway may generate a traffic matching identifier according to the name identifier of the requester domain and the service category corresponding to the service request, and then obtain traffic matching information corresponding to the traffic matching identifier from the traffic matching information according to the traffic matching identifier. In this embodiment, the format of the traffic matching identifier needs to correspond to the format of the traffic matching information, for example, the format of the traffic matching information indicating that a name identifier is in a certain service category is: name identification # service class { element name 1: flow ratio1, unit name 2: flow ratio2, the flow ratio identifier may be name identifier # service type, for example, in unit 1a # ratio1, and according to the flow ratio identifier, the corresponding flow ratio information may be found in the flow ratio information of each name identifier under each service type.
206. And distributing the service request to a service unit of the target network domain according to the flow ratio information corresponding to the service request.
Specifically, the requester network domain gateway may obtain, according to the traffic matching information corresponding to the service request, a name and a distribution ratio of a service unit of the target network domain to be distributed, and then send, according to the name and the distribution ratio of the service unit of the target network domain to be distributed, the service request to the service unit of the target network domain under the corresponding name according to a preset distribution ratio.
For example, the name of the requester network domain of a service request is identified as unit 2b, the type is ratio2, the service request can be distributed to unit 2d or unit 3d of the C-site computer room according to the traffic matching information corresponding to the service request, if there is only one service request of this type, the probability that the service request is distributed to unit 2d is 2/5, and the probability that the service request is distributed to unit 3d is 3/5, if there are 50 service requests of this type, the number of service requests distributed to unit 2d is approximately 20, and the number of service requests distributed to unit 3d is approximately 30.
207. And receiving a service processing result of the service request sent by the service unit of the target network domain.
Specifically, the requester network domain gateway may receive a service processing result of the service request sent back by the service unit of the target network domain, so as to complete the processing of the cross-domain service request.
The method for distributing traffic of a cross-domain request according to this embodiment can automatically update traffic matching information according to the time node, balance the processing load of the target network domain on the cross-domain service request at each time point, shorten the access time of the cross-domain service request, and enhance the stability of the requester network domain and the target network domain in cross-domain access.
Further, as a specific implementation of the method shown in fig. 1 to fig. 3, this embodiment provides a cross-domain requested traffic distribution apparatus, as shown in fig. 4, the apparatus includes: a service request obtaining module 31, a request information extracting module 32, a traffic ratio obtaining module 33, and a service request distributing module 34.
A service request obtaining module 31, configured to obtain a service request sent by a requester network domain, where the service request carries a service code and a name identifier of the requester network domain;
a request information extraction module 32, configured to obtain a service category corresponding to the service request according to the service code;
a traffic matching obtaining module 33, configured to obtain traffic matching information corresponding to the service request according to the name identifier of the requester domain and the service category corresponding to the service request;
the service request distribution module 34 is configured to distribute the service request to the service unit of the target network domain according to a preset ratio for processing, according to the traffic matching information corresponding to the service request.
In a specific application scenario, as shown in fig. 5, the apparatus further includes a traffic matching update module 35, where the traffic matching update module 35 is specifically configured to obtain traffic matching information of each name identifier of the requester network domain under each service category according to the current time and a preset traffic configuration plan.
In a specific application scenario, the flow rate matching update module 35 is specifically configured to obtain, in a database, a flow rate configuration file corresponding to a time node when the current time is the same as the time node in the flow rate configuration plan; and analyzing the flow configuration file to obtain the flow ratio information of each name identifier of the requester network domain under each service type.
In a specific application scenario, as shown in fig. 5, the apparatus further includes a configuration information obtaining module 36, where the configuration information obtaining module 36 is specifically configured to obtain configuration information of each service code in a database; the request information extracting module 32 is specifically configured to obtain a service category corresponding to the service request from the configuration information of each service code according to the service code.
In a specific application scenario, the traffic matching information obtaining module 33 is specifically configured to generate a traffic matching identifier according to the name identifier of the requester domain and the service category corresponding to the service request; and acquiring the traffic ratio information corresponding to the service request from the traffic ratio information of each name identifier of the requester network domain under each service class according to the traffic ratio identifier.
In a specific application scenario, the service request distribution module 34 may be specifically configured to obtain, according to traffic matching information corresponding to a service request, a name and a distribution ratio of a service unit of a target network domain to be distributed; and sending the service request to the service unit of the target network domain under the name according to the name and the distribution ratio of the service unit of the target network domain to be distributed.
In a specific application scenario, as shown in fig. 5, the apparatus further includes a processing result receiving module 37, where the processing result receiving module 37 is configured to receive a service processing result of the service request sent by the service unit of the target network domain.
It should be noted that other corresponding descriptions of the functional units related to the traffic distribution device for cross-domain request provided in this embodiment may refer to the corresponding descriptions in fig. 1 to fig. 3, and are not described herein again.
Based on the methods shown in fig. 1 and fig. 2, correspondingly, the present embodiment further provides a storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the method for allocating traffic of the cross-domain request shown in fig. 1 and fig. 2 is implemented.
Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, and the software product to be identified may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, or the like), and include several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the method according to the implementation scenarios of the present application.
Based on the foregoing methods shown in fig. 1 to fig. 3 and the embodiments of the traffic distribution device for cross-domain request shown in fig. 4 and fig. 5, to achieve the foregoing object, this embodiment further provides an entity device for cross-domain request traffic distribution, which may specifically be a personal computer, a server, a smart phone, a tablet computer, a smart watch, or other network devices, and the entity device includes a storage medium and a processor; a storage medium for storing a computer program; a processor for executing the computer program to implement the above-mentioned methods as shown in fig. 1 and fig. 2.
Optionally, the entity device may further include a user interface, a network interface, a camera, a Radio Frequency (RF) circuit, a sensor, an audio circuit, a WI-FI module, and the like. The user interface may include a Display screen (Display), an input unit such as a keypad (Keyboard), etc., and the optional user interface may also include a USB interface, a card reader interface, etc. The network interface may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface), etc.
Those skilled in the art will appreciate that the physical device structure of the cross-domain requested traffic distribution provided by the present embodiment does not constitute a limitation to the physical device, and may include more or less components, or combine some components, or arrange different components.
The storage medium may further include an operating system and a network communication module. The operating system is a program for managing the hardware of the above-mentioned entity device and the software resources to be identified, and supports the operation of the information processing program and other software and/or programs to be identified. The network communication module is used for realizing communication among components in the storage medium and communication with other hardware and software in the information processing entity device.
Through the above description of the embodiments, those skilled in the art will clearly understand that the present application can be implemented by software plus a necessary general hardware platform, and can also be implemented by hardware. By applying the technical scheme of the application, the flow distribution of cross-domain access from the requester network domain to the target network domain can be realized. Compared with the prior art, the method can distribute the service requests with different name identifications and service types to the service units of different target network domains according to the service characteristics of the service requests according to the preset proportion, avoids all cross-domain accesses from being concentrated into one or more service units, reduces the processing burden of the target network domains on the cross-domain service requests, effectively shortens the access time of the cross-domain service requests, and enhances the stability of a requester network domain and the target network domain in the cross-domain access.
Those skilled in the art will appreciate that the figures are merely schematic representations of one preferred implementation scenario and that the blocks or flow diagrams in the figures are not necessarily required to practice the present application. Those skilled in the art will appreciate that the modules in the devices in the implementation scenario may be distributed in the devices in the implementation scenario according to the description of the implementation scenario, or may be located in one or more devices different from the present implementation scenario with corresponding changes. The modules of the implementation scenario may be combined into one module, or may be further split into a plurality of sub-modules.
The above application serial numbers are for description purposes only and do not represent the superiority or inferiority of the implementation scenarios. The above disclosure is only a few specific implementation scenarios of the present application, but the present application is not limited thereto, and any variations that can be made by those skilled in the art are intended to fall within the scope of the present application.
Claims (10)
1. A method for distributing traffic of cross-domain requests, the method comprising:
acquiring a service request sent by a requester network domain, wherein the service request carries a service code and a name identifier of the requester network domain;
acquiring a service type corresponding to the service request according to the service code;
acquiring traffic ratio information corresponding to the service request according to the name identifier of the requester network domain and the service category corresponding to the service request;
and distributing the service request to a service unit of a target network domain according to a preset proportion for processing according to the flow ratio information corresponding to the service request.
2. The method of claim 1, further comprising:
and acquiring the traffic ratio information of each name identifier of the requester network domain under each service category according to the current time and a preset traffic configuration plan.
3. The method according to claim 2, wherein the obtaining traffic proportioning information of each name identifier of the requester network domain under each service category according to the current time and a preset traffic configuration plan comprises:
when the current time is the same as the time node in the flow configuration plan, acquiring a flow configuration file corresponding to the time node in a database;
and analyzing the flow configuration file to obtain the flow ratio information of each name identifier of the requester network domain under each service type.
4. The method according to claim 3, wherein before the obtaining the service type corresponding to the service request according to the service code, the method further comprises:
acquiring configuration information of each service code in a database;
then, the obtaining the service category corresponding to the service request according to the service code includes:
and acquiring the service type corresponding to the service request in the configuration information of each service code according to the service code.
5. The method according to claim 4, wherein the obtaining traffic matching information corresponding to the service request according to the name identifier of the requester network domain and the service category corresponding to the service request includes:
generating a flow ratio identifier according to the name identifier of the requester network domain and the service type corresponding to the service request;
and acquiring the traffic ratio information corresponding to the service request from the traffic ratio information of each name identifier of the requester network domain under each service category according to the traffic ratio identifier.
6. The method of claim 5, wherein the distributing the service request to a service unit of a target network domain according to the traffic matching information corresponding to the service request comprises:
obtaining the name and the distribution proportion of the service unit of the target network domain to be distributed according to the flow ratio information corresponding to the service request;
and sending the service request to the service unit of the target network domain under the name according to the name and the distribution proportion of the service unit of the target network domain to be distributed.
7. The method of claim 6, further comprising:
and receiving a service processing result of the service request sent by the service unit of the target network domain.
8. An apparatus for distributing traffic across domain requests, the apparatus comprising:
the service request acquisition module is used for acquiring a service request sent by a requester network domain, wherein the service request carries a service code and a name identifier of the requester network domain;
the request information extraction module is used for acquiring the service type corresponding to the service request according to the service code;
a traffic matching obtaining module, configured to obtain traffic matching information corresponding to the service request according to the name identifier of the requester domain and the service category corresponding to the service request;
and the service request distribution module is used for distributing the service request to a service unit of a target network domain according to a preset proportion for processing according to the flow ratio information corresponding to the service request.
9. A storage medium having a computer program stored thereon, the computer program, when being executed by a processor, realizing the steps of the method of any one of claims 1 to 7.
10. A computer arrangement comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 7 when executed by the processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010127860.7A CN111431818B (en) | 2020-02-28 | 2020-02-28 | Cross-domain request flow distribution method and device, storage medium and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010127860.7A CN111431818B (en) | 2020-02-28 | 2020-02-28 | Cross-domain request flow distribution method and device, storage medium and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111431818A true CN111431818A (en) | 2020-07-17 |
| CN111431818B CN111431818B (en) | 2023-06-09 |
Family
ID=71551572
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010127860.7A Active CN111431818B (en) | 2020-02-28 | 2020-02-28 | Cross-domain request flow distribution method and device, storage medium and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111431818B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112751717A (en) * | 2021-01-05 | 2021-05-04 | 北京大禹智芯科技有限公司 | Service flow management system and method |
| CN114500542A (en) * | 2020-11-12 | 2022-05-13 | 中移信息技术有限公司 | Service flow distribution method, device, equipment and computer storage medium |
| CN115242723A (en) * | 2022-07-20 | 2022-10-25 | 中国银行股份有限公司 | Cross-system current limiting method and device |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102056333A (en) * | 2009-11-05 | 2011-05-11 | ***通信集团河南有限公司 | WAP (wireless application protocol) gateway, service processing method thereof and WAP proxy server |
| CN102209030A (en) * | 2011-05-19 | 2011-10-05 | 中兴通讯股份有限公司 | Service traffic splitting method, device and system |
| CN102487530A (en) * | 2010-12-02 | 2012-06-06 | 中兴通讯股份有限公司 | Data distribution method and system |
| CN103391299A (en) * | 2012-05-08 | 2013-11-13 | 深圳市腾讯计算机***有限公司 | Load balance method and load balance system |
| CN105515884A (en) * | 2014-09-24 | 2016-04-20 | 腾讯科技（深圳）有限公司 | Method and apparatus for counting flow |
| CN105898794A (en) * | 2016-04-08 | 2016-08-24 | 努比亚技术有限公司 | Device and method of transmitting data |
| CN107734017A (en) * | 2017-09-30 | 2018-02-23 | 平安科技（深圳）有限公司 | Data service method and system |
| CN108491267A (en) * | 2018-03-13 | 2018-09-04 | 百度在线网络技术（北京）有限公司 | Method and apparatus for generating information |
| CN109344045A (en) * | 2018-07-27 | 2019-02-15 | 阿里巴巴集团控股有限公司 | Operation system switching method, device, electronic equipment and storage medium |
| WO2019184727A1 (en) * | 2018-03-26 | 2019-10-03 | 华为技术有限公司 | Service upgrade management method, apparatus, and storage medium |
-
2020
- 2020-02-28 CN CN202010127860.7A patent/CN111431818B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102056333A (en) * | 2009-11-05 | 2011-05-11 | ***通信集团河南有限公司 | WAP (wireless application protocol) gateway, service processing method thereof and WAP proxy server |
| CN102487530A (en) * | 2010-12-02 | 2012-06-06 | 中兴通讯股份有限公司 | Data distribution method and system |
| CN102209030A (en) * | 2011-05-19 | 2011-10-05 | 中兴通讯股份有限公司 | Service traffic splitting method, device and system |
| CN103391299A (en) * | 2012-05-08 | 2013-11-13 | 深圳市腾讯计算机***有限公司 | Load balance method and load balance system |
| CN105515884A (en) * | 2014-09-24 | 2016-04-20 | 腾讯科技（深圳）有限公司 | Method and apparatus for counting flow |
| CN105898794A (en) * | 2016-04-08 | 2016-08-24 | 努比亚技术有限公司 | Device and method of transmitting data |
| CN107734017A (en) * | 2017-09-30 | 2018-02-23 | 平安科技（深圳）有限公司 | Data service method and system |
| CN108491267A (en) * | 2018-03-13 | 2018-09-04 | 百度在线网络技术（北京）有限公司 | Method and apparatus for generating information |
| WO2019184727A1 (en) * | 2018-03-26 | 2019-10-03 | 华为技术有限公司 | Service upgrade management method, apparatus, and storage medium |
| CN109344045A (en) * | 2018-07-27 | 2019-02-15 | 阿里巴巴集团控股有限公司 | Operation system switching method, device, electronic equipment and storage medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114500542A (en) * | 2020-11-12 | 2022-05-13 | 中移信息技术有限公司 | Service flow distribution method, device, equipment and computer storage medium |
| CN112751717A (en) * | 2021-01-05 | 2021-05-04 | 北京大禹智芯科技有限公司 | Service flow management system and method |
| CN112751717B (en) * | 2021-01-05 | 2021-11-05 | 北京大禹智芯科技有限公司 | Service flow management system and method |
| CN115242723A (en) * | 2022-07-20 | 2022-10-25 | 中国银行股份有限公司 | Cross-system current limiting method and device |
| CN115242723B (en) * | 2022-07-20 | 2024-03-01 | 中国银行股份有限公司 | Cross-system current limiting method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111431818B (en) | 2023-06-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111431818B (en) | Cross-domain request flow distribution method and device, storage medium and computer equipment | |
| US11070433B2 (en) | Network function NF management method and NF management device | |
| CN111163130B (en) | Network service system and data transmission method thereof | |
| KR20210119504A (en) | Communication method and apparatus, entity and computer readable storage medium | |
| KR20120021054A (en) | Method and apparatus for providing application service and thereof system | |
| CN105245500A (en) | Multimedia resource sharing method and device | |
| CN108810120B (en) | Block chain node communication method and device and block chain node | |
| CN110691042A (en) | Resource allocation method and device | |
| CN110868339A (en) | Node distribution method and device, electronic equipment and readable storage medium | |
| CN111414361A (en) | Label data storage method, device, equipment and readable storage medium | |
| EP3054401A1 (en) | Data label carrier information application and processing system and method | |
| CN101925158A (en) | System and method for obtaining number detail | |
| CN114245182B (en) | Live video stream acquisition method and device | |
| CN111275495A (en) | Advertisement putting monitoring method, device and system based on block chain | |
| CN108632399A (en) | A kind of address distribution method and device | |
| CN112788518A (en) | Location service processing method and related equipment | |
| CN106685708B (en) | Method, device and system for determining service relationship | |
| CN110830492B (en) | Method and system for mutually scheduling edge applications based on CoreDNS registration service | |
| CN112104680B (en) | Method, device and equipment for determining edge application and storage medium | |
| CN110933070A (en) | User identification method, system, equipment and computer readable storage medium | |
| CN112188591B (en) | Network access method, device, computer equipment and storage medium | |
| CN114157720A (en) | Method, device, electronic equipment and medium for processing service request | |
| CN110134547B (en) | Middleware-based repeated data deleting method and related device | |
| CN113392350A (en) | Page routing processing method, device, equipment, storage medium and program product | |
| CN108712507B (en) | Block link point access method and device and block link point |
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 |