TW201117867A - Non-real-time internet game protocol - Google Patents

Abstract

The non-real-time internet game protocol is used to solve the problems caused by huge resource requirement needed by non-real-time internet games and is used to implement single hardware platform for multiple non-real time games. The protocol consists three types of message between server and client: object message, control message, event message. Object messages are managed by server and generated or vanished by client's events. Event messages are came from clients. Control messages are communication messages between server and client other then object messages and event messages.

Description

201117867 Μ. 5. If there is a chemical formula, please disclose the chemical formula that best describes the characteristics of the invention: ^, invention description: [Technical field of invention] The agreement 'in particular refers to the agreement of non-immediate online games . There are many ways to use the client. But =Flash Player. There are a lot of resources needed. For ^"=如大*翁' Boao class only need some 2D ^ _ paste picture and put

Therefore, for non-immediacy, only 2D two is harder and thinner, it is more game-friendly. * It is also a big profit for the mussels, and when it is spent [invention] It is an agreement to provide a kind of non-immediate online game, which aims to solve the ugly resources of the game platform and can play more. Qingke _ Lu Xian. The production of the lake age 201117867 single, easy to use, full-featured, fast response, to the client $ hardware, you can use cheap _ embedded system without blame π

In order to realize this creation, the message transmitted by the server and the client is divided into two objects: 〇bjects' control (contr〇is), event (A server manages and generates and subtracts according to client events). The Xuan «I event is from the client, and the control message is a pipeline that facilitates communication between the two parties besides the object message _, and the event 。μ. The concept of "object-oriented" is downloaded by the ship to each client. Hardware object (output signal to the hardware). It can be counted without the miner's timing according to the client's event. Ζ Ζ Ζ Ζ Ζ Ζ 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排 安排The server requires the server to re-server when it cannot be deleted. The client will reply to the processing. The message center (the control message of the source is full) must be independent of the server [implementation] line. Each object ^ example, H The realization of the abstract object model of the product and the method or step of its implementation are born!ΐ: The classware Jf is the data 'providing - the player's capital, etc.. Touching = has parameters related to itself, such as the game passed Channels in the protocol object is preclude the use of object-oriented approach, the data name, object type entry address thereof may be knife group thousand objects, application object, 201,117,867

The only thing that is created is the three kinds of messages: control, object, and event. Introduce these three kinds of messages. The following detailed control messages contain some system initialization, such as ^μ π _ - information query performance information, etc.

SyymKChenteSever): Department, the beginning of the system. The server is on the client = the tool is initialized, and the picture, sound, character, clock, etc. required for initialization are loaded. • The client initiates an error. When the client/end starts to make an error, the client feeds back a message to the feeder, indicating that the initialization error occurred. The server received the error message and will re-initialize the client. Sysjnit-ok (Client=>Sever)·· The client starts normally. When the client is initialized correctly, the client feeds back a message to the server indicating that the initialization is normal.

Sys-enq_sys (Client<=Sever): Query client system information. Feeder Check the client in real time to see if there is any system information. If there is system information, the feeder will take corresponding measures.

Sys_info(Client=>Sever): Client Display/Character Set/Sound/Clock/φ Input/Customer Hardware Performance Information. Display with resolution, color (16 bit/24bit), character set (big5/gb/en/utf), sound capability (WAV/MIDI), clock (RTC/SYS), input (keyboard/mouse), client Hardware (customer special hardware device).

Sys_ping(Client<=Sever) : ping. The server pings the client and pings ’, then the server can communicate with the client to transmit information; otherwise, it cannot communicate.

Sys_ping_ack(Client=>Sever) : ping ack. The server pings the client and pings it. The client sends a response message to the server to inform the server that it has pinged.

Sys-logout_req(Client=>Sever): logout request. The client 201117867 issues a logout request to the server. :logout ack. Server to the guest: set the year / month / day / hour / minute / second. : Read year/month/day/hour/minute/second. Servant receives client event message

Sys_logout_ack (Client<=Sever) The client replies with a logout request. Sys_time_set(Client<=Server) Sy s_t i me_get(C1i ent=>Server) Sys_svr_ok(Client<=Server)' The reply is received correctly. The server receives a client event message

Sys_svr_err(Client<=Server): An error was received after the reply.

Sys-cln-ok (Client=>Server): The client receives the server object and the reply is received correctly. heart

Sys_cln-reload(Client=>Server): The client receives the correct response from the server object, but the object does not exist on the client and must be downloaded by the server.

Sys-c 1 n_ful 1 (C1 ient=>Server) · When the client receives the server object message, the reply is received correctly, but the system resources are full and the object cannot be loaded. The server must delete some objects. ,

Sys-cln_err(Client=>Server): The client receives an error after receiving the server object message. The object mainly has four objects: picture/sound/text/hardware information, the picture can be / static JPG or dynamic GIF, the picture can set the starting point / path / zoom, and trigger mode / condition. The triggering method can be repeated, random, an event appears, and so on. In addition to sending text and hardware information objects to the client, the server can also request input text and hardware information from the client. The following is a detailed description of the object message: 〇bj_img(Client<=Sever): Obj_ID, Layer(n),

Type(Jpg/G if/M j peg/MP4/Theora/D i rac), Size(w, h), 〇rigin(w, h), Scale(x/y), Path((xO, yO), (xl, yl),...), Time(sys_time/obj_time,from_time, to_time,step-time), Trig(trig_repeat/trig_random/trig_by_event/trig_by_〇b 201117867 j/trig-area),Len,(image Data. ·.), CRC. The server sends the customer a picture object. When an event on the client is to be stupid, the server will generate a picture object to be sent to the client. The image object contains the ID of the image object, drawing layer, class & (Jpg/Gif/Mjpeg/MP4/The〇ra/Dirac), size 'picture can set the starting point / path / zoom / time, and trigger mode / condition. The trigger can be repeated, or random, or an event/object appears, or an area. Is the length, image data and CRC.

Obj_img_trig(Client<=Sever): Obj_ID, Layer(n),

Type(Jpg/G i f/M j peg/MP4/Theora/D i rac), ’

SizeCw, h), 0rigin(w, h), Scale(x/y), Path((x〇, y〇), (xi, yl) ,···),

Time (sys_time/obj_time, from_time, to_time, step_time), Trig(on/off/trig_repeat/trig_random/trig_by_event/tri g_by_obj/ trig-area). Similar to the bj_img function, but used for graphics objects that have been previously downloaded, so there is no need to download graphical information. 〇bj_snd(Client<=Sever): Obj_ID, Type(Wav/MP3/0GG/MIDI),

Time(sys_time/obj—time, from—time), Trig(on/off/trig—re peat/ _ trig_random/trig_by_event/trig_by_obj/trig_area), Len, (audiodata·..), CRC. The sound object message sent by the server to the client. When a certain event is used by an event on the client, the server will generate a sound object and send it to the client. The sound object message contains the ID of the sound object, type (Wav/MIDI/MP3/0GG), system time/start time when the sound is played, and trigger mode/condition. Triggers can be recurring, or random, or an event/object appears, or an area. Followed by length, audio data and CRC〇

〇bj_snd_trig(Client<=Sever): Obj_ID, Type(Wav/MIDI MP3/0GG), Time(sys-time/obj-time, from-time), Trig(on/of f/ 6 『5: 201117867 tr i G_repeat / tr i g_random/tr i g_by_event/tr i g_by_〇bj / tr ig one area). Similar to the Obj_snd function, but used for sound objects that have been previously downloaded, so there is no need to download sound information.

Ob j_text_out(Cl ient<=Sever): 〇b j_JD,

Type (on/of f / i nverse/ f 1 ash),

Time(sys_time/obj_time, from_time), Size(w, h), 0rigin(w, h),

Range(from,to), Len, (text data... ), CRC. The text output object, output from the server to the client' is mainly the form, time, size, starting point, display paragraph, data length of the output text, and finally the text data and CRC.

Obj_text_out_trig(Client<=Sever) :0bj_ID, Type(on/off/i nverse/flash), Time(sys_time/obj_time, from_time), Size(w, h), 0rigin(w, h),Range(from,to ). Similar to the 〇bj-text_out function, but used for text objects that have been previously downloaded, so there is no need to download text information.

Obj_text_in(Client=>Sever): 〇bj_JD, Length. The text input object is required to be input from the client to the server, including the 11} and length of the input text.

Obj_HW_out(Cl ient<=Sever) : 0bj ID HW_ID, LEN, (data...), — ’ CRC. A hardware object that outputs data from the server to the client. 〇bj_HW_in(Client=>Sever): 〇bj_ID, HW_ID, LEN, (data...), CRC ° hardware object, requires data input from the client to the feeder. 〇bj_close(Client<=Sever): ObjJD. As long as the object ID is given, the server can close the client's object. 2 gas is, shape / keyboard / hardware event, when the mouse and keyboard / hardware have output server must be output by the event message. The following is a detailed description of the event message: 201117867 Event Message Output 'includes ID data located above several objects and objects.

Evn—mouse_click(Client=>Sever): no, (〇bj_ID,...). When the client mouse clicks on an object to be sent to the server, the mouse can click on the event message and output, including the number of click objects and the ID data of the object.

Evn—KB (Client=>Sever): (data), CRC. When the client keyboard has data that must be sent to the server, the message can be output by a keyboard event.

Evn_text__in(Cl ient=>Sever) : 0b j_ID , LEN , (text data·. ·) ' CRC. The text input event message is output from the client to the server, including the length of the input text, data, and the like. °

Evn—HW (Client=>Sever): HWJD, (hw data), CRC. When the client hardware is mixed, it must be sent to the service_|, which can be output by the hardware event message.

Evn_HW_in(Client=>Sever): ObLID, HW_ID, LEN, (hwdata···), CRC: Hardware input event message 'outputs data from the client to the server. When the ship is connected to the yarn at the client, it must first understand the customer = screen resolution / character information, and select the corresponding pin. = Some hardware, we will specify that the client must support, and some are options. The client hardware is the hardware of the client, which may be the electronic chessboard/golf analyzer, etc., the hardware ID of 2, there is a wealth, as long as the server side sets a clear and ^ agreement, the hardware manufacturer can Design a compatible product. ^, the overall architecture diagram such as 1 Π 'feeder and client through the Internet message, control messages, event messages. The client accepts the keyboard 'J output as input' to generate graphics, sound, and hardware input as outputs. Shichuang, the flow chart is shown in Figure 2 'The connection between all servers and the client is started by the customer two = server, the server will first send out the control message of the starting client, and the user will start the initial action after receiving it. Then the server will ask the client for each of the 'segment size/color capabilities, supported graphics/sound grid models, etc.'. With this information, the server can generate different objects for the h client', for example only support The 256-color client, the feeding device will cry ^ (4) ^ 1 ί / 24 ^ ί / 32 Μ ί graphics first converted into 256 colors. After that, the sinking or pure phase object is first loaded into the client, and then the 201117867 enters the main loop. = The two-way diagram is shown in Figure 3. The client continuously monitors and inputs the hardware. If any, the event m is sent from the user. If the keyboard/month is 0K, then the next step-step, no service, and the feeder ACK is Different objects will be generated depending on the event, for example, ^ is I-shaped. Produce good objects' server to the customer's venue, the map received and then reply to the positive ACK, otherwise the feeding service ^ f message 'client or object is not in the system memory ^ / new ^ ^ fn) ί; It is necessary to generate different graphics accordingly: = Two-way ί households must give the new 1 〇 码 code to ^=. Connect ======/== At the beginning of the weight: bundle connection, otherwise it will process the control message from the request and execute the control message, and then return to the main loop after processing. Start repeating Figure 4 is when the object downloads the client reply is not 〇 κ processing resources to the downloaded object, if the resource has = two objects (Garbage (10) milk · "long, the end of the brother recalls the body, the client will issue Reload ί ί 有 魏 Wei Lai's _ message. If you fill all the client _ source, the feed will be S to close the temporarily unwanted items, and although 201117867 [schematic description] Figure 1 Architecture diagram Figure 2 This creation flow chart Figure 3 The main loop diagram of the creation Figure 4 Full and reload processing flow chart when downloading the object [Main component symbol description]

VII. The scope of patents for the month of the month: De said that the instant online game agreement is used in the service of the service shop 11 and the client, which is characterized by including: object, control, and event.

The server manages and generates and reduces the I ift event according to the client event from the client. The control message is the pipeline for communication between the two parties except the object G: event message.什 也— (4) __峨, the fine lies in;

Sys_init(Client<=Sever): system start; gys_init_err(client=>Sever): client start error; ice s-lnit-ok (Client=>Sever): client starts When ii^sys(cl ient<=Sever): Query the client information, the server 1 2 queries the client to check whether there is any system information, if there is any information, the corresponding measures will be taken; for example, “info(Client=&gt) ;Sever): client display / character set / sound / clock

Claims (1)

201117867 [Simple diagram of the diagram] Figure 1 Architecture diagram of the creation system Figure 2 Flow chart of the creation of the diagram Figure 3 Flow chart of the main loop of the creation Figure 4 Flow chart of the full and reload processing of the object download [Description of the main components] VII. The scope of the patent for the month of the month: De said that the instant online game agreement 'used in the service shop 11 and the customer's heart, is characterized by: ································· According to the client event, the I ift event is generated from the client, and the control message is the pipeline for communication between the two parties except the object G: event message.什 也—(d) __峨, the fine is,; Sys-init(Client<=Sever): system start; gys-init_err(client=>Sever): client start error; ice s-lnit-ok (Client =>Sever): The client starts and stops. ii^sys(cl ient<=Sever): Query the client information, servo 1 2 query the client, check if there is any system information, if there is any information will be taken Corresponding measures; such as "info (Client => Sever): client display / character set / sound / clock 201117867 input / customer hardware performance information; Sys_ping (Client < = Sever): ping, server ping client Sys_ping_ack(Client=>Sever): ping ack, the client sends a response message to the word server; ° Sys_logout-req(Client=>Sever): logout request, the client sends a logout request to the server; % Sys —logout_ack(Client<=Sever): logout ack, the server replies to the client to receive the logout request; ° Sys_time_set(Client<=Server): set year/month/曰/hour/minute/second; Sys_time_get(Client=>Server): read year/month/曰/hour/minute/second; Sys-svr_ok(Client< =Server): The server received the client's message from the second reply and received it correctly; °~ Sys_svr-err(Client<=Server): The server received the client event and received a reply after receiving the error; ° ~ Sys_c 1 n—ok(C 1 ient=>Server): The client receives the correct response after receiving the server object; °~ Sys_cln-reload(Client=>Server): The client receives the server After the object message is received, the reply is correct, but the object does not exist in the client, and the device must be re-downloaded; Sys_cln-ful 1 (Cl ient=>Server): After receiving the server object message, the client receives the reply correctly. However, the system resources are full and the objects cannot be loaded. Servo crying must delete some objects; SyS_cln-err (Client=>Server): The client receives an error after receiving the server. 3. The non-instant online game protocol of claim 1, wherein the object information is: , j_img(Cl ient<=Sever): 〇bj_ID, Layer, Type, Size, Origin, Scale, Path , Time' Trig' LEN, (img data..*), CRC: picture object from, contains the ID of the picture object, drawing layer, type, size, picture can be said ^ 201117867 length, the starting point of the image capital / Path/zoom/time, and triggering method, CRC check code; ' 〇bj_img_trig(Client<=Sever)· 〇hi τη τ Origin,Scale,Path,Time,Tri^:^LfeUyPe,Size, ID of picture object , draw layer, _ big two trigger object message ' contains start / path / zoom / time, and trigger mode, the slice can be set to appear Obj_snd (Client <= Sever): 〇bj - Π), Type Timp τ. A. dl ), ^: sound object message, including = Trig:^ 曰 Trigger object wire, including the ID system time/start time of the sound object, trigger mode/condition; 狐bj_text_out (Client<=Sever): 〇bijD, Type, Time, Size, Origin , Range, LEN, (text data... ) , CRC: , 4 5 server to input ij to the client, mainly the form of some output text, time, small, starting point, no paragraph, data length, and finally Is text data and CRC; Ubj_text_out_trig(Client<=Sever): 〇bLID, Type(on/off/in verse/ lash), Time(sys_time/obj_time,from_time), Size(w,h), ^=ιη ^, ίι),Range(from,to): The text output trigger object, from the servo β rain to the client, mainly the form, time, size, starting point, and display paragraph of the output text; Obj^text—in(Client =>Sever): 〇bj_ID, LEN: text input object, required to input from the client to the server, including the ID of the input text, length; °bj JW_〇ut (Client<=Sever): 〇bj_ID, HW_ID, LEN, (data...), CRC: Hardware object 'outputs data from the server to the client, including hardware ID, long , data and CRC; 〇bj_HW_in( Client=>Sever): 〇bj__ID, HW_ID, LEN, (data...), CRC: hardware object, requiring input of data from the client to the server including hardware ID, 『 51 12 201117867 Length, data and CRC; Obj_close(Client<=Sever): Obj-ID: as long as the object ID is given, the word of the client can be closed; 4. The non-instant network according to claim 1. The game agreement 'is characterized by: the event message is: ' 々 Evn_mouse one over (Client => Sever): no, (0bj - ID, ...): The mouse is output through the event message, including several objects ID information of the top and object: Evn_mouse_click(Client=>Sever): no, (0bj_ID,...): The output of the slippery click event message, including clicking on the ID data of several objects and objects ''; Evn_KB(Client=> Sever): (data), CRC: keyboard event message output, including keyboard data and CRC; Evn_text_in(Cl ient=>Sever): Ob j_ID , LEN , (text data. ..), CRC: text message client output For the server, including the length of the input text, data, CRC; Evn_HW (Client=>Sever): HW_ID, LEN, (hw data), CRC: Hardware event message output, including hardware ID, length, data, CRC; Evn_HW_in( Client=>Sever): ObjID , HW_ID , LEN , (hw data· · · ), CRC. Hardware input event messages, including hardware ID, length, data, CRC. 13