Data processing method, device, conference management and scheduling system, and computer medium

By using the division of labor between task threads and main thread in the conference management and scheduling system, the waste of time and thread resource occupation in the message transmission and processing process between the interaction layer and the logic layer are solved, and the efficiency of video conference call is improved.

CN111880944BActive Publication Date: 2024-11-26VISIONVERA INFORMATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010544444.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-06-15
Publication Date
2024-11-26
Estimated Expiration
2040-06-15

AI Technical Summary

Technical Problem

When the existing conference management and scheduling system starts video conferencing on a third-party platform, the message transmission and processing process between the interaction layer and the logic layer is wasted time and thread resources, resulting in the increase in the call time of the third-party platform on the web layer interface. .

Method used

By introducing task threads and main threads into the conference management scheduling system, the task thread obtains business requests from the message queue of the interaction layer, sends them to the logic layer for processing, and immediately ends the processing process. The main thread is responsible for receiving business processing returned by the logic layer. As a result, task threads are prevented from waiting for the logical layer to return the result, thereby improving the speed of the interactive layer processing business requests in the message queue.

Benefits of technology

It saves the time when the task thread waits for the logical layer to return the business processing results, improves the efficiency of calling the web layer interface by third-party platforms, and reduces the call time.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111880944B_ABST
    Figure CN111880944B_ABST
Patent Text Reader

Abstract

The present invention provides a data processing method, device, conference management and scheduling system, and computer-readable storage medium. The method includes: the task thread obtains a first target business request from the message queue of the interactive layer, the task thread sends the first target business request to the logic layer, the task thread ends the processing of the first target business request, and the main thread receives the business processing result returned by the logic layer. Using the data processing method of the present invention, the task thread can cyclically obtain other first target business requests for processing after sending the first target business request to the logic layer, saving the time for the task thread to wait for the logic layer to return the business processing result, and can improve the speed of the interactive layer processing business requests in the message queue, thereby reducing the calling time of the third-party platform.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of data processing, and in particular to a data processing method, device, conference management and scheduling system and computer medium. Background Art

[0002] Third-party platforms on the Internet (such as GIS, surgical instruction, and other third-party platforms) can use the conference management and scheduling system to organize and start multi-party video conferences on the visual network, and watch the video content of other terminals in the conference on the display screen of the visual network video device.

[0003] At present, when starting a video conference on a third-party platform, the web layer interface of the conference management and scheduling system is called to send messages to the web layer of the conference management and scheduling system. Then, through the collaboration between the web layer, interaction layer and logic layer of the conference management and scheduling system, message transmission and processing during the conference are realized, thereby ensuring the normal progress of the entire conference process.

[0004] However, the message transmission and processing between the interaction layer and the logic layer of the existing conference management and scheduling system wastes time and thread resources, and increases the calling time of the third-party platform to the web layer interface. Summary of the invention

[0005] In view of the above problems, embodiments of the present invention are proposed to provide a data processing method, device, conference management and scheduling system, and computer medium that overcome the above problems or at least partially solve the above problems.

[0006] In order to solve the above problems, an embodiment of the present invention discloses a data processing method, which is applied to a conference management and scheduling system. The conference management and scheduling system includes an interaction layer and a logic layer. The interaction layer includes a main thread and a task thread. The method includes:

[0007] The task thread obtains a first target service request from a message queue of the interaction layer;

[0008] The task thread sends the first target service request to the logic layer;

[0009] The task thread ends processing of the first target service request;

[0010] The main thread receives the business processing result returned by the logic layer.

[0011] Optionally, the business processing result includes an identity, a business code and specific business data, and the business processing result and the corresponding first target business request carry the same identity. After the main thread receives the business processing result returned by the logic layer, the method further includes:

[0012] The main thread determines, according to the identity carried by the business processing result, the first target business request corresponding to the business processing result;

[0013] The main thread obtains the service type of the first target service request according to the first target service request;

[0014] When the main thread determines that the service type is the first service type, the service code is sent to the web layer, the state of the first target service request is changed from the waiting reply state to the processing success state, and the first target service request is deleted from the message queue;

[0015] When the main thread determines that the business type is the second business type, the business code is sent to the web layer, the specific business data is inserted into the message queue of the web layer, the status of the first target business request is changed from the waiting reply status to the processing success status, and the first target business request is deleted from the message queue.

[0016] Optionally, the interaction layer further includes a detection thread, and the method further includes:

[0017] The detection thread determines whether there is a first target service request that meets a preset rule in the message queue of the interaction layer;

[0018] In the case that there is the first target service request satisfying the preset rule, the detection thread determines the first target service request satisfying the preset rule as an abnormal service request;

[0019] The detection thread generates an exception handling result according to the abnormal service request;

[0020] The detection thread sends the exception processing result to the web layer, and deletes the first target service request that meets the preset rule from the message queue.

[0021] Optionally, the method further comprises:

[0022] The detection thread obtains the sending time of the first target service request;

[0023] The detection thread determines whether there is a first target service request that meets a preset rule in the message queue of the interaction layer, including:

[0024] The detection thread determines whether the difference between the sending time of the first target service request in the message queue of the interaction layer and the current time is greater than a preset time interval;

[0025] When the difference between the sending time of the first target service request and the current time is greater than a preset time interval, the detection thread determines that the first target service request satisfies a preset rule.

[0026] Optionally, after the task thread sends the first target service request to the logic layer, the method further includes:

[0027] The task thread changes the state of the first target service request from the initial state to the waiting for reply state;

[0028] The detection thread obtains the sending time of the first target service request, including:

[0029] The detection thread obtains the sending time of the first target service request in the waiting reply state.

[0030] The embodiment of the present invention also discloses a conference management and scheduling system, the system comprising:

[0031] An interaction layer and a logic layer, wherein the interaction layer includes a main thread and a task thread;

[0032] The task thread is used to obtain the first target service request from the message queue of the interaction layer;

[0033] The task thread is further used to send the first target service request to the logic layer;

[0034] The task thread is further used to end the processing of the first target service request;

[0035] The main thread is used to receive the business processing results returned by the logic layer.

[0036] Optionally, the business processing result includes an identity identifier, a business code and specific business data, and the business processing result and the corresponding first target business request carry the same identity identifier;

[0037] The main thread is further configured to determine the first target service request corresponding to the service processing result according to the identity carried by the service processing result;

[0038] The main thread is further configured to obtain a service type of the first target service request according to the first target service request;

[0039] The main thread is further configured to, when the main thread determines that the service type is the first service type, send the service code to the web layer, change the state of the first target service request from the waiting reply state to the processing success state, and delete the first target service request from the message queue;

[0040] The main thread is also used to send the business code to the web layer, insert the specific business data into the message queue of the web layer, change the status of the first target business request from the waiting reply status to the processing success status, and delete the first target business request from the message queue when the main thread determines that the business type is the second business type.

[0041] Optionally, the interaction layer further includes a detection thread;

[0042] The detection thread is used to determine whether there is a first target service request that meets a preset rule in the message queue of the interaction layer;

[0043] In the case where there is the first target service request that satisfies the preset rule, the detection thread is further used to determine the first target service request that satisfies the preset rule as an abnormal service request;

[0044] The detection thread is further used to generate an exception handling result according to the abnormal business request;

[0045] The detection thread is further used to send the exception processing result to the web layer, and delete the first target business request that meets the preset rule from the message queue.

[0046] Optionally, the detection thread is further used to obtain the sending time of the first target service request;

[0047] The detection thread is further used to determine whether the difference between the sending time of the first target service request in the message queue of the interaction layer and the current time is greater than a preset time interval;

[0048] In the case that the difference between the sending time of the first target service request and the current time is greater than a preset time interval, the detection thread is further used to determine whether the first target service request meets a preset rule.

[0049] Optionally, the task thread is further used to change the state of the first target service request from an initial state to the waiting for reply state;

[0050] The detection thread is further used to obtain the sending time of the first target service request in the waiting reply state.

[0051] The embodiment of the present invention further discloses a data processing device, including:

[0052] one or more processors; and

[0053] One or more computer-readable media having instructions stored thereon, when executed by the one or more processors, enable the device to perform the data processing method as described in any of the embodiments of the present invention.

[0054] The embodiment of the present invention further discloses a computer-readable storage medium, which stores a computer program that enables a processor to execute the data processing method described in the embodiment of the present invention.

[0055] The embodiments of the present invention include the following advantages:

[0056] In the data processing method provided by the embodiment of the present invention, the task thread of the interaction layer only needs to send the first target business request to the logic layer, and the task thread will end the processing of the first target business request. The task thread does not have to wait for the logic layer to return the business processing result, and the main thread receives the business processing result returned by the logic layer. In this way, after sending the first target business request to the logic layer, the task thread can cyclically obtain other first target business requests for processing, saving the time of the task thread waiting for the logic layer to return the business processing result, and can improve the speed of the interaction layer processing the business requests in the message queue, thereby reducing the calling time of the third-party platform. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0058] Figure 2 is a flow chart of a data processing method provided by an embodiment of the present application;

[0059] Figure 3 This is a structural block diagram of a conference management and scheduling system provided by an embodiment of the present application;

[0060] Figure 4 This is a schematic diagram of a visual network provided by an embodiment of the present application;

[0061] Figure 5 This is a schematic diagram of the hardware structure of a node server provided in one embodiment of the present application;

[0062] Figure 6 This is a schematic diagram of the hardware structure of an access switch provided in an embodiment of the present application;

[0063] Figure 7 It is a hardware structure diagram of an Ethernet protocol conversion gateway provided in one embodiment of the present application. DETAILED DESCRIPTION

[0064] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0065] Please refer to Figure 1 , Figure 1 This is a schematic diagram of an application scenario provided by an embodiment of the present application. Figure 1 As shown, the application scenario includes: a third-party platform, a conference management and scheduling system, a chairman terminal, a video network server and multiple video terminals (video terminal 1 to video terminal N) that are connected in communication in sequence, wherein the third-party platform and the conference management and scheduling system are located in the Internet, the chairman terminal, the video network server and the multiple video terminals are all located in the video network, the third-party platform, the conference management and scheduling system and the chairman terminal are connected through the Internet, and the chairman terminal, the video network server and the multiple video terminals are connected through the video network.

[0066] At present, in the process of starting a video conference on a third-party platform, the third-party platform sends a business request to the web layer of the conference management and scheduling system by calling the web layer interface of the conference management and scheduling system. The web layer then sends the business request to the interaction layer of the conference management and scheduling system, and the interaction layer inserts the business request into the message queue. Then the task thread obtains the business request from the message queue and sends it to the logic layer of the conference management and scheduling system for processing, and blocks on an m_signal semaphore (m_signal=0 at this time) waiting for the result. After the logic layer processes the business logic in the business request, it sends the result message back to the task thread. After receiving the message, the task thread activates the semaphore (m_signal=1 at this time) to release the wait, and then returns the result message to the web layer, which returns it to the third-party platform.

[0067] This message exchange mode between the interaction layer and the logic layer is synchronous. The thread that processes the message in the interaction layer will be blocked after sending the message, and will not continue to execute until the logic layer processes and returns the result. During this period, the thread can only wait, which will waste time and thread resources.

[0068] To solve the above mentioned problem of wasting time and thread resources, please refer to Figure 2 , Figure 2 1 is a flow chart of a data processing method provided by an embodiment of the present application. The data processing method of the present application can be applied to a conference scheduling management system. The conference management scheduling system includes an interaction layer and a logic layer. The interaction layer includes a main thread and a task thread. Figure 2As shown, the method may specifically include the following steps:

[0069] Step S21: the task thread obtains a first target service request from the message queue of the interaction layer.

[0070] In this embodiment, when a third-party platform such as GIS or surgical teaching holds a meeting, the business request is sent to the web layer by calling the interface of the web layer of the conference management and scheduling system. The web layer then sends the business request to the interaction layer. After the main thread of the interaction layer receives the business request, it parses the business request in JSON format and puts it into the message queue of the interaction layer. The task thread in the thread pool then cyclically takes out the business request for processing.

[0071] The interaction layer, also known as CMS, is a subroutine in the conference scheduling management system, responsible for message interaction with the web layer and logic layer.

[0072] The logic layer, also known as DMS, is also a subroutine in the conference scheduling management system, responsible for the underlying scheduling operation logic processing of the conference, that is, processing business requests.

[0073] Multiple business requests can be stored in the message queue of the interaction layer, and multiple task threads can also be opened in the thread pool. For example, suppose there are 200 business requests in the message queue and 50 task threads are opened, of which 50 task threads can work simultaneously, that is, the 50 task threads take out the first 50 business requests in the message queue in turn for processing. After a task thread processes a business request, it can take out other unprocessed business requests in turn for processing. The business request taken out for processing by the task thread is the first target business request.

[0074] Step S22: The task thread sends the first target service request to the logic layer.

[0075] Step S23: the task thread ends processing the first target service request.

[0076] Each business thread in the interaction layer executes the same operation process, except that the specific business requests for the operations are different. After the task thread takes out the first target business request from the message queue of the interaction layer in a copy manner, it sends the first target business request to the logic layer. After sending the first target business request to the logic layer, the task thread will end the processing of the first target business request, and then cyclically take out the next unprocessed business request to continue processing, that is, take out the next unprocessed business request and send it to the logic layer, and repeat this cycle until there are no more unprocessed business requests in the message queue of the interaction layer.

[0077] Step S24: the main thread receives the business processing result returned by the logic layer.

[0078] After the task thread sends the first target service request to the logic layer, the logic layer performs subsequent processing on the first target service request. Specifically, the logic layer can parse the service field content in the first target service request, and analyze whether the first target service request should be processed by the logic layer itself according to the service field content, for example: executing some addition, deletion, modification and query operations in the conference management and scheduling system database; or whether it needs to be sent to the visual network server for processing by the visual network server, for example: cutting the video stream switching service, speaker switching service, etc.

[0079] If the logic layer analyzes that the first target business request is processed by itself, then the logic layer directly processes the first target business request to generate a business processing result; if the logic layer analyzes that the first target business request is processed by the visual network server, then the logic layer transmits the first target business request to the visual network server through the chairman terminal. After the visual network server processes the first target business request, the logic layer receives the business processing result returned by the visual network server. Regardless of whether it is a business request processed by the logic layer itself or a business request processed by the visual network server, the final business processing result is sent by the logic layer to the interaction layer, and then received by the main thread of the interaction layer.

[0080] Here, the chairman terminal is a visual networking terminal, which is connected to the visual networking server and communicates with the visual networking server based on the visual networking protocol. The chairman terminal can convert the first target service based on the Internet protocol sent by the logic layer, obtain the first target service request based on the visual networking protocol, and then transparently transmit the first target service request based on the visual networking protocol to the visual networking server. Similarly, after processing the first target service request based on the visual networking protocol, the visual networking server generates a service processing result based on the visual networking protocol and sends it to the chairman terminal. After the chairman terminal converts the service processing result based on the visual networking protocol, it obtains the service processing result based on the Internet protocol and transparently transmits it to the interaction layer, which is received by the main thread of the interaction layer.

[0081] In the data processing method provided by this embodiment, the task thread of the interaction layer only needs to send the first target business request to the logic layer, and the task thread will end the processing of the first target business request. The task thread does not have to wait for the logic layer to return the business processing result, and the main thread receives the business processing result returned by the logic layer. In this way, after sending the first target business request to the logic layer, the task thread can cyclically obtain other first target business requests for processing, which saves the time of the task thread waiting for the logic layer to return the business processing result, and can improve the speed of the interaction layer in processing the business requests in the message queue, thereby reducing the calling time of the third-party platform.

[0082] In one embodiment, considering that multiple task threads are used in the interaction layer to jointly process multiple business requests in the message queue of the interaction layer, resulting in different states of different business requests, for example, some business requests are not processed, and some business requests are being processed. In order to avoid the idle task thread from repeatedly obtaining business requests that are being processed or completed by other task threads for processing, the unprocessed business requests in the message queue of the interaction layer can be marked as the initialization state, and after the task thread sends the first target business request to the logic layer, the task thread can also modify the state of the first target business request from the initial state to the waiting reply state. In this way, the task thread will not cyclically obtain business requests that have been processed by other task threads.

[0083] In combination with the above embodiment, the business processing result and the corresponding first target business request carry the same identity identifier. After receiving the business processing result returned by the logic layer, the main thread can process the business processing result, and specifically perform the following steps:

[0084] Step S25: The main thread determines the first target service request corresponding to the service processing result according to the identity carried by the service processing result.

[0085] Step S26: The main thread obtains the service type of the first target service request according to the first target service request.

[0086] Step S27-1, when the main thread determines that the business type is the first business type, sends the business code to the web layer, changes the status of the first target business request from the waiting reply status to the processing success status, and deletes the first target business request from the message queue.

[0087] Step S27-2, when the main thread determines that the business type is the second business type, the business code is sent to the web layer, the specific business data is inserted into the message queue of the web layer, the status of the first target business request is changed from the waiting reply status to the processing success status, and the first target business request is deleted from the message queue.

[0088] In this embodiment, the content of the first target service request may generally include a service type, a conference ID, a device ID, an identity identifier, and fields required by the service (including specific services and service parameters).

[0089] The content of the business processing result may generally include an identity identifier, a business code, and specific business data.

[0090] The identity identifier is used to find the first target service request corresponding to the service processing result. Usually, the service processing result and the corresponding first target service request carry the same identity identifier.

[0091] The service code is used to indicate whether the service request is processed successfully or not. For example, a successful service request can be indicated by 0, and a failed service request can be indicated by -1.

[0092] For specific business data, not all first-target business requests can generate specific business data. For business requests that do not generate specific business data, the specific business data field in the business processing result can be represented by a null value. For example, for a request to raise your hand to speak, after processing by the logic layer, specific business data of the speaker list can be generated. For another example, for a business request to obtain a list of participants, after processing by the logic layer, specific business data of the participant list can be generated. For another example, for a business request to start a meeting, after processing by the logic layer, the specific business data generated is a null value.

[0093] Among them, the business type may specifically include a first business type and a second business type. The first business type refers to a business type in which the specific business data field in the business processing result obtained after executing the first target business request is a null value. Therefore, for the first target business request executing the first business type, after obtaining the business processing result, it is only necessary to send the business code in the obtained business processing result to the web layer; the second business type refers to a business type in which the specific business data field in the business processing result obtained after executing the first target business request is not a null value. For example, the business data field mentioned above can be the specific business data of the conference participant list, the specific business data of the speaker list, etc. Since the specific business data of the conference participant list or the specific business data of the speaker list, etc., usually have a large amount of data, therefore, for the first target business request executing the second business type, after obtaining the business processing result, it is necessary to send the business code in the obtained business processing result to the web layer, and it is also necessary to insert the specific business data in the business processing result into the message queue of the web layer.

[0094] After processing the first target business request of the first business type, the specific business data field in the business processing result obtained by the logic layer is an empty value. Therefore, it is only necessary to feedback the business code to the third-party platform. Considering that the amount of business code data is not large, the business code can be sent to the web layer, and then sent to the third-party platform through web layer message transmission to ensure transmission efficiency. After processing the first target business request of the second business type, the specific business data field in the business processing result obtained by the logic layer is not an empty value. Therefore, it is necessary to return the business code and specific business data to the third-party platform. Considering that the specific business data usually contains a large amount of data, by inserting the specific business data into the message queue of the web layer, allowing the third-party platform to directly obtain the specific business data from the message queue of the web layer, the data transmission efficiency can be improved and data loss can also be avoided.

[0095] In this embodiment, since the business processing result also carries an identity identifier and is the same as the corresponding first target business request, after receiving the business processing result, the main thread can parse the identity identifier carried by the business processing result, and search for the first target business request with the same identity identifier in the message queue of the interaction layer based on the identity identifier carried by the business processing result, and then parse the content of the business type field from the found first target business request, thereby obtaining the business type of the first target business request.

[0096] If it is determined that the first target business request is of the first business type, the main thread calls the first success function corresponding to the first business type to send the business code to the web layer, and deletes the first target business request from the message queue. If it is determined that the first target business request is of the second business type, the main thread calls the second success function corresponding to the second business type to send the business code to the web layer, inserts the specific business data into the message queue of the web layer, and deletes the first target business request from the message queue.

[0097] After the main thread sends the business code to the web layer, or the business code is sent to the web layer and the specific business data is inserted into the mq message queue of the web layer, the first target business request in the interactive layer message queue is considered to be completely processed. At this time, the first target business request can be deleted from the message queue to reduce the consumption of queue memory by useless business requests.

[0098] In addition, considering that after the main thread sends the business code to the web layer, or sends the business code to the web layer and inserts the specific business data into the mq message queue of the web layer, special circumstances may occur, such as a sudden program stop, at which time the main thread does not have time to delete the first target business request that has been processed, and after the interactive layer program runs again, in order to be able to distinguish the first target business request that has been processed, in this application, after the main thread sends the business code to the web layer, or the main thread sends the business code to the web layer and inserts the specific business data into the mq message queue of the web layer, the state of the first target business request can be changed from the waiting reply state to the processing success state. So that the detection thread can delete it after the program is restarted and the first target business request in the processing success state is detected.

[0099] In addition, considering that after the task thread sends the first target business request to the logic layer, the logic layer cannot guarantee that each business request can be successfully processed, therefore, in order to ensure the timeliness of the business, it is necessary to be able to timely discover the abnormal processing situation and generate the result to inform the third-party platform. Therefore, in one embodiment, the interaction layer also includes a detection thread, and the data processing method of the present application can also specifically include the following steps:

[0100] Step S201: the detection thread determines whether there is a first target service request that meets a preset rule in the message queue of the interaction layer.

[0101] Step S202: When there is the first target service request that meets the preset rule, the detection thread determines the first target service request that meets the preset rule as an abnormal service request.

[0102] Step S203: the detection thread generates an exception handling result according to the abnormal service request.

[0103] Step S204: the detection thread sends the exception processing result to the web layer, and deletes the first target service request that meets the preset rule from the message queue.

[0104] In this embodiment, the detection thread is a resident thread opened by the interaction layer, which can determine whether there is a first target business request that meets the preset rules in the message queue. If there is the first target business request that meets the preset rules, the first target business request is determined to be an abnormal business request, and an exception handling result related to the abnormal business request can be generated. The exception handling result can then be sent to the web layer, and then sent to the third-party platform by the web layer. In this way, the third-party platform can know which business request processing exception is initiated, and re-initiate the business request, or debug the equipment related to the business request.

[0105] Similarly, after the detection thread sends the exception processing result to the web layer, the first target business request is completely processed and the first target business request is deleted from the message queue to reduce the consumption of queue memory by useless business requests.

[0106] In a specific implementation, the preset rule may be whether the time interval between the service request sending time and the current time detected by the detection thread exceeds the preset time interval. At this time, in order to obtain the judgment condition of the preset rule, the data processing method of the present application may further include the steps of:

[0107] Step S200: The detection thread obtains the sending time of the first target service request.

[0108] In this embodiment, a field may be added to the first target service request in the message queue to store the sending time of the first target service request. After sending the first target service request to the logic layer, the task thread may also record the sending time of the first target service request and record the sending time in the corresponding field in the first target service request, so that the detection thread can obtain the sending time of the first target service request.

[0109] Accordingly, the above step S201 may specifically include the following steps:

[0110] Step S2011, the detection thread determines whether the difference between the sending time of the first target service request in the message queue of the interaction layer and the current time is greater than a preset time interval;

[0111] Step S2012: When the difference between the sending time of the first target service request and the current time is greater than a preset time interval, the detection thread determines that the first target service request satisfies a preset rule.

[0112] In this embodiment, since the main thread deletes the first target business result after receiving the business processing result and performing corresponding processing, the remaining first target business requests in the message queue have not yet received the corresponding business processing results. Therefore, for these first target business requests that have not yet received the corresponding business processing results, the detection thread obtains the sending time of these first target business requests to determine whether the difference between the sending time of the first target business request and the current time is greater than the preset time interval. If the difference between the sending time of the first target business request and the current time is greater than the preset time interval, it is determined that the first target business request meets the preset rules. The fact that the first target business request meets the preset rules indicates that the logic layer has not returned the business processing result for a long time, indicating that there is an exception in the first target business request, which is an abnormal business request. At this time, the corresponding exception processing result can be a timeout exception.

[0113] In combination with the above embodiments, in one implementation manner, after the task thread sends the first target service request to the logic layer, the data processing method of the present application may further include the following steps:

[0114] Step S22-1: the task thread changes the state of the first target service request from the initial state to the waiting for reply state.

[0115] Accordingly, the above step S200 may specifically include the step of: the detection thread acquiring the sending time of the first target service request in the waiting reply state.

[0116] In this embodiment, there are multiple states of business requests in the message queue. The business request that is not taken out by the task thread and sent to the logic layer corresponds to the initial state. The first target business request that is taken out by the task thread and sent to the logic layer but the business code is not sent to the web layer, or the business code is not sent to the web layer, and the specific business data is not inserted into the message queue of the web layer corresponds to the waiting reply state. The first target business request that sends the business code to the web layer, or the business code is sent to the web layer, and the specific business data is inserted into the message queue of the web layer corresponds to the processing success state.

[0117] Taking into account that the first target business request corresponding to the successful processing status has actually completed the processing of the business request, but has not been deleted in time, it cannot be regarded as a timeout exception. Therefore, in this embodiment, the detection thread obtains the sending time of the first target business request in the waiting reply status for judgment.

[0118] In this embodiment, by adding a status identifier to the business request in the message queue, the status of each business thread can be effectively distinguished, avoiding idle task threads from repeatedly obtaining and processing business requests that have been processed by other task threads. At the same time, the first target business request is further distinguished into a waiting for reply state and a successfully processed state, and only the first target business request in the waiting for reply state is selected to determine whether it complies with the preset rules. This can avoid the detection thread from determining whether it complies with the preset rules for the first target business request that has been processed but has not been deleted in time under special circumstances, resulting in the same first target business request generating two results and sending them to the web layer, causing an error.

[0119] That is to say, if the first target business request is not distinguished in detail, for special circumstances where the first target business request that has been processed is not deleted in time, it is highly likely that it meets the preset rules. At this time, the detection thread regards it as an abnormal business request, and will generate an abnormal processing result again and send it to the web layer. In fact, the first target business request has actually generated a normal business processing result (business code, or business code and specific business data) and sent it to the web layer. This causes the same first target business request to send the result to the web layer twice, causing an error.

[0120] It should be noted that, for the sake of simplicity, the method embodiments are described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0121] Based on the same technical concept, please refer to Figure 3 , Figure 3 FIG. 4 shows a structural block diagram of a conference management and scheduling system 30 provided in an embodiment of the present application. Figure 3 As shown, the conference management and scheduling system includes:

[0122] A web layer 31, an interaction layer 32 and a logic layer 33, wherein the interaction layer includes a main thread 321, a task thread 322 and a detection thread 323;

[0123] The task thread is used to obtain the first target service request from the message queue of the interaction layer;

[0124] The task thread is further used to send the first target service request to the logic layer;

[0125] The task thread is further used to end the processing of the first target service request;

[0126] The main thread is used to receive the business processing results returned by the logic layer.

[0127] Optionally, the business processing result includes an identity identifier, a business code and specific business data, and the business processing result and the corresponding first target business request carry the same identity identifier;

[0128] The main thread is further configured to determine the first target service request corresponding to the service processing result according to the identity carried by the service processing result;

[0129] The main thread is further configured to obtain a service type of the first target service request according to the first target service request;

[0130] The main thread is further configured to, when the main thread determines that the service type is the first service type, send the service code to the web layer, change the state of the first target service request from the waiting reply state to the processing success state, and delete the first target service request from the message queue;

[0131] The main thread is also used to send the business code to the web layer, insert the specific business data into the message queue of the web layer, change the status of the first target business request from the waiting reply status to the processing success status, and delete the first target business request from the message queue when the main thread determines that the business type is the second business type.

[0132] Optionally, the detection thread is used to determine whether there is a first target service request that meets a preset rule in the message queue of the interaction layer;

[0133] In the case where there is the first target service request that satisfies the preset rule, the detection thread is further used to determine the first target service request that satisfies the preset rule as an abnormal service request;

[0134] The detection thread is further used to generate an exception handling result according to the abnormal business request;

[0135] The detection thread is further used to send the exception processing result to the web layer, and delete the first target business request that meets the preset rule from the message queue.

[0136] Optionally, the detection thread is further used to obtain the sending time of the first target service request;

[0137] The detection thread is further used to determine whether the difference between the sending time of the first target service request in the message queue of the interaction layer and the current time is greater than a preset time interval;

[0138] In the case that the difference between the sending time of the first target service request and the current time is greater than a preset time interval, the detection thread is further used to determine whether the first target service request meets a preset rule.

[0139] Optionally, the task thread is further used to change the state of the first target service request from an initial state to the waiting for reply state;

[0140] The detection thread is further used to obtain the sending time of the first target service request in the waiting reply state.

[0141] An embodiment of the present invention further provides a data processing device, including:

[0142] one or more processors; and

[0143] One or more computer-readable storage media having instructions stored thereon, when executed by the one or more processors, enable the device to perform the data processing method as described in any of the embodiments of the present invention.

[0144] An embodiment of the present invention further provides a computer-readable storage medium, which stores a computer program that enables a processor to execute the data processing method described in the embodiment of the present invention.

[0145] As for the data processing device embodiment, since it is basically similar to the data processing method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the data processing method embodiment.

[0146] The visual Internet is an important milestone in the development of the Internet. It is a real-time network that can realize real-time transmission of high-definition video and push many Internet applications towards high-definition video and high-definition face-to-face communication.

[0147] The visual network adopts real-time high-definition video exchange technology. It can integrate the required services such as high-definition video conferencing, video monitoring, intelligent monitoring analysis, emergency command, digital radio and television, delayed TV, online teaching, live broadcast, VOD on demand, TV mail, personalized recording (PVR), intranet (self-operated) channels, intelligent video broadcast control, information release and dozens of other video, voice, picture, text, communication, data and other services on a single system platform, and realize high-definition quality video playback through TV or computer.

[0148] In order to enable those skilled in the art to better understand the embodiments of the present invention, the visual network is introduced as follows:

[0149] Some of the technologies used in the visual Internet of Things are as follows:

[0150] Network Technology

[0151] The network technology innovation of visual networking improves the traditional Ethernet to cope with the huge potential video traffic on the network. Different from simple network packet switching or network circuit switching, visual networking technology uses packet switching to meet streaming needs. Visual networking technology has the flexibility, simplicity and low price of packet switching, and the quality and security guarantee of circuit switching, realizing the seamless connection of the whole network switching virtual circuit and data format.

[0152] Switching Technology

[0153] Visual networking uses the two advantages of Ethernet: asynchronism and packet switching. It eliminates Ethernet defects under the premise of full compatibility, and has seamless end-to-end connection across the entire network, directly connects to user terminals, and directly carries IP data packets. User data does not require any format conversion within the entire network. Visual networking is a more advanced form of Ethernet and a real-time switching platform that can achieve large-scale real-time transmission of high-definition video across the entire network, which is currently unattainable on the Internet, and pushes many network video applications towards high definition and unification.

[0154] Server Technology

[0155] The server technology on the visual network and unified video platform is different from the traditional server. Its streaming media transmission is based on connection-oriented. Its data processing capability is independent of traffic and communication time. A single network layer can include signaling and data transmission. For voice and video services, the complexity of streaming media processing on the visual network and unified video platform is much simpler than data processing, and its efficiency is more than 100 times higher than that of traditional servers.

[0156] Storage Technology

[0157] The ultra-high-speed storage technology of the unified video platform adopts the most advanced real-time operating system to adapt to the media content with ultra-large capacity and ultra-large flow, mapping the program information in the server command to the specific hard disk space. The media content no longer passes through the server, but is directly delivered to the user terminal in an instant. The user generally waits for less than 0.2 seconds. The optimized sector distribution greatly reduces the mechanical movement of the hard disk head seeking, and the resource consumption accounts for only 20% of the same level of IP Internet, but it generates 3 times more concurrent traffic than the traditional hard disk array, and the overall efficiency is improved by more than 10 times.

[0158] Network Security Technology

[0159] The structural design of the visual network completely eradicates the network security issues that plague the Internet through separate licensing for each service and complete isolation of equipment and user data. Generally, anti-virus programs and firewalls are not required, and attacks by hackers and viruses are eliminated, providing users with a structurally worry-free and secure network.

[0160] Service Innovation Technology

[0161] The unified video platform integrates services and transmission. Whether it is a single user, a private network user or a network, it is just an automatic connection. User terminals, set-top boxes or PCs are directly connected to the unified video platform to obtain rich and colorful multimedia video services in various forms. The unified video platform uses a "recipe-style" table configuration mode to replace traditional complex application programming. Complex applications can be implemented with very little code, realizing "unlimited" new business innovation.

[0162] The networking of the visual network is as follows:

[0163] Visual networking is a centrally controlled network structure. The network can be a tree network, star network, ring network, etc., but on this basis, there needs to be a centralized control node in the network to control the entire network.

[0164] like Figure 4 As shown in the figure, the visual network is divided into two parts: access network and metropolitan area network.

[0165] The equipment in the access network can be divided into three categories: node server, access switch, and terminal (including various set-top boxes, encoding boards, storage, etc.). The node server is connected to the access switch, and the access switch can be connected to multiple terminals and can be connected to Ethernet.

[0166] The node server is a node in the access network that performs centralized control functions and can control access switches and terminals. The node server can be directly connected to the access switch or directly connected to the terminal.

[0167] Similarly, the devices in the metropolitan area network can also be divided into three categories: metropolitan area servers, node switches, and node servers. The metropolitan area servers are connected to the node switches, and the node switches can be connected to multiple node servers.

[0168] The node server is a node server of the access network part, that is, the node server belongs to both the access network part and the metropolitan area network part.

[0169] The metropolitan area server is a node with centralized control function in the metropolitan area network, which can control the node switch and node server. The metropolitan area server can be directly connected to the node switch or the node server.

[0170] It can be seen from this that the entire visual network is a hierarchical and centrally controlled network structure, and the network controlled by the node server and the metropolitan area server can be various structures such as tree, star, and ring.

[0171] Figuratively speaking, the access network part can form a unified video platform (the part in the dotted circle), and multiple unified video platforms can form a visual network; each unified video platform can be interconnected through the metropolitan area and wide area visual networks.

[0172] Visual networking equipment classification

[0173] 1.1 The devices in the visual network of the embodiment of the present invention can be mainly divided into three categories: servers, switches (including Ethernet gateways), terminals (including various set-top boxes, encoding boards, storage devices, etc.). The visual network as a whole can be divided into a metropolitan area network (or a national network, a global network, etc.) and an access network.

[0174] 1.2 The equipment in the access network can be mainly divided into three categories: node server, access switch (including Ethernet gateway), terminal (including various set-top boxes, encoding boards, storage, etc.).

[0175] The specific hardware structure of each access network device is as follows:

[0176] Node server:

[0177] like Figure 5 As shown, it mainly includes a network interface module 501, a switching engine module 502, a CPU module 503, and a disk array module 504;

[0178] Among them, the packets coming from the network interface module 501, the CPU module 503, and the disk array module 504 all enter the switching engine module 502; the switching engine module 502 performs an operation of checking the address table 505 on the incoming packets, thereby obtaining the packet's guidance information; and according to the packet's guidance information, the packet is stored in the queue of the corresponding packet buffer 506; if the queue of the packet buffer 506 is close to full, it is discarded; the switching engine module 502 polls all packet buffer queues, and forwards if the following conditions are met: 1) the port sending buffer is not full; 2) the queue packet counter is greater than zero. The disk array module 504 mainly implements the control of the hard disk, including the initialization, reading and writing of the hard disk; the CPU module 503 is mainly responsible for the protocol processing between the access switch and the terminal (not shown in the figure), the configuration of the address table 505 (including the downstream protocol packet address table, the upstream protocol packet address table, and the data packet address table), and the configuration of the disk array module 504.

[0179] Access switch:

[0180] like Figure 6 As shown, it mainly includes a network interface module (a downlink network interface module 601, an uplink network interface module 602), a switching engine module 603 and a CPU module 604;

[0181] Among them, the packet (uplink data) coming from the downlink network interface module 601 enters the packet detection module 605; the packet detection module 605 detects whether the destination address (DA), source address (SA), data packet type and packet length of the packet meet the requirements. If they meet the requirements, the corresponding stream identifier (stream-id) is allocated and enters the switching engine module 603, otherwise it is discarded; the packet (downlink data) coming from the uplink network interface module 602 enters the switching engine module 603; the data packet coming from the CPU module 604 enters the switching engine module 603; the switching engine module 603 processes the incoming packet The address table 606 is looked up to obtain the packet's guidance information; if the packet entering the switching engine module 603 is from the downstream network interface to the upstream network interface, the packet is stored in the queue of the corresponding packet buffer 607 in combination with the stream identifier (stream-id); if the queue of the packet buffer 607 is nearly full, it is discarded; if the packet entering the switching engine module 603 is not from the downstream network interface to the upstream network interface, the data packet is stored in the queue of the corresponding packet buffer 607 according to the packet's guidance information; if the queue of the packet buffer 607 is nearly full, it is discarded.

[0182] The switching engine module 603 polls all packet buffer queues. In the embodiment of the present invention, there are two situations:

[0183] If the queue is from the downlink network interface to the uplink network interface, it is forwarded if the following conditions are met: 1) the port send buffer is not full; 2) the queue packet counter is greater than zero; 3) a token generated by the bit rate control module is obtained;

[0184] If the queue is not going from the downstream network interface to the upstream network interface, it is forwarded if the following conditions are met: 1) the port send buffer is not full; 2) the queue packet counter is greater than zero.

[0185] The code rate control module 608 is configured by the CPU module 604 to generate tokens for all packet buffer queues from the downstream network interface to the upstream network interface within a programmable interval to control the code rate of the upstream forwarding.

[0186] The CPU module 604 is mainly responsible for protocol processing with the node server, configuration of the address table 606 , and configuration of the bit rate control module 608 .

[0187] Ethernet protocol conversion gateway:

[0188] like Figure 7As shown, it mainly includes a network interface module (a downlink network interface module 701, an uplink network interface module 702), a switching engine module 703, a CPU module 704, a packet detection module 705, a bit rate control module 708, an address table 706, a packet buffer 707, a MAC adding module 709, and a MAC deleting module 710.

[0189] The data packet from the downlink network interface module 701 enters the packet detection module 705; the packet detection module 705 detects whether the Ethernet MAC DA, Ethernet MAC SA, Ethernet length or frame type, visual network destination address DA, visual network source address SA, visual network data packet type and packet length of the data packet meet the requirements, and if they meet the requirements, the corresponding stream identifier (stream-id) is assigned; then, the MAC deletion module 710 subtracts the MAC DA, MAC SA, length or frame type (2 bytes) and enters the corresponding receiving buffer, otherwise it is discarded;

[0190] The downlink network interface module 701 detects the sending buffer of the port. If there is a packet, it obtains the Ethernet MAC DA of the corresponding terminal based on the visual network destination address DA of the packet, adds the Ethernet MAC DA of the terminal, the MACSA of the Ethernet protocol conversion gateway, and the Ethernet length or frame type, and sends it.

[0191] The functions of other modules in the Ethernet protocol conversion gateway are similar to those of the access switch.

[0192] terminal:

[0193] It mainly includes network interface module, business processing module and CPU module; for example, the set-top box mainly includes network interface module, audio and video encoding and decoding engine module, CPU module; the encoding board mainly includes network interface module, audio and video encoding engine module, CPU module; the memory mainly includes network interface module, CPU module and disk array module.

[0194] 1.3 The equipment in the metropolitan area network can be divided into two categories: node server, node switch, and metropolitan area server. Among them, the node switch mainly includes network interface module, switching engine module and CPU module; the metropolitan area server mainly includes network interface module, switching engine module and CPU module.

[0195] 2. Definition of Visual Network Data Packet

[0196] 2.1 Access Network Data Packet Definition

[0197] The data packet of the access network mainly includes the following parts: destination address (DA), source address (SA), reserved bytes, payload (PDU), and CRC.

[0198] As shown in the following table, the data packet of the access network mainly includes the following parts:

[0199] DA S Reserved Payload CRC

[0200] in:

[0201] The destination address (DA) consists of 8 bytes. The first byte indicates the type of data packet (such as various protocol packets, multicast data packets, unicast data packets, etc.), with a maximum of 256 possibilities. The second to sixth bytes are the metropolitan area network address, and the seventh and eighth bytes are the access network address.

[0202] The source address (SA) is also composed of 8 bytes and has the same definition as the destination address (DA).

[0203] The reserved bytes consist of 2 bytes;

[0204] The payload part has different lengths depending on the type of datagram. If it is a protocol packet, it is 64 bytes. If it is a single multicast data packet, it is 32+1024=1056 bytes. Of course, it is not limited to the above two types.

[0205] CRC consists of 4 bytes and its calculation method follows the standard Ethernet CRC algorithm.

[0206] 2.2 Definition of Metropolitan Area Network Data Packet

[0207] The topology of the metropolitan area network is a graph. There may be two or more connections between two devices, that is, there may be more than two connections between a node switch and a node server, a node switch and a node switch, and a node switch and a node server. However, the metropolitan area network address of a metropolitan area network device is unique. In order to accurately describe the connection relationship between metropolitan area network devices, a parameter: a label is introduced in the embodiment of the present invention to uniquely describe a metropolitan area network device.

[0208] The definition of labels in this manual is similar to the definition of labels in MPLS (Multi-Protocol Label Switch). Assuming that there are two connections between device A and device B, there are two labels for the data packet from device A to device B, and there are two labels for the data packet from device B to device A. Labels are divided into input labels and output labels. Assuming that the label of the data packet entering device A (input label) is 0x0000, the label of the data packet when leaving device A (output label) may become 0x0001. The access process of the metropolitan area network is a centralized access process, which means that the address allocation and label allocation of the metropolitan area network are dominated by the metropolitan area server, and the node switch and node server are only passively executed. This is different from the label allocation of MPLS, which is the result of mutual negotiation between the switch and the server.

[0209] As shown in the following table, the data packets of the metropolitan area network mainly include the following parts:

[0210] DA S Reserved Label Payload CRC

[0211] That is, destination address (DA), source address (SA), reserved byte (Reserved), label, payload (PDU), CRC. The label format can refer to the following definition: the label is 32 bits, of which the upper 16 bits are reserved and only the lower 16 bits are used. It is located between the reserved bytes and payload of the data packet.

[0212] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0213] It will be appreciated by those skilled in the art that the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0214] The embodiments of the present invention are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of the processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0215] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0216] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0217] Although the preferred embodiments of the present invention have been described, those skilled in the art may make other changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0218] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the elements.

[0219] The data processing method, the data processing device, the conference management and scheduling system and the computer-readable storage medium provided by the present invention are introduced in detail above. The principles and implementation methods of the present invention are explained in detail using specific examples. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for those skilled in the art, according to the idea of ​​the present invention, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A data processing method, characterized in that: Applied to a conference management and scheduling system, the conference management and scheduling system includes an interaction layer and a logic layer, the interaction layer includes a main thread and a task thread, and the method includes: The task thread obtains a first target service request from a message queue of the interaction layer; The task thread sends the first target service request to the logic layer; The task thread ends processing of the first target service request; The main thread receives the business processing result returned by the logic layer; The business processing result includes an identity identifier, a business code, and specific business data. The business processing result and the corresponding first target business request carry the same identity identifier. After the main thread receives the business processing result returned by the logic layer, the method further includes: The main thread determines, according to the identity carried by the business processing result, the first target business request corresponding to the business processing result; The main thread obtains the service type of the first target service request according to the first target service request.

2. The method according to claim 1, characterized in that: The method further comprises: When the main thread determines that the service type is the first service type, the service code is sent to the web layer, the state of the first target service request is changed from the waiting reply state to the processing success state, and the first target service request is deleted from the message queue; When the main thread determines that the business type is the second business type, the business code is sent to the web layer, the specific business data is inserted into the message queue of the web layer, the status of the first target business request is changed from the waiting reply status to the processing success status, and the first target business request is deleted from the message queue.

3. The method according to claim 2, characterized in that The interaction layer also includes a detection thread, and the method further includes: The detection thread determines whether there is a first target service request that meets a preset rule in the message queue of the interaction layer; In the case that there is the first target service request satisfying the preset rule, the detection thread determines the first target service request satisfying the preset rule as an abnormal service request; The detection thread generates an exception handling result according to the abnormal service request; The detection thread sends the exception processing result to the web layer, and deletes the first target service request that meets the preset rule from the message queue.

4. The method according to claim 3, characterized in that The method further comprises: The detection thread obtains the sending time of the first target service request; The detection thread determines whether there is a first target service request that meets a preset rule in the message queue of the interaction layer, including: The detection thread determines whether the difference between the sending time of the first target service request in the message queue of the interaction layer and the current time is greater than a preset time interval; When the difference between the sending time of the first target service request and the current time is greater than a preset time interval, the detection thread determines that the first target service request satisfies a preset rule.

5. The method according to claim 4, characterized in that After the task thread sends the first target service request to the logic layer, the method further includes: The task thread changes the state of the first target service request from the initial state to the waiting for reply state; The detection thread obtains the sending time of the first target service request, including: The detection thread obtains the sending time of the first target service request in the waiting reply state.

6. A conference management and scheduling system, characterized in that: The system comprises: An interaction layer and a logic layer, wherein the interaction layer includes a main thread and a task thread; The task thread is used to obtain the first target service request from the message queue of the interaction layer; The task thread is further used to send the first target service request to the logic layer; The task thread is further used to end the processing of the first target service request; The main thread is used to receive the business processing results returned by the logic layer; The business processing result includes an identity identifier, a business code, and specific business data, and the business processing result and the corresponding first target business request carry the same identity identifier; The main thread is further configured to determine the first target service request corresponding to the service processing result according to the identity carried by the service processing result; The main thread is further configured to obtain a service type of the first target service request according to the first target service request.

7. The system according to claim 6, characterized in that The main thread is further configured to, when the main thread determines that the service type is the first service type, send the service code to the web layer, change the state of the first target service request from the waiting reply state to the processing success state, and delete the first target service request from the message queue; The main thread is also used to send the business code to the web layer, insert the specific business data into the message queue of the web layer, change the status of the first target business request from the waiting reply status to the processing success status, and delete the first target business request from the message queue when the main thread determines that the business type is the second business type.

8. The system according to claim 7, characterized in that The interaction layer also includes a detection thread; The detection thread is used to determine whether there is a first target service request that meets a preset rule in the message queue of the interaction layer; In the case where there is the first target service request that satisfies the preset rule, the detection thread is further used to determine the first target service request that satisfies the preset rule as an abnormal service request; The detection thread is further used to generate an exception handling result according to the abnormal business request; The detection thread is further used to send the exception processing result to the web layer, and delete the first target business request that meets the preset rule from the message queue.

9. A data processing device, characterized in that: include: one or more processors; and One or more computer-readable storage media having instructions stored thereon, when executed by the one or more processors, enable the device to perform the data processing method according to any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that: The computer program stored therein enables the processor to execute the data processing method as described in any one of claims 1 to 5.