Business request processing method and device, electronic equipment and storage medium

Abstract

Embodiments of the present application disclose a service request processing method and device, electronic equipment and storage medium, and relate to the technical field of computers, which comprises the following steps: receiving a request identifier included in a service sub-request; determining the processing level of the service sub-request according to the request identifier; responding to the service sub-request when the processing level is a preset level; sending the service sub-request to a cloud server when the processing level is not the preset level, so that the cloud server responds to the service sub-request; and completing the processing of the service request when all service sub-requests generated by the service request are responded to. The scheme provided in the embodiments can decouple multiple service sub-requests generated by a service request by determining the processing level of the service sub-request, thereby improving the processing speed of the service sub-request, reducing the data processing pressure of the cloud server, improving the processing efficiency of the service request, and improving the user experience.

Description

Technical Field

[0001] The embodiments of the present invention relate to computer technology, and more particularly to a business request processing method, apparatus, electronic device, and storage medium. Background Technology

[0002] In various application areas (such as e-commerce, banking, or healthcare), it is necessary to process a large number of business requests sent by user devices in a short period of time. To improve user experience, how to respond quickly to a large number of business requests is a key issue that needs to be addressed.

[0003] In existing solutions, all request data generated by business requests is typically aggregated and processed in the cloud, with the response based on the processing results. However, when traffic is high, sending all request data to the cloud can lead to data accumulation on the cloud server, resulting in slow processing speeds. Furthermore, the long data transmission links during data transfer make response time susceptible to factors such as bandwidth and network latency, resulting in a poor user experience. Summary of the Invention

[0004] This invention provides a service request processing method, apparatus, electronic device, and storage medium, which can improve existing solutions for processing service requests.

[0005] In a first aspect, embodiments of the present invention provide a service request processing method, including:

[0006] The service sub-request includes a request identifier, which is generated according to the timing of processing service requests;

[0007] The processing level of the business sub-request is determined based on the request identifier; wherein, when the processing level is a preset level, the business sub-request is responded to; when the processing level is not a preset level, the business sub-request is sent to the cloud server so that the cloud server responds to the business sub-request.

[0008] The processing of the business request is completed when all business sub-requests generated by the business request have been responded to.

[0009] Secondly, embodiments of the present invention provide a service request processing apparatus, the apparatus comprising:

[0010] The request receiving module is used to receive the request identifier included in the business sub-request, wherein the business sub-request is generated according to the timing of processing business requests;

[0011] The level determination module is used to determine the processing level of the business sub-request based on the request identifier; wherein, when the processing level is a preset level, the business sub-request is responded to; when the processing level is not a preset level, the business sub-request is sent to the cloud server so that the cloud server responds to the business sub-request.

[0012] The request-response module is used to complete the processing of the business request when all business sub-requests generated by the business request have been responded to.

[0013] Thirdly, embodiments of the present invention also provide an electronic device, the electronic device comprising:

[0014] At least one processor; and

[0015] A memory communicatively connected to the at least one processor; wherein,

[0016] The memory stores a computer program that can be executed by the at least one processor, which enables the at least one processor to perform the service request processing method according to any embodiment of the present invention.

[0017] Fourthly, embodiments of the present invention also provide a computer-readable storage medium storing computer instructions, which are used to cause a processor to execute and implement the business request processing method described in any embodiment of the present invention.

[0018] The business request processing scheme of this invention first receives a request identifier included in a business sub-request; then determines the processing level of the business sub-request based on the request identifier; finally, when the processing level is a preset level, it responds to the business sub-request; when the processing level is not a preset level, it sends the business sub-request to the cloud server so that the cloud server responds to the business sub-request; when all business sub-requests generated by the business request have been responded to, the processing of the business request is completed. The scheme provided in this embodiment decouples multiple business sub-requests generated by a business request, allowing responses to business sub-requests at the device end when they belong to a preset level, and responses at the cloud server when they do not belong to a preset level. This improves the processing speed of business sub-requests and reduces the data processing pressure on the cloud server, solving problems such as data accumulation and slow response time on the cloud server in existing solutions, thus achieving the beneficial effects of improving business request processing efficiency and enhancing user experience.

[0019] It should be understood that the description in this section is not intended to identify key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the embodiments of the present invention will become readily apparent from the following description. Attached Figure Description

[0020] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation on the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart illustrating a business request processing method provided in an embodiment of the present invention;

[0022] Figure 2 This is another flowchart illustrating the business request processing method provided in this embodiment of the invention;

[0023] Figure 3 This is a schematic diagram of a business request processing device provided in an embodiment of the present invention;

[0024] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0025] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0026] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention, and not all of the structures.

[0027] Figure 1 This is a flowchart illustrating a service request processing method provided in an embodiment of the present invention. This embodiment is applicable to processing service requests sent by a device. The method can be executed by a service request processing device, which can be implemented in hardware and / or software and can be configured in a user equipment. (Reference) Figure 1 The method may specifically include the following steps:

[0028] S110, Receive the request identifier included in the service sub-request.

[0029] Business sub-requests are generated in the order in which business requests are processed. A business request can be understood as a request generated when a user is handling a corresponding business; the current business involves related businesses in multiple fields, such as shopping in e-commerce, deposit and withdrawal in banking, and registration and report inquiry in healthcare; the specific scenarios in which business requests are generated are not limited here.

[0030] When processing user service requests, each service request generates multiple sub-requests in chronological order. The current sub-request is related to the previous one; that is, the current sub-request is generated after the previous one is completed. For example, taking a user's transfer request on their device as an example, the sequential responses to the transfer request may include: login sub-requests, query sub-requests, transfer sub-requests, and balance update sub-requests, etc. The specific application scenarios for each service request generating sub-requests in chronological order are not limited here.

[0031] It should be noted that each business sub-request is not necessarily generated from the user's device. It may also be generated in association with business sub-requests processed in the previous time period. For example, the balance update business sub-request means that after the transfer or deposit business is completed, the user's account balance needs to be automatically updated based on the response results of the login business sub-request and the transfer business sub-request.

[0032] The aforementioned user equipment can be mobile terminals (smartphones, smart tablets), computer terminals, and Internet of Things (IoT) terminals (ATMs, ticket dispensers, report inquiry machines), etc. The specific type of user equipment is not limited here.

[0033] The above request identifier is the identifier corresponding to each business sub-request. This identifier is used to indicate which business the current user needs to perform. Each request identifier can be encoded in a combination of numbers, letters, or symbols. The specific representation of the request identifier is not limited here, as long as it can be mapped to the corresponding business sub-request.

[0034] S120. Determine the processing level of the business sub-request based on the request identifier.

[0035] The purpose of determining the processing level of a business sub-request is to identify the processing subsystem that handles the corresponding business sub-request based on the request identifier of each business sub-request, so as to process the business sub-request according to the corresponding processing subsystem. The business request processing scheme provided in this embodiment of the invention can be applied to a business request processing system, which may include an edge computing subsystem and a cloud service subsystem. The execution entity of this scheme is the edge computing subsystem, which is mounted on the user equipment that generates the business request. When the user equipment receives the business sub-requests generated by each business request, it can determine the processing level of each business sub-request, thereby achieving decoupling of the business sub-requests generated by the business request.

[0036] Specifically, when the processing level is at a preset level, the user device can respond to business sub-requests based on the edge computing subsystem. When the processing level is not at the preset level, the edge computing subsystem can send the business sub-requests to the cloud server, so that the cloud server subsystem can respond to the business sub-requests. The advantage of this approach is that responding to business sub-requests that meet the preset level on the user device based on the edge computing subsystem differs from the existing solution's method of sending all business requests to the cloud server for response. This solves the problem of slow processing of business requests due to transmission bandwidth and network speed latency in the existing solution. When a massive number of business requests are generated simultaneously, the user device's method of responding to business sub-requests can also solve the problem of request data backlog on the cloud server, thereby improving the processing efficiency of business requests and enhancing the user experience.

[0037] In the edge computing subsystem, the processing level of all business sub-requests generated by each business scenario can be pre-determined, and the request identifiers corresponding to business sub-requests belonging to the same processing level can be stored in the same database. After obtaining the request identifier corresponding to the current business sub-request, the processing level of the current business sub-request can be determined based on the request identifier. Business sub-requests corresponding to request identifiers stored in the same database can be responded to using the same subsystem.

[0038] The above methods for determining the processing level of business sub-requests can include: determining the corresponding processing level based on the complexity of each business request implementation; determining the corresponding processing level based on the priority order of each business request implementation; or determining the processing level of a business sub-request based on the algorithm difficulty of the encryption algorithm used in each business request, etc. No specific method for determining the processing level of a business sub-request is limited here.

[0039] S130. The processing of the business request is completed when all business sub-requests generated by the business request have been responded to.

[0040] During the process of responding to all business sub-requests generated by the business request, some business sub-requests are responded to by the edge computing subsystem integrated on the user device; the other part of the business sub-requests are sent by the edge computing subsystem to the cloud server so that the cloud service subsystem can respond, thereby realizing the rapid processing of user business requests.

[0041] In one application scenario, taking the user's mobile banking transfer transaction in step S110 as an example, the processing level of each business sub-request in the mobile banking is pre-set in the business request processing system. For example, the login and query sub-requests involved in the transfer transaction belong to the preset level; the transfer sub-request and balance update sub-request do not belong to the preset level. Then, after the user enters the login password on the login interface, a login sub-request is sent to the edge computing framework subsystem, which can directly respond to the login sub-request. Furthermore, when the user device sends a query sub-request, the edge computing framework subsystem can directly respond to the query sub-request. When the user device sends a transfer sub-request, if the edge computing framework subsystem determines that it does not belong to the preset processing level, it can send the transfer sub-request to the cloud server, so that the cloud service subsystem can respond to the transfer sub-request. After the response is completed, the cloud service subsystem further updates the balance in the current user account.

[0042] Optionally, when processing each business sub-request on the cloud server, a thread pool can be used to improve data collection and response speed, depending on the transaction type and the complexity of the response algorithm. For example, when staff need to compile quarterly deposit and withdrawal reports for the bank, and need to flexibly query large amounts of data to generate reports, multiple worker threads from the thread pool can be used to split the report data columns, reducing the number of table joins during the query process and accelerating the formation of the result data.

[0043] The business request processing scheme provided in this embodiment of the invention first receives a request identifier included in a business sub-request; then determines the processing level of the business sub-request based on the request identifier; finally, when the processing level is a preset level, the business sub-request is responded to; when the processing level is not a preset level, the business sub-request is sent to the cloud server so that the cloud server responds to the business sub-request; when all business sub-requests generated by the business request have been responded to, the processing of the business request is completed. The scheme provided in this embodiment, by decoupling multiple business sub-requests generated by a business request, allows for responses on the device side when the business sub-request belongs to a preset level, and responses on the cloud server when the business sub-request does not belong to a preset level. This improves the processing speed of business sub-requests and reduces the data processing pressure on the cloud server, solving problems such as data accumulation and slow response time on the cloud server in existing solutions, and achieving the beneficial effects of improving business request processing efficiency and enhancing user experience.

[0044] Figure 2 This is another flowchart illustrating the business request processing method provided in this embodiment of the invention. The relationship between this embodiment and the above embodiments further refines the corresponding features of the above embodiments. Figure 2 As shown, the method may include the following steps:

[0045] S210, Receive the request identifier included in the service sub-request.

[0046] Business sub-requests are generated in the order in which business requests are processed. Each business sub-request includes at least one, and at least one business sub-request is generated by at least one user device. The business sub-request also includes the device type.

[0047] In practical applications, there are situations where a large number of users send business sub-requests from at least one user device within a short period of time. For example, a large number of users log in to the same application on their mobile terminals within a short period of time. After successfully logging in, various business sub-requests are generated based on the functions displayed on the login interface and the different needs of each user.

[0048] Optionally, when a large number of users send the same or different business sub-requests to the same application, there may be situations where different users use different user devices. For example, user devices can be mobile terminals (smartphones, smart tablets), computer terminals, and IoT terminals (ATMs, ticket dispensers, report query machines), etc. When different user devices are used, the communication between each user device and the edge computing subsystem will also be different. Each communication method corresponds to a communication message format, resulting in the received business sub-requests having multiple message formats. To improve this problem, after receiving the business sub-request, steps S220 to S221 are further executed.

[0049] S220. Obtain the target protocol file corresponding to the target device type included in the target service sub-request.

[0050] With the increasing diversity of user device application scenarios, the data sources received are no longer limited to those from applications on computers or smartphones, but also include applications from various smart terminals or IoT devices. The data types generated by different user devices are often multi-type and multi-format, generally requiring conversion processing by other subsystems before subsequent analysis. Since different types of user devices communicate with the edge computing subsystem using different methods, it is necessary to obtain the target device type included in the target service sub-request before establishing a communication connection. The current target service sub-request is any one of at least one service sub-request; that is, for any given service sub-request, each service sub-request includes the device type that generated the current service sub-request.

[0051] The edge computing subsystem includes a device access unit, which stores protocol files for communication of each device type. Therefore, the target protocol file can be obtained for the target device type.

[0052] The aforementioned protocol file stores the communication protocol corresponding to each device type, specifying which communication protocol the current user device must use to communicate with the edge computing subsystem. For example, the communication protocol may include: Transport Control Protocol / Internet Protocol (TCP / IP), Enhanced User Interface (NetBEUI) protocol, and Internet Packet Exchange / Sequence Packet Exchange (IPX / SPX) protocol, etc. The specific type of communication protocol is not limited here and depends on the user device type.

[0053] S221. Communicate with the target user equipment that generated the target service sub-request based on the communication protocol included in the target protocol file.

[0054] After obtaining the communication protocol included in the target protocol file in the device access unit, a communication connection can be established with the target user device that generated the target service sub-request based on the current communication protocol, thereby facilitating subsequent data transmission between the target user device and the edge computing subsystem. In the service request processing scheme provided in the embodiments of the present invention, the edge computing subsystem can support multiple types of device data access and convert multiple types of data formats into a unified data format for data processing within the system, thereby eliminating reliance on other systems for data conversion and transmission, reducing system coupling and data interaction overhead.

[0055] S230. Convert the data format corresponding to the requested data into the target format to obtain the target data.

[0056] The aforementioned request identifier includes request data, which can be the data required to verify each sub-request when sending a business sub-request on the user device. For example, the request data included in a login business sub-request can be a login password and login biometric verification (facial recognition, fingerprint recognition, etc.); a transfer business sub-request can include the transfer amount and transfer password; a balance update business sub-request can include the transfer amount, etc. The target data is the data converted from each request data to the target format; the specific request data included in each business sub-request is not limited here.

[0057] To expand the data source channels of the system and simplify the data transmission process, the business request processing solution provided in this embodiment can convert request data of different formats into a target format, such as Jason (Javascript Object Notation), when receiving business sub-requests sent by different user devices. For example, in a banking business scenario, Bluetooth devices or Near Field Communication (NFC) devices are used to verify user permissions when handling related business or promoting products to customers. After receiving a business sub-request sent by the corresponding device type, the edge computing subsystem establishes a communication connection with the corresponding user device based on the communication protocol included in the target protocol file, and directly converts the request data into the target format in a unified manner. This facilitates the unified storage of the received request data and allows the cloud service subsystem to quickly respond to the business sub-requests in subsequent steps.

[0058] S231. Decrypt the encryption algorithm corresponding to the target data to obtain the decryption result.

[0059] When a user equipment sends each service sub-request, it can encrypt the target data using a corresponding encryption algorithm to ensure the security of data transmission. After the edge computing subsystem receives the service sub-request, it can decrypt it using a corresponding decryption algorithm to obtain the decryption result, and thus determine the purpose of the current service sub-request based on the decryption result.

[0060] Specifically, one type of encryption algorithm can be used for business sub-requests processed by the edge computing subsystem; another type of encryption algorithm can be used for encryption calculations for business sub-requests processed by the cloud service subsystem; the above encryption algorithms can be symmetric encryption algorithms, asymmetric encryption algorithms, and hash algorithms, etc.; the specific method and type of encryption algorithm used when sending different business sub-requests on the user device side are not restricted here.

[0061] S232. Determine whether decryption was successful.

[0062] If yes, proceed to step S233; otherwise, proceed to step S250.

[0063] S233. Set the processing level of the business sub-request with a decryption success result to the preset level.

[0064] If the edge computing subsystem can successfully decrypt the received current business sub-request using the corresponding decryption algorithm, it indicates that the edge computing subsystem can process the current business sub-request, meaning that the current business sub-request belongs to the preset level and the edge computing subsystem can respond to the current business sub-request.

[0065] For multiple business sub-requests received simultaneously, the edge computing subsystem can use a pre-set decryption algorithm to decrypt them concurrently, resulting in two types of sub-requests: those successfully decrypted by the edge computing subsystem and those whose processing level is set to a preset level; and those that cannot be decrypted, indicating a higher encryption level and therefore unprocessable by the edge computing subsystem, requiring them to be sent to the cloud server for processing. This approach is advantageous because the edge computing subsystem operates on the data source side, with shorter transmission links and lower latency, enabling rapid responses to sub-requests at the preset level. This achieves decoupling of business sub-requests within the edge computing subsystem, improving overall processing speed.

[0066] Optionally, the edge computing subsystem includes a data processing unit, which is used to classify and filter multiple received business sub-requests, determine the business sub-requests that the edge computing subsystem can process as a preset level, and otherwise determine the remaining business sub-requests as another level, distinguishing them from the business sub-requests determined to be at the preset level.

[0067] S240. Invoke the corresponding request rule based on the request identifier.

[0068] In the edge computing subsystem, corresponding request rules can be flexibly configured for each business sub-request that can be responded to. For example, the number of authentication attempts, the number of password verification attempts, the transfer limit, and the data content of the target data corresponding to each business sub-request can be set. The specific request rules for each business request are not limited here. After receiving a business sub-request, the data processing unit can obtain the corresponding request rules based on the request identifier carried by the current business sub-request.

[0069] S241. Verify the compliance of the target data according to the request rules and obtain the verification result.

[0070] Taking the current business sub-request as a login business sub-request as an example, if the request rule of the current login business sub-request is that the number of password inputs is less than or equal to 5, if 5 consecutive incorrect inputs are made, it indicates that the target data is not compliant, such as an incorrect login password, and the verification result is verification failure; if the target data is compliant within 5 attempts, that is, the target data is correct, the verification result is verification pass.

[0071] S242. Respond to the business sub-request based on the verification result.

[0072] In this step, the edge computing subsystem may include a command issuing unit, which responds to business sub-requests based on the verification result. That is, if the verification result is successful, the edge computing subsystem can directly process the current business sub-request. For example, after the target data in the login business sub-request is verified to be compliant, a verification success command can be sent to the user device to control the user device to display the interface after successful login, thus enabling the user to proceed with subsequent operations. If the verification result is unsuccessful, the edge computing subsystem can directly reject the business sub-request, such as password verification failure. The specific method by which the edge computing subsystem responds to business sub-requests based on the verification result is not limited here.

[0073] After the edge computing subsystem responds to a service sub-request, it needs to send the corresponding response data to the corresponding user device. The service request processing scheme provided in this embodiment of the invention includes a device identifier in the service sub-request. Responding to the service sub-request according to the verification result includes: determining the response data for responding to the service sub-request according to the verification result; and sending the response data to the corresponding device identifier to complete the response to the service sub-request.

[0074] The response data mentioned above can be understood as a reply to the current business sub-request, such as "pass" or "fail". Since the edge computing subsystem receives multiple business sub-requests, when sending response data, it is necessary to determine which user device the current response data should be sent to. The business sub-request includes a device identifier, and the current response data is sent to the corresponding device identifier to complete the response to the business sub-request.

[0075] It should be noted that when the edge computing subsystem responds to the current business sub-request, since it includes multiple device types, when sending response data to the user device corresponding to the corresponding device identifier, the response data can be converted into the corresponding communication protocol in the HTTP mode, and the response data can be sent based on the communication protocol corresponding to the user device, so as to enable the user device to identify the response data.

[0076] S250. Send the target data corresponding to the business sub-request whose decryption result is unsuccessful to the cloud server so that the cloud server can decrypt the target data and respond.

[0077] In the current step, the edge computing subsystem may include an output unit for inputting business sub-requests that cannot be processed by the edge computing subsystem to the cloud server, so that the cloud service subsystem integrated on the cloud server can respond to the business sub-requests.

[0078] On the cloud server, the data processing characteristics of each business sub-request can be analyzed. Based on the transaction type and the complexity of the calculation, a thread pool can be used to improve the data collection and response speed. For example, when dealing with transaction scenarios that require flexible querying of large amounts of data to form reports, multiple thread pool worker threads can be used to split the report data columns, reduce the number of table joins in the query process, and accelerate the formation of result data.

[0079] The cloud service includes a data storage center that can classify and store data for various business scenarios. The storage method can adopt a distributed database approach, which can not only meet the throughput of large-capacity data, but also avoid service crashes caused by database downtime.

[0080] S260. The processing of the business request is completed when all business sub-requests generated by the business request have been responded to.

[0081] In another preferred embodiment, to alleviate the pressure of transmitting data from the edge computing subsystem to the cloud server, the business request processing scheme provided in this embodiment of the invention obtains the number of target data to be sent to the cloud server at preset time intervals; when the number of target data is less than a preset value, the response data of the business sub-requests in the previous time interval is sent to the cloud server so that the cloud server can store the response data.

[0082] An edge computing subsystem may include a storage unit, which utilizes storage resources on a gateway or server equipped with an edge computing framework to store valid information from the data. For example, it stores response data sent by the edge computing subsystem to user devices; and when the amount of target data sent to the cloud server is less than a preset value, the stored response data is sent to the cloud server, enabling the cloud server to store the response data. By asynchronously sending data from the edge computing subsystem to the cloud server, peak traffic can be smoothed out during periods of high data volume.

[0083] The business request processing method provided in this embodiment can quickly respond to business sub-requests and issue commands by introducing an edge computing subsystem. Since the scope of the edge computing framework is on the data source side, the transmission link is shorter, data transmission latency is low, and service requests and responses are rapid. Combined with parallel execution of transaction logic processing using a thread pool, this greatly improves the user experience. Furthermore, the response data in this solution can be stored in the edge computing subsystem and sent asynchronously to the cloud server, which reduces the pressure of large-volume data transmission and optimizes the storage structure of the business request processing system, improving the response efficiency of business requests.

[0084] Figure 3 This is a schematic diagram of a business request processing apparatus provided in an embodiment of the present invention. This apparatus is suitable for executing the business request processing method provided in an embodiment of the present invention. Figure 3 As shown, the device may specifically include: a request receiving module 310, a level determination module 320, and a request response module 330, wherein:

[0085] The request receiving module 310 is used to receive the request identifier included in the business sub-request, wherein the business sub-request is generated according to the timing of processing business requests;

[0086] The level determination module 320 is used to determine the processing level of the business sub-request based on the request identifier; wherein, when the processing level is a preset level, the business sub-request is responded to; when the processing level is not a preset level, the business sub-request is sent to the cloud server so that the cloud server responds to the business sub-request.

[0087] The request-response module 330 is used to complete the processing of the business request when all business sub-requests generated by the business request have been responded to.

[0088] The business request processing apparatus provided in this embodiment of the invention first receives a request identifier included in a business sub-request; then determines the processing level of the business sub-request based on the request identifier; finally, when the processing level is a preset level, it responds to the business sub-request; when the processing level is not a preset level, it sends the business sub-request to the cloud server so that the cloud server responds to the business sub-request; when all business sub-requests generated by the business request have been responded to, the processing of the business request is completed. The solution provided in this embodiment decouples multiple business sub-requests generated by a business request, allowing responses to business sub-requests at the device end when they belong to a preset level, and responses at the cloud server when they do not belong to a preset level. This improves the processing speed of business sub-requests and reduces the data processing pressure on the cloud server, solving problems such as data accumulation and slow response time on the cloud server in existing solutions, thus achieving the beneficial effects of improving business request processing efficiency and enhancing user experience.

[0089] In one embodiment, the service sub-request includes at least one, and the at least one service sub-request is generated by at least one user equipment, the service sub-request further including a device type; the apparatus further includes:

[0090] The file acquisition module is used to acquire the target protocol file corresponding to the target device type included in the target service sub-request, wherein the target service sub-request is any one of at least one service sub-request.

[0091] The device communication module is used to communicate with the target user equipment that generated the target service sub-request based on the communication protocol included in the target protocol file.

[0092] In one embodiment, the request identifier includes request data; the level determination module 320 includes: a format conversion unit, an algorithm decryption unit, and a level determination unit, wherein:

[0093] The format conversion unit is used to convert the data format corresponding to the request data into the target format to obtain the target data.

[0094] The algorithm decryption unit is used to decrypt the encryption algorithm corresponding to the target data and obtain the decryption result;

[0095] The level determination unit is used to determine the processing level of the business sub-request whose decryption result is successful as the preset level.

[0096] In one embodiment, each of the service sub-requests includes a request identifier, and the request response module 330 includes: a data determination unit and a request response unit, wherein:

[0097] A data determination unit is used to determine response data for responding to the business sub-request based on the verification result;

[0098] The request-response unit is used to send the response data to the device identifier to complete the response to the service sub-request.

[0099] In one embodiment, the request-response module 330 further includes: a data sending unit, wherein:

[0100] The data sending unit is used to send the target data corresponding to the business sub-request whose decryption result is unsuccessful to the cloud server, so that the cloud server can decrypt the target data and respond.

[0101] In one embodiment, the request-response module 330 further includes: a data volume acquisition unit; wherein:

[0102] The data acquisition unit is used to acquire the amount of target data sent to the cloud server at preset time intervals.

[0103] The data sending unit is used to send the response data of responding to the business sub-request in the previous time period to the cloud server when the amount of the target data is less than a preset value, so that the cloud server can store the response data.

[0104] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional modules is merely an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the functional modules described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0105] This invention also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to execute the service request processing method described in any embodiment of this invention.

[0106] This invention also provides a computer-readable medium storing computer instructions that, when executed by a processor, implement the business request processing method described in any embodiment of this invention.

[0107] The following is for reference. Figure 4 It shows a schematic diagram of the structure of a computer system 500 suitable for implementing an electronic device according to embodiments of the present invention. Figure 4 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments of the present invention.

[0108] like Figure 4 As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 502 or programs loaded from storage section 508 into random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the system 500. The CPU 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0109] The following components are connected to I / O interface 505: an input section 506 including a keyboard, mouse, etc.; an output section 507 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN card, modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to I / O interface 505 as needed. A removable medium 511, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 510 as needed so that computer programs read from it can be installed into storage section 508 as needed.

[0110] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 509, and / or installed from removable medium 511. When the computer program is executed by central processing unit (CPU) 501, it performs the functions defined above in the system of this invention.

[0111] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0112] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0113] The modules and / or units described in the embodiments of the present invention can be implemented in software or hardware. The described modules and / or units can also be housed in a processor; for example, a processor can be described as including an acquisition module, a determination module, and a creation module. The names of these modules do not necessarily limit the module itself.

[0114] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, which, when executed by the device, cause the device to include: receiving a request identifier included in a service sub-request, the service sub-request being generated according to the timing of processing service requests; determining a processing level of the service sub-request based on the request identifier; responding to the service sub-request when the processing level is a preset level; sending the service sub-request to a cloud server when the processing level is not a preset level, so that the cloud server responds to the service sub-request; and completing the processing of the service request when all service sub-requests generated by the service request have been responded to.

[0115] According to the technical solution of the present invention, by decoupling multiple business sub-requests generated from a business request, the response is made on the device side when the business sub-request belongs to a preset level, and on the cloud server side when the business sub-request does not belong to the preset level. This improves the processing speed of business sub-requests and reduces the data processing pressure on the cloud server. It solves the problems of data accumulation and slow response time on the cloud server in the existing solution, and achieves the beneficial effects of improving the efficiency of business request processing and enhancing user experience.

[0116] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A business request processing method, characterized in that, The service sub-request includes a request identifier, which is generated according to the time sequence of processing service requests. The current service sub-request is generated after the previous service sub-request has been responded to. The processing level of the business sub-request is determined based on the request identifier; wherein, when the processing level is a preset level, the business sub-request is responded to; when the processing level is not a preset level, the business sub-request is sent to the cloud server so that the cloud server responds to the business sub-request. The processing of the business request is completed when all business sub-requests generated by the business request have been responded to. Wherein, the request identifier includes request data; determining the processing level of the business sub-request based on the request identifier includes: Convert the data format corresponding to the requested data into the target format to obtain the target data; The encryption algorithm corresponding to the target data is decrypted to obtain the decryption result; The processing level of the business sub-request whose decryption result is successful is determined as the preset level; Wherein, sending the business sub-request to the cloud server when the processing level is not a preset level includes: The target data corresponding to the business sub-request that failed to decrypt is sent to the cloud server so that the cloud server can decrypt the target data and respond; wherein, the encryption algorithm corresponding to the business sub-request that failed to decrypt has a higher level than the encryption algorithm corresponding to the business sub-request that succeeded in decryption. The method further includes: The number of target data sent to the cloud server is obtained at preset time intervals; When the amount of target data is less than a preset value, the response data of responding to the business sub-request in the previous time period will be sent to the cloud server so that the cloud server can store the response data.

2. The method according to claim 1, characterized in that, The service sub-request includes at least one, and at least one service sub-request is generated by at least one user device. The service sub-request also includes a device type. After receiving the request identifier included in the business sub-request, it also includes: Obtain the target protocol file corresponding to the target device type included in the target service sub-request, wherein the target service sub-request is any one of at least one service sub-request; The target user equipment that generates the target service sub-request communicates with the target user equipment based on the communication protocol included in the target protocol file.

3. The method according to claim 1, characterized in that, When the processing level is a preset level, responding to the business sub-request includes: Invoke the corresponding request rule based on the request identifier; Verify the compliance of the target data according to the request rules, and obtain the verification result; The business sub-request is responded to based on the verification result.

4. The method according to claim 3, characterized in that, The service sub-request includes a device identifier; the step of responding to the service sub-request based on the verification result includes: The response data for the business sub-request is determined based on the verification result; The response data is sent to the corresponding device identifier to complete the response to the service sub-request.

5. A business request processing device, characterized in that, include: The request receiving module is used to receive the request identifier included in the business sub-request. The business sub-request is generated according to the timing of processing business requests, and the current business sub-request is generated after the previous business sub-request has been responded to. The level determination module is used to determine the processing level of the business sub-request based on the request identifier; wherein, when the processing level is a preset level, the business sub-request is responded to; when the processing level is not a preset level, the business sub-request is sent to the cloud server so that the cloud server responds to the business sub-request. The request-response module is used to complete the processing of the business request when all business sub-requests generated by the business request have been responded to. The request identifier includes request data; the level determination module includes: The format conversion unit is used to convert the data format corresponding to the request data into the target format to obtain the target data. The algorithm decryption unit is used to decrypt the encryption algorithm corresponding to the target data and obtain the decryption result; A level determination unit is used to determine the processing level of the business sub-request whose decryption result is successful as the preset level; The request-response module further includes: A data sending unit is used to send the target data corresponding to the business sub-request whose decryption result is unsuccessful to the cloud server, so that the cloud server can decrypt the target data and respond; wherein, the encryption algorithm corresponding to the unsuccessful business sub-request has a higher level than the encryption algorithm corresponding to the successfully decrypted business sub-request. The request-response module also includes: The data acquisition unit is used to acquire the amount of target data sent to the cloud server at preset time intervals. The data sending unit is used to send the response data of responding to the business sub-request in the previous time period to the cloud server when the amount of the target data is less than a preset value, so that the cloud server can store the response data.

6. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the service request processing method according to any one of claims 1-4.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the business request processing method as described in any one of claims 1-4.

Images