CN112860271A - Method, device, equipment and storage medium for switching between new system and old system - Google Patents

Method, device, equipment and storage medium for switching between new system and old system Download PDF

Info

Publication number
CN112860271A
CN112860271A CN202110342609.7A CN202110342609A CN112860271A CN 112860271 A CN112860271 A CN 112860271A CN 202110342609 A CN202110342609 A CN 202110342609A CN 112860271 A CN112860271 A CN 112860271A
Authority
CN
China
Prior art keywords
new
state
abnormal
interface
calling
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
Application number
CN202110342609.7A
Other languages
Chinese (zh)
Other versions
CN112860271B (en
Inventor
沈文东
陆沛卿
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Industrial and Commercial Bank of China Ltd ICBC
Original Assignee
Industrial and Commercial Bank of China Ltd ICBC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Industrial and Commercial Bank of China Ltd ICBC filed Critical Industrial and Commercial Bank of China Ltd ICBC
Priority to CN202110342609.7A priority Critical patent/CN112860271B/en
Publication of CN112860271A publication Critical patent/CN112860271A/en
Application granted granted Critical
Publication of CN112860271B publication Critical patent/CN112860271B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/547Remote procedure calls [RPC]; Web services
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/60Software deployment

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Hardware Redundancy (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Provided are a method, a device, equipment and a storage medium for switching between an old system and a new system, wherein the method comprises the following steps: performing flow switching on a target interface of a target calling party according to a flow table to be switched to obtain a new calling relation after the flow switching; monitoring the success rate of the target calling party calling the target interface in the new calling relation in real time; monitoring the basic state corresponding to the target interface in the new calling relation in real time; and determining and switching back an interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation. The method provided by the invention can reduce labor consumption and realize automatic system switching.

Description

Method, device, equipment and storage medium for switching between new system and old system
Technical Field
The present application relates to the field of system switching, and in particular, to a method, an apparatus, a device, and a storage medium for switching between an old system and a new system.
Background
In the current nationalized wave tide, new and old system switching is a common project. In a large project of a bank, the switching process of the old system and the new system is quite complex, for example, the process of switching a personal financial application from an IBM host to a homemade development platform host core, which involves switching of multiple interfaces of 108 channel application systems 4700. Because each interface corresponds to a plurality of calling parties (including bank counter, ATM, mobile phone bank, etc.), each interface needs to be cut into a plurality of batches of flows, the accumulated flow cutting scene exceeds 1 ten thousand times, and a scene that the old system needs to be cut back due to insufficient testing or other problems exists in the switching process.
In the prior art, in the switching and back-switching processes of new and old systems, the switching or back-switching operation is mostly executed after the switching or back-switching condition is manually judged. The process of manual judgment consumes manpower, and the degree of automation and informatization is low. Therefore, a method for switching between new and old systems is needed to reduce the labor consumption and achieve automatic system switching.
Disclosure of Invention
The embodiments herein aim to provide a method, an apparatus, a device and a storage medium for switching between a new system and an old system, so as to reduce labor consumption and realize automatic system switching.
To achieve the above object, in one aspect, an embodiment herein provides a method for switching between an old system and a new system, where the method includes:
performing flow switching on a target interface of a target calling party according to a flow table to be switched to obtain a new calling relation after the flow switching;
monitoring the success rate of the target calling party calling the target interface in the new calling relation in real time;
monitoring the basic state corresponding to the target interface in the new calling relation in real time;
and determining and switching back an interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
Preferably, the determining and switching back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation includes:
judging whether the success rate of the new call relation is outside the confidence interval of the new call relation and continuously exceeds a preset time period;
and if the success rate of the new call relation is outside the confidence interval of the new call relation and continuously exceeds a preset time period, determining the new call relation as an abnormal new call relation, and switching back an interface corresponding to the abnormal new call relation.
Preferably, the determining and switching back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation further includes:
determining the number of abnormal new call relations corresponding to the same interface in a set time period;
judging whether the number is larger than a set number;
and if the number is larger than the set number, determining all new calling relations corresponding to the interface as abnormal new calling relations.
Preferably, the basic state corresponding to the target interface in the new invocation relationship includes: network state, fault domain state, CPU state, memory state and server heartbeat detection state.
Preferably, the determining and switching back the interface corresponding to the abnormal new invocation relation according to the basic state corresponding to the target interface in the new invocation relation includes:
determining a state flag bit of each state corresponding to the target interface in the new call relation according to the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new call relation;
judging whether all state flag bits corresponding to the target interface in the new calling relationship have abnormal marks or not;
and if the abnormal mark exists, determining the new calling relationship as an abnormal new calling relationship, and switching back an interface corresponding to the abnormal new calling relationship.
Preferably, determining the status flag bit of each state corresponding to the target interface in the new invocation relationship according to the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new invocation relationship includes:
judging whether an abnormal state exists in the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new calling relationship, wherein the abnormal state continuously exceeds a calibration time period;
if an abnormal state exists in the states and the abnormality lasts for more than a calibration time period, determining that the state flag bit corresponding to the state is an abnormal flag;
otherwise, the state flag bit corresponding to the default state is a normal flag.
Preferably, the determining and switching back the interface corresponding to the abnormal new invocation relation according to the basic state corresponding to the target interface in the new invocation relation further includes:
and determining all new calling relations which are the same as the interface called by the abnormal new calling relation as the abnormal new calling relation.
In another aspect, embodiments herein provide an apparatus for switching between an old system and a new system, the apparatus including:
a tangential flow module: performing flow switching on a target interface of a target calling party according to a flow table to be switched to obtain a new calling relation after the flow switching;
success rate monitoring module: monitoring the success rate of the target calling party calling the target interface in the new calling relation in real time;
basic state monitoring module: monitoring the basic state corresponding to the target interface in the new calling relation in real time;
back cutting the module: and determining and switching back an interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
In yet another aspect, embodiments herein also provide a computer device comprising a memory, a processor, and a computer program stored on the memory, the computer program, when executed by the processor, performing the instructions of any one of the methods described above.
In yet another aspect, embodiments herein also provide a computer-readable storage medium having stored thereon a computer program, which when executed by a processor of a computer device, performs the instructions of any one of the methods described above.
According to the technical scheme provided by the embodiment, the embodiment performs switching of the new system and the old system through the pre-established flow table to be switched, and determines the abnormal new calling relationship and switches back the interface of the abnormal new calling relationship by monitoring the success rate of the target calling party calling the target interface in the new calling relationship and the basic state of the target interface in real time. The whole process is automatically switched and back-switched through the system without manual judgment and intervention, so that the labor consumption is reduced, and the automation degree is higher.
In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a flowchart illustrating a method for switching between an old system and a new system according to an embodiment of the present disclosure;
fig. 2 is a schematic flowchart illustrating an interface for determining an abnormal new call relationship according to a success rate according to an embodiment of the present disclosure;
fig. 3 is another schematic flowchart illustrating an interface for determining an abnormal new call relationship according to a success rate according to an embodiment of the present disclosure;
fig. 4 is a schematic flowchart illustrating an interface for determining an abnormal new invocation relationship according to a base state according to an embodiment of the present disclosure;
FIG. 5 is another flowchart of an interface for determining an abnormal new invocation relationship according to a base state provided in an embodiment of the present disclosure;
fig. 6 is a schematic block diagram illustrating an apparatus for switching between an old system and a new system according to an embodiment of the present disclosure;
fig. 7 shows a schematic structural diagram of a computer device provided in an embodiment herein.
Description of the symbols of the drawings:
100. a flow cutting module;
200. a success rate monitoring module;
300. a basic state monitoring module;
400. cutting back the module;
702. a computer device;
704. a processor;
706. a memory;
708. a drive mechanism;
710. an input/output module;
712. an input device;
714. an output device;
716. a presentation device;
718. a graphical user interface;
720. a network interface;
722. a communication link;
724. a communication bus.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments herein without making any creative effort, shall fall within the scope of protection.
In the prior art, in the switching and back-switching processes of new and old systems, the switching or back-switching operation is mostly executed after the switching or back-switching condition is manually judged. The process of manual judgment consumes manpower, and the degree of automation and informatization is low.
In order to solve the above problems, embodiments herein provide a method for switching between a new system and an old system, which can reduce labor consumption and implement automatic system switching. Fig. 1 is a schematic diagram of steps of a method for switching between an old system and a new system provided in an embodiment herein, and the present specification provides the method operation steps as described in the embodiment or the flowchart, but more or less operation steps may be included based on conventional or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual system or apparatus product executes, it can execute sequentially or in parallel according to the method shown in the embodiment or the figures.
Referring to fig. 1, a method for switching between an old system and a new system, the method comprising:
s101: and performing flow switching on the target interface of the target calling party according to the flow table to be switched to obtain a new calling relation after the flow switching.
S102: and monitoring the success rate of the target calling party calling the target interface in the new calling relation in real time.
S103: and monitoring the basic state corresponding to the target interface in the new calling relation in real time.
S104: and determining and switching back an interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
And switching the flow of the new system and the old system through a pre-established flow table to be switched, and determining an abnormal new calling relationship and switching back the interface of the abnormal new calling relationship by monitoring the success rate of the target calling party calling the target interface in the new calling relationship and the basic state of the target interface in real time. The whole process is automatically switched and back-switched through the system without manual judgment and intervention, so that the labor consumption is reduced, and the automation degree is higher.
Before switching between a new system and an old system, a flow table to be cut is established, and the call relationship between a caller and an interface in the old system and the call relationship between the caller and the interface in the new system are recorded in the flow table to be cut. As shown in table 1, the calling relationship between the caller and the interface in the new and old systems of legal entity relationship query interface is recorded, the first piece of data is the calling relationship in the old system, and the second piece of data is the calling relationship in the new system.
TABLE 1
Figure BDA0002999699610000061
After the switching list is established, the calling party needs to be batched before the system switching is performed. In a calling relationship (one calling party calls one interface), all calling parties are divided into a test point batch, a first batch and a second batch … … Nth batch, and the specific batch number can be determined according to the actual conditions of different systems. Only after the trial batch is successfully cut and continuously and successfully operated for a period of time, the first batch can be cut, the second batch can be cut after the first batch is successfully cut and continuously and successfully operated for a period of time, and the third batch to the Nth batch are the same, so that the details are not repeated.
Before system switching, all interfaces need to perform function test and switch switching test to check whether the interfaces are normal, and similarly, all callers need to perform function test and switch switching test to check whether the callers are normal. After the test of the interface and the caller passes, the caller in the test set can be started, and the interface of the caller is cut according to the flow table to be cut, so as to obtain a new call relationship after the cut (one caller calls one interface in the new system). The new system has several interfaces A, B … …, and several callers 1 and 2 … … call several interfaces separately to form several new calling relations, such as caller 1 calling interface A and caller 1 calling interface B, which are two new calling relations.
Referring to fig. 2, in this embodiment, the determining and switching back the interface corresponding to the abnormal new invocation relation according to the success rate of the new invocation relation includes:
s201: and judging whether the success rate of the new call relation is outside the confidence interval of the new call relation and continuously exceeds a preset time period.
S202: and if the success rate of the new call relation is outside the confidence interval of the new call relation and continuously exceeds a preset time period, determining the new call relation as an abnormal new call relation, and switching back an interface corresponding to the abnormal new call relation.
Specifically, a confidence interval of a new calling relationship is determined, a success rate of a target calling party in the new calling relationship calling a target interface in an old system is obtained, and the confidence interval is determined according to the success rate. The probability of successful calling of the target calling party in the old system within each period of time (which can be 1 hour) can be obtained as a success rate, and multiple success rates of the target calling party in the old system within a period of time (which can be 24 hours) can be obtained by multiple times of obtaining. And solving the mean value X of the power and the standard deviation S of the power to obtain a confidence interval of [ X-3 × S, X +3 × S ]. And monitoring the success rate of the new call relation (in the new system) in real time, and when the power is out of the confidence interval and continuously exceeds a preset time period, determining the new call relation is an abnormal new call relation, wherein the preset time period can be set according to actual working requirements.
By the method, when the power is outside the confidence interval for a long time, the target interface can be automatically switched back without manual intervention, and the automation degree is high.
In addition, if the calling party in the abnormal new calling relation is a test point batch, only the interface corresponding to the test point batch needs to be switched back; if the caller in the abnormal new call relationship is the first batch, the trial batch and the interface corresponding to the first batch need to be switched back, and the second batch to the Nth batch are the same, so that the details are not repeated. Because the problems which do not occur in the pilot batch occur in the first batch or the Nth batch, the problem expansion can be prevented as much as possible by the method, and the stable and normal operation of a new system is ensured.
Referring to fig. 3, in this embodiment, the determining and switching back the interface corresponding to the abnormal new invocation relation according to the success rate of the new invocation relation further includes:
s203: and determining the number of abnormal new call relations corresponding to the same interface in a set time period.
S204: and judging whether the number is larger than a set number.
S205: and if the number is larger than the set number, determining all new calling relations corresponding to the interface as abnormal new calling relations.
Specifically, the set time period and the set number may be determined according to the actual condition of the system, the set time period may be one day (24 hours), and if a large number (exceeding the set number) of abnormal new invocation relationships correspond to the same interface in one day, it is proved that the interface may have a fault, all the new invocation relationships corresponding to the interface need to be determined as abnormal new invocation relationships, and the interface is called to be switched back all over. If the calling party in the abnormal new calling relation is a test point batch, only the interface corresponding to the test point batch needs to be switched back; if the caller in the abnormal new call relationship is the first batch, the trial batch and the interface corresponding to the first batch need to be switched back, and the second batch to the Nth batch are the same, so that the details are not repeated. Because the interface may have problems, the problem of the interface can be prevented from being enlarged, the radiation range of the problem is reduced, and the new system can run stably.
In this embodiment, the base state corresponding to the target interface in the new invocation relation includes: network state, fault domain state, CPU state, memory state and server heartbeat detection state.
Referring to fig. 4, further, the determining and switching back the interface corresponding to the abnormal new invocation relationship according to the base state corresponding to the target interface in the new invocation relationship includes:
s301: and determining the status flag bit of each state corresponding to the target interface in the new call relationship according to the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new call relationship.
S302: and judging whether abnormal marks exist in all the state flag bits corresponding to the target interface in the new calling relationship.
S303: and if the abnormal mark exists, determining the new calling relationship as an abnormal new calling relationship, and switching back an interface corresponding to the abnormal new calling relationship.
Further, determining a status flag bit of each status corresponding to the target interface in the new invocation relationship according to the network status, the fault domain status, the CPU status, the memory status, and the server heartbeat detection status corresponding to the target interface in the new invocation relationship includes:
judging whether an abnormal state exists in the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new calling relationship, wherein the abnormal state continuously exceeds a calibration time period;
if an abnormal state exists in the states and the abnormality lasts for more than a calibration time period, determining that the state flag bit corresponding to the state is an abnormal flag;
otherwise, the state flag bit corresponding to the default state is a normal flag.
Specifically, the network state of the area where the server in the new system to which the target interface belongs is located, the fault domain state of the new system container, the server CPU state in the new system, the server memory state in the new system and the server heartbeat detection state in the new system are monitored in real time. The calibration time period can be set according to the specific condition of the system, and initially, the state flag bits of the states are all defaulted to be normal marks to indicate that the states are normal.
When the network has faults, such as network disconnection and the like, and the situation continuously exceeds a calibration time period, setting the state flag bit corresponding to the network state as an abnormal flag. And when the fault domain is abnormal, such as storage fault of a hard disk occurs and the like and continuously exceeds a calibration time period, setting the flag bit corresponding to the fault domain state as an abnormal flag. When the CPU occupancy rate exceeds a first extreme value (which can be set to 90% according to the system condition) and continuously exceeds the calibration time period, setting the flag bit corresponding to the CPU state as an abnormal flag. And when the memory occupancy rate exceeds a second extreme value (which can be set to 90% according to the system condition) and continuously exceeds the calibration time period, setting the flag bit corresponding to the memory state as an abnormal flag. And when the server heartbeat detects disconnection and continuously exceeds a calibration time period, setting a flag bit corresponding to the server state as an abnormal flag.
Referring to fig. 5, further, the determining and switching back the interface corresponding to the abnormal new invocation relationship according to the base state corresponding to the target interface in the new invocation relationship further includes:
s304: and determining all new calling relations which are the same as the interface called by the abnormal new calling relation as the abnormal new calling relation.
Specifically, as long as one abnormal flag exists in all the status flag bits corresponding to the target interface, the new call relationship is determined as an abnormal new call relationship, and the interface corresponding to the abnormal new call relationship is switched back. And all the calling relations calling the interface are determined as abnormal new calling relations, and then the interface is switched back. If the calling party in the abnormal new calling relation is a test point batch, only the interface corresponding to the test point batch needs to be switched back; if the caller in the abnormal new call relationship is the first batch, the trial batch and the interface corresponding to the first batch need to be switched back, and the second batch to the Nth batch are the same, so that the details are not repeated.
Based on the method for switching between the new system and the old system, the embodiment of the invention also provides a device for switching between the new system and the old system. The apparatus may include systems (including distributed systems), software (applications), modules, components, servers, clients, etc. that employ the methods described herein in embodiments, in conjunction with any necessary apparatus to implement the hardware. Based on the same innovative concepts, embodiments herein provide an apparatus as described in the following embodiments. Since the implementation scheme of the apparatus for solving the problem is similar to that of the method, the specific apparatus implementation in the embodiment of the present disclosure may refer to the implementation of the foregoing method, and repeated details are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Specifically, fig. 6 is a schematic block diagram of an embodiment of an apparatus for switching between an old system and a new system provided in an embodiment of the present disclosure, and referring to fig. 6, the apparatus for switching between an old system and a new system provided in an embodiment of the present disclosure includes: a flow cutting module 100, a success rate monitoring module 200, a basic state monitoring module 300 and a back cutting module 400.
The tangential flow module 100: performing flow switching on a target interface of a target calling party according to a flow table to be switched to obtain a new calling relation after the flow switching;
success rate monitoring module 200: monitoring the success rate of the target calling party calling the target interface in the new calling relation in real time;
basic state monitoring module 300: monitoring the basic state corresponding to the target interface in the new calling relation in real time;
back cutting module 400: and determining and switching back an interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
In an embodiment herein, referring to fig. 7, a computer device 702 is also provided. Computer device 702 may include one or more processors 704, such as one or more Central Processing Units (CPUs) or Graphics Processors (GPUs), each of which may implement one or more hardware threads. The computer device 702 may also include any memory 706 for storing any kind of information, such as code, settings, data, etc., and in a particular embodiment, a computer program on the memory 706 and executable on the processor 704, which computer program when executed by the processor 704 may perform instructions according to the above-described method. For example, and without limitation, the memory 706 can include any one or more of the following in combination: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 702. In one case, when the processor 704 executes associated instructions that are stored in any memory or combination of memories, the computer device 702 can perform any of the operations of the associated instructions. The computer device 702 also includes one or more drive mechanisms 708, such as a hard disk drive mechanism, an optical disk drive mechanism, or the like, for interacting with any memory.
Computer device 702 can also include an input/output module 710(I/O) for receiving various inputs (via input device 712) and for providing various outputs (via output device 714). One particular output mechanism may include a presentation device 716 and an associated graphical user interface 718 (GUI). In other embodiments, input/output module 710(I/O), input device 712, and output device 714 may also not be included, as only one computer device in a network. Computer device 702 can also include one or more network interfaces 720 for exchanging data with other devices via one or more communication links 722. One or more communication buses 724 couple the above-described components together.
Communication link 722 may be implemented in any manner, such as over a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. Communication link 722 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.
Corresponding to the methods in fig. 1-5, the embodiments herein also provide a computer-readable storage medium having stored thereon a computer program, which, when executed by a processor, performs the steps of the above-described method.
Embodiments herein also provide computer readable instructions, wherein when executed by a processor, a program thereof causes the processor to perform the method as shown in fig. 1-5.
It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.
It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments herein.
In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The principles and embodiments of this document are explained herein using specific examples, which are presented only to aid in understanding the methods and their core concepts; meanwhile, for the general technical personnel in the field, according to the idea of this document, there may be changes in the concrete implementation and the application scope, in summary, this description should not be understood as the limitation of this document.

Claims (10)

1. A method for switching between old and new systems, the method comprising:
performing flow switching on a target interface of a target calling party according to a flow table to be switched to obtain a new calling relation after the flow switching;
monitoring the success rate of the target calling party calling the target interface in the new calling relation in real time;
monitoring the basic state corresponding to the target interface in the new calling relation in real time;
and determining and switching back an interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
2. The method according to claim 1, wherein determining and switching back an interface corresponding to an abnormal new call relationship according to the success rate of the new call relationship comprises:
judging whether the success rate of the new call relation is outside the confidence interval of the new call relation and continuously exceeds a preset time period;
and if the success rate of the new call relation is outside the confidence interval of the new call relation and continuously exceeds a preset time period, determining the new call relation as an abnormal new call relation, and switching back an interface corresponding to the abnormal new call relation.
3. The method according to claim 2, wherein the determining and switching back the interface corresponding to the abnormal new call relation according to the success rate of the new call relation further comprises:
determining the number of abnormal new call relations corresponding to the same interface in a set time period;
judging whether the number is larger than a set number;
and if the number is larger than the set number, determining all new calling relations corresponding to the interface as abnormal new calling relations.
4. The method according to claim 1, wherein the base state corresponding to the target interface in the new invocation relation includes: network state, fault domain state, CPU state, memory state and server heartbeat detection state.
5. The method according to claim 4, wherein the determining and switching back the interface corresponding to the abnormal new call relationship according to the basic state corresponding to the target interface in the new call relationship comprises:
determining a state flag bit of each state corresponding to the target interface in the new call relation according to the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new call relation;
judging whether all state flag bits corresponding to the target interface in the new calling relationship have abnormal marks or not;
and if the abnormal mark exists, determining the new calling relationship as an abnormal new calling relationship, and switching back an interface corresponding to the abnormal new calling relationship.
6. The method according to claim 5, wherein the determining the status flag bit of each status corresponding to the target interface in the new invocation relationship according to the network status, the fault domain status, the CPU status, the memory status, and the server heartbeat detection status corresponding to the target interface in the new invocation relationship comprises:
judging whether an abnormal state exists in the network state, the fault domain state, the CPU state, the memory state and the server heartbeat detection state corresponding to the target interface in the new calling relationship, wherein the abnormal state continuously exceeds a calibration time period;
if an abnormal state exists in the states and the abnormality lasts for more than a calibration time period, determining that the state flag bit corresponding to the state is an abnormal flag;
otherwise, the state flag bit corresponding to the default state is a normal flag.
7. The method according to claim 4, wherein the determining and switching back the interface corresponding to the abnormal new call relation according to the basic state corresponding to the target interface in the new call relation further comprises:
and determining all new calling relations which are the same as the interface called by the abnormal new calling relation as the abnormal new calling relation.
8. An apparatus for switching between old and new systems, the apparatus comprising:
a tangential flow module: performing flow switching on a target interface of a target calling party according to a flow table to be switched to obtain a new calling relation after the flow switching;
success rate monitoring module: monitoring the success rate of the target calling party calling the target interface in the new calling relation in real time;
basic state monitoring module: monitoring the basic state corresponding to the target interface in the new calling relation in real time;
back cutting the module: and determining and switching back an interface corresponding to the abnormal new call relation according to the success rate of the new call relation or the basic state corresponding to the target interface in the new call relation.
9. A computer device comprising a memory, a processor, and a computer program stored on the memory, wherein the computer program, when executed by the processor, performs the instructions of the method of any one of claims 1-7.
10. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor of a computer device, is adapted to carry out the instructions of the method according to any one of claims 1-7.
CN202110342609.7A 2021-03-30 2021-03-30 New and old system switching method, device, equipment and storage medium Active CN112860271B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110342609.7A CN112860271B (en) 2021-03-30 2021-03-30 New and old system switching method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110342609.7A CN112860271B (en) 2021-03-30 2021-03-30 New and old system switching method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN112860271A true CN112860271A (en) 2021-05-28
CN112860271B CN112860271B (en) 2024-03-29

Family

ID=75993249

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110342609.7A Active CN112860271B (en) 2021-03-30 2021-03-30 New and old system switching method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN112860271B (en)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600384A (en) * 2018-12-28 2019-04-09 江苏满运软件科技有限公司 Flow switching method, system, equipment and storage medium in RPC interface upgrade
CN109710447A (en) * 2019-01-08 2019-05-03 网易无尾熊(杭州)科技有限公司 For the method, apparatus of data access, medium and calculate equipment
CN110298650A (en) * 2019-05-21 2019-10-01 深圳壹账通智能科技有限公司 Interface calls charging method, device, equipment and storage medium
CN110737575A (en) * 2018-07-20 2020-01-31 北京金山云网络技术有限公司 interface testing method, device, electronic equipment and storage medium
CN111343294A (en) * 2020-02-14 2020-06-26 京东数字科技控股有限公司 Network environment switching method, device, equipment and computer readable storage medium
CN111679968A (en) * 2020-04-28 2020-09-18 平安普惠企业管理有限公司 Interface calling abnormity detection method and device, computer equipment and storage medium
CN112346794A (en) * 2020-10-21 2021-02-09 深圳鼎盛电脑科技有限公司 Interface calling method, device, equipment and medium

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110737575A (en) * 2018-07-20 2020-01-31 北京金山云网络技术有限公司 interface testing method, device, electronic equipment and storage medium
CN109600384A (en) * 2018-12-28 2019-04-09 江苏满运软件科技有限公司 Flow switching method, system, equipment and storage medium in RPC interface upgrade
CN109710447A (en) * 2019-01-08 2019-05-03 网易无尾熊(杭州)科技有限公司 For the method, apparatus of data access, medium and calculate equipment
CN110298650A (en) * 2019-05-21 2019-10-01 深圳壹账通智能科技有限公司 Interface calls charging method, device, equipment and storage medium
CN111343294A (en) * 2020-02-14 2020-06-26 京东数字科技控股有限公司 Network environment switching method, device, equipment and computer readable storage medium
CN111679968A (en) * 2020-04-28 2020-09-18 平安普惠企业管理有限公司 Interface calling abnormity detection method and device, computer equipment and storage medium
CN112346794A (en) * 2020-10-21 2021-02-09 深圳鼎盛电脑科技有限公司 Interface calling method, device, equipment and medium

Also Published As

Publication number Publication date
CN112860271B (en) 2024-03-29

Similar Documents

Publication Publication Date Title
EP3852420B1 (en) Method and device for determining load threshold
US9779377B2 (en) Customization of event management and incident management policies
WO2011009000A1 (en) Method and apparatus for telecommunications network performance anomaly events detection and notification
CN113434337B (en) Retry strategy control method and device and electronic equipment
CN112286770A (en) Alarm notification method, device, computer equipment and storage medium
CN110875841A (en) Alarm information pushing method and device and readable storage medium
CN114268957A (en) Abnormal business data processing method, device, server and storage medium
CN112968811A (en) PFC exception handling method and device for RDMA network
CN112860271A (en) Method, device, equipment and storage medium for switching between new system and old system
CN113760634A (en) Data processing method and device
CN115373729B (en) Method and device for processing auditing node
CN109600250B (en) Service system fault notification method, device, electronic device and storage medium
CN113726572B (en) Method, system, equipment and storage medium for automatically modifying switch port
CN110968456A (en) Method and device for processing fault disk in distributed storage system
CN112559233B (en) Method, device, equipment and computer readable medium for identifying fault type
US10897401B2 (en) Determining the importance of network devices based on discovered topology, managed endpoints, and activity
CN111385167B (en) Network connection recovery method, device, computer device and storage medium
CN112559084A (en) Method, apparatus, device, storage medium, and program product for administering a service
CN115118673B (en) Service traffic migration method, device, equipment and computer readable storage medium
CN107783852B (en) Dump file generation method and terminal
CN115242621B (en) Network private line monitoring method, device, equipment and computer readable storage medium
CN113259531B (en) Automatic voice service operation and maintenance method and system for call center
CN113761066A (en) Transaction processing method and device
CN115065946B (en) Short message sending method, device, equipment and medium
CN114338535B (en) Zookeeper-based cluster current limiting method, system, equipment and storage medium

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