CN111431966A

CN111431966A - Service request processing method and device, electronic equipment and storage medium

Info

Publication number: CN111431966A
Application number: CN202010108884.8A
Authority: CN
Inventors: 邹斌斌; 贺传森; 王晓燕; 杨春晖
Original assignee: Visionvera Information Technology Co Ltd
Current assignee: Visionvera Information Technology Co Ltd
Priority date: 2020-02-21
Filing date: 2020-02-21
Publication date: 2020-07-17
Anticipated expiration: 2040-02-21
Also published as: CN111431966B

Abstract

The application provides a service request processing method, a service request processing device, electronic equipment and a storage medium, wherein the method comprises the following steps: receiving a service request sent by a target terminal, and determining a target autonomous server according to the service request; obtaining a target autonomous user account corresponding to the target autonomous server, wherein the target autonomous user account is the only one account which is created by the target autonomous server for a target system user account currently logged in by the target terminal in advance; sending the service request to the target autonomous server through the target autonomous user account; receiving response data aiming at the service request returned by the target autonomous server through the target autonomous user account; and sending the response data to the target terminal. Because one system user account is uniquely corresponding to one autonomous user account, the parallel processing of multi-user services can be realized, and the service processing performance of the client is obviously improved.

Description

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

Technical Field

The present invention relates to the field of data processing technologies, and in particular, to a method and an apparatus for processing a service request, an electronic device, and a storage medium.

Background

In the technical field of video networking communication, an autonomous server can receive a service request sent by a client, process the service request and return corresponding service data. In the above process, the client needs to complete the processing of the service request by using the autonomous user account created by the autonomous server, specifically, the service request is sent to the corresponding autonomous server through the autonomous user account, and the response data is obtained from the corresponding autonomous server through the autonomous user account. In a related technology, the number of system user accounts in the client is much larger than that of autonomous user accounts, and in a scenario of high concurrent service requests, the client cannot respond to service requests initiated by the multiple system user accounts in time, and service processing performance is extremely low.

Disclosure of Invention

The embodiment of the application provides a service request processing method and device, electronic equipment and a storage medium, and aims to improve the performance of a client for processing a service request.

A first aspect of an embodiment of the present application provides a method for processing a service request, where the method includes:

receiving a service request sent by a target terminal, and determining a target autonomous server according to the service request;

obtaining a target autonomous user account corresponding to the target autonomous server, wherein the target autonomous user account is the only one account which is created by the target autonomous server for a target system user account currently logged in by the target terminal in advance;

sending the service request to the target autonomous server through the target autonomous user account;

receiving response data aiming at the service request returned by the target autonomous server through the target autonomous user account;

and sending the response data to the target terminal.

Optionally, obtaining a target autonomous user account corresponding to the target autonomous server includes:

acquiring a plurality of autonomous user accounts which are created by all autonomous servers for the target system user account in advance, wherein each autonomous server creates an autonomous user account for each system user account;

determining an autonomous user account corresponding to the target autonomous server in the plurality of autonomous user accounts as the target autonomous user account;

activating the target autonomous user account;

sending the service request to the target autonomous server through the target autonomous user account, including:

sending the service request to the target autonomous server through the target autonomous user account in an activated state;

receiving, by the target autonomous user account, response data for the service request returned by the target autonomous server, where the response data includes:

and receiving response data which is returned by the target autonomous server and aims at the service request through the target autonomous user account in the activated state.

Optionally, before sending the service request to the target autonomous server through the target autonomous user account, the method further includes:

obtaining an idle transaction credential from the target autonomous user account, the transaction credential being used to uniquely identify a service request in the target autonomous user account;

adding the transaction credential to the transaction request;

sending the response data to the target terminal, including:

and sending the response data to the target terminal when the credential carried in the response data is the same as the transaction credential carried in the service request.

obtaining a free transaction certificate from a transaction certificate list, wherein the transaction certificate is used for uniquely identifying a service request;

adding the transaction credential to the transaction request;

sending the response data to the target terminal, including:

and sending the response data to the target terminal when the credential carried in the response data is the same as the transaction credential in the service request.

Optionally, receiving a service request sent by a target terminal includes:

receiving a plurality of service requests sent by a target terminal, wherein the service requests are initiated by aiming at the same target autonomous server within a preset time period;

adding the transaction credential to the transaction request, including:

obtaining a plurality of different transaction receipts, and respectively adding the transaction receipts into the service requests according to a one-to-one rule;

sending the plurality of business requests added with the business credentials to the target autonomous server through the target autonomous user account;

receiving response data which is returned by the target autonomous server and aims at the plurality of service requests through the target autonomous user account;

sending the response data to the target terminal, including:

and sending the response data to the target terminal according to the corresponding relation between the transaction credentials in the response data and the transaction credentials in the plurality of service requests.

A second aspect of the present application provides a method for processing a service request, where the method includes:

receiving a service request sent by a background server of a client through a target autonomous user account, wherein the service request is sent to the background server by a target terminal; the target autonomous user account is the only one account which is created in the background server for the target system user account currently logged in by the target terminal in advance;

obtaining response data of the service request;

obtaining the transaction credential carried in the service request, and adding the transaction credential to the response data;

and sending the response data to the background server through the target autonomous user account so that the background server sends the response data to the target terminal.

A third aspect of the present embodiment provides a service request processing apparatus, where the apparatus includes:

the first receiving module is used for receiving a service request sent by a target terminal and determining a target autonomous server according to the service request;

the first obtaining module is used for obtaining a target autonomous user account corresponding to the target autonomous server, wherein the target autonomous user account is the only one account which is created by the target autonomous server for a target system user account currently logged in by the target terminal in advance;

the first sending module is used for sending the service request to the target autonomous server through the target autonomous user account;

the second receiving module is used for receiving response data which is returned by the target autonomous server and aims at the service request through the target autonomous user account;

and the second sending module is used for sending the response data to the target terminal.

Optionally, the first obtaining module includes:

the first obtaining submodule is used for obtaining a plurality of autonomous user accounts which are created by all autonomous servers for the target system user account in advance, and each autonomous server creates an autonomous user account for each system user account;

the determining module is used for determining an autonomous user account corresponding to the target autonomous server in the plurality of autonomous user accounts as the target autonomous user account;

the activation module is used for activating the target autonomous user account;

the first transmitting module includes:

the first sending sub-module is used for sending the service request to the target autonomous server through the target autonomous user account in an activated state;

the second receiving module includes:

and the second receiving submodule is used for receiving response data which is returned by the target autonomous server and aims at the service request through the target autonomous user account in an activated state.

Optionally, the apparatus further comprises:

a second obtaining module, configured to obtain an idle transaction credential from the target autonomous user account, where the transaction credential is used to uniquely identify a service request in the target autonomous user account;

a first adding module, configured to add the transaction credential to the service request;

the second sending module includes:

and the second sending submodule is used for sending the response data to the target terminal when the credential carried in the response data is the same as the transaction credential carried in the service request.

Optionally, the apparatus further comprises:

a third obtaining module, configured to obtain an idle transaction credential from a transaction credential list, where the transaction credential is used to uniquely identify a service request;

the second adding module is used for adding the transaction credential into the business request;

the second sending module includes:

and a third sending submodule, configured to send the response data to the target terminal when a credential carried in the response data is the same as a transaction credential in the service request.

Optionally, the first receiving module includes:

the third receiving submodule is used for receiving a plurality of service requests sent by a target terminal, wherein the service requests are initiated by aiming at the same target autonomous server within a preset time period;

the first adding module or the second adding module comprises:

the adding submodule is used for obtaining a plurality of different transaction receipts and respectively adding the transaction receipts into the service requests according to a one-to-one rule;

the first transmitting module includes:

a fourth sending submodule, configured to send the plurality of service requests to which the transaction credentials are added to the target autonomous server through the target autonomous user account;

the second receiving module includes:

a fourth receiving submodule, configured to receive, through the target autonomous user account, response data, which is returned by the target autonomous server and is for the plurality of service requests, where the response data is sent to the target autonomous server;

the second sending module includes:

and a fifth sending sub-module, configured to send the response data to the target terminal according to a correspondence between the transaction credential in the response data and the transaction credential in the multiple service requests.

A fourth aspect of the embodiments of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the steps of the method according to the first aspect of the present application when executed.

A fifth aspect of embodiments of the present application provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, performs the steps in the method according to the first aspect of the present application.

A sixth aspect of the present embodiment provides a service request processing apparatus, including:

the third receiving module is used for receiving a service request sent by a background server of the client through a target autonomous user account, wherein the service request is sent to the background server by a target terminal; the target autonomous user account is the only one account which is created in the background server for the target system user account currently logged in by the target terminal in advance;

a fourth obtaining module, configured to obtain response data of the service request;

a fifth obtaining module, configured to obtain a transaction credential carried in the service request, and add the transaction credential to the response data;

and the third sending module is used for sending the response data to the background server through the target autonomous user account so that the background server sends the response data to the target terminal.

A seventh aspect of the embodiments of the present application provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the steps of the method according to the second aspect of the present application when executed.

An eighth aspect of embodiments of the present application provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps in the method according to the second aspect of the present application.

The application provides a service request processing method, which comprises the steps of firstly receiving a service request sent by a target terminal, determining a target autonomous server according to the service request, obtaining a unique target autonomous user account established by the target autonomous server under a target system user account currently logged in by the target terminal, then sending the service request to the target autonomous server through the target autonomous user account, processing the service request by the target autonomous server, simultaneously receiving response data returned by the target autonomous server through the target autonomous user account, and sending the response data to the target terminal. The account established by the autonomous server under the system user account is the only account, so that each system user account only corresponds to one autonomous user account and cannot share the autonomous user account with other system user accounts, therefore, under the condition that a plurality of different system user accounts simultaneously initiate service requests, the parallel processing of the service requests of the multi-system user accounts can be realized through the autonomous user account corresponding to each system user account, the service processing efficiency can be effectively improved, the condition of high concurrent requests can be dealt with, and compared with the mode that the multi-system user accounts share one autonomous user account in the related technology, the service request processing method can obviously improve the service processing performance of the client.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

FIG. 1 is a schematic diagram of an implementation environment shown in an embodiment of the present application;

fig. 2 is a flowchart illustrating a service request processing method according to an embodiment of the present application;

fig. 3 is a flowchart illustrating another service request processing method according to an embodiment of the present application;

fig. 4 is a schematic overall flow chart illustrating a service request processing according to an embodiment of the present application;

fig. 5 is a schematic overall flow chart illustrating another service request processing according to an embodiment of the present application;

fig. 6 is a block diagram illustrating a structure of a service request processing apparatus according to an embodiment of the present application;

fig. 7 is a block diagram illustrating another service request processing apparatus according to an embodiment of the present application;

FIG. 8 is a schematic networking diagram of a video network, according to an embodiment of the present application;

fig. 9 is a schematic diagram illustrating a hardware structure of a node server according to an embodiment of the present application;

fig. 10 is a schematic diagram illustrating a hardware structure of an access switch according to an embodiment of the present application;

fig. 11 is a schematic diagram of a hardware structure of an ethernet protocol conversion gateway according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Fig. 1 is a schematic diagram of an implementation environment according to an embodiment of the present application. In fig. 1, a background server of a client communicates and interacts with an autonomous server through an autonomous user account, and a user can log in a system user account through a terminal client installed on a terminal device (e.g., a mobile phone, a computer, etc.) carried by the user, and communicate and interact with the client background server through the system user account.

In the related art, a background server of a client processes service requests initiated by a plurality of system user accounts by using a rule that the plurality of system user accounts correspond to one autonomous user account, and although the plurality of system user accounts can initiate a plurality of service requests simultaneously, a serial processing mode is still adopted in the implementation of a bottom layer, that is: when the last service request is processed, the next service request can be processed. Therefore, the service processing mode in the related art is low in efficiency, the service processing performance of the client is extremely low, and the scene of high concurrent service requests cannot be effectively responded.

In order to overcome the above problems, the present application provides a service request processing method, which is applied to a background server of the client in fig. 1. Fig. 2 is a flowchart illustrating a service request processing method according to an embodiment of the present application. Referring to fig. 2, the service request processing method of the present application may include the following steps:

step S11: and receiving a service request sent by a target terminal, and determining a target autonomous server according to the service request.

In this embodiment, the client includes a background server and a terminal client, as shown in fig. 2, a user may install the terminal client on a terminal device (e.g., a mobile phone, a computer, etc.) carried by the user, and log in a pre-created system user account through the terminal client. After logging in, a user can initiate a service request, wherein the service request needs to specify an autonomous server for processing the service request, and then the terminal device sends the service request to a background server of a client.

In step S11, the user initiates a service request on the target terminal through the user account of the target system, and specifies a target autonomous server for processing the service request in the service request, and then the target terminal sends the service request to the background server of the client, and the background server sends the service request to the target autonomous server.

Step S12: and obtaining a target autonomous user account corresponding to the target autonomous server, wherein the target autonomous user account is the only one account which is created by the target autonomous server for a target system user account currently logged in by the target terminal in advance.

In this embodiment, after receiving a service request, a background server determines a target autonomous server according to the service request, and then obtains a unique autonomous user account created by the target autonomous server under a target system user account, that is: a target autonomous user account.

Step S13: and sending the service request to the target autonomous server through the target autonomous user account.

In this embodiment, the target autonomous user account is an account used by a background server of the client when each autonomous server performs service processing. And after the background server obtains the target autonomous user account, the background server can send the service request to the target autonomous server through the target autonomous user account.

Step S14: and receiving response data aiming at the service request returned by the target autonomous server through the target autonomous user account.

In this embodiment, the target autonomous server receives the service request, processes the service request, and sends the processed result as response data to the background server through the target autonomous user account.

Step S15: and sending the response data to the target terminal.

In this embodiment, after obtaining the response data, the background server sends the response data to the target terminal.

In this embodiment, when a user initiates a service request through a system user account, the user may not designate an autonomous server for processing the service request, and when receiving the service request, the background server automatically determines the autonomous server for processing the service request according to the type of the service request (for example, a plurality of types are designated for the service request in advance, and different autonomous servers respectively process the service requests of the respective types), and sends the service request to the autonomous server.

In this embodiment, the same user may register multiple system user accounts, may log in multiple system user accounts on multiple terminal clients, and may log in only one system user account on the same terminal client.

Illustratively, a user a wants to process a service request X through the autonomous server 1 (for example, obtain data of a certain service under the autonomous server 1), the user a may log in a pre-registered system user account through a terminal client installed on a mobile phone or a computer, initiate a service request X through the system user account (the service request X carries the autonomous server 1 selected by the user), and send the service request X to a background server, the background server determines a target server as the autonomous server 1 according to the service request X after receiving the service request X, obtains a unique autonomous user account previously created by the autonomous server 1 under the system user account currently logged in by the user a, sends the service request X to the autonomous server 1 through the autonomous user account, the autonomous server 1 processes the service request X after receiving the service request X, and taking the processing result as response data Y, sending the response data Y to the background server through the autonomous user account, sending the response data Y to a system user account currently logged in by the user A through the background server, and simultaneously displaying the response data Y on a terminal interface of the user A for the user A to check.

When the service request is processed by the service request processing method provided by the embodiment of the application, firstly, the service request sent by the target terminal is received, the target autonomous server is determined according to the service request, the only one target autonomous user account created by the target autonomous server under the target system user account currently logged in by the target terminal is obtained, then, the service request is sent to the target autonomous server through the target autonomous user account, the service request is processed by the target autonomous server, meanwhile, the response data returned by the target autonomous server is received through the target autonomous user account, and the response data is sent to the target terminal. The account established by the autonomous server under the system user account is the only account, so that each system user account only corresponds to one autonomous user account and cannot share the autonomous user account with other system user accounts, therefore, under the condition that a plurality of different system user accounts simultaneously initiate service requests, the parallel processing of the service requests of the multi-system user accounts can be realized through the autonomous user account corresponding to each system user account, the service processing efficiency can be effectively improved, the condition of high concurrent requests can be dealt with, and compared with the mode that the multi-system user accounts share one autonomous user account in the related technology, the service request processing method can obviously improve the service processing performance of the client.

With reference to the foregoing embodiments, in one implementation manner, the present application further provides a manner of obtaining a target autonomous user account. Specifically, step S12 may include:

activating the target autonomous user account;

accordingly, step S13 includes:

accordingly, step S14 includes:

In this embodiment, all the autonomous servers create a unique autonomous user account under each system user account in advance, so that each system user account corresponds to all the autonomous user accounts of the autonomous servers, and the background server can be switched to the required autonomous user account at any time according to the service requirement.

In this embodiment, only one of the plurality of autonomous user accounts corresponding to each system user account is in an activated state at the same time, and when a certain autonomous user account is activated, the other remaining autonomous user accounts will automatically fail. The system user account can apply for processing service request from the autonomous server through the activated autonomous user account.

In the process, after the background server determines the target autonomous server, a target autonomous user account created by the target autonomous server is determined in a plurality of autonomous user accounts corresponding to a target system user account, and the target autonomous user account is activated; and then, sending the service request to the target autonomous server through the target autonomous user account in the activated state, and receiving response data returned by the target autonomous server through the target autonomous user account in the activated state.

In this embodiment, all autonomous servers create a unique autonomous user account under each system user account in advance, so that each system user account corresponds to all autonomous user accounts of the autonomous servers, and the background server can switch to a required autonomous user account at any time according to the selection of a user, thereby meeting the diversified requirements of the user and effectively improving the service processing efficiency.

With reference to the foregoing embodiments, in an implementation manner, before the background server sends the service request to the autonomous server, a transaction credential may be further added to each service request, so as to uniquely identify one service request, thereby implementing concurrent processing of multitask requests. Specifically, before the service request is sent to the target autonomous server through the target autonomous user account, the service request processing method of the present application further includes:

adding the transaction credential to the transaction request;

accordingly, step S15 may include:

In this embodiment, each autonomous user account may preset a plurality of different transaction credentials for identifying a plurality of service requests initiated by a system user account corresponding to the autonomous user account.

Illustratively, the autonomous user account 1 corresponds to the system user account 1, and the autonomous user account 1 has 50 transaction credentials, which are transaction credentials 1-50, and are all in an idle state. Supposing that a system user account 1 continuously initiates 3 service requests which are respectively service requests 1-3, when receiving the service request 1, a background server obtains a transaction credential 1 from the transaction credentials 1-50, adds the transaction credential 1 into the service request 1, and then sends the service request 1 to an autonomous server through an autonomous user account 1; when receiving the service request 2, the background server continues to obtain the transaction credential 2 from the transaction credentials 1-50, adds the transaction credential 2 to the service request 2, and then sends the service request 2 to the autonomous server through the autonomous user account 1, and since the service request 1 and the service request 2 are both added with identification distinction, the service request 2 is not sent to the autonomous server until the response data of the service request 1 is received, and similarly, the service request 3 is also processed according to the rule.

Accordingly, after processing the service request, the autonomous server will add the transaction credential in the service request to the response data. After the background server obtains the response data, the transaction credentials in the response data are analyzed and obtained, so that the service request corresponding to the response data can be determined, and the response data are sent to the corresponding system user account.

In this embodiment, the number of transaction credentials of each autonomous user account is limited, and therefore, a time-sharing manner is adopted, that is, the same transaction credential can only be used for identifying one task request at the same time, and until the task request is processed, the transaction credential cannot be used for identifying other task requests. After receiving the response data, the background server returns the response data through the original channel (the autonomous user account used when the service request is sent), so that even if the same transaction credentials exist in different autonomous user accounts, the situation that the response data is sent to the wrong system user account cannot be caused.

In this embodiment, when processing a service request initiated by a corresponding system user account, an autonomous user account only needs to add an identifier to the service request, and then sends the service request to the autonomous server, and does not need to wait until receiving response data of a previous service request, and then sends the current service request, so that concurrent processing of multiple service requests in the same system user account can be realized, and the service processing efficiency is effectively improved.

With reference to the foregoing embodiments, in an implementation manner, the transaction credential may also be set by a background server, and the background server may also preset a plurality of different transaction credentials, and adopt a time-sharing mode. Specifically, before sending the service request to the target autonomous server through the target autonomous user account, the service request processing method of the present application may further include:

adding the transaction credential to the transaction request;

accordingly, step S15 may include:

In this embodiment, the transaction credentials are set by the server, and the server uniformly sets a plurality of different transaction credentials, so that the transaction credentials can be managed more conveniently, and the processing efficiency of the service is further improved. With respect to the specific use of the transaction document, reference may be made to the foregoing description, and the application is not limited thereto.

With the above embodiments, in an implementation manner, a same system user account may continuously initiate service requests for different autonomous servers, which causes the background server to frequently switch the autonomous user accounts, thereby affecting the service processing efficiency. Thus, the following may be taken:

receiving a service request sent by a target terminal, may include:

adding the transaction credential to the transaction request may include:

sending the service request to the target autonomous server through the target autonomous user account may include:

receiving, by the target autonomous user account, response data for the service request returned by the target autonomous server, where the response data may include:

sending the response data to the target terminal may include:

In this embodiment, the background server is provided with a service request list for each system user account, and is configured to cache a plurality of service requests initiated by the system user account according to a time sequence. If a system user account respectively and continuously initiates a plurality of service requests for different autonomous servers, for example, the 1 st service request in the service request list is for the autonomous server 1, the 2 nd service request is for the autonomous server 2, the 3 rd service request is for the autonomous server 3, the 4 th service request is for the autonomous server 1, and the 5 th service request is for the autonomous server 2, then the background server may first obtain the 1 st service request and the 4 th service request for centralized processing, and after that, obtain the 2 nd service request and the 5 th service request for centralized processing, and sequentially process the subsequent service requests according to the rule.

In this embodiment, when the service requests are processed in a centralized manner, each service request may be sequentially obtained, the transaction credential may be added, and then the transaction credential may be sent to the autonomous server, or a plurality of different transaction credentials may be obtained, and the transaction credential may be added to each service request in a one-to-one manner, and then the transaction credential may be sent to the autonomous server in a data packet manner.

In this embodiment, a plurality of service requests initiated by the same target autonomous server within a preset time period are obtained for the system user account and are processed in a centralized manner, so that parallel processing of the plurality of service requests of the same system user account is realized, the situation that the background server frequently switches the autonomous user accounts can be avoided, and the processing efficiency of the service requests is effectively improved.

The application also provides a service request processing method, which is applied to the autonomous server in fig. 1. Fig. 3 is a flowchart illustrating another service request processing method according to an embodiment of the present application. Referring to fig. 3, the service request processing method of the present application may include the following steps:

step S21: receiving a service request sent by a background server of a client through a target autonomous user account, wherein the service request is sent to the background server by a target terminal; the target autonomous user account is the only one account which is created in the background server for the target system user account currently logged in by the target terminal in advance;

step S22: obtaining response data of the service request;

step S23: obtaining the transaction credential carried in the service request, and adding the transaction credential to the response data;

step S24: and sending the response data to the background server through the target autonomous user account so that the background server sends the response data to the target terminal.

In this embodiment, after receiving the service request, the autonomous server processes the service request, generates response data according to a processing result, obtains a transaction credential carried in the service request, adds the transaction credential to the response data, and finally sends the response data to the background server. Specific procedures can be referred to the above, and the present application is not specifically limited thereto.

Fig. 4 is a schematic overall flow chart of service request processing according to an embodiment of the present application. Fig. 5 is a schematic overall flow chart of another service request processing shown in an embodiment of the present application. The service request processing method of the present application will be described in conjunction with fig. 4 and 5 as a whole.

In fig. 4, the system, that is, the background server mentioned in this application (see fig. 1 in detail), system user a, system user B, system user C, and the like are all system user accounts registered by users, autonomous user a is an autonomous user account created by autonomous server 1 under system user a, autonomous user B is an autonomous user account created by autonomous server 1 under system user B (the autonomous user account created by autonomous server 1 under system user C is not shown in fig. 4), and autonomous user C is an autonomous user account created by autonomous server 2 under system user C (the autonomous user account created by autonomous server 2 under system user A, B is not shown in fig. 4). The certificate is the transaction certificate mentioned in the present application, and the service request mentioned in the present application. In fig. 4, when processing a service initiated by a system user, the system implements concurrent processing of tasks of multiple system users in a manner that one system user corresponds to one autonomous user, and adds credentials to each service one by one for multiple services initiated by one system user, thereby implementing concurrent processing of multiple services within the same system user. After the system takes the response data returned by the autonomous server, matching each item of response data with the corresponding business according to the corresponding relation between the credential in the response data and the credential in the business.

For example, referring to fig. 5, it is assumed that a system user continuously initiates a service a and a service b, the system adds a credential 1 to the service a, obtains a service packet 1, adds a credential 2 to the service b, obtains a service packet 2, then sends the service packet 1 and the service packet 2 to an autonomous server through the autonomous user, and after receiving a response packet, the system parses the response packet, determines that the response packet is the response packet of the service a if the credential carried in the response packet is the credential 1, and determines that the response packet is the response packet of the service b if the credential carried in the response packet is the credential 2.

In this embodiment, concurrent processing of tasks of multiple system users is implemented in a manner that one system user corresponds to one autonomous user, and concurrent processing of multiple services within the same system user is implemented by adopting a rule of adding different credentials to different services.

By adopting the service request processing method, the multi-user multi-task parallel processing of the client (comprising the background server of the client and the terminal client) is realized, the service processing performance of the client is improved, and on the basis, the client can also be applied to the limit performance test of the autonomous server, for example, the number of autonomous users which can be processed by the test server in a concurrent manner. Compared with the prior art that when multiple system users share one autonomous user, the number of the autonomous users still cannot meet the test requirements of the autonomous server when a client reaches a limit (the number of the processed system users reaches an upper limit). Therefore, the client adopting the service request processing method can provide various test scenes, for example, the limit performance of the server can be effectively tested in a super-large scale conference scene in the video internet.

It should be noted that, for simplicity of description, the method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the illustrated order of acts, as some steps may occur in other orders or concurrently in accordance with the embodiments of the present invention. Further, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred and that no particular act is required to implement the invention.

The present application further provides a service request processing apparatus 600, which is applied to the backend server in fig. 1, as shown in fig. 6. Fig. 6 is a block diagram illustrating a structure of a service request processing apparatus according to an embodiment of the present application. Referring to fig. 6, the apparatus 600 may include:

a first receiving module 601, configured to receive a service request sent by a target terminal, and determine a target autonomous server according to the service request;

a first obtaining module 602, configured to obtain a target autonomous user account corresponding to the target autonomous server, where the target autonomous user account is the only one account that is created by the target autonomous server in advance for a target system user account currently logged in the target terminal;

a first sending module 603, configured to send the service request to the target autonomous server through the target autonomous user account;

a second receiving module 604, configured to receive, through the target autonomous user account, response data, which is returned by the target autonomous server and is addressed to the service request;

a second sending module 605, configured to send the response data to the target terminal.

Optionally, the first obtaining module 602 includes:

the first sending module 603 includes:

the second receiving module 604 comprises:

Optionally, the apparatus 600 further comprises:

the second sending module 605 includes:

Optionally, the apparatus 600 further comprises:

the second sending module 605 includes:

Optionally, the first receiving module 601 includes:

the first adding module or the second adding module comprises:

the first sending module 603 includes:

the second receiving module 604 comprises:

the second sending module 605 includes:

Based on the same inventive concept, the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the electronic device implements the steps in the service request processing method according to any of the embodiments of the present application.

Based on the same inventive concept, the present application provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the steps in the service request processing method according to any of the above embodiments of the present application.

The present application also provides another service request processing apparatus 700, which is applied to the autonomous server in fig. 1, as shown in fig. 7. Fig. 7 is a block diagram illustrating another service request processing apparatus according to an embodiment of the present application. Referring to fig. 7, the apparatus 700 may include:

a third receiving module 701, configured to receive a service request sent by a background server of a client through a target autonomous user account, where the service request is sent to the background server by a target terminal; the target autonomous user account is the only one account which is created in the background server for the target system user account currently logged in by the target terminal in advance;

a fourth obtaining module 702, configured to obtain response data of the service request;

a fifth obtaining module 703, configured to obtain a transaction credential carried in the service request, and add the transaction credential to the response data;

a third sending module 704, configured to send the response data to the background server through the target autonomous user account, so that the background server sends the response data to the target terminal.

For the device embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, refer to the partial description of the method embodiment.

The video networking is an important milestone for network development, is a real-time network, can realize high-definition video real-time transmission, and pushes a plurality of internet applications to high-definition video, and high-definition faces each other.

The video networking adopts a real-time high-definition video exchange technology, can integrate required services such as dozens of services of video, voice, pictures, characters, communication, data and the like on a system platform on a network platform, such as high-definition video conference, video monitoring, intelligent monitoring analysis, emergency command, digital broadcast television, delayed television, network teaching, live broadcast, VOD on demand, television mail, Personal Video Recorder (PVR), intranet (self-office) channels, intelligent video broadcast control, information distribution and the like, and realizes high-definition quality video broadcast through a television or a computer.

To better understand the embodiments of the present invention, the following description refers to the internet of view:

some of the technologies applied in the video networking are as follows:

network Technology (Network Technology)

Network technology innovation in video networking has improved over traditional Ethernet (Ethernet) to face the potentially enormous video traffic on the network. Unlike pure network Packet Switching (Packet Switching) or network circuit Switching (circuit Switching), the Packet Switching is adopted by the technology of the video networking to meet the Streaming requirement. The video networking technology has the advantages of flexibility, simplicity and low price of packet switching, and simultaneously has the quality and safety guarantee of circuit switching, thereby realizing the seamless connection of the whole network switching type virtual circuit and the data format.

Switching Technology (Switching Technology)

The video network adopts two advantages of asynchronism and packet switching of the Ethernet, eliminates the defects of the Ethernet on the premise of full compatibility, has end-to-end seamless connection of the whole network, is directly communicated with a user terminal, and directly bears an IP data packet. The user data does not require any format conversion across the entire network. The video networking is a higher-level form of the Ethernet, is a real-time exchange platform, can realize the real-time transmission of the whole-network large-scale high-definition video which cannot be realized by the existing Internet, and pushes a plurality of network video applications to high-definition and unification.

Server Technology (Server Technology)

The server technology on the video networking and unified video platform is different from the traditional server, the streaming media transmission of the video networking and unified video platform is established on the basis of connection orientation, the data processing capacity of the video networking and unified video platform is independent of flow and communication time, and a single network layer can contain signaling and data transmission. For voice and video services, the complexity of video networking and unified video platform streaming media processing is much simpler than that of data processing, and the efficiency is greatly improved by more than one hundred times compared with that of a traditional server.

Storage Technology (Storage Technology)

The super-high speed storage technology of the unified video platform adopts the most advanced real-time operating system in order to adapt to the media content with super-large capacity and super-large flow, the program information in the server instruction is mapped to the specific hard disk space, the media content is not passed through the server any more, and is directly sent to the user terminal instantly, and the general waiting time of the user is less than 0.2 second. The optimized sector distribution greatly reduces the mechanical motion of the magnetic head track seeking of the hard disk, the resource consumption only accounts for 20% of that of the IP internet of the same grade, but concurrent flow which is 3 times larger than that of the traditional hard disk array is generated, and the comprehensive efficiency is improved by more than 10 times.

Network Security Technology (Network Security Technology)

The structural design of the video network completely eliminates the network security problem troubling the internet structurally by the modes of independent service permission control each time, complete isolation of equipment and user data and the like, generally does not need antivirus programs and firewalls, avoids the attack of hackers and viruses, and provides a structural carefree security network for users.

Service Innovation Technology (Service Innovation Technology)

The unified video platform integrates services and transmission, and is not only automatically connected once whether a single user, a private network user or a network aggregate. The user terminal, the set-top box or the PC are directly connected to the unified video platform to obtain various multimedia video services in various forms. The unified video platform adopts a menu type configuration table mode to replace the traditional complex application programming, can realize complex application by using very few codes, and realizes infinite new service innovation.

Networking of the video network is as follows:

the video network is a centralized control network structure, and the network can be a tree network, a star network, a ring network and the like, but on the basis of the centralized control node, the whole network is controlled by the centralized control node in the network.

Fig. 8 is a networking diagram of a video network according to an embodiment of the present application. As shown in fig. 8, the video network is divided into an access network and a metropolitan network.

The devices of the access network part can be mainly classified into 3 types: node server, access switch, terminal (including various set-top boxes, coding boards, memories, etc.). The node server is connected to an access switch, which may be connected to a plurality of terminals and may be connected to an ethernet network.

The node server is a node which plays a centralized control function in the access network and can control the access switch and the terminal. The node server can be directly connected with the access switch or directly connected with the terminal.

Similarly, devices of the metropolitan network portion may also be classified into 3 types: a metropolitan area server, a node switch and a node server. The metro server is connected to a node switch, which may be connected to a plurality of node servers.

The node server is a node server of the access network part, namely the node server belongs to both the access network part and the metropolitan area network part.

The metropolitan area server is a node which plays a centralized control function in the metropolitan area network and can control a node switch and a node server. The metropolitan area server can be directly connected with the node switch or directly connected with the node server.

Therefore, the whole video network is a network structure with layered centralized control, and the network controlled by the node server and the metropolitan area server can be in various structures such as tree, star and ring.

The access network part can form a unified video platform (the part in the dotted circle), and a plurality of unified video platforms can form a video network; each unified video platform may be interconnected via metropolitan area and wide area video networking.

Video networking device classification

1.1 devices in the video network of the embodiment of the present invention can be mainly classified into 3 types: servers, switches (including ethernet gateways), terminals (including various set-top boxes, code boards, memories, etc.). The video network as a whole can be divided into a metropolitan area network (or national network, global network, etc.) and an access network.

1.2 wherein the devices of the access network part can be mainly classified into 3 types: node servers, access switches (including ethernet gateways), terminals (including various set-top boxes, code boards, memories, etc.).

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

a node server:

fig. 9 is a schematic diagram illustrating a hardware structure of a node server according to an embodiment of the present application. As shown in fig. 9, the system mainly includes a network interface module 201, a switching engine module 202, a CPU module 203, and a disk array module 204;

the network interface module 201, the CPU module 203, and the disk array module 204 all enter the switching engine module 202; the switching engine module 202 performs an operation of looking up the address table 205 on the incoming packet, thereby obtaining the direction information of the packet; and stores the packet in a queue of the corresponding packet buffer 206 based on the packet's steering information; if the queue of the packet buffer 206 is nearly full, it is discarded; the switching engine module 202 polls all packet buffer queues for forwarding if the following conditions are met: 1) the port send buffer is not full; 2) the queue packet counter is greater than zero. The disk array module 204 mainly implements control over the hard disk, including initialization, read-write, and other operations on the hard disk; the CPU module 203 is mainly responsible for protocol processing with an access switch and a terminal (not shown in the figure), configuring an address table 205 (including a downlink protocol packet address table, an uplink protocol packet address table, and a data packet address table), and configuring the disk array module 204.

The access switch:

fig. 10 is a schematic diagram illustrating a hardware structure of an access switch according to an embodiment of the present application. As shown in fig. 10, the network interface module (downlink network interface module 301, uplink network interface module 302), switching engine module 303 and CPU module 304 are mainly included;

wherein, the packet (uplink data) coming from the downlink network interface module 301 enters the packet detection module 305; the packet detection module 305 detects whether the Destination Address (DA), the Source Address (SA), the packet type, and the packet length of the packet meet the requirements, and if so, allocates a corresponding stream identifier (stream-id) and enters the switching engine module 303, otherwise, discards the stream identifier; the packet (downstream data) coming from the upstream network interface module 302 enters the switching engine module 303; the incoming data packet of the CPU module 304 enters the switching engine module 303; the switching engine module 303 performs an operation of looking up the address table 306 on the incoming packet, thereby obtaining the direction information of the packet; if the packet entering the switching engine module 303 is from the downstream network interface to the upstream network interface, the packet is stored in the queue of the corresponding packet buffer 307 in association with the stream-id; if the queue of the packet buffer 307 is nearly full, it is discarded; if the packet entering the switching engine module 303 is not from the downlink network interface to the uplink network interface, the data packet is stored in the queue of the corresponding packet buffer 307 according to the guiding information of the packet; if the queue of the packet buffer 307 is nearly full, it is discarded.

The switching engine module 303 polls all packet buffer queues, which in this embodiment of the present invention is divided into two cases:

if the queue is from the downlink network interface to the uplink network interface, the following conditions are met for forwarding: 1) the port send buffer is not full; 2) the queued packet counter is greater than zero; 3) obtaining a token generated by a code rate control module;

if the queue is not from the downlink network interface to the uplink network interface, the following conditions are met for forwarding: 1) the port send buffer is not full; 2) the queue packet counter is greater than zero.

The rate control module 208 is configured by the CPU module 204, and generates tokens for packet buffer queues from all downstream network interfaces to upstream network interfaces at programmable intervals to control the rate of upstream forwarding.

The CPU module 304 is mainly responsible for protocol processing with the node server, configuration of the address table 306, and configuration of the code rate control module 308.

Ethernet protocol conversion gateway：

Fig. 11 is a schematic diagram of a hardware structure of an ethernet protocol conversion gateway according to an embodiment of the present application. As shown in fig. 11, the system mainly includes a network interface module (a downlink network interface module 401 and an uplink network interface module 402), a switching engine module 403, a CPU module 404, a packet detection module 405, a rate control module 408, an address table 406, a packet buffer 407, a MAC adding module 409, and a MAC deleting module 410.

Wherein, the data packet coming from the downlink network interface module 401 enters the packet detection module 405; the packet detection module 405 detects whether the ethernet MAC DA, the ethernet MAC SA, the ethernet length or frame type, the video network destination address DA, the video network source address SA, the video network packet type, and the packet length of the packet meet the requirements, and if so, allocates a corresponding stream identifier (stream-id); then, the MAC deletion module 410 subtracts MAC DA, MAC SA, length or frame type (2byte) and enters the corresponding receiving buffer, otherwise, discards it;

the downlink network interface module 401 detects the sending buffer of the port, and if there is a packet, obtains the ethernet MAC DA of the corresponding terminal according to the destination address DA of the packet, adds the ethernet MAC DA of the terminal, the MACSA of the ethernet coordination gateway, and the ethernet length or frame type, and sends the packet.

The other modules in the ethernet protocol gateway function similarly to the access switch.

A terminal:

the system mainly comprises a network interface module, a service processing module and a CPU module; for example, the set-top box mainly comprises a network interface module, a video and audio coding and decoding engine module and a CPU module; the coding board mainly comprises a network interface module, a video and audio coding engine module and a CPU module; the memory mainly comprises a network interface module, a CPU module and a disk array module.

1.3 devices of the metropolitan area network part can be mainly classified into 2 types: node server, node exchanger, metropolitan area server. The node switch mainly comprises a network interface module, a switching engine module and a CPU module; the metropolitan area server mainly comprises a network interface module, a switching engine module and a CPU module.

2. Video networking packet definition

2.1 Access network packet definition

The data packet of the access network mainly comprises the following parts: destination Address (DA), Source Address (SA), reserved bytes, payload (pdu), CRC.

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

DA

SA

Reserved

Payload

CRC

wherein:

the Destination Address (DA) is composed of 8 bytes (byte), the first byte represents the type of the data packet (such as various protocol packets, multicast data packets, unicast data packets, etc.), there are 256 possibilities at most, the second byte to the sixth byte are metropolitan area network addresses, and the seventh byte and the eighth byte are access network addresses;

the Source Address (SA) is also composed of 8 bytes (byte), defined as the same as the Destination Address (DA);

the reserved byte consists of 2 bytes;

the payload part has different lengths according to different types of datagrams, and is 64 bytes if the datagram is various types of protocol packets, and is 32+1024 or 1056 bytes if the datagram is a unicast packet, of course, the length is not limited to the above 2 types;

the CRC consists of 4 bytes and is calculated in accordance with the standard ethernet CRC algorithm.

2.2 metropolitan area network packet definition

The topology of a metropolitan area network is a graph and there may be 2, or even more than 2, connections between two devices, i.e., there may be more than 2 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 metro network address of the metro network device is unique, and in order to accurately describe the connection relationship between the metro network devices, parameters are introduced in the embodiment of the present invention: a label to uniquely describe a metropolitan area network device.

In this specification, the definition of the label is similar to that of a label of MP L S (Multi-Protocol L abel Switch), and assuming that there are two connections between device a and device B, there are 2 labels for a packet from device a to device B, and there are 2 labels for a packet from device B to device a. the label is divided into an incoming label and an outgoing label, and assuming that the label (incoming label) of a packet entering device a is 0x0000, the label (outgoing label) of the packet leaving device a may become 0x 0001.

As shown in the following table, the data packet of the metro network mainly includes the following parts:

DA

SA

Reserved

label (R)

Payload

CRC

Namely Destination Address (DA), Source Address (SA), Reserved byte (Reserved), tag, payload (pdu), CRC. The format of the tag may be defined by reference to the following: the tag is 32 bits with the upper 16 bits reserved and only the lower 16 bits used, and its position is between the reserved bytes and payload of the packet.

Based on the characteristics of the video network, one of the core concepts of the embodiment of the invention is provided, and the protocol of the video network is followed, when the service request is processed by the service request processing method provided by the embodiment of the invention, the service request sent by the target terminal is firstly received, the target autonomous server is determined according to the service request, and the only one target autonomous user account created by the target autonomous server under the target system user account currently logged in by the target terminal is obtained, then the service request is sent to the target autonomous server through the target autonomous user account, the service request is processed by the target autonomous server, and simultaneously, the response data returned by the target autonomous server is received through the target autonomous user account and is sent to the target terminal.

The embodiments in the present specification are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus, or computer program product. Accordingly, embodiments of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Embodiments of the present invention are described with reference to flowchart illustrations and/or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing terminal to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing terminal to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing terminal to cause a series of operational steps to be performed on the computer or other programmable terminal to produce a computer implemented process such that the instructions which execute on the computer or other programmable terminal provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or terminal. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or terminal that comprises the element.

The service request processing method, the service request processing device, the electronic device and the storage medium provided by the invention are introduced in detail, and a specific example is applied in the text to explain the principle and the implementation of the invention, and the description of the above embodiment is only used to help understanding the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims

1. A service request processing method is characterized by comprising the following steps:

and sending the response data to the target terminal.

2. The method of claim 1, wherein obtaining a target autonomous user account corresponding to the target autonomous server comprises:

activating the target autonomous user account;

3. The method of claim 1, wherein prior to sending the service request to the target autonomous server through the target autonomous user account, the method further comprises:

adding the transaction credential to the transaction request;

sending the response data to the target terminal, including:

4. The method of claim 1, wherein prior to sending the service request to the target autonomous server through the target autonomous user account, the method further comprises:

adding the transaction credential to the transaction request;

sending the response data to the target terminal, including:

5. The method according to claim 3 or 4, wherein receiving the service request sent by the target terminal comprises:

adding the transaction credential to the transaction request, including:

sending the response data to the target terminal, including:

6. A service request processing method is characterized by comprising the following steps: receiving a service request sent by a background server of a client through a target autonomous user account, wherein the service request is sent to the background server by a target terminal; the target autonomous user account is the only one account which is created in the background server for the target system user account currently logged in by the target terminal in advance;

obtaining response data of the service request;

7. A service request processing apparatus, comprising:

8. A service request processing apparatus, comprising:

9. An electronic device, comprising:

one or more processors; and

one or more machine-readable media having instructions stored thereon, which when executed by the one or more processors, cause the apparatus to perform the service request processing method of any of claims 1 to 6.

10. A computer-readable storage medium storing a computer program for causing a processor to execute the service request processing method according to any one of claims 1 to 6.