Service scheduling method based on scheduling component, scheduling component, equipment and medium

Abstract

The invention provides a service scheduling method based on a scheduling component, the scheduling component, equipment and a medium, the scheduling component comprises a gateway and a background management system, the gateway comprises a service system and is deployed in a service platform, and the method comprises the following steps: the background management system receives configuration information, authorizing all applications according to the configuration information to obtain authorization information, and sending the authorization information to a gateway; the gateway receives a service scheduling request and determines a target application corresponding to the service scheduling request; the gateway performs authentication processing on the target application according to the authorization information, and obtains a target identifier in a service scheduling request in response to the fact that the authentication of the target application is passed; the gateway sends the target identifier to a corresponding service intermediate station, so that the service intermediate station performs signature verification on the target identifier, and corresponding intermediate station service is returned to the gateway in response to verification passing; and the gateway provides the middle station service for the user through a service system.

Description

Technical Field

[0001] The present disclosure relates to the field of service scheduling, and in particular to a service scheduling method based on a scheduling component, a scheduling component, a device and a medium. Background Art

[0002] The gateway can be used for both wide area network interconnection and local area network interconnection. The gateway mainly includes user gateways based on open application programming interfaces, user gateways based on plug-ins or modules, and user gateways based on microservices.

[0003] Current gateways usually have basic authentication, session management and other functions, but often have the following problems: First, the technical specifications are not unified. The access protocols, request response data structures, encoding rules, error declaration and processing methods, public parameters, encryption and decryption methods of each gateway are not unified, which increases the difficulty of accessing application services. Second, the implementation methods are not unified. The implementation methods of each gateway in terms of authentication and authorization methods, session management modes, and security protection functions are not unified, which increases the difficulty of integration and maintenance costs. Summary of the invention

[0004] In view of this, the purpose of the present disclosure is to propose a service scheduling method based on a scheduling component, a scheduling component, a device and a medium to solve or partially solve the above-mentioned problems.

[0005] Based on the above purpose, the first aspect of the present disclosure provides a service scheduling method based on a scheduling component, wherein the scheduling component includes a gateway and a background management system, the gateway includes a business system and the gateway is deployed in a business middle station, and the method includes:

[0006] The backend management system receives the configuration information, authorizes all applications according to the configuration information, obtains authorization information, and sends the authorization information to the gateway;

[0007] The gateway receives the service scheduling request and determines a target application corresponding to the service scheduling request;

[0008] The gateway performs authentication processing on the target application according to the authorization information, and obtains the target identifier in the service scheduling request in response to the target application passing the authentication;

[0009] The gateway sends the target identifier to the corresponding business middle station, so that the business middle station performs signature verification on the target identifier, and returns the corresponding middle station service to the gateway in response to the verification passing;

[0010] The gateway provides the middle office service to users through the business system.

[0011] Based on the same inventive concept, the second aspect of the present disclosure proposes a scheduling component, the scheduling component includes a gateway and a background management system, the gateway includes a business system and the gateway is deployed in the business middle station, including:

[0012] An information receiving module is configured to receive configuration information from a backend management system, authorize all applications according to the configuration information, obtain authorization information, and send the authorization information to a gateway;

[0013] A request receiving module, configured to receive a service scheduling request at a gateway and determine a target application corresponding to the service scheduling request;

[0014] An authentication processing module is configured to perform authentication processing on the target application according to the authorization information, and obtain a target identifier in the service scheduling request in response to the target application being authenticated;

[0015] The service determination module is configured so that the gateway sends the target identifier to the corresponding business middle station, so that the business middle station performs signature verification on the target identifier, and returns the corresponding middle station service to the gateway in response to passing the verification;

[0016] The service providing module is configured as a gateway to provide the middle office service to users through the business system.

[0017] Based on the same inventive concept, the third aspect of the present disclosure proposes an electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable by the processor, wherein the processor implements the service scheduling method based on the scheduling component as described above when executing the computer program.

[0018] Based on the same inventive concept, the fourth aspect of the present disclosure proposes a non-transitory computer-readable storage medium, which stores computer instructions, and the computer instructions are used to enable a computer to execute the service scheduling method based on the scheduling component as described above.

[0019] Based on the same inventive concept, the fifth aspect of the present disclosure provides a vehicle, comprising the scheduling component described in the second aspect or the electronic device described in the third aspect or the storage medium described in the fourth aspect.

[0020] From the above, it can be seen that the present disclosure proposes a service scheduling method, scheduling component, device and medium based on a scheduling component. The background management system receives configuration information, authorizes all applications according to the configuration information, obtains authorization information, and sends the authorization information to the gateway to achieve smooth access to the user gateway. The gateway receives a service scheduling request and determines the target application corresponding to the service scheduling request. The gateway performs authentication processing on the target application according to the authorization information, and obtains the target identifier in the service scheduling request in response to the target application authentication passing. The gateway sends the target identifier to the corresponding business middle station so that the business middle station performs signature verification on the target identifier, and returns the corresponding middle station service to the gateway in response to the verification passing. The gateway provides the middle station service to users through the business system, and verifies it with the target identifier, thereby realizing the core functions such as authentication authorization, session management, and security protection in a unified manner, improving the security of the system, reducing the risk of external attacks, and also reducing the difficulty of integration and operation and maintenance costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the present disclosure or related technologies, the drawings required for use in the embodiments or related technical descriptions are briefly introduced below. Obviously, the drawings described below are only embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 A flowchart of a service scheduling method based on a scheduling component according to an embodiment of the present disclosure;

[0023] Figure 2 is a structural block diagram of a scheduling component of an embodiment of the present disclosure;

[0024] Figure 3 is a structural block diagram of a scheduling component according to another embodiment of the present disclosure;

[0025] Figure 4 It is a schematic diagram of the structure of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0026] In order to make the objectives, technical solutions and advantages of the present disclosure more clearly understood, the present disclosure is further described in detail below in combination with specific embodiments and with reference to the accompanying drawings.

[0027] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should be understood by people with ordinary skills in the field to which the present disclosure belongs. The "first", "second" and similar words used in the embodiments of the present disclosure do not indicate any order, quantity or importance, but are only used to distinguish different components. "Including" or "comprising" and similar words mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. "Connect" or "connected" and similar words are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. "Up", "down", "left", "right" and the like are only used to indicate relative positional relationships. When the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0028] The terms used in this disclosure are explained as follows:

[0029] API: Application Programming Interface (API) is a set of predefined functions that aims to provide applications and developers with the ability to access a set of routines based on certain software or hardware without having to access the source code or understand the details of the internal working mechanism.

[0030] AES-256: AES is the Advanced Encryption Standard, also known as Rijndael encryption in cryptography. It is a block encryption standard adopted by the U.S. federal government.

[0031] RSA: RSA algorithm is an asymmetric encryption algorithm. Unlike the symmetric encryption algorithm, the RSA algorithm has two different keys, one is the public key and the other is the private key.

[0032] ECC: Elliptic curve cryptography (ECC), an algorithm for building public key encryption, based on elliptic curve mathematics. The use of elliptic curves in cryptography was independently proposed by Neal Koblitz and Victor Miller in 1985.

[0033] The gateway can be used for both wide area network interconnection and local area network interconnection. The gateway mainly includes user gateways based on open application programming interfaces, user gateways based on plug-ins or modules, and user gateways based on microservices.

[0034] User gateway based on open API, this architecture allows third-party developers or enterprises to customize gateway functions according to their own needs through open application programming interface (API). This gateway architecture is flexible and easy to expand, but there may be security and stability issues.

[0035] Plug-in or module-based user gateway, this architecture adopts plug-in or modular design, so that the gateway can add or delete functional modules according to different applications and user needs. This architecture has good scalability and flexibility, but it needs to solve the compatibility issues between plug-ins or modules.

[0036] Microservice-based user gateway, the microservice architecture splits a large application into multiple small services, each of which runs in an independent process and communicates through the network. This architecture can improve the scalability and flexibility of the system, but it needs to solve the communication and coordination problems between microservices.

[0037] Current gateways usually have basic authentication, session management and other functions, but often have the following problems: First, the technical specifications are not unified. The access protocols, request response data structures, encoding rules, error statements and processing methods, public parameters, encryption and decryption methods of each gateway are not unified, which increases the difficulty of accessing application services. Second, the implementation methods are not unified. The implementation methods of each gateway in terms of authentication and authorization methods, session management modes, and security protection functions are not unified, which increases the difficulty of integration and maintenance costs. Third, user data is not integrated. Each business system independently builds a user gateway, and the data cannot be connected, making it impossible to analyze the usage of each business application and user data from a global level; Fourth, the monitoring and analysis functions are not perfect, and there is a lack of operational monitoring and data analysis functions for business applications.

[0038] Based on the above description, this embodiment proposes a service scheduling method based on a scheduling component, such as Figure 1 As shown, the scheduling component includes a gateway and a background management system, the gateway includes a business system and the gateway is deployed in the business middle station, and the method includes:

[0039] Step 101: the background management system receives configuration information, authorizes all applications according to the configuration information, obtains authorization information, and sends the authorization information to the gateway.

[0040] In specific implementation, the scheduling component includes a gateway and a background management system. The gateway includes a business system and is deployed in the business middle platform. The gateway includes a user gateway and a service gateway. The user gateway connects the user or browser and multiple business systems, and is used to verify the user or browser to determine the business system that the user or browser is allowed to access. The service gateway connects multiple business systems and multiple middle platform services, and is used to verify each business system, determine the target service and target interface corresponding to each business system, and allocate multiple middle platform services to each business system.

[0041] In this embodiment, the scheduling component is a unified service scheduling component, which includes a gateway and a backend management system, wherein the gateway includes a user gateway and a service gateway. For the convenience of description, the system is used to replace the scheduling component in the subsequent embodiments.

[0042] The backend management system receives configuration information, wherein the configuration information is user-defined configuration information, which includes application information that each user or browser is allowed to access. All applications are authorized according to the configuration information to obtain authorization information, and the authorization information is sent to the gateway, so that the gateway can judge the application requested by the user according to the authorization information and determine whether to allow access.

[0043] Step 102: The gateway receives a service scheduling request and determines a target application corresponding to the service scheduling request.

[0044] During specific implementation, the gateway receives a service scheduling request from a user and determines a target application corresponding to the service scheduling request, so as to subsequently determine whether the user has the authority to access the target application.

[0045] Step 103: The gateway performs authentication processing on the target application according to the authorization information, and obtains the target identifier in the service scheduling request in response to the target application being authenticated.

[0046] In specific implementation, the gateway receives the authorization information sent by the background management system, and authenticates the target application according to the authorization information, that is, verifies the user's identity. When the target application is authenticated, it means that the user has the right to access the target application, obtains the target identifier in the service scheduling request, and then authenticates the application according to the target identifier.

[0047] Step 104, the gateway sends the target identifier to the corresponding business middle station, so that the business middle station performs signature verification on the target identifier, and returns the corresponding middle station service to the gateway in response to the verification passing.

[0048] In specific implementation, application authentication is the ability of the unified service scheduling component to identify applications. Applications obtain tokens through issued keys. The process of the unified service scheduling component obtaining application information through tokens is called application authentication. Application data comes from unified permissions. For applications that exist on the digital capability opening platform but are not in the unified permissions, the digital capability opening platform synchronizes permissions and issues keys. Application authentication returns the ability of tokens through application appid and secret information. This function is integrated with unified permissions, and the scheduling component proxies this capability. In this embodiment, application authentication adopts the authentication and authorization mechanisms of OAuth 2.0 and OpenID Connect (OIDC) standards. This solution will ensure the consistency of authentication and authorization in all business systems accessed through Spring CloudGateway, simplify user management, improve security, and enhance scalability.

[0049] In this embodiment, the data signature uses the HMAC-SHA256 algorithm to generate the request signature to ensure the integrity and non-tamperability of the request data. For scenarios with higher security requirements, RSA-SHA256 is used for digital signature.

[0050] Step 105: The gateway provides the middle office service to the user through the business system.

[0051] During specific implementation, the gateway provides users with access to middle-office services and corresponding interface permissions through the business system.

[0052] The unified service scheduling component is responsible for forwarding all the service call requests of the middle office. The traffic and concurrency of each business scenario vary greatly. If all the traffic is borne by one gateway cluster, it is easy to cause mutual interference between different businesses, which is not conducive to the promotion and application of the unified service scheduling component. Tenant isolation technology is required to separate the service scheduling of different middle offices. The unified service scheduling component also provides business-related data management such as application registration, service directory, and call log, which requires data isolation. Tenant isolation in the unified service scheduling component refers to the deployment of a unified scheduling gateway with independent resources for different business middle offices, and the isolation of tenant resources from other business middle offices in terms of physical resources, so as to avoid the mutual influence of different business middle offices on unified service scheduling.

[0053] Through the above scheme, the background management system receives configuration information, authorizes all applications according to the configuration information, obtains authorization information, and sends the authorization information to the gateway to achieve smooth access to the user gateway. The gateway receives a service scheduling request and determines the target application corresponding to the service scheduling request. The gateway authenticates the target application according to the authorization information, and obtains the target identifier in the service scheduling request in response to the target application being authenticated. The gateway sends the target identifier to the corresponding business middle station so that the business middle station performs signature verification on the target identifier, and returns the corresponding middle station service to the gateway in response to the verification being passed. The gateway provides the middle station service to users through the business system and verifies it with the target identifier, thereby realizing core functions such as authentication authorization, session management, and security protection in a unified manner, improving the security of the system, reducing the risk of external attacks, and also reducing integration difficulty and operation and maintenance costs.

[0054] In this embodiment, the data is encrypted for transmission, and the specific encryption and decryption method is not limited. The encryption method can use symmetric encryption or asymmetric encryption, wherein the symmetric encryption uses the AES-256 standard for symmetric encryption to ensure the security of the data. Asymmetric encryption uses RSA or ECC for asymmetric encryption.

[0055] In some embodiments, taking the authorization code mode (Authorization Code Grant) as an example, the specific process of authorization in step 104 includes:

[0056] Step 1041, user authentication, the user accesses the business application (Client) through the browser, and after Spring CloudGateway receives the request, it redirects the user to the login page of the authorization server.

[0057] Step 1042: The user enters credentials on the authorization server for identity authentication (such as user name, password, secondary authentication, etc.), and the authorization server generates an authorization code after successfully verifying the user's identity.

[0058] Step 1043, obtain the authorization code, and the authorization server transmits the authorization code back to the client (through Spring Cloud Gateway) through redirection.

[0059] Step 1044, requesting an access token, Spring Cloud Gateway uses the obtained authorization code to send a request to the authorization server to exchange the access token and ID token.

[0060] Step 1045: Access the resource server. Spring Cloud Gateway holds the access token and initiates an API request to the resource server on behalf of the user. The resource server verifies the legitimacy and permissions of the token and allows or denies the request.

[0061] Step 1046, refresh the token. When the access token expires, the client can use the refresh token to request a new access token from the authorization server without the user having to log in again.

[0062] Among them, Authorization Server is responsible for processing user authentication requests and issuing access tokens, refresh tokens and identity tokens.

[0063] Resource Server: Stores and protects user resources and decides whether to grant access rights to clients through access tokens. The API interface of the business system usually serves as a resource server.

[0064] Client: Requests a token from the authorization server on behalf of the user and uses the token to access the resource server. The application that passes through Spring Cloud Gateway is the client.

[0065] Resource Owner: Usually refers to the user himself, who authorizes the client to access its protected resources.

[0066] In some embodiments, the application authentication in step 104 adopts the authentication and authorization mechanism of OAuth 2.0 and OpenID Connect (OIDC) standards. On the basis of OAuth 2.0, OpenID Connect provides the following functions:

[0067] ID Token: ID Token contains the user's identity information, such as user ID, login time, etc. The client can obtain and verify the user's identity by decoding the ID Token.

[0068] UserInfo Endpoint: Provides an API endpoint that allows clients to further query user details (such as email address, name, etc.), enhancing the user experience.

[0069] In some embodiments, when the application authentication is implemented in step 104, the authentication server is configured using an existing authentication server (such as Keycloak, Okta, or a self-built OAuth 2.0 server) to implement client registration, identity authentication, and token signing and encryption. The client registration registers an OAuth client for each business system, and configures information such as the authorization type and redirection URI. Identity authentication configures multi-factor authentication (MFA) and other security measures to ensure the security of the user login process. Token signing and encryption uses RSA or ECDSA algorithms to sign and encrypt tokens to ensure the integrity and tamper-proofness of tokens.

[0070] At the same time, when implementing the application authentication in step 104, Spring Cloud Gateway integration is adopted. Specifically, the integration with the OAuth 2.0 server is configured in Spring Cloud Gateway, such as using Filter configuration, using the SpringSecurity OAuth2 module, configuring the OAuth 2.0 filter chain, intercepting all protected API requests, and verifying the validity of the token. Configure the Token Relay mechanism to forward the token received from the client to the resource server to ensure the continuity of the user session. Configure the exception handling mechanism. When the token verification fails or expires, the gateway should provide an appropriate error response and guide the user to re-authenticate.

[0071] In some embodiments, in order to ensure the consistency and security of user session data during cross-system and cross-node operations, a centralized session management solution is adopted to uniformly manage session data through a Redis cluster. Redis is a high-performance in-memory key-value database with low latency and high throughput, which is suitable for the storage and management of session data. In this embodiment, the Redis cluster mode is adopted to ensure the high availability and data consistency of session data among multiple nodes, specifically including:

[0072] Store user session data in Redis. Each session data uses a unique Session ID as the key, and related session information (such as user identity, permissions, login time, etc.) is stored as the value.

[0073] The nodes in the Redis cluster ensure the synchronization and consistency of session data through automatic data sharding and replication mechanisms. Even if a node fails, the system can still read session data from other nodes.

[0074] After the user logs in, the system creates a new session in Redis to store relevant user information and status. Each time a user requests, the session information is read from Redis through Spring Cloud Gateway or microservices to verify the validity of the session. After the user operates, the session information (such as the last activity time, status, etc.) will be updated and synchronized to Redis. The system regularly checks the session data in Redis, automatically cleans up expired sessions, and releases memory resources.

[0075] At the same time, to ensure the security of session data, the built-in SSL / TLS encryption mechanism of Redis ensures the security of session data during transmission to prevent data from being stolen or tampered with. At the same time, access rights to the Redis cluster are restricted, allowing only authenticated applications and services to perform read and write operations to prevent unauthorized access.

[0076] In this embodiment, in order to ensure the stability of system performance, the cache function of Redis is used to cache frequently accessed session data into the memory, reduce the delay of data reading and writing, and improve the system response speed. For larger session data, the built-in compression function of Redis can be used to reduce memory usage and improve data transmission efficiency.

[0077] In some embodiments, in order to ensure the stability of the system, a security protection architecture is adopted to specifically implement anti-replay attack, XSS security filtering and SQL injection prevention.

[0078] Among them, the anti-replay attack adopts the timestamp and Nonce mechanism, adding the timestamp and random number (Nonce) parameters to each request. When verifying the request, the server checks whether the timestamp is within the allowed time range and whether the Nonce has been used, thereby preventing replay attacks. At the same time, the request parameters are digitally signed, and the server verifies the correctness of the signature to ensure that the request data has not been tampered with.

[0079] XSS security filtering removes or escapes characters that may contain malicious scripts, such as `<`, `>`, `&`, `"`, etc., by strictly validating and filtering all user input. It also performs HTML encoding on dynamic content output to the web page to prevent malicious scripts from being injected and executed in the user's browser.

[0080] SQL injection prevention uses prepared statements. Prepared statements are used in all SQL queries to avoid SQL injection attacks. The data entered by the user is verified to ensure that it conforms to the expected format to avoid injecting malicious code into SQL queries.

[0081] Before the gateway determines the target application corresponding to the service scheduling request, the application needs to access the gateway in advance. Therefore, in some embodiments, before step 102, the following is also included:

[0082] Step 1021: For each application among all the applications, obtain a first protocol corresponding to the application.

[0083] Step 1022: In response to the first protocol being a preset protocol, accessing the application to the gateway via the first protocol.

[0084] or,

[0085] Step 1023: In response to the first protocol not being a preset protocol, convert the first protocol into a preset protocol, and connect the application to the gateway through the preset protocol.

[0086] In a specific implementation, for each application among all the applications, a first protocol corresponding to the application is obtained, and it is determined whether the first protocol is a preset protocol, wherein the preset protocol is a protocol preset by a user.

[0087] If the first protocol is a preset protocol, the application can be directly connected to the gateway using the first protocol. If the first protocol is not a preset protocol, the first protocol needs to be converted to the preset protocol, and the application is connected to the gateway using the preset protocol.

[0088] In this embodiment, the preset protocol can use a standard RESTful API for inter-system communication, using HTTP / HTTPS as the transmission protocol. At the same time, for scenarios requiring efficient binary communication, the gRPC protocol can be used. gRPC can achieve low-latency, high-performance communication, and is particularly suitable for internal communication between microservices. For scenarios requiring real-time two-way communication, the WebSocket protocol is used to ensure stability under high concurrency. In this embodiment, in order to ensure the security of application access, all API communications must use the HTTPS protocol.

[0089] In this embodiment, the data structure of the request and response data is limited, and the standard request and response data format uses JSON (JavaScript Object Notation). Protobuf (Protocol Buffers) is used for efficient binary transmission when necessary. Notifications use lowercase camelCase to ensure that field names are consistent and readable.

[0090] In some embodiments, after step 105, the method further includes:

[0091] Step 10A, the gateway monitors the operation data of the target application;

[0092] Step 10B: In response to detecting that the operating data is abnormal, the gateway outputs a prompt message to prompt that the target application has an operating abnormality.

[0093] In specific implementation, the gateway can monitor the operating data of the target application, that is, monitor and warn the performance of the application. When abnormalities are detected in the operating data, prompt information is output to prompt that the target application has abnormal operation problems.

[0094] In this embodiment, Prometheus or Grafana is used to monitor API traffic, response time, error rate and other indicators in real time. When the monitoring indicators exceed the set threshold, an early warning is automatically triggered and the relevant maintenance personnel are notified. The notification method can be email, SMS, Slack, etc.

[0095] In this embodiment, the operation data can be default data or custom data, where the default data includes the number of interface calls, total number of requests, QPS (query rate per second), number of concurrencies, average response time, CPU usage, memory usage, disk IO, network bandwidth, etc. Custom data includes the response time threshold of a specific interface, the change in the number of requests within a specific time period, etc.

[0096] In this embodiment, logs can be stored in structured formats such as JSON and Protobuf to facilitate subsequent query and analysis. Automatic classification and indexing of logs are supported to improve query efficiency. Different log levels (such as DEBUG, INFO, WARN, ERROR) can be set according to the importance of information to reduce unnecessary log noise. Logs can be automatically analyzed regularly (such as daily and weekly) to identify potential problems and performance bottlenecks. Analysis reports are generated to provide decision support for operation and maintenance personnel.

[0097] Through the above solution, operational monitoring and data analysis are realized: the user gateway can monitor and analyze user access behavior and application performance. Real-time monitoring and early warning of application performance are carried out to timely discover and solve potential performance problems and ensure the stable operation of the application.

[0098] In some embodiments, the method further comprises:

[0099] Step A: The gateway obtains all service scheduling requests and determines the first application corresponding to each service scheduling request in all service scheduling requests.

[0100] Step B: The gateway determines the user data corresponding to each first application, divides the first applications according to the user data, and divides the first applications with the same user data into the same user group to obtain at least one user group.

[0101] Step C: The gateway stores all user groups.

[0102] In specific implementation, the gateway obtains all service scheduling requests and determines the first application corresponding to each service scheduling request in all service scheduling requests. The gateway determines the user data corresponding to each first application, and the user data is the user identity information. The first applications are divided according to the user data, and the first applications with the same user data are divided into the same user group to obtain at least one user group, and the gateway stores all user groups.

[0103] Specifically, after the data center is connected to the scheduling component, the APIs of each business system are connected to the unified service scheduling component through the API gateway. The scheduling component is responsible for the centralized management of these APIs, including registration, publishing, routing, current limiting, and fuse functions. Through this component, user data of each system can be collected and stored according to unified standards to ensure data consistency and reliability.

[0104] At the same time, the data center sends data requests to the headquarters and provincial data centers respectively through the two-level routing mechanism of the scheduling component, and then aggregates the results, which improves the timeliness of data processing and reduces data redundancy and storage pressure.

[0105] APIs are standardized through unified service scheduling components to ensure that APIs of all business systems follow the same specifications. This includes the governance of existing APIs and the centralized management of new APIs to achieve API standardization and unified management. Through standardization, the inconsistency of data interfaces is reduced and the ability to share and reuse data is improved.

[0106] Through the above solution, user data integration is achieved: the user gateway can integrate and consolidate user data scattered in various applications, manage and utilize data resources more efficiently, and maximize the value of data.

[0107] In some embodiments, the method further comprises:

[0108] Step 10a: In response to a gateway failure, the gateway performs a fuse process on all services, and sets the status of all services to a fuse state.

[0109] Step 10b: The gateway checks the blown fuse status, wherein the blown fuse status includes service quality information within a preset time period.

[0110] During the specific implementation, the unified service scheduling component management and control tool realizes the threshold configuration of the service, supports dynamic activation and dynamic adjustment of thresholds, supports the configuration function of distinguishing between core and non-core applications and services, limits the flow of services on demand, and prioritizes the high availability of core functions.

[0111] The unified service scheduling component uses Alibaba's open source Sentinel component as a current limiting and circuit-breaking solution. By using Sentinel global current limiting, priority-based current limiting can be implemented. For example, when the overall traffic volume is large, non-core services and non-core applications are given priority for current limiting.

[0112] In some embodiments, step 10a specifically includes:

[0113] Step 10a1: for each service among all services, the gateway determines a registration method for the service.

[0114] Step 10a2: In response to the registration mode being automatic registration, the gateway obtains preset microservice information and performs fuse processing on the service according to the preset microservice information.

[0115] or,

[0116] Step 10a3, in response to the registration mode being manual registration, the gateway obtains service information of the service, and performs fuse processing on the service according to the service information.

[0117] During specific implementation, for each service among all services, the gateway determines a registration method for the service, where the registration methods include automatic registration and manual registration.

[0118] When the registration method is automatic registration, the gateway obtains the preset microservice information and performs fuse processing on the service according to the preset microservice information. When the registration method is manual registration, the gateway obtains the service information of the service and performs fuse processing on the service according to the service information. The service information is the address, port and context.

[0119] That is, the service circuit breaker rules are fused according to microservices. For manually registered services, the rules are fused according to the address + port + context method, and the circuit breaker group can be configured.

[0120] The service circuit breaker console supports viewing the current circuit breaker status of all services, for example, the latest 5-minute service quality information such as service response time and service success rate. Manual circuit breaker can be performed based on these indicators.

[0121] In some embodiments, the method further comprises:

[0122] Step 10A: The gateway performs flow control on the service scheduling request according to the service needs of the business middle station.

[0123] Step 10B: In response to the service scheduling request reaching a preset flow limiting condition, the gateway outputs a result of service scheduling failure through the business system.

[0124] During the specific implementation, the business system is subject to flow control according to the needs of the business middle office service. When the flow limit conditions are met, a quick failure return is performed. The flow limit rules must support flow control according to the interface and microservice dimensions.

[0125] It should be noted that the method of the embodiment of the present disclosure can be performed by a single device, such as a computer or a server. The method of the present embodiment can also be applied in a distributed scenario and completed by multiple devices cooperating with each other. In the case of such a distributed scenario, one of the multiple devices can only perform one or more steps in the method of the embodiment of the present disclosure, and the multiple devices will interact with each other to complete the described method.

[0126] It should be noted that the above describes some embodiments of the present disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the above embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0127] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure further provides a scheduling component.

[0128] refer to Figure 2 , Figure 2 The scheduling component of the embodiment includes a gateway and a background management system, the gateway includes a business system and the gateway is deployed in the business middle station, including:

[0129] The backend management system is configured to receive the configuration information, authorize all applications according to the configuration information, obtain authorization information, and send the authorization information to the gateway;

[0130] The gateway is configured to receive a service scheduling request, determine a target application corresponding to the service scheduling request; perform authentication processing on the target application according to the authorization information, obtain a target identifier in the service scheduling request in response to the target application being authenticated, and send the target identifier to a corresponding business middle station; and provide the middle station service returned by the business middle station to the user through the business system;

[0131] The business middle station is configured to perform signature verification on the target identifier, and in response to the verification passing, return the corresponding middle station service to the gateway.

[0132] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure further provides a scheduling component.

[0133] refer to Figure 3 , Figure 3 The scheduling component of the embodiment includes a gateway and a background management system, the gateway includes a business system and the gateway is deployed in the business middle station, including:

[0134] The information receiving module 201 is configured to receive configuration information in the background management system, authorize all applications according to the configuration information, obtain authorization information, and send the authorization information to the gateway;

[0135] The request receiving module 202 is configured to receive the service scheduling request at the gateway and determine the target application corresponding to the service scheduling request;

[0136] The authentication processing module 203 is configured as a gateway to perform authentication processing on the target application according to the authorization information, and in response to the target application being authenticated, obtain the target identifier in the service scheduling request;

[0137] The service determination module 204 is configured so that the gateway sends the target identifier to the corresponding service middle station, so that the service middle station performs signature verification on the target identifier, and returns the corresponding middle station service to the gateway in response to the verification passing;

[0138] The service providing module 205 is configured as a gateway to provide the middle office service to the user through the business system.

[0139] In some embodiments, the scheduling component further includes a protocol determination module, and the protocol determination module is specifically configured to:

[0140] For each application among all the applications, obtaining a first protocol corresponding to the application;

[0141] In response to the first protocol being a preset protocol, accessing the application to the gateway through the first protocol; or,

[0142] In response to the first protocol not being a preset protocol, the first protocol is converted into a preset protocol, and the application is connected to the gateway through the preset protocol.

[0143] In some embodiments, the scheduling component further includes an abnormality monitoring module, and the abnormality monitoring module is specifically configured to:

[0144] The gateway monitors the operating data of the target application;

[0145] In response to detecting that the operating data is abnormal, the gateway outputs a prompt message to prompt that the target application has an operating abnormality.

[0146] In some embodiments, the scheduling component further includes a storage module, and the storage module is specifically configured to:

[0147] The gateway obtains all service scheduling requests and determines a first application corresponding to each service scheduling request in all service scheduling requests;

[0148] The gateway determines user data corresponding to each first application, divides the first applications according to the user data, and divides the first applications with the same user data into the same user group to obtain at least one user group;

[0149] The gateway stores all user groups.

[0150] In some embodiments, the scheduling component further includes a fuse processing module, and the fuse processing module specifically includes:

[0151] A fuse unit is configured to respond to a gateway failure, and the gateway performs fuse processing on all services and sets the status of all services to a fuse state;

[0152] The monitoring unit is configured to check the fuse status as a gateway, wherein the fuse status includes service quality information within a preset time period.

[0153] In some embodiments, the fuse unit is specifically configured as follows:

[0154] For each of all services, the gateway determines how the service is registered;

[0155] In response to the registration mode being automatic registration, the gateway obtains preset microservice information, and performs fuse processing on the service according to the preset microservice information; or,

[0156] In response to the registration method being manual registration, the gateway obtains service information of the service and performs fuse processing on the service according to the service information.

[0157] In some embodiments, the scheduling component further includes a current limiting control module, and the current limiting control module is specifically configured to:

[0158] The gateway performs flow control on the service scheduling request according to the service needs of the business middle station;

[0159] In response to the service scheduling request reaching a preset flow limiting condition, the gateway outputs a result of service scheduling failure through the business system.

[0160] Based on the same inventive concept, another embodiment of the present disclosure proposes a unified service scheduling component, which includes a user authentication and authorization module, a distributed session management module, an application and user data analysis module, a security management module, a service scheduling management module, and an operation monitoring management module. The unified service scheduling component covers the core capabilities of the user gateway, supports the user gateway to give full play to its value, and provides a unified technical guarantee for improving the stability, maintainability and scalability of the business system and enhancing the security of the system.

[0161] The user authentication and authorization module integrates ISC, third-party authentication and user-defined authentication to verify the user's identity and determine their access rights, which can effectively prevent malicious requests, ensure the security of user data, maintain the stable operation of applications and effectively protect the system from potential threats. The user authentication and authorization module specifically includes a third-party user authentication management unit, a customized user authentication management unit and a multiple identity authentication unit.

[0162] The third-party user authentication management unit is configured to support integration of the ISC unified authority management system to implement user authentication management capabilities, and access to third-party authentication is achieved through configuration.

[0163] The custom user authentication management unit is configured so that applications accessing the user gateway can implement custom user authentication in accordance with the standard user authentication interface provided by the user gateway, and supports dynamic scripts and jar packages.

[0164] The multi-authentication unit is specifically configured to integrate ISC and configure verification policies, so that the user gateway can provide other verification methods in addition to traditional username and password verification, such as: mobile phone verification code, fingerprint recognition, facial recognition, etc. The application of these methods can significantly improve the security of the account.

[0165] The distributed session management module can realize the sharing and management of user session information across service nodes, ensure that users can seamlessly switch between different service nodes, and improve the system availability and user experience. The distributed session management module includes a session configuration and management unit, a user behavior tracking unit, and a session control management unit.

[0166] The session configuration and management unit is configured to provide flexible session management configuration, allowing the administrator to adjust session parameters such as timeout period etc. as needed.

[0167] The user behavior tracking unit is configured to allow the user to control his own session, for example: session logout, session lock, etc. An open interface may be provided for the application to perform session control.

[0168] The session control management unit is configured to track the user's behavior in the session and collect user access information, including: accessed applications, application services and middle-end service information.

[0169] The application and user data analysis module helps developers and operation and maintenance personnel gain an in-depth understanding of user characteristics, user needs, business application usage, application service call status and performance, and provides support for further optimizing business system functions and performance, improving user experience, and efficiently carrying out application operations. The application and user data analysis module includes a user feedback analysis unit, a user portrait construction unit, an application service call analysis unit, and an application service commonality analysis unit.

[0170] The user feedback analysis unit is configured to collect and analyze user feedback information for improving and optimizing application services and middle platform services.

[0171] The user portrait construction unit is configured to construct a user portrait based on user behavior data, track the user's operation path within the application, and thus understand the user's usage habits and behavior patterns.

[0172] The application service call analysis unit is configured to obtain indicators such as response time, throughput, error rate, etc. of each application service through analysis of log information, so as to help find performance bottlenecks and optimization points of the application service.

[0173] The application service commonality analysis unit is configured to perform application service commonality capability analysis based on the access frequency of the application service and the versatility of the service (multiple scenarios being called).

[0174] The security management module effectively prevents malicious requests and attacks, ensuring user data security and stable application operation. The security management module includes a security protection management unit, a security integration management unit, a data privacy protection unit and a session security management unit.

[0175] The security protection management unit is configured to intercept request types, sensitive words, blacklist, SQL injection prevention, XSS security filtering, request replay prevention, and link encryption.

[0176] The security integrated management unit is configured to access a third-party risk control system and a third-party security protection system.

[0177] The data privacy protection unit is configured to process sensitive information when sharing or displaying data to prevent leakage of personal privacy, ensure compliance with data privacy regulations, and protect user personal information.

[0178] The session security management unit is configured as a security mechanism to ensure the security, integrity and privacy of session information during network communication, which is generally achieved by encrypting the session.

[0179] The service scheduling management module optimizes the scheduling strategy according to factors such as service load and request type, realizes efficient request routing and forwarding, ensures reliable and stable operation of the service, and improves the overall system performance and user experience. The service scheduling management module includes a service registration unit, a service routing unit, a service fuse unit and a service current limiting unit.

[0180] The service registration unit is configured to realize dynamic discovery and connection of API services, ensure that requests can be accurately and efficiently routed to corresponding service instances, and realize load balancing and fault tolerance of services.

[0181] The service routing unit is configured to implement intelligent distribution of requests, ensuring that each request can be accurately and efficiently routed to the corresponding backend service, thereby ensuring the stability and performance of the system.

[0182] The service fuse unit is configured to quickly cut off requests when a backend service fails, prevent the failure from spreading, and ensure the overall stability and availability of the system.

[0183] The service flow limiting unit is configured to protect the system from being overwhelmed by a large number of requests. When the system resources are insufficient to cope with a large number of requests, the system access flow is limited to ensure that the limited resources can provide normal services.

[0184] The operation monitoring and management module helps developers and operation and maintenance personnel understand the performance of application services, identify potential problems and optimize them by real-time or regular monitoring and analysis of the traffic of application service requests and responses. Its main indicators include: number of interface calls, total number of requests, QPS, number of concurrent requests, average response time, etc. The operation monitoring and management module includes a session monitoring and analysis unit, a session audit unit, an application service health monitoring unit, and a log storage unit.

[0185] The operation monitoring management module stores an authentication log for recording authentication events for use in problem troubleshooting and security auditing.

[0186] The session monitoring and analysis unit is configured to monitor session activities, store and analyze session data, so as to timely discover abnormal behaviors or potential security threats.

[0187] The session audit unit is configured to record and audit session activities for compliance checking and post-analysis.

[0188] The application service health monitoring unit is configured to track key performance indicators, monitor application service resource usage, monitor external services that the application service depends on, and can set real-time alarms to immediately notify operators when application health changes.

[0189] The log storage unit is configured to record call logs, set different log levels according to the importance of information, store logs in a structured manner, and regularly analyze logs to identify potential problems and performance bottlenecks.

[0190] The user gateway in the unified service scheduling component inherits some capabilities of the service gateway, and the routing rules of the user gateway are similar to those of the service gateway, which are divided into public routing rules and custom routing rules.

[0191] The public routing rule is the default rule mode adopted by the system, which adopts the mode of using the microservice code in the first segment of the path context, followed by the microservice interface path. For example, http: / / gw.sgcc.com.cn / yx-customer-service / customer / info interface, where yx-customer-service is the microservice code, and the subsequent customer / info is the actual path of the interface in the code.

[0192] Custom rules are used to meet the business system's needs for URL personalization, and the rewriting path mode is used to meet the business system's requirements for paths. For example, the context of the power grid resource center is / WMCenter, but according to the path rules of the microservice context, it is impossible for all power grid resource center services to be implemented in the same microservice, so it is necessary to support URL rewriting. Rewriting rules support URL and header information, and can be matched arbitrarily. Considering the matching performance issue, in principle, the number of routing rules for each gateway tenant should not exceed 2,000.

[0193] The unified service scheduling component can also realize service log recording, which is the basis for the unified service scheduling component to provide operation analysis data later. The user gateway should record the log in an asynchronous manner, and the performance of the service agent will not be affected by the log recording. By writing the log to a file, the State Grid Cloud Huawei component and the State Grid Cloud Alibaba component are used to collect the data of the log file to the corresponding system for analysis.

[0194] State Grid Cloud Huawei Edition: The log management component of State Grid Cloud Huawei Edition is LTS (Log Tank Service). It supports the configuration of log collection paths, realizes the collection and storage of access logs, and supports open log search through API interfaces. LTS collects log data through ICAgent.

[0195] After the log data of the host and cloud service is reported to the Cloud Log Service, it can be stored for 30 days. For log data that needs to be stored for a long time, the Cloud Log Service provides a dump function that can dump the logs to the Object Storage Service (OBS) or Data Access Service (DIS) for long-term storage.

[0196] The log search function can be used to search for the required logs in massive logs. It supports query and analysis of original logs, and can also perform SQL query and analysis on structured logs. By configuring word segmentation, the log content can be segmented into multiple words according to the word segmentation symbol, and the segmented words can be used for search when searching logs.

[0197] State Grid Cloud Alibaba Edition: Asynchronous log collection is performed through the Tlog component, and the Jstorm component cleans and processes the collected log data, puts the statistical data into the storage data, and puts the detailed data into ES for building monitoring links and detailed queries.

[0198] The unified service scheduling component can also implement service fusing to protect the gateway from rapid failure return when a backend service of the gateway proxy fails, reducing resource calls, and at the same time protecting the failed service from being overwhelmed by traffic when it is restarted to a certain extent.

[0199] Service Fuse Console: supports viewing the current fuse status of all services, the latest 5-minute service quality information such as service response time and service success rate, and manual fuses can be performed based on these indicators.

[0200] Service circuit breaker rules are fused according to microservices. For manually registered services, the rules are fused according to the address + port + context method, and the circuit breaker group can be configured.

[0201] For user gateways, the unified service scheduling component provides distributed unified session capabilities. Through gateway requests, user authentication information is carried and forwarded to the business system, which facilitates session-free processing of business system microservices and reduces the impact of expansion and contraction on users.

[0202] A whitelist is set for the user gateway's request proxy, and forwarding access is supported for the whitelisted microservices. For microservices that provide middleware interfaces, user gateway forwarding is not performed, and only forwarding through the service gateway is supported. The most important purpose of this capability is to prevent services from being called from the user gateway. Through the distributed session capability, all user gateway requests are limited to requests from the user's browser. Both CAS and JWT authentication methods must be supported.

[0203] In PMS3.0 and Marketing 2.0 user gateways, security testing requirements such as anti-replay, encryption and decryption are implemented. These functions are necessary public implementations of user gateways. In addition, the key and switch of the algorithm need to be switched on and off according to the microservice context to be compatible with different business systems. Encryption and decryption use the national secret algorithm, SM2 is used for the transmission of keys and passwords, SM3 is used for the signature verification of passwords and submitted data, and SM4 is used for symmetric encryption to encrypt the request body.

[0204] In view of the current security requirements, the user gateway needs to support the import of SSL certificates and enable HTTPS to encrypt traffic to improve the security of the business system.

[0205] Security control is performed on HTTP request reference pages to prevent them from being used by hotlinks. iframe hijacking protection: prevent business system pages from being hijacked and inserted into other business systems, and protect the uniqueness of the access address. XSS script attack: security protection is performed on cross-site scripting and other attack methods to prevent XSS attacks.

[0206] For the convenience of description, the above device is described by dividing it into various modules according to its functions. Of course, when implementing the present disclosure, the functions of each module can be implemented in the same or multiple software and / or hardware.

[0207] The device of the above embodiment is used to implement the corresponding service scheduling method based on the scheduling component in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0208] Based on the same inventive concept, corresponding to any of the above-mentioned embodiments and methods, the present disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the service scheduling method based on the scheduling component described in any of the above embodiments is implemented.

[0209] Figure 4 A more specific schematic diagram of the hardware structure of an electronic device provided in this embodiment is shown, and the device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 are connected to each other through the bus 1050 in the device.

[0210] The processor 1010 can be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0211] The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 may store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program codes are stored in the memory 1020 and are called and executed by the processor 1010.

[0212] The input / output interface 1030 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.

[0213] The communication interface 1040 is used to connect a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).

[0214] The bus 1050 includes a path that transmits information between the various components of the device (eg, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

[0215] It should be noted that, although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040 and the bus 1050, in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figure.

[0216] The electronic device of the above embodiment is used to implement the corresponding service scheduling method based on the scheduling component in any of the above embodiments, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0217] Based on the same inventive concept, corresponding to any of the above-mentioned embodiment methods, the present disclosure also provides a non-transitory computer-readable storage medium, wherein the non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to enable the computer to execute the service scheduling method based on the scheduling component as described in any of the above embodiments.

[0218] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.

[0219] The computer instructions stored in the storage medium of the above embodiment are used to enable the computer to execute the service scheduling method based on the scheduling component as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0220] It is understandable that before using the technical solutions of each embodiment of the present disclosure, the type, scope of use, usage scenarios, etc. of the personal information involved will be informed to the user in an appropriate manner, and the user's authorization will be obtained.

[0221] For example, in response to receiving an active request from a user, a prompt message is sent to the user to clearly remind the user that the operation requested to be performed will require obtaining and using the user's personal information. Thus, the user can independently choose whether to provide personal information to software or hardware such as an electronic device, application, server, or storage medium that performs the operation of the technical solution of the present disclosure according to the prompt message.

[0222] As an optional but non-limiting implementation, in response to receiving the user's active request, the prompt information may be sent to the user in the form of a pop-up window, in which the prompt information may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0223] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0224] Those skilled in the art should understand that the discussion of any of the above embodiments is merely illustrative and is not intended to imply that the scope of the present disclosure is limited to these examples. Based on the concept of the present disclosure, the technical features in the above embodiments or different embodiments may be combined, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the present disclosure as described above, which are not provided in detail for the sake of simplicity.

[0225] In addition, to simplify the description and discussion, and in order not to make the embodiments of the present disclosure difficult to understand, the known power / ground connections to the integrated circuit (IC) chips and other components may or may not be shown in the provided figures. In addition, the device can be shown in the form of a block diagram to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that the details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure will be implemented (that is, these details should be fully within the scope of understanding of those skilled in the art). Where specific details (e.g., circuits) are set forth to describe exemplary embodiments of the present disclosure, it is apparent to those skilled in the art that the embodiments of the present disclosure can be implemented without these specific details or with changes in these specific details. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0226] Although the present disclosure has been described in conjunction with specific embodiments of the present disclosure, many replacements, modifications and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.

[0227] The embodiments of the present disclosure are intended to cover all such substitutions, modifications and variations that fall within the broad scope of the present application. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present disclosure should be included in the protection scope of the present disclosure.

Claims

1. A service scheduling method based on a scheduling component, characterized in that: The scheduling component includes a gateway and a background management system. The gateway includes a business system and is deployed in the business middle station, including: The backend management system receives the configuration information, authorizes all applications according to the configuration information, obtains authorization information, and sends the authorization information to the gateway; The gateway receives the service scheduling request and determines a target application corresponding to the service scheduling request; The gateway performs authentication processing on the target application according to the authorization information, and obtains the target identifier in the service scheduling request in response to the target application passing the authentication; The gateway sends the target identifier to the corresponding business middle station, so that the business middle station performs signature verification on the target identifier, and returns the corresponding middle station service to the gateway in response to the verification passing; The gateway provides the middle office service to users through the business system.

2. The method according to claim 1, characterized in that Before the gateway receives the service dispatch request, it also includes: For each application among all the applications, obtaining a first protocol corresponding to the application; In response to the first protocol being a preset protocol, accessing the application to the gateway through the first protocol; or, In response to the first protocol not being a preset protocol, the first protocol is converted into a preset protocol, and the application is connected to the gateway through the preset protocol.

3. The method according to claim 1, characterized in that After the gateway provides the middle platform service to the user through the business system, it also includes: The gateway monitors the operating data of the target application; In response to detecting that the operating data is abnormal, the gateway outputs a prompt message to prompt that the target application has an operating abnormality.

4. The method according to claim 1, characterized in that: Also includes: The gateway obtains all service scheduling requests and determines a first application corresponding to each service scheduling request in all service scheduling requests; The gateway determines user data corresponding to each first application, divides the first applications according to the user data, and divides the first applications with the same user data into the same user group to obtain at least one user group; The gateway stores all user groups.

5. The method according to claim 1, characterized in that Also includes: In response to a gateway failure, the gateway performs a fuse process on all services, setting the status of all services to the fuse state; The gateway checks the blown fuse status, wherein the blown fuse status includes service quality information within a preset time period.

6. The method according to claim 5, characterized in that The gateway performs fuse processing on all services, including: For each of all services, the gateway determines how the service is registered; In response to the registration mode being automatic registration, the gateway obtains preset microservice information, and performs fuse processing on the service according to the preset microservice information; or, In response to the registration method being manual registration, the gateway obtains service information of the service and performs fuse processing on the service according to the service information.

7. The method according to claim 1, characterized in that Also includes: The gateway performs flow control on the service scheduling request according to the service needs of the business middle station; In response to the service scheduling request reaching a preset flow limiting condition, the gateway outputs a result of service scheduling failure through the business system.

8. A scheduling component, characterized in that: The scheduling component includes a gateway and a background management system. The gateway includes a business system and is deployed in the business middle station, including: The backend management system is configured to receive the configuration information, authorize all applications according to the configuration information, obtain authorization information, and send the authorization information to the gateway; The gateway is configured to receive a service scheduling request, determine a target application corresponding to the service scheduling request; perform authentication processing on the target application according to the authorization information, obtain a target identifier in the service scheduling request in response to the target application being authenticated, and send the target identifier to a corresponding business middle station; and provide the middle station service returned by the business middle station to the user through the business system; The business middle station is configured to perform signature verification on the target identifier, and in response to the verification passing, return the corresponding middle station service to the gateway.

9. An electronic device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the method according to any one of claims 1 to 7 is implemented.

10. A non-transitory computer-readable storage medium, characterized in that: The non-transitory computer-readable storage medium stores computer instructions, and the computer instructions are used to cause a computer to execute the method according to any one of claims 1 to 7.

Images