WO2019169763A1 - Electronic apparatus, service system risk control method, and storage medium - Google Patents

Electronic apparatus, service system risk control method, and storage medium Download PDF

Info

Publication number
WO2019169763A1
WO2019169763A1 PCT/CN2018/089455 CN2018089455W WO2019169763A1 WO 2019169763 A1 WO2019169763 A1 WO 2019169763A1 CN 2018089455 W CN2018089455 W CN 2018089455W WO 2019169763 A1 WO2019169763 A1 WO 2019169763A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
request
client
priority level
threshold
Prior art date
Application number
PCT/CN2018/089455
Other languages
French (fr)
Chinese (zh)
Inventor
江亮
Original Assignee
平安科技（深圳）有限公司
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 平安科技（深圳）有限公司 filed Critical 平安科技（深圳）有限公司
Publication of WO2019169763A1 publication Critical patent/WO2019169763A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5038—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the execution order of a plurality of tasks, e.g. taking priority or time dependency constraints into consideration
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/30—Monitoring
    • G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements 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/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/505—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering the load
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/81—Threshold

Definitions

  • the present application relates to the field of Internet data interaction, and in particular, to an electronic device, a business system risk control method, and a storage medium.
  • the present application proposes an electronic device, an internet service system risk warning method, and a storage medium, which can accurately and effectively control the operational risk of the Internet service system.
  • the present application provides an electronic device including a memory and a processor connected to the memory, the processor for executing a business system risk control program stored on the memory,
  • the business system risk control program is implemented by the processor to implement the following steps:
  • the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
  • the present application further provides a service system risk control method, where the method includes the following steps:
  • the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
  • the present application further provides a computer readable storage medium storing a business system risk control program, the business system risk control program being executable by at least one processor, Having the at least one processor perform the steps of:
  • the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
  • the electronic device, the business system risk control method and the storage medium proposed by the present application analyze whether the execution of the request exists according to a predetermined business system risk analysis rule after receiving the service request sent by the client. If the risk is determined, the service priority level corresponding to the service request is determined according to the predetermined priority determination rule, and the total number of the first tasks of the service type to which the service request belongs is determined to be greater than the predefined second service threshold. And determining that the service request needs to be preferentially processed according to the determined priority level; if it is determined that the risk exists, returning the service request to the client, and sending the risk prompt information to the predetermined operation and maintenance mailbox. It can prevent business system concurrency risks, reduce database downtime, and improve business efficiency and user experience.
  • FIG. 1 is a schematic diagram of an optional hardware architecture of an electronic device proposed by the present application.
  • FIG. 2 is a schematic diagram of a program module of a business system risk control program in an embodiment of an electronic device of the present application
  • FIG. 3 is a flow chart of an implementation of a preferred embodiment of a risk control method for a service system of the present application.
  • the electronic device 10 may include, but is not limited to, the memory 11, the processor 12, and the network interface 13 being communicably connected to each other through the communication bus 14. It should be noted that FIG. 1 only shows the electronic device 10 having the components 11-14, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.
  • the memory 11 includes at least one type of computer readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (for example, SD or DX memory, etc.), a random access memory (RAM), and a static memory.
  • the memory 11 may be an internal storage unit of the electronic device 10, such as a hard disk or memory of the electronic device 10.
  • the memory 11 may also be an outsourced storage device of the electronic device 10, such as a plug-in hard disk equipped on the electronic device 10, a smart memory card (SMC), and a secure digital (Secure Digital, SD) ) cards, flash cards, etc.
  • the memory 11 can also include both an internal storage unit of the electronic device 10 and an outsourced storage device thereof.
  • the memory 11 is generally used to store an operating system installed on the electronic device 10 and various types of application software, such as a business system risk control program. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.
  • Processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments.
  • the processor 12 is typically used to control the overall operation of the electronic device 10.
  • the processor 12 is configured to run program code or process data stored in the memory 11, such as running a business system risk control program.
  • the network interface 13 may include a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the electronic device 10 and other electronic devices.
  • Communication bus 14 is used to implement a communication connection between components 11-13.
  • FIG. 1 shows only electronic device 10 having components 11-14 and a business system risk control program, but it should be understood that not all illustrated components may be implemented and that more or fewer components may be implemented instead.
  • the electronic device 10 may further include a user interface (not shown in FIG. 1), and the user interface may include a display, an input unit such as a keyboard, wherein the user interface may further include a standard wired interface, a wireless interface, and the like.
  • the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED touch device, or the like. Further, the display may also be referred to as a display screen or display unit for displaying information processed in the electronic device 10 and a user interface for displaying visualizations.
  • the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
  • the predetermined risk analysis rule may be, for example, the first number of requests in the total task queue corresponding to the service system that executes the service request, and the first request number and the received service are calculated. The sum of the requests, the total number of second tasks;
  • the second request number corresponding to the service type matching the service request is obtained from the total task queue, and the second request number is calculated and received. The sum of the number of requests, the total number of the first tasks;
  • the predetermined priority determining rule may be, for example, traversing a first mapping relationship table between a pre-stored service type and a fault indicator value, and determining that the received service request corresponds to The fault indicator value of the service type;
  • the service system A is configured to process five preset types of services, and the five preset types of services respectively have different service priority levels, which are respectively the first service priority level. a second service priority level, a third service priority level, a fourth service priority level, and a fifth service priority level; wherein the fault indicator value of the service system A includes a first time threshold (RTO) for allowing a service failure, and allowing The second time threshold for the loss of business data (referred to as RPO).
  • RTO first time threshold
  • RPO The second time threshold for the loss of business data
  • the priority level corresponding to the fault indicator value of the service system is determined, and the priority level of the service fault indicator value is the service priority level corresponding to the received service request, usually, the same service
  • the priority level of the service fault indicator value is the service priority level corresponding to the received service request, usually, the same service.
  • the first time threshold corresponding to the service type of the first priority level corresponding to the service system A is 36 hours, and the second time threshold is 8 hours;
  • the first time threshold corresponding to the second priority service system is 72 hours, and the second time threshold is 24 hours;
  • the first time threshold corresponding to the third priority service system is 7 days, and the second time threshold is 36 hours;
  • the first time threshold corresponding to the fourth priority service system is 30 days, and the second time threshold is 7 days;
  • the first time threshold corresponding to the fifth priority service system is 60 days, and the second time threshold is 30 days.
  • the second service threshold corresponding to the service type with the higher service priority level corresponding to the same service system may be predefined, and in some special cases, in order to ensure smooth operation
  • the second service threshold of the service priority level may be set in advance, and the first service threshold is greater than or equal to the second service threshold.
  • the first service threshold is a total number of threads that the corresponding service system can provide.
  • the total number of threads that can be allocated by the predetermined service system A is 30, and the service priority of the service system A is the first priority service in the first predefined time.
  • the total number of first requests of the type is 25, the total number of first requests for the service type with the service priority of the second priority is 5, and the total number of the first requests for the service type with the other priority is 0.
  • the first service threshold of the predefined service system is 30, the second service threshold of the service type of the first priority is 20, and the service type of the second priority is processed.
  • the second service threshold of the service type that exceeds the first priority level may be determined, and the service with a higher priority level needs to be processed according to different priority levels of the service type.
  • Type of business request so as to avoid the occurrence of the number of concurrent threads of the business system being exhausted, the risk of data downtime of the business system occurs, and the risk is increased. Business efficiency.
  • the service system risk control program stored in the memory 11 when executed by the processor 12, the following operations are also implemented, the number of requests returned to the client is obtained in real time, and the number of requests returned to the client is calculated. The ratio of the number of requests sent by the client;
  • the client is sent for a second predefined time (eg, half an hour) Not transmitting an instruction for the service type request to the service system.
  • the electronic device proposed by the present application analyzes whether the operation of processing the request exists according to a predetermined risk analysis rule after receiving a request for acquiring a predefined service type sent by the client after the service system receives the request.
  • Risk if it is determined that there is no risk, determining a priority level of the service type according to a predetermined priority level determination rule; if it is determined that the total number of first tasks for processing the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be preferentially processed according to the determined priority level; if it is determined that there is a risk, returning the service request to the client, and sending the risk prompt information to the predetermined operation and maintenance mailbox. It can prevent business system concurrency risks, reduce database downtime, and improve business efficiency.
  • the business system risk control program of the present application may be described by a program module having the same function according to different functions implemented by each part thereof.
  • FIG. 2 is a schematic diagram of a program module of a business system risk control program in an embodiment of the electronic device of the present application.
  • the service system risk control program may be divided into an analysis module 201, a priority determination module 202, and a transmission module 203 according to different functions implemented by the respective parts.
  • the program module referred to in the present application refers to a series of computer program instruction segments capable of performing a specific function, and is more suitable than the program to describe the execution process of the Internet business system risk warning program in the electronic device 10.
  • the functions or operational steps implemented by the modules 201-203 are similar to the above, and are not described in detail herein, by way of example, for example:
  • the analyzing module 201 is configured to analyze whether the execution of the request is risky according to a predetermined business system risk analysis rule after receiving the service request sent by the client;
  • the priority determining module 202 is configured to determine, according to the predetermined priority level determining rule, a service priority level corresponding to the service request, if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined
  • the second service threshold determines that the service request needs to be preferentially processed according to the determined priority level
  • the sending module 203 is configured to: if the risk is determined, return the service request to the client, and send the risk prompt information to the predetermined operation and maintenance mailbox.
  • the present application further provides a service system risk control method.
  • the service system risk control method includes the following steps:
  • Step S301 after receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
  • Step S302 if it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and determining that the total number of the first tasks of the service type to which the service request belongs is greater than the predefined second service. Threshold, determining that the service request needs to be preferentially processed according to the determined priority level;
  • Step S303 if it is determined that there is a risk, return the service request to the client, and send the risk prompt information to the predetermined operation and maintenance mailbox.
  • the predetermined risk analysis rule may be, for example, the first number of requests in the total task queue corresponding to the service system that executes the service request, and the first request number and the received service are calculated. The sum of the requests, the total number of second tasks;
  • the second request number corresponding to the service type matching the service request is obtained from the total task queue, and the second request number is calculated and received. The sum of the number of requests, the total number of the first tasks;
  • the predetermined priority determining rule may be, for example, traversing a first mapping relationship table between a pre-stored service type and a fault indicator value, and determining that the received service request corresponds to The fault indicator value of the service type;
  • the service system A is configured to process five preset types of services, and the five preset types of services respectively have different service priority levels, which are respectively the first service priority level. a second service priority level, a third service priority level, a fourth service priority level, and a fifth service priority level; wherein the fault indicator value of the service system A includes a first time threshold (RTO) for allowing a service failure, and allowing The second time threshold for the loss of business data (referred to as RPO).
  • RTO first time threshold
  • RPO The second time threshold for the loss of business data
  • the priority level corresponding to the fault indicator value of the service system is determined, and the priority level of the service fault indicator value is the service priority level corresponding to the received service request, usually, the same service
  • the priority level of the service fault indicator value is the service priority level corresponding to the received service request, usually, the same service.
  • the first time threshold corresponding to the service type of the first priority level corresponding to the service system A is 36 hours, and the second time threshold is 8 hours;
  • the first time threshold corresponding to the second priority service system is 72 hours, and the second time threshold is 24 hours;
  • the first time threshold corresponding to the third priority service system is 7 days, and the second time threshold is 36 hours;
  • the first time threshold corresponding to the fourth priority service system is 30 days, and the second time threshold is 7 days;
  • the first time threshold corresponding to the fifth priority service system is 60 days, and the second time threshold is 30 days.
  • the second service threshold corresponding to the service type with the higher service priority level corresponding to the same service system may be predefined, and in some special cases, in order to ensure smooth operation
  • the second service threshold of the service priority level may be set in advance, and the first service threshold is greater than or equal to the second service threshold.
  • the first service threshold is a total number of threads that the corresponding service system can provide.
  • the total number of threads that can be allocated by the predetermined service system A is 30, and the service priority of the service system A is the first priority service in the first predefined time.
  • the total number of first requests of the type is 25, the total number of first requests for the service type with the service priority of the second priority is 5, and the total number of the first requests for the service type with the other priority is 0.
  • the first service threshold of the predefined service system is 30, the second service threshold of the service type of the first priority is 20, and the service type of the second priority is processed.
  • the second service threshold of the service type that exceeds the first priority level may be determined, and the service with a higher priority level needs to be processed according to different priority levels of the service type.
  • Type of business request so as to avoid the occurrence of the number of concurrent threads of the business system being exhausted, the risk of data downtime of the business system occurs, and the risk is increased. Business efficiency.
  • the service system risk control program stored in the memory 11 when executed by the processor 12, the following operations are also implemented, the number of requests returned to the client is obtained in real time, and the number of requests returned to the client is calculated. The ratio of the number of requests sent by the client;
  • the client is sent for a second predefined time (eg, half an hour) Not transmitting an instruction for the service type request to the service system.
  • the service system risk control method proposed by the present application analyzes and executes the processing of the request according to the predetermined risk analysis rule after receiving the request of the client to obtain the predefined service type. Whether there is a risk in the operation; if it is determined that there is no risk, the priority level of the service type is determined according to the predetermined priority level determination rule; if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than the predefined second service
  • the threshold determines that the service request needs to be preferentially processed according to the determined priority level; if it is determined that the risk exists, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox. It can prevent business system concurrency risks, reduce database downtime, and improve business efficiency.
  • the present application further provides a computer readable storage medium, where the business system risk control program is stored, and the business system risk control program is executed by the processor to:
  • the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
  • the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better.
  • Implementation Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
  • the optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Quality & Reliability (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Abstract

Disclosed are an electronic apparatus, a service system risk control method, and a storage medium. The method comprises: after a service request that is sent by a client is received, analyzing, according to a pre-determined service system risk analysis rule, whether there is a risk in executing the request; if it is determined that there is no risk, determining, according to a pre-determined priority level determination rule, a service priority level corresponding to the service request, and if it is determined that the total number of first tasks for processing a service type to which the service request belongs is greater than a pre-defined second service threshold, determining that it is necessary to choose to preferentially process the service request according to the determined priority level; and if it is determined that there is a risk, returning the service request to the client, and sending risk warning information to a pre-determined operation and maintenance mailbox. Concurrent risks of a service system can be prevented, database crashes can be reduced, and the service efficiency can be improved.

Description

电子装置、业务系统风险控制方法及存储介质Electronic device, business system risk control method and storage medium
本申请要求于2018年03月06日提交中国专利局、申请号为201810184861.8、发明名称为“电子装置、业务系统风险控制方法及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在申请中。The present application claims priority to Chinese Patent Application No. 201101184861.8, entitled "Electronic Device, Business System Risk Control Method and Storage Medium", filed on March 06, 2018, the entire contents of which are incorporated by reference. In the application.
技术领域Technical field
本申请涉及互联网数据交互领域，尤其涉及一种电子装置、业务系统风险控制方法及存储介质。The present application relates to the field of Internet data interaction, and in particular, to an electronic device, a business system risk control method, and a storage medium.
背景技术Background technique
随着互联网通信技术的发展，各企业之间通常通过开放平台进行信息交互，例如，通过购物网站购买日常生活用品，或者通过聊天工具在线远程沟通等，但是当用户同时发起的业务请求数量超过一定的级别后，有可能导致业务系统的并发线程数被消耗殆尽，导致业务系统的数据库宕机，业务效率降低。With the development of Internet communication technology, enterprises usually exchange information through open platforms, for example, purchase daily necessities through shopping websites, or remotely communicate through chat tools, but when the number of business requests initiated by users exceeds certain After the level, the number of concurrent threads of the business system may be exhausted, resulting in a downtime of the database of the business system and a decrease in business efficiency.
发明内容Summary of the invention
有鉴于此，本申请提出一种电子装置、互联网业务系统风险预警方法及存储介质，能够精确有效地控制互联网业务系统的运行风险。In view of this, the present application proposes an electronic device, an internet service system risk warning method, and a storage medium, which can accurately and effectively control the operational risk of the Internet service system.
首先，为实现上述目的，本申请提出一种电子装置，所述电子装置包括存储器、及与所述存储器连接的处理器，所述处理器用于执行所述存储器上存储的业务系统风险控制程序，所述业务系统风险控制程序被所述处理器执行时实现如下步骤：First, in order to achieve the above object, the present application provides an electronic device including a memory and a processor connected to the memory, the processor for executing a business system risk control program stored on the memory, The business system risk control program is implemented by the processor to implement the following steps:
接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；After receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请 求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；If it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be prioritized according to the determined priority level;
若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。If it is determined that there is a risk, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
此外，为了实现上述目的，本申请还提出一种业务系统风险控制方法，所述方法包括如下步骤：In addition, in order to achieve the above object, the present application further provides a service system risk control method, where the method includes the following steps:
接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；After receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；If it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be prioritized according to the determined priority level;
若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。If it is determined that there is a risk, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
此外，为了实现上述目的，本申请还提出一种计算机可读存储介质，所述计算机可读存储介质存储有业务系统风险控制程序，所述业务系统风险控制程序可被至少一个处理器执行，以使所述至少一个处理器执行下述步骤：In addition, in order to achieve the above object, the present application further provides a computer readable storage medium storing a business system risk control program, the business system risk control program being executable by at least one processor, Having the at least one processor perform the steps of:
接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；After receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；If it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be prioritized according to the determined priority level;
若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。If it is determined that there is a risk, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
相较于现有技术，本申请提出的电子装置，业务系统风险控制方法及存储介质，通过在接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。能够预防业务系统并发风险，减少数据库宕机，提高业务效率及用户体验效果。Compared with the prior art, the electronic device, the business system risk control method and the storage medium proposed by the present application analyze whether the execution of the request exists according to a predetermined business system risk analysis rule after receiving the service request sent by the client. If the risk is determined, the service priority level corresponding to the service request is determined according to the predetermined priority determination rule, and the total number of the first tasks of the service type to which the service request belongs is determined to be greater than the predefined second service threshold. And determining that the service request needs to be preferentially processed according to the determined priority level; if it is determined that the risk exists, returning the service request to the client, and sending the risk prompt information to the predetermined operation and maintenance mailbox. It can prevent business system concurrency risks, reduce database downtime, and improve business efficiency and user experience.
附图说明DRAWINGS
图1是本申请提出的电子装置一可选的硬件架构的示意图；1 is a schematic diagram of an optional hardware architecture of an electronic device proposed by the present application;
图2是本申请电子装置一实施例中业务系统风险控制程序的程序模块示意图；2 is a schematic diagram of a program module of a business system risk control program in an embodiment of an electronic device of the present application;
图3是本申请业务系统风险控制方法较佳实施例的实施流程图。3 is a flow chart of an implementation of a preferred embodiment of a risk control method for a service system of the present application.
本申请目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings.
具体实施方式Detailed ways
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处所描述的具体实施例仅用以解释本申请，并不用于限定本申请。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.
需要说明的是，在本申请中涉及“第一”、“第二”等的描述仅用于描述目的，而不能理解为指示或暗示其相对重要性或者隐含指明所指示的技术特征的数 量。由此，限定有“第一”、“第二”的特征可以明示或者隐含地包括至少一个该特征。另外，各个实施例之间的技术方案可以相互结合，但是必须是以本领域普通技术人员能够实现为基础，当技术方案的结合出现相互矛盾或无法实现时应当认为这种技术方案的结合不存在，也不在本申请要求的保护范围之内。It should be noted that the descriptions of "first", "second" and the like in the present application are for the purpose of description only, and are not to be construed as indicating or implying their relative importance or implicitly indicating the number of technical features indicated. . Thus, features defining "first" or "second" may include at least one of the features, either explicitly or implicitly. In addition, the technical solutions between the various embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the combination of the technical solutions is contradictory or impossible to implement, it should be considered that the combination of the technical solutions does not exist. Nor is it within the scope of protection required by this application.
参阅图1所示，是本申请提出的电子装置一可选的硬件架构示意图。本实施例中，电子装置10可包括，但不仅限于，可通过通信总线14相互通信连接存储器11、处理器12、网络接口13。需要指出的是，图1仅示出了具有组件11-14的电子装置10，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。Referring to FIG. 1 , it is an optional hardware architecture diagram of the electronic device proposed by the present application. In this embodiment, the electronic device 10 may include, but is not limited to, the memory 11, the processor 12, and the network interface 13 being communicably connected to each other through the communication bus 14. It should be noted that FIG. 1 only shows the electronic device 10 having the components 11-14, but it should be understood that not all illustrated components may be implemented, and more or fewer components may be implemented instead.
其中，存储器11至少包括一种类型的计算机可读存储介质，计算机可读存储介质包括闪存、硬盘、多媒体卡、卡型存储器(例如，SD或DX存储器等)、随机访问存储器(RAM)、静态随机访问存储器(SRAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、可编程只读存储器(PROM)、磁性存储器、磁盘、光盘等。在一些实施例中，存储器11可以是电子装置10的内部存储单元，例如电子装置10的硬盘或内存。在另一些实施例中，存储器11也可以是电子装置10的外包存储设备，例如电子装置10上配备的插接式硬盘，智能存储卡(Smart Media Card,SMC)，安全数字(Secure Digital,SD)卡，闪存卡(Flash Card)等。当然，存储器11还可以既包括电子装置10的内部存储单元也包括其外包存储设备。本实施例中，存储器11通常用于存储安装于电子装置10的操作系统和各类应用软件，例如业务系统风险控制程序等。此外，存储器11还可以用于暂时地存储已经输出或者将要输出的各类数据。The memory 11 includes at least one type of computer readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (for example, SD or DX memory, etc.), a random access memory (RAM), and a static memory. Random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, and the like. In some embodiments, the memory 11 may be an internal storage unit of the electronic device 10, such as a hard disk or memory of the electronic device 10. In other embodiments, the memory 11 may also be an outsourced storage device of the electronic device 10, such as a plug-in hard disk equipped on the electronic device 10, a smart memory card (SMC), and a secure digital (Secure Digital, SD) ) cards, flash cards, etc. Of course, the memory 11 can also include both an internal storage unit of the electronic device 10 and an outsourced storage device thereof. In this embodiment, the memory 11 is generally used to store an operating system installed on the electronic device 10 and various types of application software, such as a business system risk control program. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.
处理器12在一些实施例中可以是中央处理器(Central Processing Unit，CPU)、控制器、微控制器、微处理器、或其他数据处理芯片。处理器12通常用于控制电子装置10的总体操作。本实施例中，处理器12用于运行存储 器11中存储的程序代码或者处理数据，例如运行业务系统风险控制程序等。 Processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 12 is typically used to control the overall operation of the electronic device 10. In this embodiment, the processor 12 is configured to run program code or process data stored in the memory 11, such as running a business system risk control program.
网络接口13可包括无线网络接口或有线网络接口，网络接口13通常用于在电子装置10与其他电子设备之间建立通信连接。The network interface 13 may include a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the electronic device 10 and other electronic devices.
通信总线14用于实现组件11-13之间的通信连接。 Communication bus 14 is used to implement a communication connection between components 11-13.
图1仅示出了具有组件11-14以及业务系统风险控制程序的电子装置10，但是应理解的是，并不要求实施所有示出的组件，可以替代的实施更多或者更少的组件。1 shows only electronic device 10 having components 11-14 and a business system risk control program, but it should be understood that not all illustrated components may be implemented and that more or fewer components may be implemented instead.
可选地，电子装置10还可以包括用户接口(图1中未示出)，用户接口可以包括显示器、输入单元比如键盘，其中，用户接口还可以包括标准的有线接口、无线接口等。Optionally, the electronic device 10 may further include a user interface (not shown in FIG. 1), and the user interface may include a display, an input unit such as a keyboard, wherein the user interface may further include a standard wired interface, a wireless interface, and the like.
可选地，在一些实施例中，显示器可以是LED显示器、液晶显示器、触控式液晶显示器以及OLED触摸器等。进一步地，显示器也可称为显示屏或显示单元，用于显示在电子装置10中处理信息以及用于显示可视化的用户界面。Optionally, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED touch device, or the like. Further, the display may also be referred to as a display screen or display unit for displaying information processed in the electronic device 10 and a user interface for displaying visualizations.
在一实施例中，存储器11中存储的业务系统风险控制程序被处理器12执行时，实现如下操作：In an embodiment, when the business system risk control program stored in the memory 11 is executed by the processor 12, the following operations are implemented:
接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；After receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；If it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be prioritized according to the determined priority level;
若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。If it is determined that there is a risk, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
在本实施例中，所述预先确定的风险分析规则可以是，例如，执行该业务请求的业务系统对应的总任务队列中的第一请求数，计算所述第一请求数 与接收到的业务请求之和，得到第二任务总数；In this embodiment, the predetermined risk analysis rule may be, for example, the first number of requests in the total task queue corresponding to the service system that executes the service request, and the first request number and the received service are calculated. The sum of the requests, the total number of second tasks;
计算所述第二任务总数与预定义的该业务系统的第一业务阈值之间的大小；Calculating a size between the total number of the second tasks and a predefined first service threshold of the service system;
若所述第二任务总数大于或等于所述第一业务阈值，则确定该业务系统执行接收到的业务请求存在风险；If the total number of the second tasks is greater than or equal to the first service threshold, determining that the service system performs the received service request is at risk;
若所述第二任务总数小于所述第一业务阈值，则从所述总任务队列中获取与所述业务请求匹配的业务类型对应的第二请求数，计算所述第二请求数与接收到的请求数之和，得到所述第一任务总数；If the total number of the second tasks is less than the first service threshold, the second request number corresponding to the service type matching the service request is obtained from the total task queue, and the second request number is calculated and received. The sum of the number of requests, the total number of the first tasks;
计算所述第一任务总数与预定义的该业务系统处理与所述业务请求匹配的业务类型的第二业务阈值之间的大小，若所述第一任务总数小于所述第二业务阈值，则确定处理接收到的请求不存在风险，或者，若所述第一任务总数大于或等于所述第二业务阈值，则确定处理接收到的请求存在风险。Calculating a size between the total number of the first tasks and a predefined second service threshold of the service type that the service system matches the service request, if the total number of the first tasks is less than the second service threshold, It is determined that there is no risk in processing the received request, or if the total number of the first tasks is greater than or equal to the second service threshold, it is determined that there is a risk in processing the received request.
进一步地，在本实施例中，所述预先确定的优先级确定规则可以是，例如，遍历预先存储的业务类型与故障指标值之间的第一映射关系表，确定接收到的业务请求对应的业务类型的故障指标值；Further, in this embodiment, the predetermined priority determining rule may be, for example, traversing a first mapping relationship table between a pre-stored service type and a fault indicator value, and determining that the received service request corresponds to The fault indicator value of the service type;
根据预先生成的故障指标值与业务优先级别之间的第二映射关系表，确定接收到的业务请求对应的故障指标值的优先级别，所述故障指标值的优先级别为接收到的业务请求对应的业务优先级别。Determining a priority level of the fault indicator value corresponding to the received service request according to the second mapping relationship between the fault indicator value and the service priority level, where the priority level of the fault indicator value is corresponding to the received service request Business priority.
在本实施例的一种实施方式中，假设业务系统A对应处理五种预设类型的业务，且该五种预设类型的业务分别具有不同的业务优先级别，分别为第一业务优先级别，第二业务优先级别，第三业务优先级别，第四业务优先级别，及第五业务优先级别；其中，业务系统A的故障指标值包括允许业务故障的第一时间阈值(简称RTO)、及允许业务数据丢失的第二时间阈值(简称RPO)。In an embodiment of the present embodiment, it is assumed that the service system A is configured to process five preset types of services, and the five preset types of services respectively have different service priority levels, which are respectively the first service priority level. a second service priority level, a third service priority level, a fourth service priority level, and a fifth service priority level; wherein the fault indicator value of the service system A includes a first time threshold (RTO) for allowing a service failure, and allowing The second time threshold for the loss of business data (referred to as RPO).
通常，根据所述第二映射关系表能够确定出，业务系统的故障指标值对应的优先级别，而业务故障指标值的优先级别即为接收到的业务请求对应的 业务优先级别，通常，同一业务系统对应业务优先级别越高的业务类型的故障指标值越小。Generally, according to the second mapping relationship table, the priority level corresponding to the fault indicator value of the service system is determined, and the priority level of the service fault indicator value is the service priority level corresponding to the received service request, usually, the same service The smaller the fault indicator value of the service type with the higher service priority level, the smaller the system.
例如，在本实施例中，根据所述第二映射关系表，确定业务系统A对应的第一优先级别的业务类型对应的所述第一时间阈值为36小时，第二时间阈值为8小时；第二优先级的业务系统对应的第一时间阈值为72小时，第二时间阈值为24小时；第三优先级的业务系统对应的第一时间阈值为7天，第二时间阈值为36小时；第四优先级的业务系统对应的第一时间阈值为30天，第二时间阈值为7天；第五优先级的业务系统对应的第一时间阈值为60天，第二时间阈值为30天。For example, in this embodiment, determining, according to the second mapping relationship table, that the first time threshold corresponding to the service type of the first priority level corresponding to the service system A is 36 hours, and the second time threshold is 8 hours; The first time threshold corresponding to the second priority service system is 72 hours, and the second time threshold is 24 hours; the first time threshold corresponding to the third priority service system is 7 days, and the second time threshold is 36 hours; The first time threshold corresponding to the fourth priority service system is 30 days, and the second time threshold is 7 days; the first time threshold corresponding to the fifth priority service system is 60 days, and the second time threshold is 30 days.
可以理解的是，在本申请的不同实施例中，可以预定义同一业务系统对应的业务优先级别越高的业务类型对应的第二业务阈值越大，且在某些特殊情况下，为了保证顺利执行业务优先级别高的业务类型，可以预先设置该业务优先级别的第二业务阈值，通常，所述第一业务阈值大于或者等于所述第二业务阈值。所述第一业务阈值为对应的业务系统可提供的总线程数。It can be understood that, in different embodiments of the present application, the second service threshold corresponding to the service type with the higher service priority level corresponding to the same service system may be predefined, and in some special cases, in order to ensure smooth operation The second service threshold of the service priority level may be set in advance, and the first service threshold is greater than or equal to the second service threshold. The first service threshold is a total number of threads that the corresponding service system can provide.
例如，在一实施例中，假设预先确定的业务系统A可分配的总线程数为30，且在第一预定义的时间内，调用该业务系统A的业务优先级别为第一优先级的业务类型的第一请求总数为25，调用业务优先级别为第二优先级的业务类型的第一请求总数为5，调用业务优先级别为其他优先级的业务类型的第一请求总数为0，进一步地，在本申请的各实施例中，假设预定义的业务系统的第一业务阈值为30，处理第一优先级别的业务类型的第二业务阈值为20，处理第二优先级别的业务类型的第二业务阈值为10，则可以确定所述第一请求总数超过所述第一优先级别的业务类型的第二业务阈值，此时需要根据业务类型的不同优先级别确定先处理优先级别较高的业务类型的业务请求，这样可以避免出现业务系统的并发线程数被消耗殆尽，出现业务系统的数据宕机的风险，提高业务效率。For example, in an embodiment, it is assumed that the total number of threads that can be allocated by the predetermined service system A is 30, and the service priority of the service system A is the first priority service in the first predefined time. The total number of first requests of the type is 25, the total number of first requests for the service type with the service priority of the second priority is 5, and the total number of the first requests for the service type with the other priority is 0. In the embodiments of the present application, it is assumed that the first service threshold of the predefined service system is 30, the second service threshold of the service type of the first priority is 20, and the service type of the second priority is processed. If the service threshold is 10, the second service threshold of the service type that exceeds the first priority level may be determined, and the service with a higher priority level needs to be processed according to different priority levels of the service type. Type of business request, so as to avoid the occurrence of the number of concurrent threads of the business system being exhausted, the risk of data downtime of the business system occurs, and the risk is increased. Business efficiency.
优选地，在本实施例中，存储器11中存储的业务系统风险控制程序被处 理器12执行时，还实现如下操作，实时获取返回至该客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Preferably, in this embodiment, when the service system risk control program stored in the memory 11 is executed by the processor 12, the following operations are also implemented, the number of requests returned to the client is obtained in real time, and the number of requests returned to the client is calculated. The ratio of the number of requests sent by the client;
若在第一预定义的时间内(如一小时内)计算得到的请求数之比大于预定义的比值阈值(超过50％)，则向该客户端发送在第二预定义时间内(如半小时内)不向所述业务系统发送所述业务类型请求的指令。If the ratio of the number of requests calculated within the first predefined time (eg, within one hour) is greater than a predefined ratio threshold (more than 50%), then the client is sent for a second predefined time (eg, half an hour) Not transmitting an instruction for the service type request to the service system.
由上述事实施例可知，本申请提出的电子装置，通过在业务系统接收到客户端发送的获取预定义的业务类型的请求后，根据预先确定的风险分析规则分析执行处理该请求的操作是否存在风险；若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务类型的优先级别；若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。能够预防业务系统并发风险，减少数据库宕机，提高业务效率。It can be seen from the above embodiments that the electronic device proposed by the present application analyzes whether the operation of processing the request exists according to a predetermined risk analysis rule after receiving a request for acquiring a predefined service type sent by the client after the service system receives the request. Risk; if it is determined that there is no risk, determining a priority level of the service type according to a predetermined priority level determination rule; if it is determined that the total number of first tasks for processing the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be preferentially processed according to the determined priority level; if it is determined that there is a risk, returning the service request to the client, and sending the risk prompt information to the predetermined operation and maintenance mailbox. It can prevent business system concurrency risks, reduce database downtime, and improve business efficiency.
进一步需要说明的是，本申请的业务系统风险控制程序依据其各部分所实现的功能不同，可用具有相同功能的程序模块进行描述。请参阅图2所示，是本申请电子装置一实施例中业务系统风险控制程序的程序模块示意图。本实施例中，业务系统风险控制程序依据其各部分所实现的功能的不同，可以被分割成分析模块201、优先级确定模块202、发送模块203。由上面的描述可知，本申请所称的程序模块是指能够完成特定功能的一系列计算机程序指令段，比程序更适合于描述互联网业务系统风险预警程序在电子装置10中的执行过程。所述模块201-203所实现的功能或操作步骤均与上文类似，此处不再详述，示例性地，例如其中：It should be further noted that the business system risk control program of the present application may be described by a program module having the same function according to different functions implemented by each part thereof. Please refer to FIG. 2, which is a schematic diagram of a program module of a business system risk control program in an embodiment of the electronic device of the present application. In this embodiment, the service system risk control program may be divided into an analysis module 201, a priority determination module 202, and a transmission module 203 according to different functions implemented by the respective parts. As can be seen from the above description, the program module referred to in the present application refers to a series of computer program instruction segments capable of performing a specific function, and is more suitable than the program to describe the execution process of the Internet business system risk warning program in the electronic device 10. The functions or operational steps implemented by the modules 201-203 are similar to the above, and are not described in detail herein, by way of example, for example:
分析模块201用于在接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；The analyzing module 201 is configured to analyze whether the execution of the request is risky according to a predetermined business system risk analysis rule after receiving the service request sent by the client;
优先级确定模块202用于若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所 属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；The priority determining module 202 is configured to determine, according to the predetermined priority level determining rule, a service priority level corresponding to the service request, if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined The second service threshold determines that the service request needs to be preferentially processed according to the determined priority level;
发送模块203用于若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。The sending module 203 is configured to: if the risk is determined, return the service request to the client, and send the risk prompt information to the predetermined operation and maintenance mailbox.
此外，本申请还提出一种业务系统风险控制方法，请参阅图3所示，所述业务系统风险控制方法包括如下步骤：In addition, the present application further provides a service system risk control method. Referring to FIG. 3, the service system risk control method includes the following steps:
步骤S301，接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；Step S301, after receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
步骤S302，若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；Step S302, if it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and determining that the total number of the first tasks of the service type to which the service request belongs is greater than the predefined second service. Threshold, determining that the service request needs to be preferentially processed according to the determined priority level;
步骤S303，若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。Step S303, if it is determined that there is a risk, return the service request to the client, and send the risk prompt information to the predetermined operation and maintenance mailbox.
在本实施例中，所述预先确定的风险分析规则可以是，例如，执行该业务请求的业务系统对应的总任务队列中的第一请求数，计算所述第一请求数与接收到的业务请求之和，得到第二任务总数；In this embodiment, the predetermined risk analysis rule may be, for example, the first number of requests in the total task queue corresponding to the service system that executes the service request, and the first request number and the received service are calculated. The sum of the requests, the total number of second tasks;
计算所述第二任务总数与预定义的该业务系统的第一业务阈值之间的大小；Calculating a size between the total number of the second tasks and a predefined first service threshold of the service system;
若所述第二任务总数大于或等于所述第一业务阈值，则确定该业务系统执行接收到的业务请求存在风险；If the total number of the second tasks is greater than or equal to the first service threshold, determining that the service system performs the received service request is at risk;
若所述第二任务总数小于所述第一业务阈值，则从所述总任务队列中获取与所述业务请求匹配的业务类型对应的第二请求数，计算所述第二请求数与接收到的请求数之和，得到所述第一任务总数；If the total number of the second tasks is less than the first service threshold, the second request number corresponding to the service type matching the service request is obtained from the total task queue, and the second request number is calculated and received. The sum of the number of requests, the total number of the first tasks;
计算所述第一任务总数与预定义的该业务系统处理与所述业务请求匹配的业务类型的第二业务阈值之间的大小，若所述第一任务总数小于所述第二 业务阈值，则确定处理接收到的请求不存在风险，或者，若所述第一任务总数大于或等于所述第二业务阈值，则确定处理接收到的请求存在风险。Calculating a size between the total number of the first tasks and a predefined second service threshold of the service type that the service system matches the service request, if the total number of the first tasks is less than the second service threshold, It is determined that there is no risk in processing the received request, or if the total number of the first tasks is greater than or equal to the second service threshold, it is determined that there is a risk in processing the received request.
进一步地，在本实施例中，所述预先确定的优先级确定规则可以是，例如，遍历预先存储的业务类型与故障指标值之间的第一映射关系表，确定接收到的业务请求对应的业务类型的故障指标值；Further, in this embodiment, the predetermined priority determining rule may be, for example, traversing a first mapping relationship table between a pre-stored service type and a fault indicator value, and determining that the received service request corresponds to The fault indicator value of the service type;
根据预先生成的故障指标值与业务优先级别之间的第二映射关系表，确定接收到的业务请求对应的故障指标值的优先级别，所述故障指标值的优先级别为接收到的业务请求对应的业务优先级别。Determining a priority level of the fault indicator value corresponding to the received service request according to the second mapping relationship between the fault indicator value and the service priority level, where the priority level of the fault indicator value is corresponding to the received service request Business priority.
在本实施例的一种实施方式中，假设业务系统A对应处理五种预设类型的业务，且该五种预设类型的业务分别具有不同的业务优先级别，分别为第一业务优先级别，第二业务优先级别，第三业务优先级别，第四业务优先级别，及第五业务优先级别；其中，业务系统A的故障指标值包括允许业务故障的第一时间阈值(简称RTO)、及允许业务数据丢失的第二时间阈值(简称RPO)。In an embodiment of the present embodiment, it is assumed that the service system A is configured to process five preset types of services, and the five preset types of services respectively have different service priority levels, which are respectively the first service priority level. a second service priority level, a third service priority level, a fourth service priority level, and a fifth service priority level; wherein the fault indicator value of the service system A includes a first time threshold (RTO) for allowing a service failure, and allowing The second time threshold for the loss of business data (referred to as RPO).
通常，根据所述第二映射关系表能够确定出，业务系统的故障指标值对应的优先级别，而业务故障指标值的优先级别即为接收到的业务请求对应的业务优先级别，通常，同一业务系统对应业务优先级别越高的业务类型的故障指标值越小。Generally, according to the second mapping relationship table, the priority level corresponding to the fault indicator value of the service system is determined, and the priority level of the service fault indicator value is the service priority level corresponding to the received service request, usually, the same service The smaller the fault indicator value of the service type with the higher service priority level, the smaller the system.
例如，在本实施例中，根据所述第二映射关系表，确定业务系统A对应的第一优先级别的业务类型对应的所述第一时间阈值为36小时，第二时间阈值为8小时；第二优先级的业务系统对应的第一时间阈值为72小时，第二时间阈值为24小时；第三优先级的业务系统对应的第一时间阈值为7天，第二时间阈值为36小时；第四优先级的业务系统对应的第一时间阈值为30天，第二时间阈值为7天；第五优先级的业务系统对应的第一时间阈值为60天，第二时间阈值为30天。For example, in this embodiment, determining, according to the second mapping relationship table, that the first time threshold corresponding to the service type of the first priority level corresponding to the service system A is 36 hours, and the second time threshold is 8 hours; The first time threshold corresponding to the second priority service system is 72 hours, and the second time threshold is 24 hours; the first time threshold corresponding to the third priority service system is 7 days, and the second time threshold is 36 hours; The first time threshold corresponding to the fourth priority service system is 30 days, and the second time threshold is 7 days; the first time threshold corresponding to the fifth priority service system is 60 days, and the second time threshold is 30 days.
可以理解的是，在本申请的不同实施例中，可以预定义同一业务系统对 应的业务优先级别越高的业务类型对应的第二业务阈值越大，且在某些特殊情况下，为了保证顺利执行业务优先级别高的业务类型，可以预先设置该业务优先级别的第二业务阈值，通常，所述第一业务阈值大于或者等于所述第二业务阈值。所述第一业务阈值为对应的业务系统可提供的总线程数。It can be understood that, in different embodiments of the present application, the second service threshold corresponding to the service type with the higher service priority level corresponding to the same service system may be predefined, and in some special cases, in order to ensure smooth operation The second service threshold of the service priority level may be set in advance, and the first service threshold is greater than or equal to the second service threshold. The first service threshold is a total number of threads that the corresponding service system can provide.
例如，在一实施例中，假设预先确定的业务系统A可分配的总线程数为30，且在第一预定义的时间内，调用该业务系统A的业务优先级别为第一优先级的业务类型的第一请求总数为25，调用业务优先级别为第二优先级的业务类型的第一请求总数为5，调用业务优先级别为其他优先级的业务类型的第一请求总数为0，进一步地，在本申请的各实施例中，假设预定义的业务系统的第一业务阈值为30，处理第一优先级别的业务类型的第二业务阈值为20，处理第二优先级别的业务类型的第二业务阈值为10，则可以确定所述第一请求总数超过所述第一优先级别的业务类型的第二业务阈值，此时需要根据业务类型的不同优先级别确定先处理优先级别较高的业务类型的业务请求，这样可以避免出现业务系统的并发线程数被消耗殆尽，出现业务系统的数据宕机的风险，提高业务效率。For example, in an embodiment, it is assumed that the total number of threads that can be allocated by the predetermined service system A is 30, and the service priority of the service system A is the first priority service in the first predefined time. The total number of first requests of the type is 25, the total number of first requests for the service type with the service priority of the second priority is 5, and the total number of the first requests for the service type with the other priority is 0. In the embodiments of the present application, it is assumed that the first service threshold of the predefined service system is 30, the second service threshold of the service type of the first priority is 20, and the service type of the second priority is processed. If the service threshold is 10, the second service threshold of the service type that exceeds the first priority level may be determined, and the service with a higher priority level needs to be processed according to different priority levels of the service type. Type of business request, so as to avoid the occurrence of the number of concurrent threads of the business system being exhausted, the risk of data downtime of the business system occurs, and the risk is increased. Business efficiency.
优选地，在本实施例中，存储器11中存储的业务系统风险控制程序被处理器12执行时，还实现如下操作，实时获取返回至该客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Preferably, in this embodiment, when the service system risk control program stored in the memory 11 is executed by the processor 12, the following operations are also implemented, the number of requests returned to the client is obtained in real time, and the number of requests returned to the client is calculated. The ratio of the number of requests sent by the client;
若在第一预定义的时间内(如一小时内)计算得到的请求数之比大于预定义的比值阈值(超过50％)，则向该客户端发送在第二预定义时间内(如半小时内)不向所述业务系统发送所述业务类型请求的指令。If the ratio of the number of requests calculated within the first predefined time (eg, within one hour) is greater than a predefined ratio threshold (more than 50%), then the client is sent for a second predefined time (eg, half an hour) Not transmitting an instruction for the service type request to the service system.
由上述事实施例可知，本申请提出的业务系统风险控制方法，通过在业务系统接收到客户端发送的获取预定义的业务类型的请求后，根据预先确定的风险分析规则分析执行处理该请求的操作是否存在风险；若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务类型的优先级别；若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈 值，则确定需要根据确定的优先级别选择优先处理该业务请求；若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。能够预防业务系统并发风险，减少数据库宕机，提高业务效率。It can be seen from the above embodiments that the service system risk control method proposed by the present application analyzes and executes the processing of the request according to the predetermined risk analysis rule after receiving the request of the client to obtain the predefined service type. Whether there is a risk in the operation; if it is determined that there is no risk, the priority level of the service type is determined according to the predetermined priority level determination rule; if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than the predefined second service The threshold determines that the service request needs to be preferentially processed according to the determined priority level; if it is determined that the risk exists, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox. It can prevent business system concurrency risks, reduce database downtime, and improve business efficiency.
此外，本申请还提出一种计算机可读存储介质，所述计算机可读存储介质上存储有业务系统风险控制程序，所述业务系统风险控制程序被处理器执行时实现如下操作：In addition, the present application further provides a computer readable storage medium, where the business system risk control program is stored, and the business system risk control program is executed by the processor to:
接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；After receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；If it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be prioritized according to the determined priority level;
若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。If it is determined that there is a risk, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
本申请计算机可读存储介质具体实施方式与上述电子装置以及业务系统风险控制方法各实施例基本相同，在此不作累述。The specific embodiment of the computer readable storage medium of the present application is substantially the same as the foregoing embodiments of the electronic device and the business system risk control method, and is not described herein.
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.
以上仅为本申请的优选实施例，并非因此限制本申请的专利范围，凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换，或直接或间 接运用在其他相关的技术领域，均同理包括在本申请的专利保护范围内。The above is only a preferred embodiment of the present application, and is not intended to limit the scope of the patent application, and the equivalent structure or equivalent process transformations made by the specification and the drawings of the present application, or directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of this application.

Claims (20)

  1. 一种电子装置，其特征在于，所述电子装置包括存储器、及与所述存储器连接的处理器，所述处理器用于执行所述存储器上存储的业务系统风险控制程序，所述业务系统风险控制程序被所述处理器执行时实现如下步骤：An electronic device, comprising: a memory, and a processor connected to the memory, the processor is configured to execute a business system risk control program stored on the memory, the business system risk control The program implements the following steps when executed by the processor:
    接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；After receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
    若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；If it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be prioritized according to the determined priority level;
    若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。If it is determined that there is a risk, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
  2. 如权利要求1所述的电子装置，其特征在于，所述根据预先确定的业务系统风险分析规则分析执行该业务请求是否存在风险的步骤包括：The electronic device according to claim 1, wherein the step of analyzing whether the execution of the service request is risky according to a predetermined business system risk analysis rule comprises:
    获取执行该业务请求的业务系统对应的总任务队列中的第一请求数，计算所述第一请求数与接收到的业务请求之和，得到第二任务总数；Obtaining a first request number in a total task queue corresponding to the service system that executes the service request, and calculating a sum of the first request number and the received service request, to obtain a total number of second tasks;
    计算所述第二任务总数与预定义的该业务系统的第一业务阈值之间的大小；Calculating a size between the total number of the second tasks and a predefined first service threshold of the service system;
    若所述第二任务总数大于或等于所述第一业务阈值，则确定该业务系统执行接收到的业务请求存在风险；If the total number of the second tasks is greater than or equal to the first service threshold, determining that the service system performs the received service request is at risk;
    若所述第二任务总数小于所述第一业务阈值，则从所述总任务队列中获取与所述业务请求匹配的业务类型对应的第二请求数，计算所述第二请求数与接收到的请求数之和，得到所述第一任务总数；If the total number of the second tasks is less than the first service threshold, the second request number corresponding to the service type matching the service request is obtained from the total task queue, and the second request number is calculated and received. The sum of the number of requests, the total number of the first tasks;
    计算所述第一任务总数与预定义的该业务系统处理与所述业务请求匹配的业务类型的第二业务阈值之间的大小，若所述第一任务总数小于所述第二业务阈值，则确定处理接收到的请求不存在风险，或者，若所述第一任务总 数大于或等于所述第二业务阈值，则确定处理接收到的请求存在风险。Calculating a size between the total number of the first tasks and a predefined second service threshold of the service type that the service system matches the service request, if the total number of the first tasks is less than the second service threshold, It is determined that there is no risk in processing the received request, or if the total number of the first tasks is greater than or equal to the second service threshold, it is determined that there is a risk in processing the received request.
  3. 如权利要求2所述的电子装置，其特征在于，所述根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别的步骤包括：The electronic device according to claim 2, wherein the step of determining a service priority level corresponding to the service request according to the predetermined priority level determining rule comprises:
    遍历预先存储的业务类型与故障指标值之间的第一映射关系表，确定接收到的业务请求对应的业务类型的故障指标值；Tracing a first mapping relationship between the pre-stored service type and the fault indicator value, and determining a fault indicator value of the service type corresponding to the received service request;
    根据预先生成的故障指标值与业务优先级别之间的第二映射关系表，确定接收到的业务请求对应的故障指标值的优先级别，所述故障指标值的优先级别为接收到的业务请求对应的业务优先级别。Determining a priority level of the fault indicator value corresponding to the received service request according to the second mapping relationship between the fault indicator value and the service priority level, where the priority level of the fault indicator value is corresponding to the received service request Business priority.
  4. 如权利要求3所述的电子装置，其特征在于，所述故障指标值包括允许业务故障的第一时间阈值及允许业务数据丢失的第二时间阈值。The electronic device of claim 3, wherein the fault indicator value comprises a first time threshold for allowing a service failure and a second time threshold for allowing service data to be lost.
  5. 如权利要求1所述的电子装置，其特征在于，所述业务系统风险控制程序被所述处理器执行时还实现如下步骤：The electronic device according to claim 1, wherein said business system risk control program is further executed by said processor when:
    实时获取返回至所述客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Obtaining the number of requests returned to the client in real time, and calculating a ratio of the number of requests returning the client to the number of requests sent by the client;
    若在第一预定义的时间内计算得到的请求数之比大于预定义的比值阈值，则向该客户端发送在第二预定义时间内不向所述业务系统发送该业务类型请求的指令。If the ratio of the number of requests calculated in the first predefined time is greater than the predefined ratio threshold, the client is sent an instruction not to send the service type request to the service system within the second predefined time.
  6. 如权利要求2所述的电子装置，其特征在于，所述业务系统风险控制程序被所述处理器执行时还实现如下步骤：The electronic device according to claim 2, wherein said business system risk control program is further executed by said processor when:
    实时获取返回至所述客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Obtaining the number of requests returned to the client in real time, and calculating a ratio of the number of requests returning the client to the number of requests sent by the client;
    若在第一预定义的时间内计算得到的请求数之比大于预定义的比值阈值，则向该客户端发送在第二预定义时间内不向所述业务系统发送该业务类型请求的指令。If the ratio of the number of requests calculated in the first predefined time is greater than the predefined ratio threshold, the client is sent an instruction not to send the service type request to the service system within the second predefined time.
  7. 如权利要求3所述的电子装置，其特征在于，所述业务系统风险控制程序被所述处理器执行时还实现如下步骤：The electronic device according to claim 3, wherein said business system risk control program is further executed by said processor when:
    实时获取返回至所述客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Obtaining the number of requests returned to the client in real time, and calculating a ratio of the number of requests returning the client to the number of requests sent by the client;
    若在第一预定义的时间内计算得到的请求数之比大于预定义的比值阈值，则向该客户端发送在第二预定义时间内不向所述业务系统发送该业务类型请求的指令。If the ratio of the number of requests calculated in the first predefined time is greater than the predefined ratio threshold, the client is sent an instruction not to send the service type request to the service system within the second predefined time.
  8. 如权利要求4所述的电子装置，其特征在于，所述业务系统风险控制程序被所述处理器执行时还实现如下步骤：The electronic device according to claim 4, wherein said business system risk control program is further executed by said processor when:
    实时获取返回至所述客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Obtaining the number of requests returned to the client in real time, and calculating a ratio of the number of requests returning the client to the number of requests sent by the client;
    若在第一预定义的时间内计算得到的请求数之比大于预定义的比值阈值，则向该客户端发送在第二预定义时间内不向所述业务系统发送该业务类型请求的指令。If the ratio of the number of requests calculated in the first predefined time is greater than the predefined ratio threshold, the client is sent an instruction not to send the service type request to the service system within the second predefined time.
  9. 一种业务系统风险控制方法，其特征在于，所述方法包括如下步骤：A business system risk control method, characterized in that the method comprises the following steps:
    接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；After receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
    若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；If it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be prioritized according to the determined priority level;
    若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。If it is determined that there is a risk, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
  10. 如权利要求9所述的业务系统风险控制方法，其特征在于，所述根据预先确定的业务系统风险分析规则分析执行该业务请求是否存在风险的步骤包括：The business system risk control method according to claim 9, wherein the step of analyzing whether the execution of the service request is risky according to the predetermined business system risk analysis rule comprises:
    获取执行该业务请求的业务系统对应的总任务队列中的第一请求数，计算所述第一请求数与接收到的业务请求之和，得到第二任务总数；Obtaining a first request number in a total task queue corresponding to the service system that executes the service request, and calculating a sum of the first request number and the received service request, to obtain a total number of second tasks;
    计算所述第二任务总数与预定义的该业务系统的第一业务阈值之间的大小；Calculating a size between the total number of the second tasks and a predefined first service threshold of the service system;
    若所述第二任务总数大于或等于所述第一业务阈值，则确定该业务系统执行接收到的业务请求存在风险；If the total number of the second tasks is greater than or equal to the first service threshold, determining that the service system performs the received service request is at risk;
    若所述第二任务总数小于所述第一业务阈值，则从所述总任务队列中获取与所述业务请求匹配的业务类型对应的第二请求数，计算所述第二请求数与接收到的请求数之和，得到所述第一任务总数；If the total number of the second tasks is less than the first service threshold, the second request number corresponding to the service type matching the service request is obtained from the total task queue, and the second request number is calculated and received. The sum of the number of requests, the total number of the first tasks;
    计算所述第一任务总数与预定义的该业务系统处理与所述业务请求匹配的业务类型的第二业务阈值之间的大小，若所述第二任务总数小于所述第二业务阈值，则确定处理接收到的请求不存在风险，或者，若所述第一任务总数大于或等于所述第二业务阈值，则确定处理接收到的请求存在风险。Calculating a size between the total number of the first tasks and a predefined second service threshold of the service type that the service system matches the service request, if the total number of the second tasks is less than the second service threshold, It is determined that there is no risk in processing the received request, or if the total number of the first tasks is greater than or equal to the second service threshold, it is determined that there is a risk in processing the received request.
  11. 如权利要求10所述的业务系统风险控制方法，其特征在于，所述根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别的步骤包括：The service system risk control method according to claim 10, wherein the step of determining a service priority level corresponding to the service request according to the predetermined priority level determination rule comprises:
    遍历预先存储的业务类型与故障指标值之间的第一映射关系表，确定接收到的业务请求对应的业务类型的故障指标值；Tracing a first mapping relationship between the pre-stored service type and the fault indicator value, and determining a fault indicator value of the service type corresponding to the received service request;
    根据预先生成的故障指标值与业务优先级别之间的第二映射关系表，确定接收到的业务请求对应的故障指标值的优先级别，所述故障指标值的优先级别为接收到的业务请求对应的业务优先级别。Determining a priority level of the fault indicator value corresponding to the received service request according to the second mapping relationship between the fault indicator value and the service priority level, where the priority level of the fault indicator value is corresponding to the received service request Business priority.
  12. 如权利要求11所述的业务系统风险控制方法，其特征在于，所述故障指标值包括允许业务故障的第一时间阈值及允许业务数据丢失的第二时间阈值。The business system risk control method according to claim 11, wherein the fault indicator value comprises a first time threshold for allowing a service failure and a second time threshold for allowing service data to be lost.
  13. 如权利要求9所述的业务系统风险控制方法，其特征在于，所述方法还包括：The business system risk control method according to claim 9, wherein the method further comprises:
    实时获取返回至所述客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Obtaining the number of requests returned to the client in real time, and calculating a ratio of the number of requests returning the client to the number of requests sent by the client;
    若在第一预定义的时间内计算得到的请求数之比大于预定义的比值阈值，则向该客户端发送在第二预定义时间内不向所述业务系统发送该业务类型请求的指令。If the ratio of the number of requests calculated in the first predefined time is greater than the predefined ratio threshold, the client is sent an instruction not to send the service type request to the service system within the second predefined time.
  14. 如权利要求10所述的业务系统风险控制方法，其特征在于，所述方法还包括：The business system risk control method according to claim 10, wherein the method further comprises:
    实时获取返回至所述客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Obtaining the number of requests returned to the client in real time, and calculating a ratio of the number of requests returning the client to the number of requests sent by the client;
    若在第一预定义的时间内计算得到的请求数之比大于预定义的比值阈值，则向该客户端发送在第二预定义时间内不向所述业务系统发送该业务类型请求的指令。If the ratio of the number of requests calculated in the first predefined time is greater than the predefined ratio threshold, the client is sent an instruction not to send the service type request to the service system within the second predefined time.
  15. 如权利要求11所述的业务系统风险控制方法，其特征在于，所述方法还包括：The service system risk control method according to claim 11, wherein the method further comprises:
    实时获取返回至所述客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Obtaining the number of requests returned to the client in real time, and calculating a ratio of the number of requests returning the client to the number of requests sent by the client;
    若在第一预定义的时间内计算得到的请求数之比大于预定义的比值阈值，则向该客户端发送在第二预定义时间内不向所述业务系统发送该业务类型请求的指令。If the ratio of the number of requests calculated in the first predefined time is greater than the predefined ratio threshold, the client is sent an instruction not to send the service type request to the service system within the second predefined time.
  16. 如权利要求12所述的业务系统风险控制方法，其特征在于，所述方法还包括：The business system risk control method according to claim 12, wherein the method further comprises:
    实时获取返回至所述客户端的请求数，计算返回该客户端的请求数与该客户端发送的请求数之比；Obtaining the number of requests returned to the client in real time, and calculating a ratio of the number of requests returning the client to the number of requests sent by the client;
    若在第一预定义的时间内计算得到的请求数之比大于预定义的比值阈值，则向该客户端发送在第二预定义时间内不向所述业务系统发送该业务类型请求的指令。If the ratio of the number of requests calculated in the first predefined time is greater than the predefined ratio threshold, the client is sent an instruction not to send the service type request to the service system within the second predefined time.
  17. 一种计算机可读存储介质，所述计算机可读存储介质存储有业务系统风险控制程序，所述业务系统风险控制程序可被至少一个处理器执行，以使 所述至少一个处理器执行如下步骤：A computer readable storage medium storing a business system risk control program, the business system risk control program being executable by at least one processor to cause the at least one processor to perform the following steps:
    接收到客户端发送的业务请求后，根据预先确定的业务系统风险分析规则分析执行该请求是否存在风险；After receiving the service request sent by the client, analyzing whether the execution of the request is risky according to a predetermined business system risk analysis rule;
    若确定不存在风险，则根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别，若确定处理该业务请求所属的业务类型的第一任务总数大于预定义的第二业务阈值，则确定需要根据确定的优先级别选择优先处理该业务请求；If it is determined that there is no risk, determining a service priority level corresponding to the service request according to the predetermined priority level determination rule, and if it is determined that the total number of the first tasks of the service type to which the service request belongs is greater than a predefined second service threshold, Determining that the service request needs to be prioritized according to the determined priority level;
    若确定存在风险，则向所述客户端返回该业务请求，并向预先确定的运维邮箱发送风险提示信息。If it is determined that there is a risk, the service request is returned to the client, and the risk prompt information is sent to the predetermined operation and maintenance mailbox.
  18. 如权利要求17所述的计算机可读存储介质，其特征在于，所述根据预先确定的业务系统风险分析规则分析执行该业务请求是否存在风险的步骤包括：The computer readable storage medium of claim 17, wherein the step of analyzing whether the execution of the service request is risky according to a predetermined business system risk analysis rule comprises:
    获取执行该业务请求的业务系统对应的总任务队列中的第一请求数，计算所述第一请求数与接收到的业务请求之和，得到第二任务总数；Obtaining a first request number in a total task queue corresponding to the service system that executes the service request, and calculating a sum of the first request number and the received service request, to obtain a total number of second tasks;
    计算所述第二任务总数与预定义的该业务系统的第一业务阈值之间的大小；Calculating a size between the total number of the second tasks and a predefined first service threshold of the service system;
    若所述第二任务总数大于或等于所述第一业务阈值，则确定该业务系统执行接收到的业务请求存在风险；If the total number of the second tasks is greater than or equal to the first service threshold, determining that the service system performs the received service request is at risk;
    若所述第二任务总数小于所述第一业务阈值，则从所述总任务队列中获取与所述业务请求匹配的业务类型对应的第二请求数，计算所述第二请求数与接收到的请求数之和，得到所述第一任务总数；If the total number of the second tasks is less than the first service threshold, the second request number corresponding to the service type matching the service request is obtained from the total task queue, and the second request number is calculated and received. The sum of the number of requests, the total number of the first tasks;
    计算所述第一任务总数与预定义的该业务系统处理与所述业务请求匹配的业务类型的第二业务阈值之间的大小，若所述第一任务总数小于所述第二业务阈值，则确定处理接收到的请求不存在风险，或者，若所述第一任务总数大于或等于所述第二业务阈值，则确定处理接收到的请求存在风险。Calculating a size between the total number of the first tasks and a predefined second service threshold of the service type that the service system matches the service request, if the total number of the first tasks is less than the second service threshold, It is determined that there is no risk in processing the received request, or if the total number of the first tasks is greater than or equal to the second service threshold, it is determined that there is a risk in processing the received request.
  19. 如权利要求18所述的计算机可读存储介质，其特征在于，所述根据 预先确定的优先级别确定规则确定该业务请求对应的业务优先级别的步骤包括：The computer readable storage medium according to claim 18, wherein the step of determining a service priority level corresponding to the service request according to the predetermined priority level determination rule comprises:
    遍历预先存储的业务类型与故障指标值之间的第一映射关系表，确定接收到的业务请求对应的业务类型的故障指标值；Tracing a first mapping relationship between the pre-stored service type and the fault indicator value, and determining a fault indicator value of the service type corresponding to the received service request;
    根据预先生成的故障指标值与业务优先级别之间的第二映射关系表，确定接收到的业务请求对应的故障指标值的优先级别，所述故障指标值的优先级别为接收到的业务请求对应的业务优先级别。Determining a priority level of the fault indicator value corresponding to the received service request according to the second mapping relationship between the fault indicator value and the service priority level, where the priority level of the fault indicator value is corresponding to the received service request Business priority.
  20. 如权利要求19所述的计算机可读存储介质，其特征在于，根据预先确定的优先级别确定规则确定该业务请求对应的业务优先级别的步骤包括：The computer readable storage medium according to claim 19, wherein the step of determining a service priority level corresponding to the service request according to the predetermined priority level determination rule comprises:
    遍历预先存储的业务类型与故障指标值之间的第一映射关系表，确定接收到的业务请求对应的业务类型的故障指标值；Tracing a first mapping relationship between the pre-stored service type and the fault indicator value, and determining a fault indicator value of the service type corresponding to the received service request;
    根据预先生成的故障指标值与业务优先级别之间的第二映射关系表，确定接收到的业务请求对应的故障指标值的优先级别，所述故障指标值的优先级别为接收到的业务请求对应的业务优先级别。Determining a priority level of the fault indicator value corresponding to the received service request according to the second mapping relationship between the fault indicator value and the service priority level, where the priority level of the fault indicator value is corresponding to the received service request Business priority.
PCT/CN2018/089455 2018-03-06 2018-06-01 Electronic apparatus, service system risk control method, and storage medium WO2019169763A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810184861.8 2018-03-06
CN201810184861.8A CN108491304B (en) 2018-03-06 2018-03-06 electronic device, business system risk control method and storage medium

Publications (1)

Publication Number Publication Date
WO2019169763A1 true WO2019169763A1 (en) 2019-09-12

Family

ID=63341736

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/089455 WO2019169763A1 (en) 2018-03-06 2018-06-01 Electronic apparatus, service system risk control method, and storage medium

Country Status (2)

Country Link
CN (1) CN108491304B (en)
WO (1) WO2019169763A1 (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109377236A (en) * 2018-10-23 2019-02-22 上海盛付通电子支付服务有限公司 A kind of risk control method, equipment and storage medium based on fusing mechanism
CN109711929A (en) * 2018-12-13 2019-05-03 中国平安财产保险股份有限公司 Business recommended method and device based on prediction model
CN110728436B (en) * 2019-09-24 2022-06-10 支付宝(杭州)信息技术有限公司 Risk identification method and device, electronic equipment and system
CN112417418A (en) * 2020-11-19 2021-02-26 刘一方 Verification method based on novel verification code
CN116777621B (en) * 2023-06-25 2024-02-06 陕西西煤云商信息科技有限公司 Trade business risk prevention and control method and prevention and control system thereof

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6725211B1 (en) * 2000-09-28 2004-04-20 International Business Machines Corporation Work load assessment heuristic for optimal task parallelism determination
US8605886B2 (en) * 2006-12-18 2013-12-10 Verizon Patent And Licensing Inc. Method and system for multimedia contact routing
CN104811952A (en) * 2014-01-26 2015-07-29 中国移动通信集团江苏有限公司 Service processing verification method and system
CN106600275A (en) * 2015-10-14 2017-04-26 阿里巴巴集团控股有限公司 Risk identification method and apparatus thereof

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104731649A (en) * 2015-04-21 2015-06-24 中国建设银行股份有限公司 Multi-task processing method and multi-task processing device
CN107040558A (en) * 2016-02-03 2017-08-11 阿里巴巴集团控股有限公司 A kind of Mission Monitor method and device
CN107391268A (en) * 2016-05-17 2017-11-24 阿里巴巴集团控股有限公司 service request processing method and device
CN107644340A (en) * 2016-07-22 2018-01-30 阿里巴巴集团控股有限公司 Risk Identification Method, client device and risk recognition system
CN107067157A (en) * 2017-03-01 2017-08-18 北京奇艺世纪科技有限公司 Business risk appraisal procedure, device and air control system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6725211B1 (en) * 2000-09-28 2004-04-20 International Business Machines Corporation Work load assessment heuristic for optimal task parallelism determination
US8605886B2 (en) * 2006-12-18 2013-12-10 Verizon Patent And Licensing Inc. Method and system for multimedia contact routing
CN104811952A (en) * 2014-01-26 2015-07-29 中国移动通信集团江苏有限公司 Service processing verification method and system
CN106600275A (en) * 2015-10-14 2017-04-26 阿里巴巴集团控股有限公司 Risk identification method and apparatus thereof

Also Published As

Publication number Publication date
CN108491304A (en) 2018-09-04
CN108491304B (en) 2019-12-10

Similar Documents

Publication Publication Date Title
WO2019169763A1 (en) Electronic apparatus, service system risk control method, and storage medium
WO2019140828A1 (en) Electronic apparatus, method for querying logs in distributed system, and storage medium
WO2019179026A1 (en) Electronic device, method for automatically generating cluster access domain name, and storage medium
WO2019148722A1 (en) Electronic device, data migrating and calling method and storage medium
WO2019179027A1 (en) Electronic device, firewall provisioning verification method, system and storage medium
WO2019148727A1 (en) Electronic device, redis-based exception warning method and storage medium
WO2019205371A1 (en) Server, message allocation method, and storage medium
WO2019136812A1 (en) Electronic device, data calling log generation and query method, and storage medium
WO2019148721A1 (en) Electronic device, risk early warning method for internet service system, and storage medium
CN108287708B (en) Data processing method and device, server and computer readable storage medium
WO2019019636A1 (en) User identification method, electronic device, and computer readable storage medium
WO2019024483A1 (en) Project information display method, electronic device, and computer readable storage medium
WO2019148728A1 (en) Electronic device, execution task assignment method for distributed system, and storage medium
WO2018223941A1 (en) Device and method for issuing multiple insurance policies and computer readable storage medium
WO2019192133A1 (en) Electronic apparatus, data link risk pre-warning method, and storage medium
WO2018214404A1 (en) Insurance policy information processing device, method, system and computer readable storage medium
US20160283532A1 (en) Alert management
WO2019179028A1 (en) Electronic device, user authentication method based on dynamic pictures, and storage medium
WO2019140829A1 (en) Electronic device, method for releasing application update version, and storage medium
WO2019174185A1 (en) Electronic device, dynamic code request processing method and storage medium
WO2019071958A1 (en) Cloud computing-based salary calculation method, application server, and computer readable storage medium
WO2019169771A1 (en) Electronic device, access instruction information acquisition method and storage medium
US10606604B2 (en) Predictive queue control and allocation
WO2019095569A1 (en) Financial analysis method based on financial and economic event on microblog, application server, and computer readable storage medium
WO2019080413A1 (en) Customer management method and system, computer device and storage medium

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18908709

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 09.12.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 18908709

Country of ref document: EP

Kind code of ref document: A1