CN117118939B

CN117118939B - Data processing method, device, equipment and storage medium

Info

Publication number: CN117118939B
Application number: CN202311382976.5A
Authority: CN
Inventors: 黄从韬; 黄钰良; 金亮; 钟畅波
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2023-10-24
Filing date: 2023-10-24
Publication date: 2024-01-30
Anticipated expiration: 2043-10-24
Also published as: CN117118939A

Abstract

The embodiment of the application provides a data processing method, device, equipment and storage medium, which are used for expanding the application scene of bot segmentation and simultaneously realizing batch pushing of information. Comprising the following steps: the method comprises the steps that a node server obtains a task to be processed, a plurality of bot applications are operated on the node server, each bot application is operated with a plurality of bot application fragments, and each bot application fragment establishes a session link with an application server; the node server analyzes the task to be processed; when the task type indicates that the task to be processed is a message pushing task, the node server generates a message to be pushed according to the task data; the node server determines a target bot application and target bot application fragments according to the task identifier; the node server pushes the message to be pushed to the application server through the target bot application fragment, so that the application server forwards the message to be pushed to the client. The technical scheme provided by the application can be applied to the fields of computers, cloud technology and the like.

Description

Data processing method, device, equipment and storage medium

Technical Field

The present disclosure relates to the field of computers, and in particular, to a data processing method, apparatus, device, and storage medium.

Background

With the development of internet technology, more and more application programs start to enable a bot to manage corresponding operations in the application programs, wherein the bot is a robot for short, and the bot interaction function of the robot can automatically issue some information, such as automatically pushing weather information and traffic information, and can realize an account number which is automatically replied.

Some applications may currently provide a program development application program interface (application programming interface, api) for the bot, through which a user may create the bot to manage groups in the application (e.g., meetings in discord) and may send messages, pictures, etc. information.

When the bot manages the groups in the application program, the number of the groups is limited due to the problem of the characteristics of the bot, and meanwhile, the information pushing is limited.

Disclosure of Invention

The embodiment of the application provides a data processing method, device, equipment and storage medium, which are used for expanding the application scene of bot segmentation and simultaneously realizing batch pushing of information.

In view of this, the present application provides, in one aspect, a data processing method, including: a node server acquires a task to be processed, a plurality of bot applications are operated on the node server, each bot application is operated with a plurality of bot application fragments, each bot application fragment establishes a session link with an application server, the application server is a background server of an application program, and the bot application is used for managing groups in the application program; the node server analyzes the task to be processed to obtain a task type, task data and task identification corresponding to the task to be processed, wherein the task data is used for indicating specific content to be executed of the task to be processed, and the task identification is used for indicating the node server, the bot application and the bot application fragments for executing the task to be processed; when the task type indicates that the task to be processed is a message pushing task, the node server generates a message to be pushed according to the task data; the node server determines a target bot application and a target bot application fragment according to the task identifier; the node server pushes the message to be pushed to the application server through the target bot application fragment, so that the application server forwards the message to be pushed to the client.

Another aspect of the present application provides a data processing apparatus, comprising: the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring a task to be processed, a plurality of bot applications are run on the node server, each bot application runs a plurality of bot application fragments, each bot application fragment establishes a session link with an application server, the application server is a background server of an application program, and the bot application is used for managing groups in the application program;

the processing module is used for analyzing the task to be processed to obtain a task type, task data and task identification corresponding to the task to be processed, wherein the task data is used for indicating specific content to be executed by the task to be processed, and the task identification is used for indicating a node server, a bot application and a bot application fragment for executing the task to be processed; when the task type indicates that the task to be processed is a message pushing task, generating a message to be pushed according to the task data; determining a target bot application and a target bot application fragment according to the task identifier;

and the sending module is used for pushing the message to be pushed to the application server through the target bot application fragment so that the application server forwards the message to be pushed to the client.

In one possible design, in another implementation manner of another aspect of the embodiments of the present application, when the task type indicates that the task to be processed is a bot application fragment adjustment task, the processing module is configured to determine a bot application to be adjusted and a bot application fragment to be adjusted according to the task identifier; and adjusting the to-be-adjusted bot application and the to-be-adjusted bot application fragments according to the task data.

In one possible design, in another implementation manner of another aspect of the embodiments of the present application, the processing module is configured to close a session link between an original bot application slice in the to-be-adjusted bot application and the application server, where the original bot application slice is used as the to-be-adjusted bot application slice; the method comprises the steps of grouping and configuring the bot application fragments of the bot application to be adjusted again to obtain updated bot application fragments; the updated bot application fragment is instructed to establish a session link with the application server.

In one possible design, in another implementation of another aspect of the embodiments of the present application, the processing module is configured to close a session link of the to-be-adjusted bot application fragment with the application server;

or,

The processing module is used for creating a session link between the to-be-adjusted bot application fragment and the application server.

In one possible design, in another implementation of another aspect of the embodiments of the present application, the obtaining module is configured to receive a first instruction, where the first instruction is forwarded by the application server through a target session link, and the first instruction is generated by the client;

the processing module is used for acquiring corresponding target data in response to the first instruction;

the sending module is configured to send the target data to the application server through the target session link, so that the application server forwards the target data to the client.

In another implementation manner of another aspect of the embodiments of the present application, the obtaining module is configured to receive the task to be processed sent by the control end device through the message queue, where the task to be processed is generated by editing the control end device, and the node server registers node registration information in the control end device, where the node registration information is used to indicate a bot application running by the node server and a bot application fragment running by each bot application;

or,

The acquisition module is used for receiving the task to be processed forwarded by the target task server through the message queue, the task to be processed is edited and generated by the control end equipment, the control end equipment sends the task to be processed to the target task server, the node server registers node registration information in the target task server, and the node registration information is used for indicating the bot application operated by the node server and the bot application fragments operated by each bot application.

In one possible design, in another implementation of another aspect of the embodiments of the present application, the message to be pushed is a rich text message and the application is a record program.

Another aspect of the present application provides a computer device comprising: a memory, a processor, and a bus system;

wherein the memory is used for storing programs;

the processor is used for executing the program in the memory, and the processor is used for executing the method according to the aspects according to the instructions in the program code;

the bus system is used to connect the memory and the processor to communicate the memory and the processor.

Another aspect of the present application provides a computer-readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform the methods of the above aspects.

In another aspect of the present application, a computer program product or computer program is provided, the computer program product or computer program comprising computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the methods provided in the above aspects.

From the above technical solutions, the embodiments of the present application have the following advantages: by deploying a plurality of bot applications on a node server, and running a plurality of bot slices in each bot application, the bot application can be expanded, so that more groups can be served. Meanwhile, messages are pushed to the application server through different bot fragments, so that the application server sends the messages to different clients, and batch message pushing to the group or the clients can be realized.

Drawings

FIG. 1 is a schematic diagram of a post-interaction interface between a bot application and a user in an embodiment of the present application;

FIG. 2 is a schematic diagram of an application scenario of a data processing system in an embodiment of the present application;

FIG. 3 is a schematic diagram of a data processing system according to an embodiment of the present application;

FIG. 4 is a schematic diagram of an architecture of a node server according to an embodiment of the present application;

FIG. 5 is a schematic diagram of another architecture of a data processing system in an embodiment of the present application;

FIG. 6a is a schematic diagram of one embodiment of a data processing method in an embodiment of the present application;

FIG. 6b is a schematic diagram of an interface for pushing messages according to an embodiment of the present application;

FIG. 7 is a schematic diagram of another embodiment of a data processing method in an embodiment of the present application;

FIG. 8 is a schematic diagram of another embodiment of a data processing method in an embodiment of the present application;

FIG. 9a is a schematic diagram of another embodiment of a data processing method in an embodiment of the present application;

FIG. 9b is a schematic diagram of an interface for responding to commands in an embodiment of the present application;

FIG. 10 is a schematic diagram of another embodiment of a data processing method in an embodiment of the present application;

FIG. 11 is a schematic diagram of an embodiment of a data processing apparatus in an embodiment of the present application;

FIG. 12 is a schematic diagram of another embodiment of a data processing apparatus in an embodiment of the present application;

fig. 13 is a schematic diagram of another embodiment of a data processing apparatus in an embodiment of the present application.

Detailed Description

The terms "first," "second," "third," "fourth" and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be capable of operation in sequences other than those illustrated or described herein, for example. Furthermore, the terms "comprises," "comprising," and "includes" and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.

With the development of internet technology, more and more applications are beginning to enable bots to manage the corresponding operations in the applications. The Bot is actually a short name of a robot, and the Bot interaction function of the robot can automatically issue some information, such as automatically pushing weather information and traffic information, and can realize an account number which is automatically replied, etc. Some applications may currently provide a program development application program interface (application programming interface, api) for the bot, through which a user may create the bot to manage groups in the application (e.g., meetings in discord) and may send messages, pictures, etc. information. Referring to fig. 1, a schematic diagram of interaction between a bot and a user is shown. As shown in fig. 1, by triggering the "XX game BOT" by the user AAAA via the @ "XX game BOT" will send a prompt message to the user AAAA, such as: "do you good, what need help? ". And the user AAAA will input corresponding advisory information such as "what the action of the game triggers YY task is". The "XX game BOT" will then reply with corresponding information, such as "A. Communicate with NPC1, B. Complete task 1, C. Acquire props A". When the bot manages the groups in the application program, there is a limit to the number of groups due to the problem of its own characteristics, and the information push may also be limited.

In order to solve the above problems, the present application provides the following technical solutions: a node server acquires a task to be processed, a plurality of bot applications are operated on the node server, each bot application is operated with a plurality of bot application fragments, each bot application fragment establishes a session link with an application server, the application server is a background server of an application program, and the bot application is used for managing groups in the application program; the node server analyzes the task to be processed to obtain a task type, task data and task identification corresponding to the task to be processed, wherein the task data is used for indicating specific content to be executed of the task to be processed, and the task identification is used for indicating the node server, the bot application and the bot application fragments for executing the task to be processed; when the task type indicates that the task to be processed is a message pushing task, the node server generates a message to be pushed according to the task data; the node server determines a target bot application and a target bot application fragment according to the task identifier; the node server pushes the message to be pushed to the application server through the target bot application fragment, so that the application server forwards the message to be pushed to the client. In this way, by deploying a plurality of bot applications in the node server, and running a plurality of bot fragments in each bot application, the bot application can be expanded, so as to serve more groups. Meanwhile, messages are pushed to the application server through different bot fragments, so that the application server sends the messages to different clients, and batch message pushing to the group or the clients can be realized.

The data processing method, the device, the equipment and the storage medium can expand the application scene of the bot fragments and realize batch pushing of information. An exemplary application of the electronic device provided by the embodiment of the present application is described below, where the electronic device provided by the embodiment of the present application may be implemented as various types of user terminals, and may also be implemented as a server.

By running the data processing scheme provided by the embodiment of the application, the electronic equipment can expand the application scenes of the bot fragments, realize batch pushing of information, and is suitable for a plurality of application scenes of the bot application. For example, the bot application of the communication software interacts with the user, such as artificial intelligence customer service, artificial intelligence consultation, and the like.

Referring to fig. 2, fig. 2 is a schematic diagram of an alternative architecture in an application scenario of the data processing method provided in the embodiment of the present application, in order to support a data processing method, the terminal device 100 is connected to the server 300 through the network 200, the server 300 is connected to the database 400, and the network 200 may be a wide area network or a local area network, or a combination of the two. The client for implementing the data processing method is disposed on the terminal device 100, where the client may run on the terminal device 100 in a browser mode, may also run on the terminal device 100 in a form of a stand-alone Application (APP), and the specific presentation form of the client is not limited herein. The server 300 according to the present application may be an independent physical server, or may be a server cluster or a distributed system formed by a plurality of physical servers, or may be a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and basic cloud computing services such as big data and artificial intelligence platforms. The terminal device 100 may be, but is not limited to, a smart phone, a tablet computer, a notebook computer, a palm computer, a personal computer, a smart television, a smart watch, a vehicle-mounted device, a wearable device, a smart voice interaction device, a smart home appliance, an aircraft, and the like. The terminal device 100 and the server 300 may be directly or indirectly connected through the network 200 by wired or wireless communication, which is not limited herein. The number of servers 300 and terminal devices 100 is also not limited. The solution provided in the present application may be independently completed by the terminal device 100, or may be independently completed by the server 300, or may be completed by the cooperation of the terminal device 100 and the server 300, which is not specifically limited in this application. The database 400 may be considered as an electronic file cabinet, i.e. a place where electronic files are stored, and a user may perform operations such as adding, querying, updating, deleting, etc. on data in the files. A "database" is a collection of data stored together in a manner that can be shared with multiple users, with as little redundancy as possible, independent of the application. The database management system (Database Management System, DBMS) is a computer software system designed for managing databases, and generally has basic functions of storage, interception, security, backup, and the like. The database management system may classify according to the database model it supports, e.g., relational, extensible markup language (Extensible Markup Language, XML); or by the type of computer supported, e.g., server cluster, mobile phone; or by classification according to the query language used, e.g. structured query language (Structured Query Language, SQL), XQuery; or by performance impact emphasis, such as maximum scale, maximum speed of operation; or other classification schemes. Regardless of the manner of classification used, some DBMSs are able to support multiple query languages across categories, for example, simultaneously. In this application, the database 400 may be used to store node registration information and registration order logic, and of course, the storage location of the node registration information and registration order logic is not limited to a database, and may be stored in a distributed file system of the terminal device 100, the blockchain, or the server 300, for example.

Based on the above description, a schematic system architecture of the technical solution provided in the present application is described below, as shown in fig. 3, where the system architecture includes a control end device, one or more node servers, an application server, and a client device; wherein the node server will run multiple bot applications, and each bot application may run multiple bot application slices. In one exemplary scenario, the node server may be configured as shown in fig. 4, where bot application 1 and bot application 2 are running, and where bot application 1 runs application tile 1, application tiles 2, … …, and application tile N, and where bot application 2 runs application tile 1, application tiles 2, … …, and application tile M. Wherein N and M are positive integers. Wherein each of the fragments will create a session link with the application server.

The control end device is used for editing configuration information of the node servers (namely, the control end device is used for indicating the number of the bot applications operated by each node server and the number of fragments operated in each bot application) and editing task information of the message to be pushed; and searching a corresponding node server, and distributing the configuration information and the task information to the node server.

The node server is used for configuring the corresponding bot application and the bot application fragment according to the configuration information, or selecting the corresponding bot application and the bot application fragment according to the task information to recommend the message to be pushed to the application server.

The application server is used for forwarding the server to be pushed to the corresponding client equipment; or the application server forwards the instruction triggered by the client device to the node server, so that the node server executes the instruction and returns corresponding target data.

The client device is used for receiving the message to be pushed or the triggering instruction.

In another exemplary scenario, as shown in fig. 5, the system architecture includes a control end device, a plurality of task servers, one or more node servers, an application server, and a client device; wherein the node server will run multiple bot applications, and each bot application may run multiple bot application slices. In one exemplary scenario, the node server may be configured as shown in fig. 4, where a bot application 1 and a bot application 2 are running, and where a bot application 1, a bot application 2, … …, and a bot application N are running, and where a bot application 2, … …, and a bot application M are running. Wherein N and M are positive integers. Wherein each of the fragments will create a session link with the application server. It should be appreciated that for the same bot application, the bot application fragments distributed at different node servers should be different. That is, it is assumed that the bot application 1 includes 4 bot application slices in total, which are distributed in the node server 1 and the node server 2. The distribution of its bot application fragments may be as follows: the bot application 1 of the node server 1 runs a bot application fragment 1 and a bot application fragment 2; the bot application 1 of the node server 2 runs a bot application slice 3 and a bot application slice 4.

The control end device is used for editing configuration information of the node servers (namely, indicating the number of the bot applications operated by each node server and the number of fragments operated in each bot application) and editing task information of the message to be pushed.

The task server is used for searching the node server and distributing the configuration information and the task information generated by the control terminal equipment to the corresponding node server.

In view of the fact that certain terms are used in this application, these terms are first described below.

Discover bot: the discovery is a free network real-time calling software and digital issuing platform specially designed for communities and developed by the discovery company in the united states. It provides a programming development api for a bot, by which a user can manage meetings on discord by creating a bot, and can send messages, pictures, etc. Hereinafter referred to as bot.

The working procedures are as follows: corresponding to the guid concept in discord, the user adds a meeting, which is equivalent to adding a server on discord.

Control end equipment: for configuring each node service and node sharding information. And simultaneously sending the rich text message.

The task server: an interface for receiving configuration and tasks is provided externally, and then distributed to corresponding node services.

The node server: and running a plurality of bot applications on each node server, running a plurality of bot application fragments in each bot application, receiving task information issued by the task server, and then distributing the task information to the designated bot application fragments for execution.

Node slicing: each bot application may launch multiple tiles, each tile handling up to 2500 meetings of messages.

bot session: each bot fragment, after being started, maintains a long connection (i.e., session link in this application) with a discord backend server (i.e., application server in this application) over which to send bot command and response packets.

Rich text information: a single message that can contain both a title, a picture, text, and a @ member. By sending rich text messages, you can provide information to chat objects in a pictogram-like manner, and the effectiveness of communication is improved.

With reference to the foregoing description and the system architecture shown in fig. 5, a method for processing data in the present application will be described with reference to fig. 6a, where an embodiment of data processing in the present application includes:

601. the control end equipment generates the task to be processed.

The control terminal device carries out corresponding coding according to the task type, the task data and the task identification of the task to be processed to generate the task to be processed.

In one exemplary scenario, the task type may be identified with "0" and "1", such as "0" for indicating that the task configures its own bot application and bot application fragments for the node server and "1" for indicating that the task pushes rich text information to the application server for the node server. The specific content of the task data is different according to the different task types. For example, when the task type of the task to be processed indicates that the node server configures its own bot application and bot application fragments, the task data may be as follows "the number of bot application fragments of the bot application 1 in the node server 1 is adjusted from 4 to 5". When the task type of the task to be processed indicates that the node server pushes rich text information to the application server, the task data may send rich text information to the job managed by the bot application fragment a in the bot application 1 in the node server 1, where the rich text information includes title 1, picture 1, text 1, and @ member a.

And the task identification may be used to indicate the node server, the bot application, and the bot application fragments that perform the task to be processed. For example, the task identification may be as follows: the node server 1, the bot application fragment a.

602. And the control end equipment sends the task to be processed to the task server.

And the control terminal equipment sends the editing generation task to be processed to the task server.

It should be understood that when the task server includes a plurality of task servers, the control end device may select one task server from the plurality of task servers according to an actual service load to send the task to be processed, so that load balancing may be effectively ensured, thereby increasing stability of the system.

603. The task server analyzes the task to be processed and determines a node server corresponding to the task to be processed.

After receiving the task to be processed, the task server analyzes the task to be processed, so as to obtain the task type, the task data and the task identification of the task to be processed; and then the task server searches the corresponding node server from the node registration information according to the node server indicated in the task identifier.

It should be understood that the node registration information is registered with the task server after the initialization process and the update, and stored in the memory of the task server. Meanwhile, the node registration information stored in each task server comprises all the node servers in the system, so that each task server can be guaranteed to realize task forwarding after receiving the task to be processed.

604. The task server sends the task to be processed to the node server.

The task server sends the task to be processed to the node server after determining the node server executing the task to be processed.

It should be understood that the task server may transfer the task to be processed into a message queue, and then forward the task to be processed to a corresponding node server by means of the message queue, so that the order of data transmission in the system may be ensured, thereby avoiding the situation that different task servers occupy transmission resources simultaneously, resulting in insufficient transmission resources and data loss.

605. The node server analyzes the task to be processed to obtain task data, task types and task identifications.

After receiving the task to be processed, the node server analyzes the task to be processed to obtain the task data, the task type and the task identification.

606. When the task type indicates that the task to be processed is a message pushing task, the node server generates a message to be pushed according to the task data.

The node server reads the identification of the task type and determines specific information of the task type; and then when the task type indicates that the task to be processed is a message pushing task, the node server generates a message to be pushed according to the task data. For example, the rich text information to be pushed is obtained by encoding according to the title 1, the picture 1, the text 1 and the @ member A indicated in the task data.

607. And the node server determines the target bot application and the target bot application fragment according to the task identifier.

After the node server analyzes the task identifier of the task to be processed, the node server can acquire the target bot application for executing the task to be processed and the target bot application fragment.

For example, the task identifier is "node server 1, bot application 1, and bot application fragment a", and then after the node server 1 parses the task identifier, the node server 1 will search the bot application 1 in the node server 1 and the bot application fragment a in the bot application 1.

608. And the node server sends the message to be pushed to the application server through the target bot application fragment.

The node server starts the target bot application and simultaneously runs the target bot application fragments; and then the node server sends the message to be pushed to the application server through the session link between the target bot application fragment and the application server.

It should be appreciated that the session link may be a websocket long link, with the session heartbeat maintained connected between the node server and the application server.

609. The application server sends the message to be pushed to the client device.

The application server sends the message to be pushed to the group member of the target bot application fragment management. For example, the target bot application partition manages a meeting a in application software corresponding to the application server, where the meeting a includes a member a and a member B, and the rich text information designates @ member a, and the application server sends the rich text information to a client of the member a. If the rich text information does not specify a member of @, the application server may send the rich text information to both the client of member a and the client of member B.

In one exemplary application scenario, as shown in fig. 6b, the node server a pushes a week war of game a to the client a.

It should be understood that, in this system architecture, the node server may also be configured to adjust the bot application slices accordingly, and when adjusting the total number of the bot application slices, the specific flow may be as shown in fig. 7:

701. the control end equipment generates the task to be processed.

702. And the control end equipment sends the task to be processed to the task server.

703. The task server analyzes the task to be processed and determines a node server corresponding to the task to be processed.

704. The task server sends the task to be processed to the node server.

705. The node server analyzes the task to be processed to obtain task data, task types and task identifications.

706. And when the task type indicates that the task to be processed is the total number of the fragments of the adjusting bot application, the node server determines the bot application to be adjusted according to the task identification.

The node server reads the identification of the task type and determines specific information of the task type; and then when the task type indicates that the task to be processed is the total number of the fragments of the adjusting bot application, the node server determines the bot application to be adjusted according to the task identification. For example, according to "node server 1, bot application 1" indicated in the task identity, it is determined that the number of bot application fragments of the bot application 1 in the node server 1 should be adjusted. And the task data may be "the number of bot application fragments of the bot application 1 in the node server 1 is adjusted from 4 to 5".

707. The node server closes the session link of the original bot application fragment of the bot application to be adjusted and the application server.

At this time, the node server instructs the original bot application fragment of the bot application to be tuned to drop the session link with the application server.

708. And the node server re-groups the bot application fragments of the bot application to be adjusted according to the task data so as to obtain updated bot application fragments.

And the node server carries out grouping configuration on the bot application fragments of the bot application to be adjusted according to the task data, so as to obtain updated bot application fragments. For example, when the task data is "the number of the bot application fragments of the bot application 1 in the node server 1 is adjusted from 4 to 5", the node server 1 breaks the session link between the original 4 bot application fragments in the bot application 1 and the application server, and then groups the 4 bot application fragments managed in the bot application 1 to obtain 5 bot application fragments. Assuming 1000 groups are managed by the original 4 bots in the bot application 1, 250 groups will be managed in the original one bot application slice, and after readjustment, 200 groups can be managed per bot application slice.

709. The node server instructs the update bot application fragment to establish a session link with the application server.

The node server instructs the update bot application fragments to establish session links with the application server again, respectively, to perform subsequent message pushing and instruction responses.

It can be understood that after the node server completes the adjustment of the bot application fragment, the node server needs to update the node registration information with the task server, and at the same time, the update bot application fragment needs to update the command logic information with the application server, so as to ensure the accuracy of the subsequent message pushing and instruction response.

It should be understood that the task identifier in the task to be processed may indicate one node server and one bot application slice running at a time, or may indicate multiple node servers and/or multiple bot applications and multiple bot application slices running at a time.

For example, the task identity may be "node server 1, bot application fragment a"; "node server 1, bot application shard A, bot application shard B"; or "node server 1, bot application fragment a, node server 2, bot application 1, bot application fragment B". Similarly, the task data may be "the number of bot application fragments of the bot application 1 in the node server 1 is adjusted from 4 to 5"; the "the number of the bot application fragments of the bot application 1 in the node server 1 is adjusted from 4 to 5, and the number of the bot application fragments of the bot application 2 in the node server 2 is adjusted from 5 to 4"; the present invention may also be "the number of the bot application fragments of the bot application 1 in the node server 1 is adjusted from 4 to 5, the number of the bot application fragments of the bot application 2 in the node server 1 is adjusted from 5 to 4", or the like, as long as the task to be processed can be accurately executed.

Optionally, in this system architecture, the node server may be further configured to correspondingly adjust the bot application slice, and when the position of the bot application slice is adjusted, the specific flow may be as shown in fig. 8:

801. the control end equipment generates the task to be processed.

802. And the control end equipment sends the task to be processed to the task server.

803. The task server analyzes the task to be processed and determines a first node server and a second node server corresponding to the task to be processed.

After receiving the task to be processed, the task server analyzes the task to be processed, so as to obtain the task type, the task data and the task identification of the task to be processed; and then the task server searches the corresponding node server from the node registration information according to the node server indicated in the task identifier. In this embodiment, the task to be processed is used to indicate to adjust the position of the bot application fragments, and the task identifier will at least indicate two node servers, where different bot application fragments of the same bot application run between the two node servers.

804. The task server sends the task to be processed to the first node server and the second node server.

The task server sends the task to be processed to the first node server and the second node server after determining the first node server and the second node server to execute the task to be processed.

805. The first node server and the second node server analyze the task to be processed to obtain task data, task types and task identifications.

After the first node server and the second node server receive the task to be processed, the task to be processed is analyzed to obtain the task data, the task type and the task identification.

It should be understood that the first node server and the second node server may parse the same task data or may parse different task data. That is, the task server can modify the task data and then send the modified task data respectively; the task data may be kept as it is and then forwarded. For example, the task data generated by the control end device is "adjusting the bot application fragment 1 of the bot application 1 in the first node server to the bot application 1 in the second node server", and the task data forwarded to the first node server by the task server may be "adjusting the bot application fragment 1 of the bot application 1 in the first node server to the bot application 1 in the second node server"; it may also be "close session link of bot application fragment 1 of bot application 1 in first node server with application server"; the task data forwarded to the second node server by the task server may be "the bot application fragment 1 of the bot application 1 in the first node server is adjusted to the bot application 1 in the second node server"; or "the bot application fragment 1 of the creation bot application 1 in the second node server and creates a session link with the application server".

806. When the task type indicates that the task to be processed is the position of the adjustment bot application fragment, the first node server and the second node server determine the adjustment bot application and the adjustment bot application fragment according to the task identification.

The first node server and the second node server read the identification of the task type and determine the specific information of the task type; and then when the task type indicates that the task to be processed is the position for adjusting the bot application fragments, the first node server and the second node server determine the bot application to be adjusted and the bot application fragments according to the task identification. For example, according to the "first node server, second node server, bot application 1, and bot application fragment a" indicated in the task identifier, it is determined to adjust the bot application fragment a of the bot application 1 in the first node server and the second node server. And the task data may be "tuning the bot application tile 1 of the bot application 1 in the first node server into the bot application 1 in the second node server".

807. The first node server closes session links of the to-be-adjusted bot application fragments of the to-be-adjusted bot application and the application server.

The first node server executes the adjustment task, and at this time, the first node server disconnects the session link of the to-be-adjusted bot application fragment of the to-be-adjusted bot application and the application server.

808. The second node server creates the to-be-adjusted bot application fragments in the corresponding to-be-adjusted bot applications.

The second node server executes the adjustment task and creates the to-be-adjusted bot application fragment in the to-be-adjusted bot application.

809. The second node server indicates that the to-be-adjusted bot application fragment establishes a session link with the application server.

The second node server executes the adjustment task and indicates the to-be-adjusted bot application fragment to establish a session link with the application server.

It should be understood that, in this system architecture, the node server may also be configured to respond to the instruction sent by the client device and feedback corresponding data, where the specific flow may be as shown in fig. 9 a:

901. the client device triggers generation of a first instruction.

The client device binds with the node server through the application server, and then the client device generates a first instruction in response to the operation of a user on an application program corresponding to the application server. The first instruction may be to consult the bot application with the current state of the game, or consult other information, which is not limited herein.

902. The client device sends the first instruction to the application server.

The client device sends the first instruction to the application server in a wireless or wired manner.

903. The application server forwards the first instruction to the node server.

The application server inquires the command logic information registered by the bot application fragments in the application server so as to find the bot application fragments corresponding to the first instructions, and then the first instructions are sent to the node server through the bot application fragments.

904. The node server executes the first instruction to obtain target data.

After the node server receives the first instruction, the node server instructs the bot application fragment corresponding to the first instruction to execute the first instruction so as to obtain corresponding target data.

For example, the first instruction is that the user inquires about the open condition of activity a in game a, and the target data will be used to describe the open condition of activity a of game a.

905. The node server sends the target data to the application server.

And the node server sends the target data to the application server according to the bot application fragments corresponding to the first instruction.

906. The application server forwards the target data to the client device.

The application server forwards the target data to the client device via a wired or wireless scheme.

In an exemplary application scenario, as shown in fig. 9b, the client device triggers a check-in instruction of game a, and the node server returns to the check-in interface of the client after responding to the check-in instruction.

It should be understood that, in this system architecture, when the node server is started, the node server needs to perform initialization configuration, and needs to perform initialization registration with the task server and the application server, and the specific flow may be as shown in fig. 10:

1001. the control terminal equipment edits and generates configuration information.

When the system is initialized, the control end device can generate the configuration information according to the configuration content of the node server. For example, the system includes a node server 1 and a node server 2, and the configuration information may be that "the node server 1 runs a bot application 1 and a bot application 2, where the bot application 1 runs a bot application fragment 1 and a bot application fragment 2, and the bot application 2 runs a bot application fragment a and a bot application fragment B; the node server 2 runs a bot application 2 and a bot application 3, wherein the bot application 1 runs a bot application slice 3 and a bot application slice 4, and the bot application 3 runs a bot application slice a and a bot application slice b. "

1002. The control end device sends the configuration information to the task server.

The control terminal device sends the editing generation configuration information to the task server.

1003. The task server distributes the configuration information to the node server.

After receiving the configuration information, the task server analyzes the configuration information to obtain a corresponding node server in the configuration information; and then the task server sends the configuration information to the corresponding node server according to the node server indicated by the configuration information.

It can be understood that, in the initialization process, the task server may send a broadcast message to the node server, where the broadcast message carries the configuration information, and may also send the configuration information to the node server in a targeted manner. The specific manner is not limited herein, as long as the node server can receive the corresponding configuration information.

1004. The node server initializes the configuration of the bot application and the bot application fragments according to the configuration information.

After receiving the configuration information, the node server initializes the bot application and the bot application fragments according to the indication information in the configuration information.

1005. The node server registers node registration information with the task server.

After the node server initializes the bot application and the bot application fragments, the node server may register the node registration information with the task server via a session heartbeat. In this embodiment, the node registration information is used to indicate the deployed bot application of the node server and the bot application fragments distributed in each bot application, so that when the task server receives a task to be processed, the corresponding node server can be queried from the node registration information.

1006. Each bot application fragment in the node server creates a session link with the application server and registers command logic information with the application server.

Each bot application fragment in the node server, after creation is completed, will create a session connection with the application server while registering command logic information with the application server through session heartbeat. In this embodiment, the command logic is configured to logically and logically indicate instruction information that the bot application fragment may be executed. Such as information query for game a; or may conduct a voice call of software a or may conduct an interaction of applet B, etc. The specific examples are not limited herein.

Referring to fig. 11, fig. 11 is a schematic diagram of an embodiment of a data processing apparatus according to an embodiment of the present application, and the data processing apparatus 20 includes:

an obtaining module 201, configured to obtain a task to be processed, where the node server runs a plurality of bot applications, each bot application runs a plurality of bot application fragments, each bot application fragment establishes a session link with an application server, the application server is a background server of an application program, and the bot application is used for managing a group in the application program;

the processing module 202 is configured to parse the task to be processed to obtain a task type, task data and task identifier corresponding to the task to be processed, where the task data is used to indicate specific content to be executed by the task to be processed, and the task identifier is used to indicate a node server, a bot application and a bot application fragment that execute the task to be processed; when the task type indicates that the task to be processed is a message pushing task, generating a message to be pushed according to the task data; determining a target bot application and a target bot application fragment according to the task identifier;

and the sending module 203 is configured to push the message to be pushed to the application server through the target bot application partition, so that the application server forwards the message to be pushed to the client.

In an embodiment of the present application, a data processing apparatus is provided. By adopting the device, the structure that a plurality of bot applications are deployed in the node server and a plurality of bot fragments are operated in each bot application simultaneously, the bot application can be expanded, so that more groups are served. Meanwhile, messages are pushed to the application server through different bot fragments, so that the application server sends the messages to different clients, and batch message pushing to the group or the clients can be realized.

Alternatively, in another embodiment of the data processing apparatus 20 provided in the embodiment of the present application based on the embodiment corresponding to fig. 11 described above,

when the task type indicates that the task to be processed is a bot application fragment adjustment task, the processing module 202 is configured to determine a bot application to be adjusted and a bot application fragment to be adjusted according to the task identifier; and adjusting the to-be-adjusted bot application and the to-be-adjusted bot application fragments according to the task data.

In an embodiment of the present application, a data processing apparatus is provided. By adopting the device, when the node server receives the adjustment task of the bot application fragments, the corresponding bot fragments are configured according to the specific configuration information, so that the refined management of the bot fragments can be realized.

Optionally, in another embodiment of the data processing apparatus 20 provided in the embodiment of fig. 11, the processing module 202 is configured to close a session link between an original bot application slice in the to-be-adjusted bot application and the application server, where the original bot application slice is used as the to-be-adjusted bot application slice; the method comprises the steps of grouping and configuring the bot application fragments of the bot application to be adjusted again to obtain updated bot application fragments; the updated bot application fragment is instructed to establish a session link with the application server.

In an embodiment of the present application, a data processing apparatus is provided. By adopting the device, when the node server receives the adjustment task of the bot application fragments, if the adjustment task is to reconfigure the total number of the bot application fragments, the node server needs to close the session link between the original bot fragments and the application server in the original node server, and then the corresponding bot fragments are reconfigured in the original node server according to the configuration information, so that the refinement management of the bot fragments can be realized.

The processing module 202 is configured to close a session link between the to-be-adjusted bot application fragment and the application server;

or,

the processing module 202 is configured to create a session link between the to-be-adjusted bot application fragment and the application server.

In an embodiment of the present application, a data processing apparatus is provided. By adopting the device, when the node server receives the adjustment task of the bot application fragments, if the adjustment task is to readjust the bot fragments to a new position, the node server needs to close the session link between the original bot fragments and the application server, and then a new bot fragment is created in the new node server, so that the refined management of the bot fragments can be realized.

the obtaining module 201 is configured to receive a first instruction, where the first instruction is forwarded by the application server through a target session link, and the first instruction is generated by the client;

the processing module 202 is configured to obtain corresponding target data in response to the first instruction;

the sending module 203 is configured to send the target data to the application server through the target session link, so that the application server forwards the target data to the client.

In an embodiment of the present application, a data processing apparatus is provided. By adopting the device, after the client registers to the corresponding command logic in the node server through the application server, the corresponding operation can be directly realized according to the instruction of the client, so that the timely interaction between the bot application and the client is realized.

Optionally, in another embodiment of the data processing apparatus 20 provided in the embodiment of the present application, on the basis of the embodiment corresponding to fig. 11, the obtaining module 201 is configured to receive the task to be processed sent by a control end device through a message queue, where the task to be processed is generated by editing the control end device, and the node server registers node registration information in the control end device, where the node registration information is used to indicate a bot application running by the node server and a bot application partition running by each bot application;

or,

the obtaining module 201 is configured to receive the task to be processed forwarded by the target task server through the message queue, where the task to be processed is generated by editing a control end device, and the control end device sends the task to be processed to the target task server, and the node server registers node registration information in the target task server, where the node registration information is used to indicate a bot application running by the node server and a bot application fragment running by each bot application.

In an embodiment of the present application, a data processing apparatus is provided. By adopting the device, the control terminal equipment can integrate the functions of editing the task to be processed and distributing the task to be processed, so that the number of equipment in the whole flow is reduced; meanwhile, a plurality of task servers can be added between the control terminal equipment and the node server, and the task server is used for distributing load balancing, so that service load balancing can be realized.

Optionally, in another embodiment of the data processing apparatus 20 provided in the embodiment of the present application, based on the embodiment corresponding to fig. 11, the message to be pushed is a rich text message, and the application is a record program.

In an embodiment of the present application, a data processing apparatus is provided. The device is mainly applied to discord software, so that the management of a large number of meetings of the discord and the batch information recommendation function of the discord are realized.

Referring to fig. 12, fig. 12 is a schematic diagram of a server structure according to an embodiment of the present application, where the server 300 may have a relatively large difference due to different configurations or performances, and may include one or more central processing units (central processing units, CPU) 322 (e.g., one or more processors) and a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) storing bot applications 342 or data 344. Wherein the memory 332 and the storage medium 330 may be transitory or persistent. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instruction operations on a server. Still further, the central processor 322 may be configured to communicate with the storage medium 330 and execute a series of instruction operations in the storage medium 330 on the server 300.

The server 300 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input/output interfaces 358, and/or one or more operating systems 341, e.g., windows Server ^TM ，Mac OS X ^TM ，Unix ^TM , Linux ^TM ，FreeBSD ^TM Etc.

The steps performed by the server in the above embodiments may be based on the server structure shown in fig. 12.

The data processing apparatus provided in the present application may be used in a terminal device, please refer to fig. 13, only the portion related to the embodiment of the present application is shown for convenience of explanation, and specific technical details are not disclosed, please refer to the method portion of the embodiment of the present application. In the embodiment of the present application, a terminal device is taken as a smart phone as an example to describe:

fig. 13 is a block diagram showing a part of a structure of a smart phone related to a terminal device provided in an embodiment of the present application. Referring to fig. 13, the smart phone includes: radio Frequency (RF) circuitry 410, memory 420, input unit 430, display unit 440, sensor 450, audio circuitry 460, wireless fidelity (wireless fidelity, wiFi) module 470, processor 480, and power supply 490. Those skilled in the art will appreciate that the smartphone structure shown in fig. 13 is not limiting of the smartphone and may include more or fewer components than shown, or may combine certain components, or a different arrangement of components.

The following describes each component of the smart phone in detail with reference to fig. 13:

the RF circuit 410 may be used for receiving and transmitting signals during the process of receiving and transmitting information or communication, in particular, after receiving downlink information of the base station, the downlink information is processed by the processor 480; in addition, the data of the design uplink is sent to the base station. In general, RF circuitry 410 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (low noise amplifier, LNA), a duplexer, and the like. In addition, the RF circuitry 410 may also communicate with networks and other devices via wireless communications. The wireless communications may use any communication standard or protocol including, but not limited to, global system for mobile communications (global system of mobile communication, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), long term evolution (long term evolution, LTE), email, short message service (short messaging service, SMS), and the like.

The memory 420 may be used to store software programs and modules, and the processor 480 may perform various functional applications and data processing of the smartphone by executing the software programs and modules stored in the memory 420. The memory 420 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, a bot application (such as a sound playing function, an image playing function, etc.) required for at least one function, etc.; the storage data area may store data (such as audio data, phonebooks, etc.) created according to the use of the smart phone, etc. In addition, memory 420 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.

The input unit 430 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the smart phone. In particular, the input unit 430 may include a touch panel 431 and other input devices 432. The touch panel 431, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 431 or thereabout using any suitable object or accessory such as a finger, a stylus, etc.), and drive the corresponding connection device according to a predetermined program. Alternatively, the touch panel 431 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device and converts it into touch point coordinates, which are then sent to the processor 480, and can receive commands from the processor 480 and execute them. In addition, the touch panel 431 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The input unit 430 may include other input devices 432 in addition to the touch panel 431. In particular, other input devices 432 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc.

The display unit 440 may be used to display information input by a user or information provided to the user and various menus of the smart phone. The display unit 440 may include a display panel 441, and optionally, the display panel 441 may be configured in the form of a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), or the like. Further, the touch panel 431 may cover the display panel 441, and when the touch panel 431 detects a touch operation thereon or nearby, the touch operation is transmitted to the processor 480 to determine the type of the touch event, and then the processor 480 provides a corresponding visual output on the display panel 441 according to the type of the touch event. Although in fig. 13, the touch panel 431 and the display panel 441 are two separate components to implement the input and input functions of the smart phone, in some embodiments, the touch panel 431 and the display panel 441 may be integrated to implement the input and output functions of the smart phone.

The smartphone may also include at least one sensor 450, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel 441 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 441 and/or the backlight when the smartphone is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for identifying the application of the gesture of the smart phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration identification related functions (such as pedometer and knocking), and the like; other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured with the smart phone are not described in detail herein.

Audio circuitry 460, speaker 461, microphone 462 can provide an audio interface between the user and the smartphone. The audio circuit 460 may transmit the received electrical signal after the audio data conversion to the speaker 461, and the electrical signal is converted into a sound signal by the speaker 461 and output; on the other hand, microphone 462 converts the collected sound signals into electrical signals, which are received by audio circuit 460 and converted into audio data, which are processed by audio data output processor 480, and transmitted via RF circuit 410 to, for example, another smart phone, or which are output to memory 420 for further processing.

WiFi belongs to a short-distance wireless transmission technology, and a smart phone can help a user to send and receive emails, browse webpages, access streaming media and the like through a WiFi module 470, so that wireless broadband Internet access is provided for the user. Although fig. 13 shows a WiFi module 470, it is understood that it does not belong to the essential constitution of a smart phone, and can be omitted entirely as required within the scope of not changing the essence of the invention.

The processor 480 is a control center of the smart phone, connects various parts of the entire smart phone using various interfaces and lines, and performs various functions and processes data of the smart phone by running or executing software programs and/or modules stored in the memory 420 and invoking data stored in the memory 420, thereby performing overall monitoring of the smart phone. Optionally, the processor 480 may include one or more processing units; alternatively, the processor 480 may integrate an application processor that primarily handles operating systems, user interface and bot applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 480.

The smart phone also includes a power supply 490 (e.g., a battery) for powering the various components, optionally in logical communication with the processor 480 through a power management system that performs functions such as managing charge, discharge, and power consumption.

Although not shown, the smart phone may further include a camera, a bluetooth module, etc., which will not be described herein.

The steps performed by the terminal device in the above-described embodiments may be based on the terminal device structure shown in fig. 13.

Also provided in embodiments of the present application is a computer-readable storage medium having a computer program stored therein, which when run on a computer, causes the computer to perform the methods as described in the foregoing embodiments.

Also provided in embodiments of the present application is a computer program product comprising a program which, when run on a computer, causes the computer to perform the methods described in the foregoing embodiments.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The above embodiments are merely for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.

Claims

1. A method of data processing, comprising:

the method comprises the steps that a node server obtains a task to be processed, wherein the task to be processed is generated by corresponding encoding according to a task type, task data and task identification of the task to be processed, a plurality of bot applications are operated on the node server, each bot application is operated with a plurality of bot application fragments, each bot application fragment establishes a session link with an application server, the application server is a background server of an application program, and the bot applications are used for managing groups in the application program;

the node server analyzes the task to be processed to obtain a task type, task data and task identification corresponding to the task to be processed, wherein the task data is used for indicating specific content to be executed of the task to be processed, and the task identification is used for indicating the node server, the bot application and the bot application fragments for executing the task to be processed;

when the task type indicates that the task to be processed is a message pushing task, the node server generates a message to be pushed according to the task data;

the node server determines a target bot application and a target bot application fragment according to the task identifier;

The node server pushes the message to be pushed to the application server through the target bot application fragment, so that the application server forwards the message to be pushed to a client;

when the task type indicates that the task to be processed is a bot application fragment adjustment task, the node server determines a bot application to be adjusted and a bot application fragment to be adjusted according to the task identifier;

and the node server adjusts the to-be-adjusted bot application and the to-be-adjusted bot application fragments according to the task data.

2. The method of claim 1, wherein the node server adjusting the to-be-adjusted bot application and the to-be-adjusted bot application fragment according to the task data comprises:

the node server closes session links between an original bot application fragment in the bot application to be adjusted and the application server, wherein the original bot application fragment is used as the bot application fragment to be adjusted;

the node server re-groups the bot application fragments of the bot application to be adjusted so as to obtain updated bot application fragments;

the node server instructs the update bot application fragment to establish a session link with the application server.

3. The method of claim 1, wherein the node server adjusting the to-be-adjusted bot application and the to-be-adjusted bot application fragment according to the task data comprises:

the node server closes session links between the to-be-adjusted bot application fragments and the application server;

or,

the node server creates a session link between the to-be-adjusted bot application fragment and the application server.

4. The method according to claim 1, wherein the method further comprises:

the node server receives a first instruction, wherein the first instruction is forwarded by the application server through a target session link, and the first instruction is generated by the client;

the node server responds to the first instruction to acquire corresponding target data;

the node server sends the target data to the application server through the target session link so that the application server forwards the target data to the client.

5. The method according to any one of claims 1 to 4, wherein the node server obtaining a task to be processed comprises:

the node server receives the task to be processed, which is sent by the control end equipment through the message queue, wherein the task to be processed is edited and generated by the control end equipment, the node server registers node registration information in the control end equipment, and the node registration information is used for indicating the bot application operated by the node server and the bot application fragments operated by each bot application;

Or,

the node server receives the task to be processed forwarded by the target task server through the message queue, the task to be processed is edited and generated by control end equipment, the control end equipment sends the task to be processed to the target task server, the node server registers node registration information in the target task server, and the node registration information is used for indicating a bot application operated by the node server and a bot application fragment operated by each bot application.

6. The method according to any of claims 1 to 4, wherein the message to be pushed is a rich text message and the application is a discord program.

7. A data processing apparatus, comprising:

the system comprises an acquisition module, a node server and an application server, wherein the acquisition module is used for acquiring a task to be processed, the task to be processed is generated by corresponding coding according to a task type, task data and task identification of the task to be processed, a plurality of bot applications are operated on the node server, each bot application is operated with a plurality of bot application fragments, each bot application fragment establishes a session link with the application server, the application server is a background server of an application program, and the bot application is used for managing groups in the application program;

the sending module is used for pushing the message to be pushed to the application server through the target bot application fragments so that the application server forwards the message to be pushed to a client;

the processing module is used for determining a to-be-adjusted bot application and a to-be-adjusted bot application fragment according to the task identifier when the task type indicates that the to-be-processed task is a bot application fragment adjustment task; and adjusting the to-be-adjusted bot application and the to-be-adjusted bot application fragments according to the task data.

8. The apparatus of claim 7, wherein the processing module is configured to close a session link between an original bot application slice in the to-be-adjusted bot application and the application server, the original bot application slice being the to-be-adjusted bot application slice; the bot application fragments of the bot application to be adjusted are reconfigured in a grouping mode to obtain updated bot application fragments; and indicating the updated bot application fragments to establish session links with the application server.

9. The apparatus of claim 7, wherein the processing module is configured to:

closing a session link between the to-be-adjusted bot application fragment and the application server;

or,

and creating a session link between the to-be-adjusted bot application fragment and the application server.

10. The apparatus of claim 7, wherein the means for obtaining is configured to receive a first instruction, the first instruction forwarded by the application server over a target session link, the first instruction generated by the client;

the processing module is used for responding to the first instruction to acquire corresponding target data;

11. The apparatus according to any one of claims 7 to 10, wherein the acquisition module is configured to

Receiving the task to be processed sent by control terminal equipment through a message queue, wherein the task to be processed is edited and generated by the control terminal equipment, and the node server registers node registration information in the control terminal equipment, wherein the node registration information is used for indicating a bot application operated by the node server and a bot application fragment operated by each bot application;

Or,

receiving the task to be processed forwarded by a target task server through a message queue, wherein the task to be processed is edited and generated by control end equipment, the control end equipment sends the task to be processed to the target task server, the node server registers node registration information in the target task server, and the node registration information is used for indicating a bot application operated by the node server and a bot application fragment operated by each bot application.

12. The apparatus according to any of claims 7 to 10, wherein the message to be pushed is a rich text message and the application is a discord program.

13. A computer device, comprising: a memory, a processor, and a bus system;

wherein the memory is used for storing programs;

the processor being for executing a program in the memory, the processor being for executing the method of any one of claims 1 to 6 according to instructions in program code;

the bus system is used for connecting the memory and the processor so as to enable the memory and the processor to communicate.

14. A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 6.