Method and device for routing requests

Abstract

The claimed solution relates to computing, and more particularly to a method and device for routing requests. The technical result consists in providing for more accurate routing of requests. This result is achieved by receiving a request for a service provided by an operator of an executing device, classifying the service request to determine the complexity factor thereof, determining the priority of the request on the basis of product type, determining a list of suitable operators and the identifiers of the executing devices thereof, and forwarding the service request in accordance with the determined list to the executing devices, where it is displayed to the operators, taking into account the priority value of the request.

Description

METHOD AND DEVICE FOR ROUTING REQUESTS AREA OF TECHNOLOGY

[0001] This technical solution generally relates to the field of computer technology, and in particular to a method and device for routing requests for the provision of services received from user devices to executive devices based on the automatically determined complexity of the requests. LEVEL OF TECHNOLOGY

[0002] The prior art discloses a system and method for setting up new financial consultation applications from various services and sub-applications for providing coordinated recommendations to consumers, clients and consultants regardless of the delivery mechanism used, disclosed in patent US 7475032 B1, published 06.01.2009. The known system includes at least one client computer on which an application program is implemented; a consultation utility server associated with the client computer and the application program; and at least one financial service associated with the consultation service server, wherein each financial service is configured to receive / transmit data from / to the consultation service server.

[0003] Also known are a method and system for distributing cases to agents, disclosed in patent CN 110727875 B, published 08.05.2020. The known system includes a user interface level, a feature processing level, a distribution matching level, a data storage level and a monitoring management level, as well as an online lawyer recommendation technology and artificial intelligence technology for automatically extracting and displaying the client's intention and portrait when searching for a lawyer, and the most relevant and suitable lawyer is selected for the client. Based on the task setting technology in the field of optimization of operational research, optimal coordination of several clients and several lawyers in the process of an agent on a legal case is implemented, while solving the problems of monitoring lawyer fatigue and balancing the distribution of sources of cases of new lawyers.

[0004] The disadvantage of known solutions is the lack of a device capable of routing user requests to executive devices to provide a service taking into account the complexity of the request. ESSENCE OF THE TECHNICAL SOLUTION

[0005] The technical problem or task set in this technical solution is the creation of a simple and reliable method and device for routing requests received from user devices to executive devices for the provision of services.

[0006] The technical result achieved by solving the above technical problem is an increase in the accuracy of request routing.

[0007] The specified technical result is achieved by implementing a method for routing requests between at least one user device and executive devices, performed by at least one computing device, containing the steps of: - receive a request for the provision of a service, which will be provided by at least one operator of the actuator; - classify a request for the provision of a service to determine the complexity coefficient of the said request; - determine the priority of the request for the provision of a service based on the type of product; - define a list of operators whose qualification parameter corresponds to the complexity value of the request, and the identifiers of their executive devices; - send a request for the provision of a service in accordance with a specific list to executive devices, which are displayed to operators taking into account the priority value of the request.

[0008] In one of the particular examples of the method implementation, additional steps are performed at which: data on the service is obtained; the type of service is determined; and the complexity factor of the request for the provision of the service is determined taking into account the type of service.

[0009] In another particular example of implementing the method, additional steps are performed at which: data about the service is obtained; the type of client is determined; and the complexity factor of the request for the provision of the service is determined taking into account the type of client.

[0010] In another particular example of implementing the method, additional steps are performed at which: data on the service is obtained; the type of sale is determined; and the complexity factor of the request for the provision of the service is determined taking into account the type of sale.

[0011] In another particular example of implementing the method, additional steps are performed at which: data on the service is obtained; the type of product is determined; and the complexity factor of the request for the provision of the service is determined taking into account the type of product.

[0012] In another particular example of implementing the method, additional steps are performed at which: data on the service is obtained; the type of industry is determined; and the complexity factor of the request for the provision of the service is determined taking into account the type of industry.

[0013] In another particular example of implementing the method, additional steps are performed at which: data about the service is obtained; the user's status is determined: resident or non-resident; and the complexity factor of the request for the provision of the service is determined taking into account the user's status.

[0014] In another particular example of implementing the method, additional steps are performed at which: data on the service is obtained; data on the body making the decision regarding the transaction is extracted; and the complexity factor of the request for the provision of the service is determined taking into account the data on the body making the decision regarding the transaction.

[0015] In another particular example of implementing the method, the following steps are additionally performed: receiving data about the service; determining whether the data about the service contains a third party insider, a person on the sanctions list, or a significant client; determining the increasing complexity factor in accordance with the information determined at the previous step, and specifying the complexity of the request for the provision of the service in accordance with the increasing factor.

[0016] In another particular example of implementing the method, the following steps are additionally performed: receiving data about the service; determining the absence of a client ID; assigning an increasing complexity factor and specifying the complexity of the request for the provision of the service in accordance with the increasing factor.

[0017] In another particular example of implementing the method, additional steps are performed in which: the presence of a special mark in the request parameters is determined, an increasing complexity factor is assigned, and the complexity of the request for the provision of a service is specified in accordance with the increasing factor.

[0018] In another particular example of implementing the method, additional steps are performed in which: it is determined that the request should be routed among a specified category of operators; it is checked whether the user profile contains a parameter indicating that the user has access to the specified category of operators; the complexity of the request is increased in accordance with the algorithm specified by the developer, if the profile contains the said parameter.

[0019] In another particular example of implementing the method, additional steps are performed in which: the presence of a parameter characterizing the user's location is determined in the request parameters; wherein the request for the provision of the service is sent to those operators whose location information corresponds to the user's location, wherein after the expiration of a specified time, the request for the provision of the service can be sent to other operators from the said list.

[0020] In another particular example of implementing the method, additional steps are performed in which: the presence of a parameter in the request parameters that characterizes the ID of the group of related borrowers (GRB) is determined; and the request for the provision of the service is sent to those operators whose profile contains a parameter indicating the ability of the operator to work with the specified GRB ID.

[0021] In another particular example of implementing the method, additional steps are performed in which: information about the operator parameters is requested from the operator profile of the actuator; the operator qualification parameter of the device is determined based on the operator parameters obtained in the previous step.

[0022] In another particular example of implementing the method, additional steps are performed in which: the presence of parameters in the operator parameters indicating the operator's skill in working with: third-party insiders, sanctions lists, significant clients, or special marks is determined; the operator's qualification parameter is specified based on the parameter obtained in the previous step.

[0023] In another preferred embodiment of the claimed solution, a request routing device is presented, comprising at least one computing device and at least one memory containing machine-readable instructions, which, when executed by at least one computing device, perform the above-mentioned method. BRIEF DESCRIPTION OF DRAWINGS

[0024] The features and advantages of the present invention will become apparent from the following detailed description of the invention and the accompanying drawings, in which: Fig. 1 shows an example of the implementation of the information processing system. Fig. 2 shows an example of the general appearance of the computing device. DETAILED DESCRIPTION OF THE INVENTION

[0025] Below we will describe the concepts and terms necessary for understanding this technical solution.

[0026] In this technical solution, the term “system” means, among other things, a computer system, a computer (electronic computer), a numerical control (CNC), a PLC (programmable logic controller), computerized control systems and any other devices capable of performing a given, clearly defined sequence of operations (actions, instructions).

[0027] A command processing unit is an electronic unit or integrated circuit (microprocessor) that executes machine instructions (programs).

[0028] The command processing unit reads and executes machine instructions (programs) from one or more storage devices. Storage devices may include, but are not limited to, hard disk drives (HDD), flash memory, ROM (read-only memory), solid-state drives (SSD), and optical drives.

[0029] A program is a sequence of instructions intended for execution by a computer control device or a command processing device.

[0030] In accordance with the diagram shown in Fig. 1, the information processing system 100 comprises at least one interconnected user device 1, executive devices 2, data transmission channels 10, request routing device 20, request classification device 30, request prioritization device 40, database (DB) 50 and operator classification device 60.

[0031] The user device 1 and the executive devices 2 can be implemented on the basis of at least one computing device equipped with data transmission means and represent, for example, a portable or stationary computer, a mobile phone or smartphone, a tablet, etc.

[0032] Data transmission channels 10, 11 can be implemented on the basis of well-known wired and wireless communication technologies to ensure data exchange between the mentioned devices 1, 2 and the request routing device 20.

[0033] The request routing device 20 can be implemented on the basis of at least one computing device connected via data transmission channels 10, 11 with at least one user device 1 and executive devices 2, and contain a module 21 for primary request processing.

[0034] The device 30 for classifying requests, the device 40 for prioritizing requests and the device 60 for classifying operators can be implemented on the basis of at least one computing device, wherein the device 30 can be equipped with: modules 31-37 for determining the complexity of a request, as well as a module 38 for increasing the complexity of a request. The mentioned modules can be implemented, for example, on the basis of logical elements implemented on transistors.

[0035] At the first stage of the operation of the data processing system 100, the user can send a request for the provision of a service via the device 1, which will be provided by at least one operator of the executive device 2. For example, the request for the provision of a service can be a request for the verification of a document by the operator of the executive device 2, for example, a specialist, in particular a lawyer, who has the appropriate qualifications for reviewing the document. The document can be any type of document and contain, for example, data on a transaction, in particular be a purchase and sale agreement, a loan agreement, etc.

[0036] Accordingly, the request for the provision of a service, in a particular embodiment of the presented solution, may contain the ID of the type of service, the ID of the set of documents, the ID of the user of the device 1, as well as the parameters of the request: indicating that the routing of the request should be performed among a specified category of operators; indicating the presence of a third-party insider; indicating the presence of a person on the sanctions lists; indicating the presence of a significant client; indicating the location of the user of the device 2. The said parameters can be specified, for example, by the user when sending the request or by means of semantic analysis of the text of the document using a neural network and loaded into the DB 50 during the process of routing the request for the provision of a service. In an alternative embodiment of the presented solution, the said parameters can be obtained from an external AS, for example, by the ID of the set of documents and saved in the data on the service, saved, for example, in the DB 50.

[0037] A request for the provision of a service is received by the request routing device 20, which records in the memory with which it may be equipped the time of receipt of said request and determines whether an operator of the device 2 has been previously assigned for said service. For this, the device 20 extracts a unique identifier (ID) of the set of documents, which may be contained in the received request, and sends it to the module 21 for primary processing of requests. The ID of the set of documents may be entered into said request by a widely known method, for example, entered by the user or assigned automatically when loading the set of documents, for example, into the DB 50 or an external AS.

[0038] The module 21 for primary processing of requests based on the ID of the set of documents accesses historical data that can be stored, for example, in the DB 50 containing the IDs of the sets of documents and the IDs of the operators that have been assigned to said sets of documents. If the module 21 determines that an operator has already been assigned to the received ID of the set of documents in the DB 50, the module 21 extracts the ID of the operator's device 2, which can also be previously entered into the DB 50 for the operator, and sends a command to the device 20 to transmit a request for the provision of a service to the device 2 of said operator to whom the document was previously assigned. Accordingly, after receiving said command, the device 20 sends a request for the provision of a service to the executive device 2 in accordance with the received ID of the device 2.

[0039] If module 21 determines that no operator has been assigned for the received document set ID, module 21 sends a command to device 20 to proceed to the next stage. At the next stage, device 20 starts the process of classifying the complexity of the service request and sends a corresponding command to request classification device 30, which determines the complexity coefficient of said request based on the type of service.

[0040] In order to determine the complexity factor of the request, the device 30 starts the module 31 , which extracts the service type ID from the request and compares it with preset data in the memory of said module 31 , characterizing the service types and the values ​​of the query complexity factors that should be assigned to the service types. For example, the service type ID may indicate that the user has requested a service for checking the legal capacity of a counterparty or a service for legal expertise of a decision of a collegial body, and in the memory of module 31 the second complexity level "Pro" may be set for the service for checking the legal capacity of a counterparty, and the minimum third complexity level "Expert" for the service for legal expertise of a decision of a collegial body. If the information on the received service ID was not found in the memory by module 31 , then module 31 assigns a complexity label indicating that the complexity is not set.Accordingly, the complexity factor determined by module 31 is sent by device 30 to device 20.

[0041] Additionally, the complexity factor of the request can be determined by the device 30 taking into account the type of client, if, for example, the data on the service contains data on the transaction, extracted, for example, from a document. For this, the device 30 starts the module 32, which requests the device 20 for data on the service, which can be loaded by the device 20 in the process of classifying the complexity of said request or before its start from the DB 50, into which said data can be loaded by known methods from external systems. The data on the service can contain: the ID of the client for the transaction (for example, TIN, OGRN, etc.), information on the type of sale, the ID of the product, the ID of the industry, the ID of the body making the decision regarding the transaction.

[0042] In particular, module 32 extracts the client ID from the service data, determines the client type, and, depending on the client type, determines the query complexity factor. To determine the client type, module 32 may be equipped with memory that stores data with client IDs, their types, and the values ​​of the query complexity factors that should be assigned to the said types. clients. For example, the client ID may represent the name of a company or a financial institution, and in the memory of module 32 for the client type - medium and large companies, the minimum third level of complexity "Expert" may be set, and for the client type - financial institutions, the second level of complexity "Profi" may be set. Also, as a complexity coefficient of the query, module 32 may assign a special label, for example, if the client type indicates who the client belongs to the military-industrial complex / military industrial complex, and information about the presence of a special label is added by module 32 to the query parameters. If module 32 did not find information in the memory for the received client ID, then module 32 assigns a complexity label indicating that the complexity is not set.

[0043] Also, the complexity factor of the query can be additionally determined by the device 30 taking into account the type of sale. For this, the device 30 starts the module 33, which extracts from the data on the service the information on the type of sale, which can indicate that the type of sale is a direct or indirect sale. Then the information on the type of sale is compared by the module 33 with the data stored in the memory containing the instructions indicating what value of the complexity factor should be assigned to the query based on the information on the type of sale. For example, if the module 33 determines that the type of sale is a "direct" sale, then the module 33 can assign the minimum third level of complexity "Expert", and if the module 33 determines that the type of sale is an "indirect" sale, then the module 33 can assign the second level of complexity "Pro".If module 33 does not find information in memory on the received type of sale, then module 33 assigns a complexity factor value indicating that the complexity is not set.

[0044] Also, the complexity factor of the request can be additionally determined by the device 30 taking into account the type of product. For this, the device 30 starts the module 34, which extracts the product ID from the service data and compares it with the preset data in the memory of the said module 34, characterizing the product IDs, their types and the values ​​of the complexity factors of the request, which should be assigned to the said types of products. For example, the product ID can indicate that the product belongs to the type of short-term express lending, which should be assigned the minimum third level of complexity "Expert", to the type of financing corporate leasing operations, which should be assigned the second level of complexity "Pro", to the type of margin lending, which should be assigned the maximum first complexity level "Super", or to the type of financing for the construction of real estate objects, which should be assigned a special label, information about the presence of which will be saved in the request parameters. If module 34 did not find information in the memory for the received product ID, then module 34 assigns a complexity label indicating that the complexity is not set.

[0045] In addition, the complexity factor of the query can be determined by the device 30 taking into account the type of industry. For this, the device 30 launches the module 35, which extracts the industry ID from the service data and compares it with the preset data in the memory of the said module 35, characterizing the industry IDs, their types and the values ​​of the complexity factors of the query, which should be assigned to the said types of industries. For example, the industry ID can indicate that the industry pertains to agriculture, for which the minimum third complexity level "Expert" should be assigned, to mechanical engineering, which should be assigned the second complexity level "Pro", to energy and water supply, which should be assigned the maximum first complexity level "Super", or to state and municipal government bodies, which should be assigned a special label, information about the presence of which will be saved in the query parameters.If module 35 does not find information in memory for the received industry ID, module 35 assigns a complexity label indicating that the complexity is not set.

[0046] Also, the complexity factor of the request can be additionally determined by the device 30 taking into account the user's status: resident or non-resident. For this, the device 30 launches the module 36, which extracts the client ID from the service data and compares it with the preset data in the memory of the said module 36, characterizing the client IDs, their statuses and the values ​​of the complexity factors of the request, which should be assigned to the said statuses. For example, the memory of the module 36 can indicate that the second complexity level "Pro" should be assigned for resident clients, and the maximum first complexity level "Super" for non-residents. If the information on the received client ID was not found in the memory by the module 36, then the module 36 assigns a complexity mark indicating that the complexity is not set.

[0047] Also, the complexity factor of the request can be additionally determined by the device 30 taking into account the data on the body making the decision regarding the transaction, if such data is contained in the transaction data. For example, for the Committee 1 body, the maximum first level of complexity can be set, for the Committee 2 body - the second level of complexity "Pro". For this, the device 30 starts the module 37, which extracts the ID of the said body and compares it with the preset data in the memory of the said module 37, characterizing the ID of all bodies, the decision-making level of the body and the values ​​of the complexity coefficients that should be assigned to the request for the provision of a service depending on the said level. If the information on the received data about the body was not found in the memory by the module 37, then the module 37 assigns a complexity mark indicating that the complexity is not set.

[0048] Accordingly, after some or all modules 31-37 have determined the values ​​of the complexity coefficients, device 30 determines the complexity coefficient (i.e. the final one), which, for example, can be determined based on the maximum value of the complexity coefficient received from at least one of the modules from 31-37. If all modules involved in classifying the complexity of the request have issued a complexity label indicating that the complexity is not set, then device 30 assigns a complexity label of the request indicating that the complexity is not set. This complexity label can also be assigned by device 30 in the event that no response has been received from modules 31-37.

[0049] Additionally, the device 30 may be configured to specify the complexity of the request for the provision of a service. To specify the complexity of the request, the device 30 is equipped with a module 38 for increasing the complexity of the request, which is configured to determine the presence of parameters that increase the complexity of the request, stored in the device 20, for example, a parameter: indicating the presence of a third-party insider; indicating the presence of a person on sanctions lists; or indicating the presence of a significant client.

[0050] Accordingly, if the query complexity increasing module 38 has determined the presence of a complexity increasing parameter, then the module 38 determines the complexity increasing factor depending on the type of said parameter. The data on the parameter types and their complexity increasing factors may be preset in the memory of the module 38. For example, if the parameter indicates the presence of a third party insider, then the module 38 may assign a complexity increasing factor indicating the need for the first marker to be present for considering the query. If the parameter indicates presence of a person on the sanctions lists, then module 38 may assign an increasing complexity factor indicating the need for a second marker to consider the request. If the parameter indicates the presence of a significant client, then module 38 may assign an increasing complexity factor indicating the need for a third marker to consider the request.

[0051] Additionally, module 38 can determine the absence of a client ID if the service data did not contain it, and then assign an increasing complexity factor indicating the need for a fourth marker to consider the request.

[0052] Additionally, module 38 may assign a complexity escalation factor in the manner described above if one of modules 31-37 has defined a special label as a complexity value and saved it in the query parameters. For example, if the special label indicates that the client belongs to the military-industrial complex / military industrial complex, module 38 may assign a complexity escalation factor indicating the need for a fifth marker to consider the query. If the special label indicates that the service belongs to the type of real estate construction financing, module 38 may assign a complexity escalation factor indicating the need for a sixth marker to consider the query. If the special label indicates that the query belongs to the industry - state and municipal government bodies, module 38 may assign a complexity escalation factor indicating the need for a seventh marker to consider the query.

[0053] The complexity factor value, the increasing complexity factor, and information about the presence of a special marker, if such a marker has been defined, are sent by device 30 to device 20, which determines the resulting complexity value of the request based on them. For example, if a request is assigned the minimum third complexity level "Expert" or the second complexity level "Profi" and the increasing complexity factor indicating the need for the first marker to be present to consider the request, then device 20 will determine the minimum third complexity level "Expert" or the second complexity level "Profi" with the first marker as the resulting complexity value of the request. Thus, when routing the request, operators with the qualification parameter "Expert" or "Profi" will not be taken into account without marker. If the device 30 receives the "not set" query complexity label as the complexity coefficient value, then the device 30 assigns the resulting query complexity value - the maximum first complexity level "Super".

[0054] After the complexity value of the request and the increasing complexity factor have been determined, the device 20 initiates the determination of the priority of the request for the provision of a service. To initiate the process of determining the priority, the device 20 sends a corresponding command to the request prioritization device 40, which extracts the product type ID from the device 20 and, on its basis, determines a priority value that indicates the order of the request for the provision of a service when displayed to the operator. The product type IDs and the priority values ​​that should be assigned to them can be preset in the memory of the device 40 by the developer.

[0055] For example, if the product type ID indicates that the product is for 7-minute credit, then the device 40 may assign a priority value of "1." If the product type ID indicates that the product is for a queuing system (QS), then the device 40 may assign a priority value of "2," "3," or "4."

[0056] After receiving the priority value, device 20 accesses DB 50, which stores information about device 2 operators, their device 2 IDs, and a qualification parameter, such as "Expert," "Pro," or "Super," and generates a list of operators whose qualification parameter corresponds to the resulting value of the complexity of the request and sends a request for the provision of a service to their devices 2, which are displayed to operators taking into account the priority value of the request. For example, all requests for the provision of a service may be displayed on device 2, with the request with the highest priority value of the request being displayed first in the list.

[0057] If the device 20 determines that the request should be routed among a specified category of operators, the device 20 accesses the user profile of the device 2, which can be saved in the DB 50 by known methods during user registration, and checks whether the said profile contains a parameter indicating that the user has access to the specified category of operators in the general queue mode and increases the complexity of the request in accordance with the algorithm specified by the developer, if the profile contains the said parameter, for example, increases the complexity of the request with minimum third level of difficulty "Expert" to the second level of difficulty "Pro".

[0058] In an alternative embodiment of the presented solution, if the data on the service contains a parameter characterizing the location of the user, then the device 20 will send a request for the provision of the service to the operator whose location information corresponds to the location of the user, and after the expiration of a specified time, the request for the provision of the service can be sent to other operators from the list.

[0059] Additionally, the service data may contain a parameter characterizing the ID of the group of related borrowers (GRB), which may be added to the service data by the user of device 1 or determined automatically by known methods based on the client ID. Accordingly, if device 20 determines the presence of the specified parameter, then device 20 will send a request for the provision of the service by the operator whose profile contains a parameter indicating the possibility of the operator working with the specified GRB ID.

[0060] Additionally, the system 100 can be designed with the ability to determine the qualification parameter of the device 2 operator. To determine the operator qualification parameter, the system 100 comprises an operator classification device 60, which requests information about the operator parameters from the operator profile from the executive device 2 or extracts them from the DB 50, in which they can be previously saved during the process of registering operators in the system 100. The operator parameters can indicate that the operator has the skill to work with a given list of services, types of clients, types of sales, types of product, types of industry, user statuses, with decision-making bodies regarding the transaction.

[0061] For example, if the operator profile contains parameters indicating that the operator has the skill to work with the counterparty due diligence service, with medium and large companies, with the direct sales type, with short-term express lending, with the agricultural sector, with the body making the decision regarding the transaction Committee 1, then device 60, based on the results of processing the parameters, can assign the minimum third qualification parameter “Expert” to the operator.

[0062] If the operator profile contains parameters indicating that the operator has the skill to work with the legal expertise service of the solution collegial body, with financial institutions, with the indirect type of sale, with financing of corporate leasing transactions, with the mechanical engineering industry, with residents, with the body making the decision regarding the transaction Committee 2, then device 60, based on the results of processing the parameters, can assign the second qualification parameter “Pro” to the operator of device 2.

[0063] Additionally, when determining the operator qualification parameter, the device 60 may take into account parameters indicating whether the operator has the skill to work with: third-party insiders, sanctions lists, significant clients, or special marks. For example, if the operator profile contains a parameter indicating the skill to work with third-party insiders, the device 60 may assign the first qualification mark. If the operator profile contains a parameter indicating the skill to work with sanctions lists, the device 60 may assign the second qualification mark. The remaining qualification marks may be assigned by the device 60 for the mentioned parameters and special marks in a similar manner in accordance with the algorithm specified by the developer.

[0064] Thus, based on the processing of the operator parameters, the device 60 determines for each operator of the device 2 a qualification parameter that characterizes the operator's qualification level. The operator parameters can be entered by the operator when registering in the system 100 by means of the device 2, or assigned automatically by the system 100 in accordance with the algorithm specified by the developer, for example, to indicate that the operator has the minimum third qualification parameter "Expert".

[0065] In general (see Fig. 2), the computing device contains one or more processors (201) connected by a common information exchange bus, memory means such as RAM (202) and ROM (203), input / output interfaces (204), input / output devices (205), and a device for network interaction (206).

[0066] The processor (201) (or several processors, a multi-core processor, etc.) can be selected from a range of devices that are widely used today, such as those from manufacturers such as: Intel™, AMD™, Apple™, Samsung Exynos™, MediaTEK™, Qualcomm Snapdragon™, etc. The processor or one of the processors used in the device (200) must also include a graphics processor, such as an NVIDIA or Graphcore GPU, the type of which is also suitable for full or partial execution method, and can also be used for training and applying machine learning models in various information systems.

[0067] RAM (202) is a random access memory and is intended for storing machine-readable instructions executed by the processor (201) to perform the necessary operations for logical data processing. RAM (202), as a rule, contains executable instructions of the operating system and the corresponding software components (applications, software modules, etc.). In this case, the available memory capacity of the graphic card or graphic processor can act as RAM (202).

[0068] ROM (203) is one or more permanent data storage devices, such as a hard disk drive (HDD), a solid-state drive (SSD), flash memory (EEPROM, NAND, etc.), optical storage media (CD-R / RW, DVD-R / RW, BlueRay Disc, MD), etc.

[0069] To organize the operation of the device components (200) and to organize the operation of external connected devices, various types of I / O interfaces (204) are used. The choice of the corresponding interfaces depends on the specific design of the computing device, which may include, but are not limited to: PCI, AGP, PS / 2, IrDa, FireWire, LPT, COM, SATA, IDE, Lightning, USB (2.0, 3.0, 3.1, micro, mini, type C), TRS / Audio jack (2.5, 3.5, 6.35), HDMI, DVI, VGA, Display Port, RJ45, RS232, etc.

[0070] To ensure interaction between the user and the device (200), various means (205) of I / O information are used, for example, a keyboard, a display (monitor), a touch display, a touchpad, a joystick, a mouse, a light pen, a stylus, a touch panel, a trackball, speakers, a microphone, augmented reality means, optical sensors, a tablet, light indicators, a projector, a camera, biometric identification means (a retina scanner, a fingerprint scanner, a voice recognition module), etc.

[0071] The network interaction means (206) ensures data transmission via an internal or external computer network, such as Intranet, Internet, LAN, etc. One or more means (206) may be, but are not limited to: an Ethernet card, GSM modem, GPRS modem, LTE modem, 5G modem, satellite communication module, NFC module, Bluetooth and / or BLE module, Wi-Fi module, etc.

[0072] Additionally, satellite navigation systems can also be used as part of the system (200), for example, GPS, GLONASS, BeiDou, Galileo. Specific the selection of device elements (200) for the implementation of various software and hardware architectural solutions can vary while maintaining the required functionality provided.

[0073] Modifications and improvements of the above-described embodiments of the present technical solution will be clear to those skilled in the art. The preceding description is provided only as an example and does not bear any limitations. Thus, the scope of the present technical solution is limited only by the scope of the attached claims.

Claims

CLAUSE OF THE INVENTION 1. A method for routing requests between at least one user device and execution devices, performed by at least one computing device, comprising the steps of: - receive a request for the provision of a service, which will be provided by at least one operator of the actuator; - classify a request for the provision of a service to determine the complexity coefficient of the said request; - determine the priority of the request for the provision of a service based on the type of product; - define a list of operators whose qualification parameter corresponds to the complexity value of the request, and the identifiers of their executive devices; - send a request for the provision of a service in accordance with a specific list to executive devices, which are displayed to operators taking into account the priority value of the request.

2. The method according to paragraph 1, characterized in that the following steps are additionally performed: - receive data about the service; - determine the type of service; moreover, the complexity coefficient of the request for the provision of a service is determined taking into account the type of service.

3. The method according to paragraph 1, characterized in that the following steps are additionally performed: - receive data about the service; - determine the type of client; moreover, the complexity coefficient of the request for the provision of a service is determined taking into account the type of client.

4. The method according to paragraph 1, characterized in that the following steps are additionally performed: - receive data about the service; - determine the type of sale; moreover, the complexity coefficient of the request for the provision of a service is determined taking into account the type of sale.

5. The method according to paragraph 1, characterized in that the following steps are additionally performed: - receive data about the service; - determine the type of product; moreover, the complexity coefficient of the request for the provision of a service is determined taking into account the type of product.

6. The method according to paragraph 1, characterized in that the following steps are additionally performed: - receive data about the service; - determine the type of industry; moreover, the complexity coefficient of the request for the provision of a service is determined taking into account the type of industry.

7. The method according to item 1, characterized in that the following steps are additionally performed: - receive data about the service; - determine the user's status: resident or non-resident; moreover, the complexity coefficient of the request for the provision of a service is determined taking into account the user's status.

8. The method according to item 1, characterized in that the following steps are additionally performed: - receive data about the service; - extract data on the body making the decision regarding the transaction; moreover, the complexity factor of the request for the provision of the service is determined taking into account data on the body making the decision regarding the transaction.

9. The method according to item 1, characterized in that the following steps are additionally performed: - receive data about the service; - determine whether the insider service data contains third parties, persons on sanctions lists, or significant clients; - determine the increasing complexity factor in accordance with the information determined at the previous stage and specify the complexity of the request for the provision of a service in accordance with the increasing factor.

10. The method according to item 1, characterized in that the following steps are additionally performed: - receive data about the service; - determine the absence of a client ID; - assign a complexity increasing coefficient and specify the complexity of the request for the provision of a service in accordance with the complexity increasing coefficient.

11. The method according to item 1, characterized in that the following steps are additionally performed: - determine the presence of a special label in the request parameters, - assign a complexity increasing coefficient and specify the complexity of the request for the provision of a service in accordance with the complexity increasing coefficient.

12. The method according to item 1, characterized in that the following steps are additionally performed: - determine that the request should be routed among a given category of operators; - check whether the user profile contains a parameter indicating that the user has access to the specified category of operators; - increase the complexity of the request in accordance with the algorithm specified by the developer, if the profile contains the mentioned parameter.

13. The method according to item 1, characterized in that the following steps are additionally performed: - determine the presence in the request parameters of a parameter characterizing the location of the user; wherein the request for the provision of the service is sent to those operators whose location information corresponds to the location of the user, wherein after the expiration of the specified time, the request for the provision of the service may be sent to other operators from the said list.

14. The method according to item 1, characterized in that the following steps are additionally performed: - determine the presence in the request parameters of a parameter characterizing the ID of the group of related borrowers (GRB); moreover, the request for the provision of the service is sent to those operators whose profile contains a parameter indicating the operator’s ability to work with the specified GRB ID.

15. The method according to item 1, characterized in that the following steps are additionally performed: - request information about the operator parameters from the operator profile of the actuator; - determine the operator qualification parameter of the device based on the operator parameters obtained in the previous stage.

16. The method according to item 15, characterized in that the following steps are additionally performed: - determine the presence in the operator parameters of parameters indicating the operator’s skill in working with: third-party insiders, sanctions lists, significant clients, or special marks; - specify the operator qualification parameter based on the parameter obtained at the previous stage.

17. A request routing device comprising at least one computing device and at least one memory device containing machine-readable instructions that, when executed by at least one computing device, perform the method according to any one of paragraphs 1-16.

Images