Flow migration method

Abstract

The invention discloses a traffic migration method, and the method comprises the steps: intercepting target traffic transmitted to a first platform in response to an access request of a target URL (Uniform Resource Locator); wherein the target traffic is generated by accessing the target uniform resource locator URL; the access request carries target user information and target application programming interface API information; determining a batch migration condition of the target traffic according to an application scene of the access request; and under the condition that the target user information and the target application programming interface API information meet the batch migration condition, migrating the target traffic to a second platform.

Description

Technical Field

[0001] The present application belongs to the field of computer technology, and specifically relates to a traffic migration method. Background Art

[0002] During the end-side upgrade of the platform reconstruction, the traffic of the old platform needs to be migrated to the new platform. In related technologies, traffic migration based on the Domain Name System (DNS) migrates all traffic to the new platform in a full-volume switching manner, which will cause the new platform to have too much capacity and cannot smoothly transition from the old platform to the new platform. Batch traffic switching migrates in batches based on traffic proportion, which cannot be targeted and accurately migrated in various application scenarios. Summary of the invention

[0003] The embodiment of the present application provides a traffic migration method, which can solve the problem in the related art that batch migration based on traffic proportion cannot perform targeted and accurate migration in various application scenarios.

[0004] In a first aspect, an embodiment of the present application provides a traffic migration method, the method comprising: in response to an access request of a target uniform resource locator URL, intercepting target traffic transmitted to a first platform; wherein the target traffic is generated by accessing the target uniform resource locator URL; the access request carries target user information and target application programming interface API information; according to an application scenario of the access request, determining a batch migration condition for the target traffic; and when the target user information and the target application programming interface API information meet the batch migration condition, migrating the target traffic to a second platform.

[0005] In a second aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0006] In a third aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0007] In a fourth aspect, an embodiment of the present application provides a chip, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method described in the first aspect.

[0008] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes a program or instructions, which, when executed, implement the steps of the method described in the first aspect.

[0009] In an embodiment of the present application, by responding to an access request of a target uniform resource locator URL, the target traffic transmitted to the first platform is intercepted, wherein the target traffic is generated by accessing the target uniform resource locator URL, and the access request carries target user information and target application programming interface API information, and then according to the application scenario of the access request, the batch migration condition of the target traffic is determined, and when the target user information and the target application programming interface API information meet the batch migration condition, the target traffic is migrated to the second platform. Thus, the target traffic that meets the batch migration condition can be accurately migrated to the second platform according to the application scenario of the access request. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Figure 1 It is a flow chart of a traffic migration method provided in an embodiment of the present application; Figure 2 It is a structural schematic diagram of a traffic migration system provided in an embodiment of the present application; Figure 3 It is a flow chart of another traffic migration method provided in an embodiment of the present application; Figure 4 It is a flow chart of another traffic migration method provided in an embodiment of the present application; Figure 5 It is a structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0011] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0012] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first", "second", etc. are generally of one type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0013] The following is a detailed description of the traffic migration method provided in the embodiment of the present application through specific embodiments and their application scenarios in combination with the accompanying drawings.

[0014] Figure 1 The flow chart of the flow migration method provided by the embodiment of the present application is shown, and the method can be executed by an electronic device. Figure 1 , the method may include the following steps.

[0015] Step 102, in response to an access request of a target uniform resource locator URL, intercept target traffic transmitted to the first platform; wherein the target traffic is generated by accessing the target uniform resource locator URL; and the access request carries target user information and target application programming interface API information.

[0016] The target users may include existing users, that is, users registered before a specific date. They may also include users who are currently registering. The target traffic may be cloud disk user domain traffic.

[0017] Step 104: Determine a batch migration condition for the target traffic according to an application scenario of the access request.

[0018] Among them, for different application scenarios, the migration conditions for determining the target traffic are not all the same.

[0019] Step 106: When the target user information and the target application programming interface (API) information meet the batch migration condition, migrate the target traffic to the second platform.

[0020] In an embodiment of the present application, by responding to an access request of a target uniform resource locator URL, the target traffic transmitted to the first platform is intercepted, and the batch migration conditions of the target traffic are determined according to the application scenario of the access request. Then, a judgment is made based on the target user information and target application programming interface API information carried in the access request and the batch migration conditions, and if the target user information and the target application programming interface API information meet the batch migration conditions, the target traffic is migrated to the second platform. In this way, the target traffic that meets the batch migration conditions can be accurately migrated to the second platform according to the application scenario of the access request.

[0021] In one implementation, the above-mentioned step 104 determines the batch migration conditions of the target traffic according to the scenario of the access request, which may include: when the scenario of the access request is a user domain transparent login interface scenario or a first platform user login interface scenario, the batch migration conditions of the target traffic are: (1) the user mobile phone number is a whitelist mobile phone number; (2) the type value of the Application Programming Interface (API) is a preset value.

[0022] In an embodiment of the present application, an application scenario of an access request is provided, namely, a user domain transparent login interface scenario or a first platform user login interface scenario. In this scenario, whether to migrate the target traffic is determined through two dimensions. By judging whether the user's mobile phone number is a whitelisted mobile phone number and whether the type value of the application programming interface API is a preset value. That is to say, when the scenario of the access request is a user domain transparent login interface scenario or a first platform user login interface scenario, when it is determined that the user's mobile phone number is a whitelisted mobile phone number and the type value of the application programming interface API is a preset value, it is determined that the target traffic can be migrated to the second platform.

[0023] In one implementation, the target user information may include the target user's mobile phone number. The target application programming interface API information may include the type value of the target application programming interface API.

[0024] In an embodiment of the present application, the access request carries the target user's mobile phone number and the type value of the target application programming interface API. When the access request scenario is a user domain transparent login interface scenario or a first platform user login interface scenario, the target user's mobile phone number and the type value of the target application programming interface API can be used to determine whether the batch migration conditions are met to migrate the target traffic. Table 1 provides a correspondence between the type value of an application programming interface API and the user domain transparent login interface scenario.

[0025] Table 1.

[0026] In one implementation, the above step 106 migrates the target traffic to the second platform when the target user information and the target application programming interface API information meet the batch migration condition, including the following steps.

[0027] Step 1061, when the scenario of the access request is a user domain transparent login interface scenario or a first platform user login interface scenario, determine that the target user mobile phone number is the whitelist mobile phone number; and determine that the type value of the target application programming interface API is a preset value.

[0028] Step 1062: Migrate the target traffic to the second platform.

[0029] In an embodiment of the present application, when the scenario of the access request is a user domain transparent login interface scenario or a first platform user login interface scenario, by using the target user mobile phone number carried in the access request to determine whether the target user mobile phone number is a whitelist mobile phone number, and by using the type value of the target application programming interface API carried in the access request to determine that the type value is a preset value, it can be determined that the target user information and the target application programming interface API information meet the batch migration conditions, thereby migrating the target traffic to the second platform, thereby achieving accurate migration of the target traffic for the user domain transparent login interface scenario or the first platform user login interface scenario.

[0030] In one implementation, the above-mentioned step 104 determines the batch migration conditions of the target traffic according to the application scenario of the access request, and may include: when the application scenario of the access request is a scenario in which the first platform can parse the user's mobile phone number interface, the batch migration conditions of the target traffic are: the user's mobile phone number is a whitelisted mobile phone number.

[0031] In the embodiment of the present application, another application scenario of the access request is provided, that is, the first platform can parse the user's mobile phone number interface scenario, in which the user's mobile phone number is used as the dimension to determine whether to migrate the target traffic. That is to say, when the access request scenario is the first platform can parse the user's mobile phone number interface scenario, when it is determined that the user's mobile phone number is a whitelist mobile phone number, it is determined that the target traffic can be migrated to the second platform.

[0032] In one implementation, the target user information may include the target user's mobile phone number. The above step 106, when the target user information and the target application programming interface API information meet the batch migration conditions, migrates the target traffic to the second platform, which may include: when the application scenario of the access request is an interface scenario where the first platform can resolve the user's mobile phone number, determining that the target user's mobile phone number is the whitelist mobile phone number; and migrating the target traffic to the second platform.

[0033] In an embodiment of the present application, when the scenario of the access request is a scenario in which the first platform can resolve the user's mobile phone number interface, by using the target user's mobile phone number carried in the access request and determining that the target user's mobile phone number is a whitelisted mobile phone number, it can be determined that the target user information meets the batch migration conditions, thereby migrating the target traffic to the second platform, thereby achieving accurate migration of the target traffic for the scenario in which the first platform can resolve the user's mobile phone number interface.

[0034] In one implementation, the above-mentioned determination that the target user's mobile phone number is the whitelist mobile phone number may include the following steps.

[0035] Step 1: Use the first three digits of the target user's mobile phone number as a key and the last eight digits of the target user's mobile phone number as an offset corresponding to the key.

[0036] Step 2: When the key and the offset are found in a preset whitelist, determine that the user mobile phone number is a whitelist mobile phone number; wherein the preset whitelist stores the key and the offset corresponding to the whitelist mobile phone number.

[0037] Among them, the preset whitelist can be stored in the database Redis, and the keys and offsets corresponding to the whitelist mobile phone numbers in the preset whitelist are stored in the form of a bitmap (BitMap) for easy query.

[0038] In the embodiment of the present application, the first three digits of the target user's mobile phone number are used as a key and the last eight digits of the target user's mobile phone number are used as an offset corresponding to the key, and then a query is performed from a preset whitelist according to the key and the offset. When the key and the offset are queried from the preset whitelist, it is determined that the user's mobile phone number is a whitelist mobile phone number, thereby realizing the determination of whether the user's mobile phone number is a whitelist mobile phone number.

[0039] In one implementation, after determining the batch migration conditions of the target traffic according to the application scenario of the access request in the above step 104, the method further includes: if the user information and the application programming interface API information do not meet the batch migration conditions, transmitting the target traffic to the first platform.

[0040] In an embodiment of the present application, in response to an access request of a target uniform resource locator URL, the target traffic transmitted to the first platform is intercepted, and after the batch migration conditions of the target traffic are determined for the application scenario of the access request, if the target user information and the target application programming interface API information meet the batch migration conditions, the target traffic is migrated to the second platform. If the user information and the application programming interface API information do not meet the batch migration conditions, the target traffic is transmitted to the first platform. Thereby, for the application scenario, if the target user information and the target application programming interface API information meet the batch migration conditions, the target traffic is migrated to the second platform, and if the target user information and the target application programming interface API information do not meet the batch migration conditions, the target traffic continues to be migrated to the original first platform, and services continue to be provided to users, avoiding affecting the user experience.

[0041] In an implementation manner, the above method may further include: in a case where a migration failure of the target traffic is detected, switching the target traffic to be transmitted to the first platform.

[0042] In an embodiment of the present application, during the migration of the target traffic, a migration failure may occur. In the event of a failure, the target traffic is switched to be transmitted only to the original first platform, and services are continued to be provided to users through the original first platform to avoid affecting the user experience.

[0043] In one implementation, before intercepting the target traffic transmitted to the first platform in the above step 102, the method further includes the following steps.

[0044] Step 1021: Determine the transmission volume of the target traffic according to the network environment and the application scenario of the access request.

[0045] Step 1022: Divide the target flow into a plurality of batch flows according to the transmission volume.

[0046] The transmission amount may be a preset data amount or a certain proportion of data amount.

[0047] In the embodiment of the present application, the transmission volume of the target traffic is determined according to the network environment and the application scenario of the access request, and the target traffic is divided into multiple batch traffic according to the transmission volume, and then the traffic is intercepted for each batch traffic, and it is determined whether the batch traffic meets the batch migration conditions, and the batch traffic is migrated when the batch traffic meets the batch migration conditions. Through the embodiment of the present application, network congestion and data loss can be effectively avoided, and the network transmission efficiency and stability can be improved.

[0048] Figure 2 A schematic diagram of the structure of a flow migration system provided in an embodiment of the present application is shown. Figure 2 The system includes a client, an Nginx cluster of the old platform, an application server (such as Application as a Service (AAS)), an old platform resource pool, an intranet server load balancer (SLB) of the new platform, a user domain adaptation layer, and a new platform resource pool.

[0049] Figure 3 A flow chart of another traffic migration method provided in an embodiment of the present application is shown. The method can be applied to Figure 2 The traffic migration system shown in Figure 3 , the method may include the following steps.

[0050] Step 301, the client sends an interface request to the F5 load balancer.

[0051] Step 302, the F5 load balancer forwards the interface request to the Nginx cluster of the old platform.

[0052] Step 303, the Nginx cluster parses the request path and determines whether the interface requested by the interface is in the list of adapted interfaces. If not, step 304 is executed. If yes, step 305 is executed.

[0053] Step 304: the Nginx cluster sends an application service request to the application server of the old platform, and the application server of the old platform returns a response.

[0054] Step 305, the Nginx cluster determines whether the user information is in the whitelist. If not, execute step 304. If yes, execute step 306.

[0055] Step 306, the Nginx cluster sends an adaptation interface request to the user domain adaptation layer of the new platform through the intranet SLB of the new platform, and the user domain adaptation layer of the new platform returns a response to migrate the traffic to the user domain adaptation layer of the new platform through the requested adaptation interface.

[0056] In one implementation, Figure 4 A flow chart of another traffic migration method provided in an embodiment of the present application is shown. The method can be applied to Figure 2 The traffic migration system shown in Figure 4 , the method may include the following steps.

[0057] Step 401, the client sends an interface request to the F5 load balancer.

[0058] In step 402, the F5 load balancer forwards the interface request to the Nginx cluster of the old platform.

[0059] In step 403, the Nginx cluster determines whether the user is a whitelist user based on the user information. If not, step 404 is executed. If yes, step 405 is executed.

[0060] Step 404: the Nginx cluster sends an application service request to the application server of the old platform, and the application server of the old platform returns a response.

[0061] Step 405: The Nginx cluster intercepts the application service request sent to the application server of the old platform.

[0062] Step 406: The Nginx cluster forwards the application service request to the user domain adaptation layer of the new platform through the intranet SLB.

[0063] Step 407: The user domain adaptation layer of the new platform returns the request result.

[0064] Step 408 (optional): during the process from step 404 to step 405, if a failure occurs, the failure switch in the Nginx cluster is turned on to switch the application service request to the application server of the old platform.

[0065] In the embodiment of the present application, it is determined by user information or interface information whether to send the application service request to the application server of the old platform or the user domain adaptation layer of the new platform, so that normal service for the user can be guaranteed regardless of whether the application service request is sent to the application server of the old platform or the user domain adaptation layer of the new platform, thus avoiding affecting the user experience and achieving a smooth transition from the old platform to the new platform.

[0066] The embodiment of the present application further provides an electronic device, which is used to execute the above-mentioned traffic migration method. Figure 5A schematic diagram of the structure of an electronic device for implementing each embodiment of the present application. The electronic device may have relatively large differences due to different configurations or performances, and may include a processor (processor) 501, a communication interface (CommunicationsInterface) 502, a memory (memory) 503 and a communication bus 504, wherein the processor 501, the communication interface 502, and the memory 503 communicate with each other through the communication bus 504. The processor 501 can call a computer program stored in the memory 503 and can be run on the processor 501 to execute the various steps of the above-mentioned traffic migration method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0067] The above electronic device structure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, the input unit may include a graphics processing unit (GPU) and a microphone, and the display unit may be configured with a display panel in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit includes a touch panel and at least one of other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0068] The memory can be used to store software programs and various data. The memory may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory may include a volatile memory or a non-volatile memory, or the memory may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DRRAM).

[0069] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor.

[0070] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned traffic migration method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0071] The processor is a processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0072] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned traffic migration method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0073] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0074] An embodiment of the present application also provides a computer program product, which includes a computer program stored on a non-transitory computer-readable storage medium, and the computer program includes a program or instructions. When the program or instructions are executed, the various processes of the above-mentioned traffic migration method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, they will not be repeated here.

[0075] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0076] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0077] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A traffic migration method, characterized in that: include: In response to an access request of a target uniform resource locator URL, intercepting target traffic transmitted to the first platform; wherein the target traffic is generated by accessing the target uniform resource locator URL; the access request carries target user information and target application programming interface API information; Determining batch migration conditions for the target traffic according to an application scenario of the access request; When the target user information and the target application programming interface API information meet the batch migration condition, the target traffic is migrated to the second platform.

2. The method according to claim 1, characterized in that The determining, according to the application scenario of the access request, a batch migration condition of the target traffic includes: When the application scenario of the access request is a user domain transparent login interface scenario or a first platform user login interface scenario, the batch migration condition of the target traffic is: The user's mobile phone number is a whitelist mobile phone number; The type value of the application programming interface API is a preset value.

3. The method according to claim 2, characterized in that The target user information includes the target user's mobile phone number; the target application programming interface API information includes the type value of the target application programming interface API.

4. The method according to claim 3, characterized in that When the target user information and the target application programming interface (API) information meet the batch migration condition, migrating the target traffic to the second platform includes: In the case where the access request scenario is a user domain transparent login interface scenario or a first platform user login interface scenario, determining that the target user mobile phone number is the whitelist mobile phone number; and determining that the type value of the target application programming interface API is a preset value; Migrate the target traffic to the second platform.

5. The method according to claim 1, characterized in that: The determining, according to the application scenario of the access request, a batch migration condition of the target traffic includes: When the application scenario of the access request is an interface scenario in which the first platform can resolve the user's mobile phone number, the batch migration conditions of the target traffic are: The user's mobile phone number is a whitelist mobile phone number.

6. The method according to claim 5, characterized in that The target user information includes a target user mobile phone number; when the target user information and the target application programming interface (API) information meet the batch migration condition, migrating the target traffic to the second platform includes: In a case where the application scenario of the access request is an interface scenario in which the first platform can parse the user's mobile phone number, determining that the target user's mobile phone number is the whitelist mobile phone number; Migrate the target traffic to the second platform.

7. The method according to claim 4 or 6, characterized in that: The step of determining that the target user's mobile phone number is the whitelist mobile phone number includes: The first three digits of the target user's mobile phone number are used as a key and the last eight digits of the target user's mobile phone number are used as an offset corresponding to the key; When the key and the offset are found in a preset whitelist, the user mobile phone number is determined to be a whitelist mobile phone number; wherein the preset whitelist stores the key and the offset corresponding to the whitelist mobile phone number.

8. The method according to claim 1, characterized in that After determining the batch migration conditions of the target traffic according to the application scenario of the access request, the method further includes: When the user information and the application programming interface (API) information do not satisfy the batch migration condition, the target traffic is transmitted to the first platform.

9. The method according to claim 1, characterized in that: The method further comprises: When a migration failure of the target traffic is detected, the target traffic is switched to be transmitted to the first platform.

10. The method according to claim 1, characterized in that Before intercepting the target traffic transmitted to the first platform, the method further includes: Determining the transmission volume of the target traffic according to the network environment and the application scenario of the access request; The target flow is divided into a plurality of batch flows according to the transmission volume.

Images