阅读说明：本技术 一种netty环境下的消息编码、消息解码的方法和装置 (Method and device for message encoding and message decoding in netty environment ) 是由 顾书宽 于 2018-08-13 设计创作，主要内容包括：本发明公开了一种netty环境下的消息编码、消息解码的方法和装置，涉及计算机技术领域。该netty环境下的消息编码方法的一具体实施方式包括：接收复合消息体数据，其中，复合消息体数据包括协议号和消息体数据；获取消息体数据的字节长度；将消息体数据的字节长度、协议号、和消息体数据进行拼接形成编码后消息。该针netty环境下的消息解码方法的一具体实施方式包括：接收该netty环境下的消息编码方法产生的编码后消息；根据编码后消息获取消息体数据的字节长度；根据消息体数据的字节长度获取消息体数据；根据编码后消息获取协议号；利用协议号所对应的解析器对消息体数据进行反序列化。从而大大提高游戏服务器对消息处理的灵活性和消息类型的可扩展性。(The invention discloses a method and a device for message encoding and message decoding in a netty environment, and relates to the technical field of computers. A specific embodiment of the message encoding method in the netty environment includes: receiving composite message body data, wherein the composite message body data comprises a protocol number and message body data; acquiring the byte length of message body data; and splicing the byte length, the protocol number and the message body data of the message body data to form the encoded message. A specific embodiment of the message decoding method in the netty environment includes: receiving the encoded message generated by the message encoding method in the netty environment; acquiring the byte length of message body data according to the coded message; acquiring message body data according to the byte length of the message body data; acquiring a protocol number according to the coded message; and deserializing the message body data by using a parser corresponding to the protocol number. Thereby greatly improving the flexibility of the game server in message processing and the expandability of the message types.)

1. A message coding method in a netty environment is characterized by comprising the following steps:

receiving composite message body data, wherein the composite message body data comprises a protocol number and message body data;

acquiring the byte length of the message body data;

and splicing the byte length of the message body data, the protocol number and the message body data to form an encoded message.

2. The message encoding method under the netty environment of claim 1, wherein the protocol number is a protobuf protocol number, and the message body data is a uniform interface of a google protocol message.

3. The message encoding method in netty environment as claimed in claim 1 or 2, wherein the data structure of the encoded message is byte array, which is sequentially byte length of message body data, protocol number, reserved field and message body data.

4. The message encoding method of claim 3, wherein the byte length of the message body data of the encoded message occupies 4 bytes, the protocol number occupies 2 bytes, and the reserved field occupies 4 bytes.

5. A message decoding method under a netty environment is characterized by comprising the following steps:

receiving an encoded message generated according to any of claims 1 to 4;

acquiring the byte length of message body data according to the coded message;

acquiring message body data according to the byte length of the message body data;

acquiring a protocol number according to the coded message;

and deserializing the message body data by using a parser corresponding to the protocol number.

6. The message decoding method under the netty environment of claim 5, wherein the protocol number is a protobuf protocol number, and the message body data is a uniform interface of a google protocol message.

7. The message decoding method in netty environment of claim 5, wherein the first four bytes of the encoded message are read as byte length, the fifth byte and the sixth byte of the encoded message are read as protocol number, and the remaining bytes after the tenth byte of the encoded message are read as message body data.

8. A message encoding apparatus in a netty environment, comprising:

the receiving unit is used for receiving the composite message body data, wherein the composite message body data comprises a protocol number and message body data;

a byte length obtaining unit, configured to obtain a byte length of the message body data;

and the splicing unit is used for splicing the byte length of the message body data, the protocol number and the message body data to form an encoded message.

9. A message decoding apparatus in a netty environment, comprising:

a receiving unit for receiving the encoded message generated in claim 8;

a byte length obtaining unit, configured to obtain the byte length of the message body data according to the encoded message;

a message body data acquiring unit, configured to acquire message body data according to the byte length of the message body data;

a protocol number obtaining unit, configured to obtain a protocol number according to the encoded message;

and the deserializing unit is used for deserializing the message body data by using the parser corresponding to the protocol number.

10. A message encoding electronic device in a netty environment, comprising:

one or more processors;

a storage device for storing one or more programs,

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of message encoding in a netty environment of any of claims 1-4.

11. An electronic device for decoding messages in a netty environment, comprising:

one or more processors;

a storage device for storing one or more programs,

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement a method of message decoding in a netty environment as claimed in any one of claims 5 to 7.

12. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out a method for encoding a message in a netty environment as claimed in any one of claims 1 to 4 and/or carries out a method for decoding a message in a netty environment as claimed in any one of claims 5 to 7.

Technical Field

The invention relates to the technical field of computers, in particular to a method and a device for message encoding and message decoding in a netty environment.

Background

The server programming in the game field relates to the following technical schemes, but each of the technical schemes at least has the following problems:

(1) the server side adopts a C + + programming language (an object-oriented programming language) to perform socket communication with the client side (two programs on a network realize data exchange through a bidirectional communication connection, one end of the connection is called a socket), and the data format adopts a Google protocol. However, the learning curve of the C + + programming language is steep, the development period is long, and the cost is high.

(2) The server side adopts java (an object-oriented programming language) or php (hypertext preprocessor) programming language to carry out http communication (hypertext transfer protocol communication) with the client side, and the data format generally adopts json (JS object numbered musical notation, which is a lightweight data exchange format). The short-connection type communication mode is usually adopted, the game system is suitable for weak networking games, and cannot be used for games with high requirements on real-time interaction.

(3) The server side carries out socket communication with the client side through java + netty, and the data format generally adopts json. However, json is inefficient when the transmission data is large to some extent, so the protocol format of Google protobuf should be adopted in order to obtain higher efficiency. However, the netty library of java only supports a single Google protobuf message type, and during the actual game development process, the Google protobuf message types interacted between the server and the client can be hundreds or thousands. The Google profobuf support provided by the current netty cannot meet the requirements of the game field. Therefore, there is a need to extend the support of netty for Google protobuf, from supporting a single Google protobuf message type to supporting any of multiple Google protobuf message types.

netty is the most popular NIO (synchronous non-blocking) framework that provides an asynchronous, event-driven web application framework and tools for the rapid development of high-performance, high-reliability web servers and client programs. Googleprotobuf is a tool library developed by Google for protocol coding and decoding in network communication.

Disclosure of Invention

In view of this, embodiments of the present invention provide a method and an apparatus for message encoding and message decoding in a netty environment, which can extend a netty library of java through a customized data structure to support any number of message types of google protobuf. Therefore, the flexibility of the server for processing the message and the expandability of the message type are greatly improved.

According to an aspect of an embodiment of the present invention, there is provided a message encoding method in a netty environment.

The message coding method in the netty environment comprises the following steps:

receiving composite message body data, wherein the composite message body data comprises a protocol number and message body data;

acquiring the byte length of the message body data;

and splicing the byte length of the message body data, the protocol number and the message body data to form an encoded message.

Optionally, the protocol number is a protocol number, and the message body data is a unified interface of a google protocol message.

Optionally, the data structure of the encoded message is a byte array, and the byte length, the protocol number, the reserved field, and the message body data of the message body data are sequentially included.

Optionally, in the encoded message, the byte length of the message body data occupies 4 bytes, the protocol number occupies 2 bytes, and the reserved field occupies 4 bytes.

According to an aspect of an embodiment of the present invention, there is provided a message decoding method in a netty environment.

The message decoding method in the netty environment comprises the following steps:

receiving a coded message generated by the message coding method in the netty environment in the embodiment of the invention;

acquiring the byte length of message body data according to the coded message;

acquiring message body data according to the byte length of the message body data;

acquiring a protocol number according to the coded message;

and deserializing the message body data by using a parser corresponding to the protocol number.

Optionally, the protocol number is a protocol number, and the message body data is a unified interface of a google protocol message.

Optionally, the first four bytes of the encoded message are read as the byte length, the fifth byte and the sixth byte of the encoded message are read as the protocol number, and the remaining bytes after the tenth byte of the encoded message are read as the message body data.

According to another aspect of an embodiment of the present invention, there is provided a message encoding apparatus in a netty environment.

The message encoding device in the netty environment of the embodiment of the invention comprises:

the receiving unit is used for receiving the composite message body data, wherein the composite message body data comprises a protocol number and message body data;

a byte length obtaining unit, configured to obtain a byte length of the message body data;

and the splicing unit is used for splicing the byte length of the message body data, the protocol number and the message body data to form an encoded message.

According to another aspect of an embodiment of the present invention, there is provided a message decoding apparatus in a netty environment.

The message decoding device in the netty environment of the embodiment of the invention comprises:

a receiving unit, configured to receive an encoded message generated by a message encoding apparatus in a netty environment according to an embodiment of the present invention;

a byte length obtaining unit, configured to obtain the byte length of the message body data according to the encoded message;

a message body data acquiring unit, configured to acquire message body data according to the byte length of the message body data;

a protocol number obtaining unit, configured to obtain a protocol number according to the encoded message;

and the deserializing unit is used for deserializing the message body data by using the parser corresponding to the protocol number.

According to yet another aspect of an embodiment of the present invention, there is provided a message encoding electronic device in a netty environment.

An electronic device for message encoding in a netty environment according to an embodiment of the present invention includes:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement a method of message encoding in a netty environment of embodiments of the present invention.

According to yet another aspect of an embodiment of the present invention, there is provided a message decoding electronic device in a netty environment.

An electronic device for message decoding in a netty environment according to an embodiment of the present invention includes:

one or more processors;

a storage device for storing one or more programs,

when the one or more programs are executed by the one or more processors, the one or more processors implement the message decoding method in a netty environment of the embodiments of the present invention.

According to yet another aspect of an embodiment of the present invention, a computer-readable medium is provided.

The computer-readable medium of the embodiment of the present invention has stored thereon a computer program that, when executed by a processor, implements a message encoding method in a netty environment of the embodiment of the present invention and/or a message decoding method in a netty environment of the embodiment of the present invention.

One embodiment of the above invention has the following advantages or benefits: by customizing the data structure, the byte length, the protocol number and the message body data of the message body data are spliced to form the coded message, and the netty library of the java can be expanded to support the message types of any number of Google protobufs. Thereby greatly improving the flexibility of the game server in message processing and the expandability of the message types.

Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.

Drawings

The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:

fig. 1 is a schematic diagram of the main steps of a message encoding method in a netty environment according to an embodiment of the invention;

fig. 2 is a schematic data structure diagram of an encoded message of a message encoding method in a netty environment according to an embodiment of the present invention;

fig. 3 is a schematic diagram of the main steps of a message decoding method in a netty environment according to an embodiment of the invention;

fig. 4 is a schematic diagram of a main flow of a message encoding method in a netty environment according to a referential embodiment of the present invention;

fig. 5 is a schematic diagram of a main flow of a message decoding method in a netty environment according to a referential embodiment of the present invention;

fig. 6 is a schematic diagram of main blocks of a message encoding apparatus in a netty environment according to an embodiment of the present invention;

fig. 7 is a schematic diagram of main blocks of a message decoding apparatus in a netty environment according to an embodiment of the present invention;

FIG. 8 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;

FIG. 9 is a schematic block diagram of a computer system suitable for use with a server implementing an embodiment of the invention.

Detailed Description

Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.

netty is the most popular NIO (synchronous non-blocking) framework that provides an asynchronous, event-driven web application framework and tools for the rapid development of high-performance, high-reliability web servers and client programs. It has been validated by hundreds of thousands of commercial/commercial projects, such as the RPC (remote procedure call) framework Avro (a data-serialized system) of Hadoop (a distributed system infrastructure), rockmq (publish-subscribe based queue model message middleware), and the mainstream distributed communication framework Dubbox (distributed service architecture), among others.

Google protobuf is a tool library developed by Google for protocol coding and decoding in network communication. It is similar to XML (extensible markup language) and Json data, saving data in some form. Googleprotobuf differs from XML and Json in that it is a binary data format and has higher transmission, packing and unpacking efficiency. Google protobuf is integrated in netty.

As shown in fig. 1, a message encoding method in a netty environment according to an embodiment of the present invention mainly includes the following steps:

step S101: composite message body data is received.

The data structure of the composite message body data can be customized, i.e. the composite message body data can include a protocol number and message body data. The protocol number can be a protobuf protocol number and is used for distinguishing different message types; the message body data is data conforming to the analysis standard of Google protocol, and may be a unified interface of Google protocol message.

Step S102: the byte length of the message body data is obtained.

Step S103: and splicing the byte length, the protocol number and the message body data of the message body data to form the encoded message.

According to the data structure of the composite message body data, the composition sequence of the encoded message can be determined for the data format of further serialization of the encoded message. Specifically, the byte length of the message body data may be set to occupy 4 bytes, the protocol number may occupy 2 bytes, and the reserved field may occupy 4 bytes. The reserved field is the extensible field reserved in the composite message body data, and the extensibility of the message type can be improved through the reserved field.

As shown in fig. 2, the encoded message may include: the byte length of the message body data; a protocol number in the composite message body data; reserved fields in the composite message body data; and message body data. The data format is determined according to the actual requirements of server programming, and the data format of the coded message can be customized differently according to the requirements of different server programming.

The message encoding method under the netty environment according to the embodiment of the invention can be seen as follows: by customizing the data structure, the byte length, the protocol number and the message body data of the message body data are spliced to form the coded message, and the netty library of the java can be expanded to support the message types of any number of Google protobufs. Thereby greatly improving the flexibility of the game server in message processing and the expandability of the message types.

As shown in fig. 3, a message decoding method in a netty environment according to an embodiment of the present invention mainly includes the following steps:

step S301: an encoded message is received.

The encoded message is generated based on the message encoding method in the netty environment of the embodiment of the invention.

Step S302: and acquiring the byte length of the message body data according to the encoded message.

The message body data is data conforming to the analysis standard of Google protocol, and may be a unified interface of Google protocol message.

Step S303: and acquiring the message body data according to the byte length of the message body data.

Step S304: and acquiring the protocol number according to the encoded message.

The protocol number may be a protobuf protocol number used to distinguish different message types.

Step S305: and deserializing the message body data by using a parser corresponding to the protocol number.

The encoded message can be read based on the encoding rule of the encoded message, in the embodiment of the present invention, the first four bytes of the encoded message are read as the byte length, the fifth byte and the sixth byte of the encoded message are read as the protocol number, and the remaining bytes after the tenth byte of the encoded message are read as the message body data.

The message decoding method under the netty environment according to the embodiment of the invention can be seen as follows: by customizing the data structure, the byte length, the protocol number and the message body data of the message body data are spliced to form the coded message, and the netty library of the java can be expanded to support the message types of any number of Google protobufs. Thereby greatly improving the flexibility of the game server in message processing and the expandability of the message types.

Fig. 4 is a schematic diagram of a main flow of a message encoding method in a netty environment according to a referential embodiment of the present invention. As shown in fig. 4, a main flow of a message encoding method in a netty environment includes: initializing relevant parameters; acquiring the actual length X (namely the byte length of the message body data) in the custom data structure; then obtaining the message number Y (namely the protocol number in the composite message body data) of the user-defined data structure; next, setting a reserved extension field Z (namely a reserved field in the composite message body data) of the custom data structure; and setting the message content M of the custom data structure (namely the message body data in the composite message body data); and finally, splicing the actual length X, the message number Y, the reserved extension field Z and the message content M to obtain complete data of a custom data structure, namely the coded message.

For example, it can be assumed that the total length of the complete serialized data is greater than 10 bytes, the first 4 bytes are used for storing the actual length in the custom data structure, the next 2 bytes are used for storing the message number, and the next 4 bytes are used as the reserved extension field and set to 0, and then the message contents of the custom data structure are concatenated on this basis, so as to obtain a complete data, that is, the total length of the serialized data is 10 bytes plus the actual number of bytes of the message contents. It should be understood that the exemplary byte lengths of the various portions in the above example are for illustration purposes only. The number of bytes can be customized according to the requirements of different server programming.

Fig. 5 is a schematic diagram of a main flow of a message decoding method in a netty environment according to a referential embodiment of the present invention. As shown in fig. 5, a main flow of a message decoding method in a netty environment includes: initializing relevant parameters; reading the actual length X (namely the byte length of the message body data) in the custom data structure; then reading the message number Y (namely the protocol number in the composite message body data) of the custom data structure; skipping a reserved extension field Z (namely a reserved field in the composite message body data) of the custom data structure, and reading the message content M (namely the message body data in the composite message body data) of the custom data structure according to the actual length X in the custom data structure; and acquiring a corresponding Google protobuf parser according to the message number Y of the custom data structure so as to perform deserialization on the message content M of the custom data structure.

For example, it can be assumed that the total length of the complete serialized data is greater than 10 bytes, the actual length in the custom data structure is read from the first 4 bytes, the message number of the custom data structure is read from the next 2 bytes, 4 reserved bytes of the custom data structure are skipped, and the message content of the custom data structure is read according to the actual length. There may also be a need to deal with the problem of half-wrapping and sticky wrapping. And then acquiring different Google protobuf resolvers according to different message numbers, and performing deserialization on the message content of the custom data structure to obtain actually-desired data.

Fig. 6 is a schematic diagram of main blocks of a message encoding apparatus in a netty environment according to an embodiment of the present invention.

As shown in fig. 6, a message encoding apparatus 600 in a netty environment according to an embodiment of the present invention includes: a receiving unit 601, a byte length obtaining unit 602 and a splicing unit 603.

Wherein the content of the first and second substances,

a receiving unit 601, configured to receive composite message body data, where the composite message body data includes a protocol number and message body data;

a byte length obtaining unit 602, configured to obtain a byte length of the message body data;

a splicing unit 603, configured to splice the byte length of the message body data, the protocol number, and the message body data to form an encoded message.

Fig. 7 is a schematic diagram of main blocks of a message decoding apparatus in a netty environment according to an embodiment of the present invention.

As shown in fig. 7, a message decoding apparatus 700 in a netty environment according to an embodiment of the present invention includes: a receiving unit 701, a byte length acquiring unit 702, a message body data acquiring unit 703, a protocol number acquiring unit 704, and an deserializing unit 705.

Wherein the content of the first and second substances,

a receiving unit 701, configured to receive an encoded message generated by a message encoding apparatus in a netty environment according to an embodiment of the present invention;

a byte length obtaining unit 702, configured to obtain a byte length of message body data according to the encoded message;

a message body data obtaining unit 703, configured to obtain message body data according to the byte length of the message body data;

a protocol number obtaining unit 704, configured to obtain a protocol number according to the encoded message;

the deserializing unit 705 is configured to deserialize the message body data by using the parser corresponding to the protocol number.

Fig. 8 shows an exemplary system architecture 800 of a message encoding method in a netty environment, a message decoding method in a netty environment, a message encoding apparatus in a netty environment, or a message decoding apparatus in a netty environment, to which embodiments of the present invention may be applied.

As shown in fig. 8, the system architecture 800 may include terminal devices 801, 802, 803, a network 804, and a server 805. The network 804 serves to provide a medium for communication links between the terminal devices 801, 802, 803 and the server 805. Network 804 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

A user may use the terminal devices 801, 802, 803 to interact with a server 805 over a network 804 to receive or send messages or the like. The terminal devices 801, 802, 803 may have installed thereon various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, and the like.

The terminal devices 801, 802, 803 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.

The server 805 may be a server that provides various services, such as a background management server that supports shopping websites browsed by users using the terminal devices 801, 802, 803. The background management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (e.g., target push information and product information) to the terminal device.

It should be noted that the message encoding method and the message decoding method under the netty environment provided by the embodiments of the present invention are generally executed by the server 805, and accordingly, the message encoding apparatus and the message decoding apparatus under the netty environment provided by the embodiments of the present invention are generally disposed in the server 805.

It should be understood that the number of terminal devices, networks, and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to FIG. 9, a block diagram of a computer system 900 suitable for use as a server in implementing embodiments of the present invention is shown. The server shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.

As shown in fig. 9, the computer system 900 includes a Central Processing Unit (CPU)901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage section 908 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the system 900 are also stored. The CPU 901, ROM 902, and RAM 903 are connected to each other via a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.

The following components are connected to the I/O interface 905: an input portion 906 including a keyboard, a mouse, and the like; an output section 907 including components such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 908 including a hard disk and the like; and a communication section 909 including a network interface card such as a LAN card, a modem, or the like. The communication section 909 performs communication processing via a network such as the internet. The drive 910 is also connected to the I/O interface 905 as necessary. A removable medium 911 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 910 as necessary, so that a computer program read out therefrom is mounted into the storage section 908 as necessary.

In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 909, and/or installed from the removable medium 911. The above-described functions defined in the system of the present invention are executed when the computer program is executed by a Central Processing Unit (CPU) 901.

It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor comprising: a determining module for determining N input conditions, expected results and logic gates therebetween; the processing module is used for carrying out permutation and combination on the N input conditions to generate M groups of combination conditions; determining an output result for each set of combining conditions based on the logic gates and the expected results; m, N is a positive integer; and the generating module is used for generating a test case by taking each group of combination conditions as a test condition and taking the output result of each group of combination conditions as the test result of the corresponding test condition. The names of these modules do not form a limitation on the module itself in some cases, for example, the determination module may also be described as a "module for generating M groups of combination conditions by arranging and combining N input conditions".

As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise: determining N input conditions, an expected result and a logic gate therebetween; arranging and combining the N input conditions to generate M groups of combination conditions; determining an output result for each set of combining conditions based on the logic gates and the expected results; m, N is a positive integer; and generating a test case by taking each group of combination conditions as test conditions and taking the output result of each group of combination conditions as the test result of the corresponding test conditions.

According to the technical scheme of the embodiment of the invention, the method has the following advantages or beneficial effects: the netty library of java can be extended through a custom data structure to support any number of message types of Google protobuf. Thereby greatly improving the flexibility of the game server in message processing and the expandability of the message types.

The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.