CN111526220A

CN111526220A - Method and system for processing information in high concurrency environment

Info

Publication number: CN111526220A
Application number: CN202010638575.1A
Authority: CN
Inventors: 陆舟; 于华章
Original assignee: Feitian Technologies Co Ltd
Current assignee: Shandong Lewen Information Technology Co.,Ltd.
Priority date: 2020-07-06
Filing date: 2020-07-06
Publication date: 2020-08-11
Anticipated expiration: 2040-07-06
Also published as: CN111526220B

Abstract

The invention discloses a method and a system for processing information in a high concurrency environment, relating to the field of communication; the method distributes the simultaneous operation requests of the client and distributes the operation requests to different service services for processing according to the service difference of the operation requests, thereby realizing the separation of connection and service processing; the client sends an operation request to a single shunting service, the shunting service acquires a processing service according to the operation request to process the client request, the single shunting service or the processing service is broken down, normal communication of other clients which are not in communication is not influenced, and the overall communication performance of the system is improved.

Description

Method and system for processing information in high concurrency environment

Technical Field

The present invention relates to the field of communications, and in particular, to a method and system for processing information in a high concurrency environment.

Background

The single service is that all services are deployed to one server, all requested services are processed by the server, and a system formed by multiple clients and one server is basically presented. In the case of stand-alone services, the connections and the business processes are coupled together without separation. When a large number of clients send operation requests simultaneously, the concurrency of the server is very large, but the capability of the stand-alone service for processing information concurrency is very limited, and the server cannot support huge pressure when the server deals with a large number of concurrent requests; in addition, once the server crashes, all clients cannot continue to communicate with the server.

Disclosure of Invention

The invention aims to overcome the defects of the prior art and provides a method and a system for processing information in a high-concurrency environment.

The invention provides a method for processing information in a high concurrency environment, which comprises the following steps:

when the shunting service receives operation data sent by a client, the shunting service determines an interface type according to an operation type in the operation data; sending the interface type to a sixth service;

when the shunting service receives the fifth service identification and the processing service identification including the implementation type, which are sent by the sixth service, the shunting service organizes third sending data according to the sending end identification, the receiving end identification and the transmission data in the operation data; calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service;

when the distribution service receives transmission data, a sending end identity and a receiving end identity which are sent by the routing service, the distribution service sends the transmission data and the sending end identity to a client corresponding to the receiving end identity;

when the sixth service receives the interface type sent by the shunting service, the sixth service determines the processing service according to the interface type and the implementation types of all the processing service identity identifications in the processing service list; determining a fifth service identifier according to the processing service identity identifier of the processing service; sending a fifth service identifier and a processing service identity identifier comprising an implementation type to the offloading service;

when the processing service receives third sending data sent by the shunting service, the processing service determines the online state of the client corresponding to the receiving end identity according to the database, organizes a data transmission success message according to the sending end identity, the receiving end identity and the transmission data when the online state is online, and sends the data transmission success message to a seventh service;

when receiving a message that the processing service sends a successful data transmission, the seventh service stores the successful data transmission message;

the routing service monitors a seventh service; when monitoring that the seventh service stores the successful data transmission message, the routing service acquires the identity identifier of the sending end, the identity identifier of the receiving end and the transmission data from the successful data transmission message; determining a shunting service according to the identity mark of the receiving end and a database; and transmitting the transmission data, the transmitting terminal identity mark and the receiving terminal identity mark to the shunting service.

The invention also provides a system for processing information in a high concurrency environment, which comprises a client, a shunting service, a sixth service, a processing service, a seventh service and a routing service;

the client is used for sending operation data to the shunting service;

the client is also used for receiving the transmission data sent by the shunting service and the identity mark of the sending end;

the shunting service is used for receiving the operation data sent by the client; when receiving operation data sent by a client, determining an interface type according to an operation type in the operation data; sending the interface type to a sixth service;

the offloading service is further configured to receive a fifth service identifier and a processing service identity identifier including an implementation type, where the fifth service identifier is sent by the sixth service; when receiving a fifth service identifier sent by the sixth service and a processing service identifier including an implementation type, the shunting service organizes third sending data according to the sending end identifier, the receiving end identifier and the transmission data in the operation data; calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service;

the distribution service is also used for receiving transmission data, a sending end identity and a receiving end identity which are sent by the routing service; when receiving transmission data, a sending end identity and a receiving end identity which are sent by a routing service, sending the transmission data and the sending end identity to a client corresponding to the receiving end identity;

a sixth service, configured to receive an interface type sent by the offload service; when receiving an interface type sent by the shunting service, determining a processing service according to the interface type and the implementation types of all processing service identity marks in a processing service list; determining a fifth service identifier according to the processing service identity identifier of the processing service; sending a fifth service identifier and a processing service identity identifier comprising an implementation type to the offloading service;

the processing service is used for receiving third sending data sent by the shunting service; when third sending data sent by the shunting service is received, determining the online state of the client corresponding to the receiving end identity according to the database, organizing a successful data transmission message according to the sending end identity, the receiving end identity and the transmission data when the online state is online, and sending the successful data transmission message to a seventh service;

a seventh service, configured to receive a message that the processing service sends a successful data transmission; when receiving a successful data transmission message sent by a processing service, storing the successful data transmission message;

the routing service is used for monitoring a seventh service; when the seventh service is monitored to store the successful data transmission message, acquiring the identity identifier of the sending end, the identity identifier of the receiving end and the transmission data from the successful data transmission message; determining a shunting service according to the identity mark of the receiving end and a database; and transmitting the transmission data, the transmitting terminal identity mark and the receiving terminal identity mark to the shunting service.

Compared with the prior art, the invention has the following advantages: the invention provides a method and a system for processing information in a high concurrency environment; the method distributes the simultaneous operation requests of the client and distributes the operation requests to different service services for processing according to the service difference of the operation requests, thereby realizing the separation of connection and service processing; the client sends an operation request to a single shunting service, the shunting service acquires a processing service according to the operation request to process the client request, the single shunting service or the processing service is broken down, normal communication of other clients which are not in communication is not influenced, and the overall communication performance of the system is improved.

Drawings

Fig. 1-1 and fig. 1-2 are flowcharts of a login operation in a method for processing information in a high concurrency environment according to a second embodiment of the present invention;

fig. 2 is a block diagram of a system for processing information in a high concurrency environment according to a fourth embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. 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 invention.

Example one

The embodiment of the invention provides a method for processing information in a high concurrency environment, which comprises the following steps:

when the shunting service receives a fifth service identifier sent by a sixth service and a processing service identifier comprising an implementation type, the shunting service organizes third sending data according to a sending end identifier, a receiving end identifier and transmission data in the operation data; calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service;

the routing service monitors a seventh service; when the seventh service is monitored to store the successful data transmission message, the routing service acquires the identity identifier of the sending end, the identity identifier of the receiving end and the transmission data from the successful data transmission message; determining a shunting service according to the identity mark of the receiving end and a database; and transmitting the transmission data, the transmitting terminal identity mark and the receiving terminal identity mark to the shunting service.

Optionally, the method in this embodiment further includes: when the client receives a first preset operation, the client acquires a receiving end identity and an operation type according to the first preset operation; when a second preset operation comprising transmission data is received, acquiring a preset third service identifier; organizing operation data according to a preset sending end identity mark, a preset receiving end identity mark, transmission data and an operation type, and sending the operation data to the shunting service according to a third service mark;

further, when the client receives a first preset operation, the client acquires the identity identifier and the operation type of the receiving terminal according to the first preset operation; when a second preset operation including transmission data is received, acquiring a preset third service identifier, specifically: when the client receives the operation of opening the conversation window, the client acquires the identity identification and the operation type of the receiving end according to the operation of opening the conversation window; when receiving a sending information operation comprising transmission data, the client acquires a preset third service identifier;

correspondingly, when the client receives the transmission data and the sending end identity sent by the shunting service, the client displays the transmission data according to the sending end identity, and the process is finished.

Optionally, in this embodiment, when the offloading service receives operation data sent by the client, the offloading service determines the interface type according to the operation type in the operation data; sending the interface type to a sixth service; when the shunting service receives a fifth service identifier sent by a sixth service and a processing service identifier comprising an implementation type, the shunting service organizes third sending data according to a sending end identifier, a receiving end identifier and transmission data in the operation data; and calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service, specifically:

correspondingly, when the shunting service receives the operation data sent by the client, the shunting service creates an auxiliary thread according to the operation data; the offloading service waits for receiving new operation data; the auxiliary thread executes auxiliary operations; when receiving processing response data returned by the processing service, the auxiliary thread is ended;

accordingly, the secondary operation comprises the steps of:

correspondingly, the auxiliary thread acquires a sending end identity corresponding to the client; determining an interface type according to an operation type in the operation data; sending the interface type to a sixth service; waiting for receiving a fifth service identifier sent by a sixth service and a processing service identity identifier comprising an implementation type;

correspondingly, when the auxiliary thread receives the fifth service identification sent by the sixth service and the processing service identification including the implementation type, the auxiliary thread organizes third sending data according to the sending end identification, the receiving end identification and the transmission data; and calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service.

Optionally, in this embodiment, the sixth service determines the processing service according to the interface type and the implementation type of the identity of all processing services in the processing service list, and includes the following steps:

accordingly, step E01: the sixth service acquires a processing service identity from the processing service list as a current processing service identity;

accordingly, step E02: the sixth service acquires the implementation type from the identity of the currently processed service, judges whether the implementation type includes the received interface type, and if so, executes step E03; otherwise, executing step E04;

accordingly, step E03: the sixth service stores the identity of the current processing service into an available processing service list; step E04 is executed;

accordingly, step E04: the sixth service judges whether the next processing service identification can be obtained from the processing service list, if so, the next processing service identification is obtained from the processing service list as the current processing service identification, and the step E02 is returned; otherwise, executing step E05;

accordingly, step E05: the sixth service is based on obtaining a processing service from the list of available processing services.

Optionally, the method in this embodiment further includes: when the processing service is started, the processing service acquires a processing service identity including an implementation type; sending a processing service identity identifier including an implementation type and a preset fifth service identifier to a sixth service;

correspondingly, when the sixth service receives the processing service identity and the fifth service identity which are sent by the processing service and include the implementation type, the sixth service correspondingly stores the processing service identity and the fifth service identity which include the implementation type to the processing service list.

Optionally, after the processing service determines the online status of the client corresponding to the receiving end identity according to the database, the processing service further includes: the processing service determines data to be stored according to the online state and the third sending data, uploads the data to be stored to the database, and sends processing response data to the shunting service;

further, determining data to be saved according to the online state and the third sending data, specifically: when the processing service inquires that the client corresponding to the receiving end identity is online, obtaining data to be stored according to the transmitting end identity, the receiving end identity, the transmission data and the operation type; when the processing service inquires that the client corresponding to the receiving end identity is not online, obtaining data to be stored according to the transmitting end identity, the receiving end identity, the transmission data, the unread state of the transmission data and the operation type;

still further, the method comprises the following steps: when the client corresponding to the receiving end identity is not on line in inquiry, the processing service uploads data to be stored, including the transmitting end identity, the receiving end identity, transmission data, the unread state of the transmission data and the operation type, to a database;

correspondingly, when the database receives the data to be saved, the database saves the data to be saved according to the identity of the receiving end;

correspondingly, when the client corresponding to the receiving end identity is online, the client inquires all transmission data in an unread state from the database according to the receiving end identity and displays the transmission data, and the process is finished;

still further, the method comprises the following steps: when the client corresponding to the identity identification of the receiving end is not on line, the processing service inquires the shunting service from the database according to the identity identification of the transmitting end; sending a transmission failure response to the offloading service;

correspondingly, when the shunting service receives the transmission failure response, the shunting service sends the transmission failure response to the client corresponding to the identity identification of the sending end;

and further correspondingly, the client corresponding to the identity identification of the sending end receives and displays the transmission failure response, and the process is finished.

Optionally, the method in this embodiment further includes the following steps:

correspondingly, the routing service inquires the shunting service from the database according to the identity of the sending terminal; sending successful transmission response data and a sending end identity to the shunting service;

correspondingly, when the shunting service receives the transmission success response data and the sending terminal identity sent by the routing service, the shunting service sends the transmission success response data to the client corresponding to the sending terminal identity;

correspondingly, when the client receives the transmission success response data, the client displays the reception of the transmission success response data, and the process is finished.

Optionally, the method further comprises: when the client receives login data comprising a client identity and a login password, the client waits for receiving login operation; when a login operation is received, generating an access login request according to a preset first service identifier, and sending the access login request to a front-end service;

correspondingly, when the client receives the notification message sent by the seventh service, the client displays the notification message, and the process is finished;

correspondingly, when the client receives a third service identifier sent by the front-end service, the client establishes long connection with the shunting service according to the third service identifier; acquiring login data; determining an operation type according to the login operation; organizing login information according to the login data and the operation type, and sending the login information to the shunting service;

correspondingly, when the front-end service receives an access login request sent by the client, the front-end service sends a query request to a sixth service according to a preset sixth service identifier;

correspondingly, when the front-end service receives a shunting service list sent by a sixth service, the front-end service acquires a third service identifier corresponding to one shunting service from the shunting service list according to a first preset rule; sending a third service identifier to the client;

correspondingly, when the sixth service receives the query request sent by the front-end service, the sixth service acquires a preset shunting service list; sending a shunting service list to a preposed service;

correspondingly, when the sixth service receives the interface type sent by the shunting service, the sixth service determines the processing service according to the interface type and the implementation types of all the processing service identity identifications in the processing service list; acquiring a fifth service identifier from the processing service list according to the processing service identity identifier of the processing service; sending a fifth service identifier and a processing service identity identifier comprising an implementation type to the offloading service;

further, still include: when the shunting service is started, the shunting service acquires a preset sixth service identifier; establishing long connection with a sixth service according to the sixth service identifier; sending a preset third service identifier to a sixth service;

further correspondingly, when the sixth service receives the third service identifier, the sixth service stores the third service identifier in the offload service list.

Further, still include: when the shunting service logs off, the shunting service sends an offline notification and a third service identifier to a sixth service;

further correspondingly, when the sixth service receives the offline notification and the third service identifier sent by the offload service, the sixth service deletes the third service identifier from the offload service list.

Further, the method described in this embodiment further includes: when the processing service is started, the processing service sends a processing service identity identifier including the implementation type and a fifth service identifier to a sixth service;

further correspondingly, when the sixth service receives the processing service identity and the fifth service identity which are sent by the processing service and include the implementation type, the sixth service correspondingly stores the processing service identity and the fifth service identity which include the implementation type to the processing service list.

Correspondingly, when the shunting service receives login information sent by the client, the shunting service determines the interface type according to the operation type; sending the interface type to a sixth service;

correspondingly, when the shunting service receives a fifth service identifier sent by the sixth service and the processing service identity identifier comprising the implementation type, the shunting service calls the implementation type in the processing service identity identifier according to the fifth service identifier to send login data to the processing service;

correspondingly, when the processing service receives login data sent by the shunting service, the processing service acquires a client identity from the login data; inquiring a client identity in a database, when the client identity is inquired, acquiring a preset password corresponding to the client identity from the database, determining whether the preset password is the same as a login password in login data, when the preset password is the same as the login password, acquiring a client object list and a notification message from an object information list according to the client identity and an operation type, generating a login success message according to the client object list and the notification message, and sending the login success message to a seventh service;

correspondingly, when the seventh service receives the login success message sent by the processing service, the seventh service saves the login success message;

correspondingly, when the routing service monitors that the seventh service stores the login success message, the routing service acquires the client object list and the notification message from the monitored login success message; sending notification messages to all clients in the client object list;

correspondingly, when the client is a sending end, the client identity is a sending end identity;

correspondingly, when the client is the receiving end, the client identity is the receiving end identity.

Example two

The second embodiment of the present invention provides a method for processing information in a high concurrency environment, where in this embodiment, transmission data is taken as an example, a client in this embodiment includes a sending end and a receiving end, and the sending end and the receiving end are only used for distinguishing a transmission data sending end and a transmission data receiving end, where the sending end is a transmission data sending end and the receiving end is a transmission data receiving end; as shown in fig. 1-1 and 1-2, the method comprises the steps of:

in this embodiment, both the first and second streaming services are streaming services, and the embodiment distinguishes the first and second streaming services only for better distinguishing the streaming services corresponding to the sending end and the receiving end; the sending end and the receiving end can correspond to the same shunting service and can also correspond to different shunting services; in this embodiment, taking an example that a sending end and a receiving end correspond to different offloading services, the sending end corresponds to a first offloading service, and the receiving end corresponds to a second offloading service;

step 201: when receiving an operation of opening a conversation window, a sending end acquires a receiving end identity and an operation type according to the operation of opening the conversation window; when receiving a sending information operation comprising transmission data, the sending end acquires a third service identifier;

in this embodiment, the operation of opening a dialog window includes opening a single chat operation, opening a group chat operation, and the like; in this embodiment, a single chat operation is opened as an example;

for example, when receiving an operation of opening a dialog window, a transmitting end acquires a receiving end identity to _ session _ id:68 and an operation type msgType: 17 according to the operation of opening the dialog window; when receiving a sending information operation comprising transmission data msg _ data HfCIwAisGETLIU 4Tw1rKw = = the sending end acquires a third service identification channelId 89123;

in this embodiment, the sending end stores 89123 a third service identifier channelId in the login process in embodiment 3;

step 202: a sending end acquires transmission data; organizing operation data according to a preset sending end identity mark, a preset receiving end identity mark, transmission data and an operation type, and sending the operation data to a first shunting service corresponding to a third service mark;

optionally, before sending the operation data to the offload service corresponding to the third service identifier, the method further includes: the sending end establishes long connection with a first shunt service corresponding to the third service identification;

for example, the transmitting end acquires transmission data msg _ data, HfCIwAisGETLIU 4Tw1rKw = =; organizing operation data { from _ user _ id:1, to _ session _ id:68, msg _ type:17, msg _ data: HfCIwAisGETLIU 4Tw1rKw = = and operation type msgType: 17 according to preset transmitting end identity identification from _ user _ id:1, receiving end identity identification to _ session _ id:68, transmission data msg _ data: HfCIwAisGETLIU 4Tw1rKw = } and operation type msgType = } sending operation data { from _ user _ id:1, to _ session _ id:68, msg _ type:17, msg _ data: CIHfAisGELDIU 4Tw1 Kw = } to the shunting service corresponding to the third service identification channelId: 89123;

step 203: the first shunting service receives and analyzes the operation data to obtain a sending end identity mark, a receiving end identity mark, transmission data and an operation type; determining the interface type according to the operation type; sending the interface type to a sixth service;

for example, the first streaming service receives and parses operation data { from _ user _ id:1, to _ session _ id:68, msg _ type:17, msg _ data: hfciwa aisgetldiu4Tw1rKw = } to obtain a transmitting end identity from _ user _ id:1, a receiving end identity to _ session _ id:68, transmission data msg _ data: hfciwa aisgetldiu4Tw1rKw = = and an operation type msgtylep: 17; determining an interface type IChatService according to the operation type msgTyep: 17; sending the interface type IChatservice to a sixth service;

step 204: a sixth service receive interface type; determining processing service according to the interface type and the implementation type of all processing service identification marks in the processing service list;

optionally, determining the processing service according to the interface type and the implementation type of the identity of all processing services in the processing service list includes the following steps:

step A11: the sixth service acquires a processing service identity from a preset processing service list as a current processing service identity;

for example, the sixth service obtains a processing service identity 192.168.0.40:8089/IChatservice from a preset processing service list as the current processing service identity;

step A12: the sixth service acquires the implementation type from the identity of the currently processed service, judges whether the implementation type includes the received interface type, and if so, executes step a 13; otherwise, executing step A14;

for example, the sixth service acquires an implementation type 192.168.0.40:8089/ChatServiceImpl from the current processing service identity, determines whether the implementation type 192.168.0.40:8089/ChatServiceImpl includes the received interface type IChatService, and if so, executes step a 13; otherwise, executing step A14;

step A13: the sixth service stores the identity of the current processing service into an available processing service list; step a14 is executed;

step A14: the sixth service judges whether the next processing service identification can be obtained from the processing service list, if so, the next processing service identification is obtained from the processing service list as the current processing service identification, and the step A12 is returned; otherwise, executing step A15;

step A15: the sixth service obtains a processing service from the list of available processing services;

optionally, the step specifically includes: the sixth service randomly obtains a processing service from the list of available processing services;

optionally, the step specifically includes: the sixth service acquires a processing service from the available processing service list according to a second preset sequence; the second preset sequence may be any preset sequence, and may be obtained by first obtaining the first from the available processing service list, then obtaining the second, and obtaining in sequence; or the last one is firstly obtained, then the last but one is obtained, and the last but one is obtained sequentially;

for example, a sixth service receives an interface type; determining processing service according to the interface type IChatservice and the realization types 192.168.0.40:8089/ChatServiceImpl of all processing service identification in the processing service list;

step 205: the sixth service acquires a fifth service identifier from the processing service list according to the processing service identity identifier of the processing service; sending a fifth service identifier and a processing service identity identifier comprising an implementation type to the first streaming service;

for example, the sixth service obtains the fifth service identifier 192.168.0.40:8089 from the processing service list according to the processing service identifier 192.168.0.40:8089/ICHATService of the processing service; sending a fifth service identification 192.168.0.40:8089 and a processing service identity 192.168.0.40:8089/ICHatService comprising an implementation type 192.168.0.40:8089/ChatServiceImpl to the first forking service;

before this step, still include:

step A21, when the processing service is started, the processing service acquires the processing service identity including the implementation type; sending a processing service identity identifier including an implementation type and a preset fifth service identifier to a sixth service;

step A22, the sixth service receives the processing service identity identifier including the implementation type and the fifth service identifier and correspondingly stores the processing service identity identifier and the fifth service identifier in a processing service list;

step 206: the first shunting service receives a fifth service identifier and a processing service identity identifier comprising an implementation type; organizing third sending data according to the sending end identity identification, the receiving end identity identification, the operation type and the transmission data; calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service;

for example, the first offload service receives the fifth service identification 192.168.0.40:8089 and the processing service identity including the implementation type; organizing third transmission data { from _ user _ id:1, to _ session _ id:68, operation type msg _ type:17 and transmission data msg _ data: HfCIwAisGETLIU 4Tw1rKw = = { from _ user _ id:1, to _ session _ id:68, msg _ type:17, msg _ data: HfCIwAisGETLIU 4Tw1rKw = }; sending third sending data { from _ user _ id:1, to _ session _ id:68, msg _ type:17, msg _ data: HfCIwAisGETLI 4Tw1rKw = } to the processing service according to the implementation type in the fifth service identification 192.168.0.40:8089 call processing service identification;

optionally, this step further includes: the first shunting service judges whether the third sending data is successfully sent to the processing service according to the implementation type in the fifth service identifier calling processing service identity identifier, if so, step 207 is executed; otherwise, returning a sending failure response to the sending end according to the identity of the sending end, and executing the step A31;

step A31: and the sending end receives and displays the sending failure response, and the process is finished.

Step 207: the processing service receives and analyzes the third sending data to obtain a sending end identity, a receiving end identity, an operation type and transmission data; inquiring whether a receiving end corresponding to the receiving end identity mark is online from a database, and when the receiving end corresponding to the receiving end identity mark is inquired to be online, organizing a successful data transmission message according to the transmitting end identity mark, the receiving end identity mark, the operation type and the transmission data, and transmitting the successful data transmission message to a seventh service;

for example, the processing service receives and parses the third transmission data { from _ user _ id:1, to _ session _ id:68, msg _ type:17, msg _ data: hfciwa aisgetldiu4Tw1rKw = } to obtain a transmitting end identity from _ user _ id:1, a receiving end identity to _ session _ id:68, an operation type msg _ type:17, and transmission data msg _ data: hfciwa aisgetldiu4Tw1rKw = }; inquiring whether a receiving end corresponding to the receiving end identity is online from a database, and when the receiving end corresponding to the receiving end identity is online, organizing a transmission data success message { user _ id: 96, session _ id: 2, msg _ id: 5698, msg _ type:17 and transmission data msg _ data according to a transmitting end identity from _ user _ id:1, a receiving end identity to _ session _ id:68, an operation type msg _ type:17 and transmission data msg _ data: HfCIwAisGELDIU 4Tw1rKw = }, and sending a transmission data success message to a seventh service;

optionally, this step further includes: and the processing service uploads the identity identification of the sending end, the identity identification of the receiving end, the transmission data and the operation type to the database.

Optionally, this step further includes: when the fact that a user corresponding to the receiving end identity is not online is inquired, the processing service uploads the sending end identity, the receiving end identity, the transmission data, the unread state of the transmission data and the operation type to the database;

correspondingly, when the database receives the identity identification of the sending end, the identity identification of the receiving end, the transmission data, the unread state and the operation type of the transmission data, the database correspondingly stores the identity identification of the sending end, the identity identification of the receiving end, the transmission data and the unread state and the operation type of the transmission data;

correspondingly, when the receiving end corresponding to the receiving end identity mark is on line, the receiving end inquires all transmission data in an unread state from the database according to the receiving end identity mark and displays the transmission data.

Step 208: the seventh service receives and stores the transmission data success message;

step 209: when the seventh service is monitored to store the successful data transmission message, the routing service acquires the identity identifier of the sending end, the identity identifier of the receiving end, the operation type and the transmission data from the monitored successful data transmission message; querying a second shunt service corresponding to the identity of the receiving end from the database; transmitting the transmission data, the transmitting end identity identification and the receiving end identity identification to a second streaming service;

for example, when the seventh service saving transmission data success message is monitored, the routing service acquires a sending end identity from _ user _ id:1, a receiving end identity to _ session _ id:68, an operation type msg _ type:17 and transmission data msg _ data: hfciwwaisgetiu 4Tw1rKw = = = from the monitored transmission data success message; inquiring a second shunt service corresponding to the receiving end identity to _ session _ id 68 from the database; transmitting the transmission data, the transmitting end identity identification and the receiving end identity identification to a second streaming service;

optionally, this step further includes: the routing service inquires a first shunt service from a database according to the identity of the sending end; sending successful transmission response data and a sending end identity to the first shunt service;

correspondingly, the first shunting service receives the successful transmission response data and the identity mark of the sending end; transmitting transmission success response data to a transmitting terminal corresponding to the transmitting terminal identity;

and correspondingly, the transmitting end receives and displays the transmission success response data, and the operation is finished.

Step 210: the second shunt service receives the transmission data and the identity mark of the sending end, and sends the transmission data and the identity mark of the sending end to the receiving end according to the identity mark of the receiving end;

optionally, the step specifically includes: the second shunt service receives the transmission data and the identity mark of the sending end, and sends the transmission data and the identity mark of the sending end to the receiving end corresponding to the identity mark of the receiving end;

for example, the second streaming service receives transmission data msg _ data, hfciwwaisgetiu 4Tw1rKw = = and sender id from _ user _ id:1, and transmits the transmission data msg _ data, hfciwwaisgetiu 4Tw1rKw = = and sender id from _ user _ id:1, to the receiver corresponding to the receiver id;

optionally, step 210 is further followed by step 211: the receiving end receives the transmission data and the identity mark of the sending end; displaying the transmission data according to the identity mark of the sending end, and ending;

optionally, the step specifically includes: the receiving end receives the transmission data and the identity mark of the sending end; displaying the transmission data on an operation interface corresponding to the identity identification of the sending end, and ending;

for example, the receiving end receives transmission data msg _ data, HfCIwAisGETLIU 4Tw1rKw = = and the transmitting end identification from _ user _ id: 1; and displaying the transmission data on an operation interface corresponding to the sending end identity from _ user _ id:1, and ending.

EXAMPLE III

The third embodiment of the present invention provides a method for processing information in a high concurrency environment, where a login operation is taken as an example in this embodiment, the method includes the following steps:

step 301: when a user inputs login data comprising a client identity and a login password, the client waits for receiving login operation; when a login operation is received, the client generates an access login request according to a preset first service identifier and sends the access login request to the front-end service;

the client identity in this embodiment includes a sending end identity and a receiving end identity, and when the client is a sending end, the client identity is the sending end identity; when the client is a receiving end, the client identity is a receiving end identity;

the service identifier of the service in this embodiment includes an IP address and a port number corresponding to the service;

step 302: the preposed service receives the access login request, generates a query request according to a preset sixth service identifier of a sixth service, and sends the query request to the sixth service;

step 303: the sixth service receives the query request and acquires a preset shunting service list; sending a shunting service list to a preposed service;

in this embodiment, when the offload service is started, the offload service registers the third service identifier of the offload service with the sixth service, and the specific registration process is as follows:

step A01, when the shunting service is started, the shunting service acquires a preset sixth service identifier; establishing long connection with a sixth service according to the sixth service identifier; sending a preset third service identifier to a sixth service;

step A02, the sixth service receives the third service identification, and correspondingly stores the third service identification to the shunting service list;

in this embodiment, when the offload service logs out, the offload service notifies the sixth service of its own log-out condition, and the specific log-out process is as follows:

step A03, when the shunting service logs off, the shunting service sends a offline notification and a third service identifier to a sixth service;

step A04, the sixth service receives the offline notification and the third service identifier, and deletes the third service identifier from the shunting service list;

alternatively, step a03 and step a04 may be replaced with: when the sixth service finds that the long connection with the offloading service is disconnected, the sixth service deletes the third service identifier of the offloading service corresponding to the disconnected long connection from the offloading service list;

step 304: the preposed service receives a shunting service list; determining a shunting service according to a first preset rule and a shunting service list; acquiring a third service identifier corresponding to the shunting service, and sending the third service identifier to the client;

optionally, determining the offloading service according to the first preset rule and the offloading service list, specifically: the front-end service randomly acquires an offload service from the offload service list.

Optionally, determining the offloading service according to the first preset rule and the offloading service list, specifically: the front-end service acquires a shunting service from the shunting service list according to a first preset sequence;

for example, the front end service acquires a first offload service in an offload service list;

for another example, the front-end service acquires the last offload service in the offload service list;

for another example, the front-end service acquires the next offload service in the offload service list;

step 305: the client receives a third service identifier; creating a long connection with the shunting service according to the third service identifier; acquiring login data; determining an operation type according to the login operation; organizing login information according to the login data and the operation type, and sending the login information to the shunting service;

optionally, a long connection is created with the offloading service according to the third service identifier, specifically: the client establishes long connection with the shunting service corresponding to the third service identifier;

further, after the long connection is created by the offload service corresponding to the third service identifier, the method further includes: the client judges whether the long connection is successfully established, if so, the step 306 is executed, otherwise, the operation is finished;

still further, the end is replaced with: the client returns to step 301.

Step 306: the shunting service receives and analyzes the login information to obtain login data and an operation type; determining the interface type according to the operation type; sending the interface type to a sixth service;

step 307: a sixth service receive interface type; determining processing service according to the interface type and the implementation type of all processing service identification marks in the processing service list; acquiring a fifth service identifier from the processing service list according to the processing service identity identifier of the processing service; sending a fifth service identifier and a processing service identity identifier comprising an implementation type to the offloading service;

optionally, in this step, determining a processing service according to the interface type and the implementation type of the identity of all processing services in the processing service list includes the following steps:

step A11: the sixth service acquires a processing service identity from the processing service list as a current processing service identity;

step A15: the sixth service obtains the processing service from the available processing service list;

optionally, the step specifically includes: the sixth service randomly acquires a processing service from the processing service list;

optionally, the step specifically includes: the sixth service acquires a processing service from the processing service list according to a second preset sequence; for example, the second preset order is to obtain the processing service of the first in the processing service list; for another example, the second preset order is to obtain the last processing service in the processing service list;

before this step, still include:

step A21, when the processing service is started, the processing service acquires the processing service identity mark comprising the implementation type and a preset fifth service mark; sending a processing service identity including an implementation type and a fifth service identity of the sixth service to the sixth service;

step 308: the shunting service receives a fifth service identifier and a processing service identity identifier comprising an implementation type; calling the implementation type in the processing service identity according to the fifth service identity to send login data to the processing service;

step 309: the processing service receives login data; acquiring a client identity from login data; inquiring a client identity in a database, when the client identity is inquired, acquiring a preset password corresponding to the client identity from the database, determining whether the preset password is the same as a login password in login data, when the preset password is the same as the login password, acquiring a client object list and a notification message from the database according to the client identity and a preset operation type, generating a login success message according to the client object list and the notification message, and sending the login success message to a seventh service;

optionally, this step further includes: when the client identity is not inquired, sending error reporting information to the distribution service, and executing the step B-01;

b-01, the shunting service receives the error information; sending error reporting information to a client;

step B-02: and the client receives and displays the error information, and the operation is finished.

In this embodiment, the distribution service, the routing service, and the processing service may access the database at any time; when a client identity mark in a client is registered to the shunting service, the shunting service sends the client identity mark, login time, a second IP address and a second port mark to a processing service, the processing service uploads the client identity mark, the login time, the second IP address and the second port mark to a database, and the database correspondingly stores the client identity mark, the login time, the second IP address and the second port mark to a client object list;

optionally, this step further includes: sending error reporting information to the shunting service, and executing the step B-01;

b-11, the shunting service receives error information; sending error information to the client, and executing the step B-12;

step B-12: and the client receives and displays the error information, and the operation is finished.

Step 310: the seventh service receives and stores the login success message;

step 311: when the seventh service storage login success message is monitored, the routing service acquires a client object list and a notification message from the monitored login success message; sending notification messages to all clients in the client object list;

step 312: the client receives and displays the notification message, and the process is finished;

optionally, before sending the notification message to all clients in the client object list, the method further includes: the routing service judges whether the client object list comprises all clients, if so, step B-21, otherwise, a notification message is sent to all clients in the client object list;

step B-21, the routing service sends a notification message to all registered shunting services;

step B-22: the flow distribution service sends a notification message to all communication clients;

step B-23: and the client displays the notification message and finishes.

Optionally, the notification message is sent to all clients in the client object list, specifically:

step B31: the routing service acquires a client object from the client object list as a current client object;

step B32: the routing service acquires the shunting service corresponding to the current client object from the database; sending a notification message to a shunting service corresponding to the current client object;

before this step, still include: when the shunting service is on line, registering the third service identification code of the shunting service to the routing service;

this step is followed by:

step B41, the shunting service receiving the notification message sends the notification message to the corresponding client object;

and step B42, the client receives and displays the notification message, and the process is finished.

Step B33: the routing service judges whether the next client object can be obtained from the client object list, if so, the next client object is obtained from the client object list and is used as the current client object, and the step B32 is returned; otherwise, the message is informed to be sent completely, and the process is finished.

Example four

The fourth embodiment of the present invention provides a system for processing information in a high concurrency environment, as shown in fig. 2: the system comprises a client, a shunting service, a sixth service, a processing service, a seventh service and a routing service;

the client is used for sending the operation data to the shunting service;

optionally, when the offloading service is used for receiving operation data sent by the client, determining the interface type according to the operation type in the operation data; sending the interface type to a sixth service; when a fifth service identification sent by a sixth service and a processing service identification including an implementation type are received, organizing third sending data according to a sending end identification, a receiving end identification and transmission data in the operation data; when the implementation type in the processing service identity is called according to the fifth service identity to send third sending data to the processing service, the offloading service is specifically configured to: when receiving operation data sent by a client, creating an auxiliary thread according to the operation data; waiting for receiving new operation data;

accordingly, the offload service includes an assist thread module;

correspondingly, the auxiliary thread module is used for executing auxiliary operation; when receiving the processing response data returned by the processing service, ending;

correspondingly, the auxiliary thread module is specifically used for acquiring the identity of the sending terminal corresponding to the client; determining an interface type according to an operation type in the operation data; sending the interface type to a sixth service; waiting for receiving a fifth service identifier sent by a sixth service and a processing service identity identifier comprising an implementation type; when a fifth service identification sent by a sixth service and a processing service identification including an implementation type are received, organizing third sending data according to the sending end identification, the receiving end identification and the transmission data; and calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service.

The shunting service is also used for receiving a fifth service identifier sent by a sixth service and a processing service identity identifier comprising an implementation type; when receiving a fifth service identifier sent by a sixth service and a processing service identifier including an implementation type, the shunting service organizes third sending data according to the sending end identifier, the receiving end identifier and the transmission data in the operation data; calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service;

optionally, the processing service is further configured to, when starting, obtain a processing service identity including the implementation type; sending a processing service identity identifier including an implementation type and a preset fifth service identifier to a sixth service;

correspondingly, the sixth service is further configured to correspondingly store the processing service identity and the fifth service identity including the implementation type in the processing service list when receiving the processing service identity and the fifth service identity including the implementation type sent by the processing service.

optionally, the sixth service comprises a determining module;

correspondingly, the determining module is used for determining the processing service according to the interface type and the implementation type of all the processing service identification marks in the processing service list;

accordingly, the determination module includes a first determination unit, a first judgment unit, a second judgment unit,

Correspondingly, the first acting unit is used for acquiring a processing service identity from the processing service list as a current processing service identity;

correspondingly, the first judging unit is used for acquiring the implementation type from the current processing service identity, judging whether the implementation type comprises the received interface type or not, and if so, triggering the first storing unit; otherwise, triggering a second judgment unit;

correspondingly, the first storing unit is used for storing the identity of the current processing service into the available processing service list and triggering the second judging unit;

correspondingly, the second judging unit is used for judging whether the next processing service identification can be obtained from the processing service list, if so, the next processing service identification is obtained from the processing service list as the current processing service identification, and the first judging unit is triggered; otherwise, a processing service is obtained from the available processing service list.

Optionally, the processing service is further configured to determine data to be saved according to the online state and the third sending data, upload the data to be saved to the database, and send processing response data to the offloading service.

Further, when the processing service is used for determining the data to be stored according to the online state and the third sending data, the processing service is specifically used for obtaining the data to be stored according to the sending end identity, the receiving end identity, the transmission data and the operation type when the client corresponding to the receiving end identity is queried to be online; when the client corresponding to the receiving end identity is not on line in inquiry, obtaining data to be stored according to the sending end identity, the receiving end identity, the transmission data, the unread state of the transmission data and the operation type;

still further, the system further comprises a database; when the processing service is used for inquiring that a client corresponding to the receiving end identity is online and obtaining data to be stored according to the sending end identity, the receiving end identity, the transmission data and the operation type, the processing service is specifically used for uploading the data to be stored, which comprises the sending end identity, the receiving end identity, the transmission data, the unread state of the transmission data and the operation type, to a database when the client corresponding to the receiving end identity is not online;

correspondingly, the database is used for storing the data to be stored according to the identity mark of the receiving end when the data to be stored is received;

correspondingly, the client corresponding to the receiving end identity is also used for inquiring all transmission data in an unread state from the database according to the receiving end identity and displaying the transmission data when the client is online, and the process is finished;

still further, the system further comprises a database; when the processing service is used for inquiring that the client corresponding to the identity identification of the receiving end is not on line, the processing service inquires the shunting service from the database according to the identity identification of the transmitting end; sending a transmission failure response to the offloading service;

correspondingly, the shunting service is further used for sending a transmission failure response to the client corresponding to the identity of the sending end when receiving the transmission failure response;

and correspondingly, the client corresponding to the identity of the sending end is also used for receiving the transmission failure response, displaying and ending.

Optionally, the routing service is further configured to query a distribution service from a database according to the identity of the sending end; sending successful transmission response data and a sending end identity to the shunting service;

correspondingly, the shunting service is also used for sending the transmission success response data to the client corresponding to the identity of the sending end when receiving the transmission success response data and the identity of the sending end sent by the routing service;

correspondingly, the client is also used for displaying the received transmission success response data when receiving the transmission success response data, and ending.

Optionally, the client in this embodiment is further configured to, when receiving the first preset operation, obtain the identity and the operation type of the receiving end according to the first preset operation; when a second preset operation comprising transmission data is received, acquiring a preset third service identifier; organizing operation data according to a preset sending end identity mark, a preset receiving end identity mark, transmission data and an operation type, and sending the operation data to the shunting service according to a third service mark; the method is also used for displaying the transmission data according to the identity of the sending end when receiving the transmission data and the identity of the sending end sent by the shunting service, and ending;

further, when the client is used for receiving the first preset operation, the client acquires the identity identifier and the operation type of the receiving terminal according to the first preset operation; when a second preset operation including transmission data is received and a preset third service identifier is acquired, the client is specifically configured to: when receiving an operation of opening a conversation window, acquiring a receiving end identity and an operation type according to the operation of opening the conversation window; and when receiving a sending information operation comprising transmission data, acquiring a preset third service identifier.

Optionally, the system in this embodiment further includes a front end service:

correspondingly, the client is also used for waiting to receive login operation when login data comprising the client identity and the login password are received; when a login operation is received, generating an access login request according to a preset first service identifier, and sending the access login request to a front-end service; the terminal is also used for displaying the notification message when receiving the notification message sent by the seventh service, and ending; the system is also used for establishing long connection with the shunting service according to the third service identification when receiving the third service identification sent by the preposed service; acquiring login data; determining an operation type according to the login operation; organizing login information according to the login data and the operation type, and sending the login information to the shunting service;

correspondingly, the front-end service is used for sending a query request to a sixth service according to a preset sixth service identifier when receiving an access login request sent by the client; the third service identifier is used for acquiring a third service identifier corresponding to a shunting service from the shunting service list according to a first preset rule when the shunting service list sent by the sixth service is received; sending a third service identifier to the client;

correspondingly, the sixth service is further configured to obtain a preset shunting service list when receiving a query request sent by the front-end service; sending a shunting service list to a preposed service; the method is also used for determining the processing service according to the interface type and the implementation types of all the processing service identification marks in the processing service list when receiving the interface type sent by the shunting service; acquiring a fifth service identifier from the processing service list according to the processing service identity identifier of the processing service; sending a fifth service identifier and a processing service identity identifier comprising an implementation type to the offloading service;

further, the shunting service is also used for acquiring a preset sixth service identifier when the shunting service is started; establishing long connection with a sixth service according to the sixth service identifier; sending a preset third service identifier to a sixth service;

correspondingly, the sixth service is further configured to, when the third service identifier is received, store the third service identifier in the offload service list.

Further, the offloading service is further configured to send a logout notification and a third service identifier to a sixth service when logging off;

correspondingly, the sixth service is further configured to delete the third service identifier from the offload service list when the offline notification and the third service identifier sent by the offload service are received.

Further, the processing service is also used for sending a processing service identity including the implementation type and a fifth service identity of the processing service to the sixth service when the processing service is started;

optionally, the sixth service is further configured to, when receiving the processing service identity and the fifth service identity that are sent by the processing service and include the implementation type, correspondingly store the processing service identity and the fifth service identity that include the implementation type in the processing service list.

Correspondingly, the shunting service is also used for determining the interface type according to the operation type when the login information sent by the client is received; sending the interface type to a sixth service; the server is also used for calling the implementation type in the processing service identity according to the fifth service identity to send login data to the processing service when receiving the fifth service identity and the processing service identity comprising the implementation type, which are sent by the sixth service;

correspondingly, the processing service is also used for acquiring the client identity identifier from the login data when the login data sent by the shunting service is received; inquiring a client identity in a database, when the client identity is inquired, acquiring a preset password corresponding to the client identity from the database, determining whether the preset password is the same as a login password in login data, when the preset password is the same as the login password, acquiring a client object list and a notification message from an object information list according to the client identity and an operation type, generating a login success message according to the client object list and the notification message, and sending the login success message to a seventh service;

correspondingly, the seventh service is further configured to store the login success message when receiving the login success message sent by the processing service;

correspondingly, the routing service is also used for acquiring a client object list and a notification message from the monitored login success message when the seventh service storage login success message is monitored; sending notification messages to all clients in the client object list;

The above description is only for the preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present invention are included in the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A method for processing information in a high concurrency environment, the method comprising:

2. The method of claim 1, further comprising: when the client receives a first preset operation, the client acquires a receiving end identity and an operation type according to the first preset operation; when a second preset operation comprising transmission data is received, acquiring a preset third service identifier; organizing operation data according to a preset sending end identity mark, a preset receiving end identity mark, transmission data and an operation type, and sending the operation data to the shunting service according to a third service mark;

and when the client receives the transmission data and the sending end identity sent by the shunting service, the client displays the transmission data according to the sending end identity and finishes.

3. The method of claim 2, wherein when the client receives the first preset operation, the client obtains the identity of the receiving end and the operation type according to the first preset operation; when a second preset operation including transmission data is received, acquiring a preset third service identifier, specifically: when the client receives the operation of opening the conversation window, the client acquires the identity identification and the operation type of the receiving end according to the operation of opening the conversation window; and when receiving a sending information operation comprising transmission data, the client acquires a preset third service identifier.

4. The method according to claim 1, wherein when the offloading service receives the operation data sent by the client, the offloading service determines the interface type according to an operation type in the operation data; sending the interface type to a sixth service; when the shunting service receives the fifth service identification and the processing service identification including the implementation type, which are sent by the sixth service, the shunting service organizes third sending data according to the sending end identification, the receiving end identification and the transmission data in the operation data; and calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service, specifically:

when the shunting service receives operation data sent by a client, the shunting service creates an auxiliary thread according to the operation data; the offloading service waits for receiving new operation data; the helper thread performs a helper operation; when processing response data returned by the processing service is received, the auxiliary thread is ended;

the secondary operation comprises the steps of:

the auxiliary thread acquires a sending end identity corresponding to the client; determining an interface type according to an operation type in the operation data; sending the interface type to a sixth service; waiting for receiving a fifth service identifier sent by a sixth service and a processing service identity identifier comprising an implementation type;

when the auxiliary thread receives a fifth service identifier sent by the sixth service and a processing service identifier including an implementation type, the auxiliary thread organizes third sending data according to the sending end identifier, the receiving end identifier and the transmission data; and calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service.

5. The method of claim 1, wherein the sixth service determines the processing service according to the interface type and the implementation type of all processing service identities in the processing service list, comprising the steps of:

step E01: the sixth service acquires a processing service identity from the processing service list as a current processing service identity;

step E02: the sixth service acquires the implementation type from the identity of the currently processed service, judges whether the implementation type includes the received interface type, and if so, executes step E03; otherwise, executing step E04;

step E03: the sixth service stores the identity of the current processing service to an available processing service list; step E04 is executed;

step E04: the sixth service determines whether the next processing service identification can be obtained from the processing service list, if so, the next processing service identification is obtained from the processing service list as the current processing service identification, and the step E02 is returned; otherwise, executing step E05;

step E05: the sixth service obtains a processing service from a list of available processing services.

6. The method of claim 1, further comprising: when the processing service is started, the processing service acquires a processing service identity including an implementation type; sending a processing service identity identifier including an implementation type and a preset fifth service identifier to a sixth service;

and when the sixth service receives the processing service identity and the fifth service identity which are sent by the processing service and comprise the implementation type, the sixth service correspondingly stores the processing service identity and the fifth service identity which comprise the implementation type to a processing service list.

7. The method of claim 1, wherein after the processing service determines the presence status of the client corresponding to the recipient identity from the database, the method further comprises: and the processing service determines data to be stored according to the online state and the third sending data, uploads the data to be stored to the database and sends processing response data to the shunting service.

8. The method according to claim 7, wherein the determining the data to be saved according to the online status and the third sending data specifically comprises: when the processing service inquires that the client corresponding to the receiving end identity is online, obtaining data to be stored according to the transmitting end identity, the receiving end identity, the transmission data and the operation type; and when the processing service inquires that the client corresponding to the receiving end identity is not online, obtaining the data to be stored according to the transmitting end identity, the receiving end identity, the transmission data, the unread state of the transmission data and the operation type.

9. The method of claim 8, further comprising the steps of:

when the client corresponding to the receiving end identity is not on line in inquiry, the processing service uploads data to be stored, including the transmitting end identity, the receiving end identity, transmission data, the unread state of the transmission data and the operation type, to a database;

when the database receives the data to be stored, the database stores the data to be stored according to the identity of the receiving end;

and when the client corresponding to the receiving end identity mark is on line, the client inquires all transmission data in an unread state from the database according to the receiving end identity mark, displays the transmission data and finishes the operation.

10. The method of claim 8, further comprising the steps of:

when the client corresponding to the identity identification of the receiving end is not on line, the processing service inquires the shunting service from the database according to the identity identification of the transmitting end; sending a transmission failure response to the offloading service;

when the shunting service receives the transmission failure response, the shunting service sends the transmission failure response to the client corresponding to the identity identification of the sending end;

and the client corresponding to the identity identification of the sending end receives and displays the transmission failure response, and the process is finished.

11. The method of claim 1, further comprising the steps of:

the routing service inquires shunting service from a database according to the identity of the sending end; sending successful transmission response data and a sending end identity to the shunting service;

when the shunting service receives the transmission success response data and the sending end identity sent by the routing service, the shunting service sends the transmission success response data to the client corresponding to the sending end identity;

and when the client receives the transmission success response data, the client displays the reception of the transmission success response data, and the process is finished.

12. The method of claim 1, further comprising:

when the client receives login data comprising a client identity and a login password, the client waits for receiving login operation; when a login operation is received, generating an access login request according to a preset first service identifier, and sending the access login request to a front-end service;

when the client receives the notification message sent by the seventh service, the client displays the notification message, and the process is finished;

when the client receives a third service identifier sent by the front-end service, the client establishes long connection with the shunting service according to the third service identifier; acquiring login data; determining an operation type according to the login operation; organizing login information according to the login data and the operation type, and sending the login information to the shunting service;

when the front-end service receives an access login request sent by a client, the front-end service sends a query request to a sixth service according to a preset sixth service identifier;

when the front-end service receives a shunting service list sent by a sixth service, the front-end service acquires a third service identifier corresponding to one shunting service from the shunting service list according to a first preset rule; sending a third service identifier to the client;

when the sixth service receives a query request sent by the front-end service, the sixth service acquires a preset shunting service list; sending a shunting service list to a preposed service;

when the sixth service receives the interface type sent by the shunting service, the sixth service determines the processing service according to the interface type and the implementation types of all the processing service identity identifications in the processing service list; acquiring a fifth service identifier from the processing service list according to the processing service identity identifier of the processing service; sending a fifth service identifier and a processing service identity identifier comprising an implementation type to the offloading service;

when the shunting service receives login information sent by a client, the shunting service determines an interface type according to an operation type; sending the interface type to a sixth service;

when the shunting service receives a fifth service identifier sent by a sixth service and a processing service identity identifier comprising an implementation type, the shunting service calls the implementation type in the processing service identity identifier according to the fifth service identifier to send login data to the processing service;

when the processing service receives login data sent by the shunting service, the processing service acquires a client identity from the login data; inquiring a client identity in a database, when the client identity is inquired, acquiring a preset password corresponding to the client identity from the database, determining whether the preset password is the same as a login password in login data, when the preset password is the same as the login password, acquiring a client object list and a notification message from an object information list according to the client identity and an operation type, generating a login success message according to the client object list and the notification message, and sending the login success message to a seventh service;

when the seventh service receives the login success message sent by the processing service, the seventh service stores the login success message;

when the routing service monitors that the seventh service stores the login success message, the routing service acquires a client object list and a notification message from the monitored login success message; sending notification messages to all clients in the client object list;

when the client is a sending end, the client identity is a sending end identity;

and when the client is a receiving end, the client identity is the receiving end identity.

13. The method of claim 12, further comprising: when the shunting service is started, the shunting service acquires a preset sixth service identifier; establishing long connection with a sixth service according to the sixth service identifier; sending a preset third service identifier to a sixth service;

and when the sixth service receives the third service identifier, the sixth service stores the third service identifier in the shunting service list.

14. The method of claim 12, further comprising: when the shunting service logs off, the shunting service sends an offline notification and a third service identifier to a sixth service;

and when the sixth service receives the offline notification and the third service identifier sent by the offloading service, the sixth service deletes the third service identifier from the offloading service list.

15. The method of claim 12, further comprising:

when the processing service is started, the processing service sends a processing service identity identifier including the implementation type and a fifth service identifier to a sixth service;

when the sixth service receives the processing service identity and the fifth service identity which are sent by the processing service and comprise the implementation type, the sixth service correspondingly stores the processing service identity and the fifth service identity which comprise the implementation type into a processing service list.

16. The system for processing the information under the high concurrency environment is characterized by comprising a client, a shunting service, a sixth service, a processing service, a seventh service and a routing service;

the client is used for sending operation data to the shunting service;

17. The system of claim 16, wherein the client is further configured to, when receiving the first preset operation, obtain a receiving end identity and an operation type according to the first preset operation; when a second preset operation comprising transmission data is received, acquiring a preset third service identifier; organizing operation data according to a preset sending end identity mark, a preset receiving end identity mark, transmission data and an operation type, and sending the operation data to the shunting service according to a third service mark;

and the client is also used for displaying the transmission data according to the identity of the sending end when receiving the transmission data and the identity of the sending end sent by the shunting service, and ending.

18. The system of claim 17, wherein when the client is configured to receive a first preset operation, the client obtains a receiving end identity and an operation type according to the first preset operation; when a second preset operation including transmission data is received and a preset third service identifier is acquired, the client is specifically configured to: when receiving an operation of opening a conversation window, acquiring a receiving end identity and an operation type according to the operation of opening the conversation window; and when receiving a sending information operation comprising transmission data, acquiring a preset third service identifier.

19. The system of claim 16, wherein when the offload service is used for receiving operation data sent by a client, the interface type is determined according to an operation type in the operation data; sending the interface type to a sixth service; when receiving a fifth service identifier sent by the sixth service and a processing service identifier including an implementation type, organizing third sending data according to a sending end identifier, a receiving end identifier and transmission data in operation data; when the third sending data is sent to the processing service according to the implementation type in the fifth service identifier calling processing service identifier, the offloading service is specifically configured to: when receiving operation data sent by a client, creating an auxiliary thread according to the operation data; waiting for receiving new operation data;

the offloading service includes an auxiliary thread module;

the auxiliary thread module is used for executing auxiliary operation; when receiving the processing response data returned by the processing service, ending;

the auxiliary thread module is specifically used for acquiring a sending end identity corresponding to the client; determining an interface type according to an operation type in the operation data; sending the interface type to a sixth service; waiting for receiving a fifth service identifier sent by a sixth service and a processing service identity identifier comprising an implementation type; when receiving a fifth service identifier sent by the sixth service and a processing service identifier including an implementation type, organizing third sending data according to the sending end identifier, the receiving end identifier and the transmission data; and calling the implementation type in the processing service identity according to the fifth service identity to send third sending data to the processing service.

20. The system of claim 16, wherein the sixth service comprises a determination module;

the determining module is used for determining the processing service according to the interface type and the implementation type of all the processing service identity identifications in the processing service list;

the determining module comprises a first acting unit, a first judging unit, a second judging unit,

The first serving unit is used for acquiring a processing service identity from a processing service list as a current processing service identity;

the first judging unit is used for acquiring the implementation type from the current processing service identity, judging whether the implementation type comprises the received interface type or not, and triggering the first storage unit if the implementation type comprises the received interface type; otherwise, triggering the second judgment unit;

the first storing unit is configured to store the identity of the current processing service in an available processing service list, and trigger the second determining unit;

the second judging unit is configured to judge whether a next processing service identity can be obtained from the processing service list, and if so, obtain the next processing service identity from the processing service list as a current processing service identity, and trigger the first judging unit; otherwise, a processing service is obtained from the available processing service list.

21. The system of claim 16, wherein the processing service is further configured to, upon startup, obtain a processing service identity comprising an implementation type; sending a processing service identity identifier including an implementation type and a preset fifth service identifier to a sixth service;

the sixth service is further configured to, when receiving the processing service identity and the fifth service identity that are sent by the processing service and include the implementation type, correspondingly store the processing service identity and the fifth service identity that include the implementation type in the processing service list.

22. The system of claim 16, wherein the processing service is further configured to determine data to be saved based on the online status and the third sent data, upload the data to be saved to the database, and send the processing response data to the offload service.

23. The system according to claim 22, wherein when the processing service is configured to determine the data to be saved according to the online status and the third sending data, the processing service is specifically configured to obtain the data to be saved according to the sending end identity, the receiving end identity, the transmission data, and the operation type when the client corresponding to the receiving end identity is queried to be online; and when the client corresponding to the receiving end identity is not on line in the inquiry, obtaining the data to be stored according to the sending end identity, the receiving end identity, the transmission data, the unread state of the transmission data and the operation type.

24. The system of claim 23, wherein the system further comprises a database;

when the processing service is used for inquiring that a client corresponding to the receiving end identity is online and obtaining data to be stored according to the sending end identity, the receiving end identity, the transmission data and the operation type, the processing service is specifically used for uploading the data to be stored comprising the sending end identity, the receiving end identity, the transmission data, the unread state of the transmission data and the operation type to a database when the client corresponding to the receiving end identity is not online;

the database is used for storing the data to be stored according to the identity mark of the receiving end when the data to be stored is received;

and the client corresponding to the receiving end identity mark is also used for inquiring all transmission data in an unread state from the database according to the receiving end identity mark and displaying the transmission data when the client is online, and ending.

25. The system of claim 23, wherein the system further comprises a database;

when the processing service is used for inquiring that the client corresponding to the identity identification of the receiving end is not on line, the processing service inquires the shunting service from the database according to the identity identification of the sending end; sending a transmission failure response to the offloading service;

the distribution service is also used for sending a transmission failure response to the client corresponding to the identity identification of the sending end when receiving the transmission failure response;

and the client corresponding to the identity of the sending end is also used for receiving and displaying the transmission failure response and ending the transmission failure response.

26. The system of claim 16, wherein the routing service is further configured to query the offload service from a database based on the sender id; sending successful transmission response data and a sending end identity to the shunting service;

the distribution service is also used for sending the transmission success response data to the client corresponding to the identity identification of the sending end when receiving the transmission success response data and the identity identification of the sending end sent by the routing service;

and the client is also used for displaying the received transmission success response data when receiving the transmission success response data and ending.

27. The system of claim 16, wherein the system further comprises a front-end service:

the client is also used for waiting for receiving login operation when login data comprising the client identity and the login password are received; when a login operation is received, generating an access login request according to a preset first service identifier, and sending the access login request to a front-end service; the terminal is also used for displaying the notification message when receiving the notification message sent by the seventh service, and ending; the system is also used for establishing long connection with the shunting service according to the third service identification when receiving the third service identification sent by the preposed service; acquiring login data; determining an operation type according to the login operation; organizing login information according to the login data and the operation type, and sending the login information to the shunting service;

the pre-service is used for sending a query request to a sixth service according to a preset sixth service identifier when receiving an access login request sent by a client; the third service identifier is used for acquiring a third service identifier corresponding to a shunting service from the shunting service list according to a first preset rule when the shunting service list sent by the sixth service is received; sending a third service identifier to the client;

the sixth service is also used for acquiring a preset shunting service list when receiving a query request sent by the front-end service; sending a shunting service list to a preposed service; the method is also used for determining the processing service according to the interface type and the implementation types of all the processing service identification marks in the processing service list when receiving the interface type sent by the shunting service; acquiring a fifth service identifier from the processing service list according to the processing service identity identifier of the processing service; sending a fifth service identifier and a processing service identity identifier comprising an implementation type to the offloading service;

the shunting service is also used for determining the interface type according to the operation type when receiving the login information sent by the client; sending the interface type to a sixth service; the server is also used for calling the implementation type in the processing service identity according to the fifth service identity to send login data to the processing service when receiving the fifth service identity and the processing service identity comprising the implementation type, which are sent by the sixth service;

the processing service is also used for acquiring the client identity identifier from the login data when the login data sent by the shunting service is received; inquiring a client identity in a database, when the client identity is inquired, acquiring a preset password corresponding to the client identity from the database, determining whether the preset password is the same as a login password in login data, when the preset password is the same as the login password, acquiring a client object list and a notification message from an object information list according to the client identity and an operation type, generating a login success message according to the client object list and the notification message, and sending the login success message to a seventh service;

the seventh service is further configured to store the login success message when receiving the login success message sent by the processing service;

the routing service is further used for acquiring a client object list and a notification message from the monitored login success message when the seventh service storage login success message is monitored; sending notification messages to all clients in the client object list;

28. The system of claim 27, wherein the offload service is further configured to, when enabled, obtain a preset sixth service identifier; establishing long connection with a sixth service according to the sixth service identifier; sending a preset third service identifier to a sixth service;

and the sixth service is further configured to store the third service identifier in the offload service list when the third service identifier is received.

29. The system of claim 27, wherein the offload service is further configured to send a logoff notification and a third service identification to a sixth service upon logoff;

the sixth service is further configured to delete the third service identifier from the offload service list when receiving the offline notification and the third service identifier sent by the offload service.

30. The system of claim 27, wherein the processing service is further configured to, when started, send a fifth service identification including an implementation type of the processing service and its own processing service identification to a sixth service;

the sixth service is further configured to correspondingly store the processing service identity and the fifth service identity including the implementation type in the processing service list when receiving the processing service identity and the fifth service identity including the implementation type sent by the processing service.