CN104852955B - A kind of data processing method and system - Google Patents

Abstract

This application discloses a kind of data processing method and systems, to improve data transmission efficiency.The method includes sending direction recipients to send request message；And receive the response message that the recipient returns according to the request message；Wherein, the request message and response message are all based on the message of custom protocol, and the protocol header of the custom protocol is carried in the request message and response message, include message length field and action type field in the protocol header.In this way, each message transmitted between sender and recipient is the message of custom protocol, just there is no redundant data in message including the agreement, so as to effectively improve data transmission efficiency, the custom protocol is used for point-to-point data interaction scene, does not include redundant data in the message based on custom protocol.

Description

A kind of data processing method and system

Technical field

This application involves field of computer technology more particularly to a kind of data processing methods and system.

Background technology

With the continuous development of Internet technology, more and more users get used to obtaining various network moneys by network Source, such as online viewing entertainment video, acquisition education material, multi-user chat etc..

Realize that the interaction and information sharing of multi-user, existing technology are exactly to be realized using general standard agreement. And the big problem of protocol comparison generally used now is to keep redundant data more, whatsoever the message of type, format only have fixed It is several.Such as general hypertext transfer protocol (Hyper Text Transfer Protocol, HTTP), it only asks and rings Two kinds of protocol definitions are answered, have general head, request header/head response, entity head, data volume in this two classes message.In fact, different The message of type needs the information carried generally different.But because http is general agreement, message will follow its intrinsic lattice Formula can carry unwanted information, cause redundant data more, and package needs more calculating to consume, so can influence Transmit the efficiency of effective information.

Invention content

A kind of data processing method of the embodiment of the present application offer and system, to improve the flexibility to data processing, from And improve data transmission efficiency.

A kind of data processing method provided by the embodiments of the present application, including：

Sending direction recipient sends request message；And

Receive the response message that the recipient returns according to the request message；

Wherein, the request message and response message are all based on the message of custom protocol, the request message and sound The protocol header for carrying the custom protocol in message is answered, includes message length field and action type in the protocol header Field, the custom protocol are used for point-to-point data interaction scene, do not include redundant digit in the message based on custom protocol According to.

A kind of data processing system provided by the embodiments of the present application, including：

Sender, for sending request message；

Recipient, for receiving request message and according to the request message returning response message；

Wherein, the request message and response message are all based on the message of custom protocol, the request message and sound The protocol header for carrying the custom protocol in message is answered, includes message length field and action type in the protocol header Field, the custom protocol are used for point-to-point data interaction scene, do not include redundant digit in the message based on custom protocol According to.

A kind of data processing method and system provided by the embodiments of the present application, this method are sent by sending direction recipient Request message；And receive the response message that the recipient returns according to the request message；Wherein, the request message and sound It answers message to be all based on the message of custom protocol, the custom protocol is carried in the request message and response message Protocol header, includes message length field and action type field in the protocol header, in the message based on custom protocol not Including redundant data.In this way, each message (request message or response message) transmitted between sender and recipient is Message based on custom protocol does not include redundant data in the message of the custom protocol, is passed so as to effectively improve data Defeated efficiency.

Description of the drawings

Attached drawing described herein is used for providing further understanding of the present application, constitutes part of this application, this Shen Illustrative embodiments and their description please do not constitute the improper restriction to the application for explaining the application.In the accompanying drawings：

Fig. 1 is a kind of data processing method flow diagram provided by the embodiments of the present application；

Fig. 2 is a kind of data interactive method flow diagram provided by the embodiments of the present application；

Fig. 3 is another data interactive method flow diagram provided by the embodiments of the present application；

Fig. 4 is another data interactive method flow diagram provided by the embodiments of the present application；

Fig. 5 is a kind of data processing system schematic diagram provided by the embodiments of the present application；

Fig. 6 is a kind of data processing system schematic diagram provided by the embodiments of the present application.

Specific implementation mode

To keep the purpose, technical scheme and advantage of the application clearer, below with reference to the application specific embodiment and Technical scheme is clearly and completely described in corresponding attached drawing.Obviously, described embodiment is only the application one Section Example, instead of all the embodiments.Based on the embodiment in the application, those of ordinary skill in the art are not doing Go out the every other embodiment obtained under the premise of creative work, shall fall in the protection scope of this application.

Referring to Fig. 1, it is a kind of data processing method provided by the embodiments of the present application, includes the following steps：

S101：Sending direction recipient sends request message.

In applying for embodiment, the sender and recipient can be：Client, scheduling proxy server, scheduling Any two in server, center machine and service balanced device etc..For example, sender is client, recipient is scheduling broker Server.

In the embodiment of the present application, the request message that described sender is sent is different according to the difference of business scenario.Than Such as, in point-to-point data interaction scene, when sender needs to download resource, be often related to registering with recipient, The processes such as login, seed download, resource downloading, then the request message can be registration class request message, login class request Message, download class request message etc.；Disappear correspondingly, the response message that recipient returns to sender can be registration class response Breath, login class response message, download class response message etc..

In practical application scene, either request message or response message are sent out during transmitting these message The side of sending or recipient are required to transmit message according to the protocol header and/or protocol entity carried in these message.

In view of in practical application scene, may not be needed to assist in the agreement of certain form of request message or response message It discusses body and only needs protocol header.Therefore, in the embodiment of the present application, disappear for the request message and response that do not need protocol entity It ceases, the protocol header of custom protocol is only carried in the request message and response message, wherein the protocol header includes message-length Field (Length fields) and action type field (OpType fields).

In view of in practical application scene, due to different types of request message or the corresponding protocol header of response message or Need the data transformation carried identical in protocol entity, therefore, some fields often existed in protocol header or protocol entity are Data need not be carried, i.e., the field is redundant field relative to current data to be sent.But in the prior art, needle To different types of request message or response message, using the agreement of set form (unified format), i.e., all types of requests Message or the protocol header of response message are identical with the format of protocol entity, this allows for sender when transmitting message, may Redundant format is also transmitted to recipient, to reduce data transmission efficiency.

Therefore, the embodiment of the present application request message and response message are the message based on custom protocol, based on self-defined Redundant data is not included in the message of agreement；Wherein, the message not comprising redundant data is：The message does not include redundancy protocol lattice Formula, alternatively, not including redundant data in protocol format.Such as, the word unrelated with current message is not included in protocol header or protocol entity Redundant content is not included in section (referred to as, redundant field) or field, it is clear that compare the prior art, based on set form Message (i.e. the protocol format of different messages is identical), can effectively improve data transmission efficiency.

Wherein, which is used to illustrate the length of the request message or response message.

For example, it is assumed that the protocol header of the custom protocol of request message or response message is P2P protocol headers (abbreviation P2P_ HEAD), then the format of P2P_HEAD is as shown in table 1.

P2P_HEAD:

Field	Length	OpType
			Type	Integer (Int)	Int
Byte length	2/4	2

Table 1

As shown in Table 1, P2P_HEAD includes Length fields and OpType fields, and the type of the two fields is whole The byte length of type, Length fields can be 2 bytes or 4 bytes, and under normal circumstances, the byte length of Length fields is 2 Byte, but for the longer message of length, Length fields can be 4 bytes.

Certainly, the description content of each field is may also include in the protocol header, e.g., the description content of Length fields is " length of entire agreement, including protocol header length ".

S102：Sender receives the response message that the recipient returns according to the request message.

In the embodiment of the present application, after recipient receives the request message of sender, it can return and be based on to sender The response message of the request message, then sender can receive the response message that the recipient returns according to request message.

Wherein, in order to improve data transmission efficiency, which is again based on the message of custom protocol, the response The protocol header of custom protocol is carried in message, equally includes Length fields and OpType fields in the protocol header.Wherein, Protocol header (such as Length fields and OpType fields) in response message is in above-mentioned steps S101 it is stated that here no longer It repeats.

Above-mentioned method shown in FIG. 1 sends request message by sending direction recipient；And receive the recipient according to The response message that the request message returns；Wherein, the request message and response message are all based on disappearing for custom protocol It ceases, the protocol header of the custom protocol is carried in the request message and response message, includes in the protocol header Length fields and OpType fields.As it can be seen that protocol header is only carried in request message and response message in the embodiment of the present application, And only including Length fields and OpType fields in the protocol header.And in the prior art, in request message and response message Protocol header in include at least general head, request header/head response, entity head etc., and regardless of whether need protocol entity, request message With protocol entity (i.e. data volume) is carried in response message.Obviously, it is transmitted between the embodiment of the present application sender and recipient Request message or response message protocol header in there is no a general head, request header/head response, these first-class redundant datas of entity, Correspondingly, redundant data just not described in request message or response message, so as to effectively improve data transmission efficiency.

In view of in practical application scene, for example, in point-to-point data interaction scene, it is understood that there may be what sender sent asks Ask the request data that data and recipient receive inconsistent, alternatively, response data and sender that recipient returns receive The inconsistent situation of response data, in this way, the reliability that may result in the data that sender or recipient receive is lower Problem.

Therefore, in the embodiment of the present application, the protocol header in the request message or response message may also include check word Section (e.g., Mark fields).

The check field is used to indicate after sender (or recipient) receives message, according to the check field to this Message is verified, and when check results are correct, determines that message is correct, follow-up data processing procedure is can perform, otherwise, it determines disappearing Mistake is ceased, stopping execution follow-up data processing procedure further can again be sent with request recipient (or sender) and be disappeared Breath.

Similar with above-mentioned Length fields and OpType fields, Mark fields also can define field name, type and byte Length etc. can also define the description content etc. of field.

Further, in the embodiment of the present application, the protocol header in the request message or response message may also include guarantor Section of writeeing down characters (Reserved fields) is used for extending.

For example, P2P_HEAD protocol headers shown in table 2 had both included Length fields and OpType fields, also include Mark words Section and Reserved fields.

P2P_HEAD：

Field	Length	Mark	OpType	Reserved
					Type	Int	Int	Int	Int
Byte length	2	4	4	4

Table 2

As shown in Table 2, it is 2 bytes, the length of remaining field that the type of each field, which is the length of integer Int, Length field, Degree is 4 bytes.

In view of in practical application scene, the request message or response message of some types not only need to carry protocol header, It also needs to carry protocol entity, for example, and needs in protocol entity carrying portion more for the content of request message or response message Point or when entire message, this just needs to carry protocol entity in request message or response message.

Therefore, in the embodiment of the present application, for the message of specified type (e.g., log in class request message or response message, Seed resource obtains class request message or response message etc.) it needs while carrying protocol header and protocol entity, it can be wrapped in the protocol entity Include at least one of universal field and other fields.

Wherein, which can be composite construction field (such as Buffer fields), which is generally used for taking With elongated data, other described fields at least may include integer type field, character string type field etc..

When there are elongated data in the request message and/or response message, carried using the universal field in protocol entity The elongated data.

For example, if client (sender) needs to send add file information request to scheduling proxy server (recipient) When message, this just needs the filename that file to be added is carried in protocol entity, so that scheduling proxy server is according to protocol entity In filename add file.So, it is also needed in the add file information request message in addition to needing to carry above-mentioned protocol header Protocol entity is carried, and the protocol entity includes universal field, the universal field is for carrying file name information.

For example, when if universal field is Buffer fields, the format of universal field Buffer is as shown in table 3.

Buffer：

Field	Buffer length	Data
			Type	Int	Character type (char)
Byte length	2/4	It is elongated

Table 3

As shown in Table 3, universal field Buffer is composite construction field, which includes Buffer length words Section and data field (Data fields)；The type of Buffer length fields is Int, and the type of Data fields is character type (char), the byte length of Data fields is elongated, and the byte length of Buffer length fields can be 2 bytes or 4 bytes. The byte length of Buffer length fields can be determined by the length of Data.For example, when Data length is when within 65535 bytes, Byte number shared by Buffer length is 2 bytes, and when Data length is more than 65535 byte, byte number shared by Buffer length is 4 Byte.

Illustrate that certain form of request message or response message only need to carry protocol header on the whole above, other The request message or phase response message of type also need to carry protocol entity.It will illustrate by taking specific scene as an example below.

In the embodiment of the present application, the data processing method can be applied to resource downloading scene, specifically, can apply In point-to-point (P2P) data interaction scene of network data, that is, the request message of interaction or response between sender and recipient Custom protocol in message can be used for P2P data interaction scenes.

In P2P data interaction scenes, in general, may include data exchange process as shown in Figure 2, the data interaction Journey includes the following steps：

S201：Client (sender) is sent to scheduling proxy server (recipient) logs in scheduling proxy server request Message.

S202：After client successfully logs in scheduling proxy server, scheduling proxy server (sender) is to dispatch service Device (recipient) sends addition subscriber information request message, which can be client name, client identity mark The information such as knowledge, client release number.

S203：Dispatch server is returned to client (sender) by scheduling proxy server (recipient) and logs in scheduling Proxy server response message.

S204：Client (sender) sends to scheduling proxy server (recipient) and obtains seed resource request message, Seed resource request message is obtained using the acquisition seed resource request message as first.

S205：Scheduling proxy server (sender) obtains seed money to dispatch server (recipient) forwarding described first The first acquisition seed resource request message to be forwarded is obtained seed resource request message by source request message as second.

It should be noted that first obtains the difference of seed resource request message and the second acquisition seed resource request message It is, the protocol header and/or protocol entity of the two are not exactly the same.

S206：Dispatch server (recipient), which returns to obtain seed resource and respond to scheduling proxy server (sender), to disappear The seed resource response message is obtained seed resource response message by breath.

S207：Scheduling proxy server (recipient) disappears to client (sender) forwarding the second acquisition seed resource response Breath obtains seed resource response message using the second acquisition seed resource response message as first.

It should be noted that first obtains the difference of seed resource response message and the second acquisition seed resource response message It is, the protocol header and/or protocol entity of the two are not exactly the same.

S208：Client (sender) is sent to service balanced device (recipient) obtains (request of log-on message request message Message).

S209：Client receives service balanced device and is rung according to the acquisition log-on message that log-on message request message returns is obtained Answer message.

S210：Client (sender) sends the request message that tests the speed to service balanced device (recipient).

S211：Service balanced device (recipient) returns to the response message that tests the speed to client (sender).

In above-mentioned Fig. 2, login scheduling proxy server request message and login in step S201 and step S203 are dispatched Proxy server response message is all based on the message of custom protocol, and carries the protocol header and agreement of custom protocol Body；Include message length field and action type field and/or check field in each protocol header.

Log in scheduling proxy server request message in protocol entity include：Two universal fields and four integer fields； Wherein, two universal fields indicate the character string and to be obtained that client registers real-time media stream protocol server generates respectively Filename, four integer fields difference presentation protocol version number, network address translation NAT types, public network Internet protocols The address (Internet Protocol, IP), IP address of internal network；Log in the protocol entity packet in scheduling proxy server response message It includes：One integer field for indicating user identifier.

For example, above-mentioned format such as 4 institute of table for logging in protocol header and protocol entity in scheduling proxy server request message Show.P2P_PROXY_AND_CLIENT_LOGIN：

Field

P2P_HEAD

PeerID

Name

Version

NAT

OutIP

InIP

Type

P2P_HEAD

Buffer

Buffer

Int

Int

Int

Int

Byte length

It is compound

It is compound

It is compound

4

2

4

4

Table 4

As shown in Table 4, P2P_HEAD fields are protocol header, remaining field is protocol entity；Wherein, the class of P2P_HEAD fields Type is P2P_HEAD protocol headers shown in table 1 or table 2, and the type of PeerID fields is that Buffer fields shown in table 3 are (i.e. logical With field), which indicates the character string that client registers real-time media stream protocol server generates；Name field Type is Buffer fields shown in table 3, which indicates the filename of seen live streaming name or institute's program request； Version fields indicate protocol version；NAT fields indicate network address translation NAT types；OutIP fields indicate public network IP Address；InIP fields indicate IP address of internal network；Wherein, Version fields, the class of NAT fields, OutIP fields and InIP fields Type is integer Int, and the byte length of Version fields, OutIP fields and InIP fields is 4 bytes, the byte of NAT fields Length is 2 bytes.In table 4, the byte length of first three field is recombination length (Complex), and recombination length refers to corresponding multiple The sum of the byte length of each field in texture field is closed, for example, being directed to P2P_HEAD fields, which is 2 institute of table 1 or table The sum of the byte length of each field in the P2P_HEAD shown；In another example for PeerID fields or Name field, recombination length is The sum of the byte length of each field in Buffer shown in table 3.

For example, the above-mentioned format for logging in protocol header and protocol entity in scheduling proxy server response message, such as 5 institute of table Show.

P2P_PROXY_AND_CLIENT_LOGIN_BACK：

Field	P2P_HEAD	P2PID
			Type	P2P_HEAD	Int
Byte length	Complex	4

Table 5

In table 5, P2P_HEAD fields are protocol header, and type is P2P_HEAD protocol headers, and byte length is Complex；P2PID fields are protocol entity, and type Int, byte length is 4 bytes, which indicates that client exists User identifier in P2P systems.

In above-mentioned Fig. 2, the addition subscriber information request message in step S202 is the message based on custom protocol, and is taken Protocol header with custom protocol and protocol entity；Include message length field, action type field and/or verification in protocol header Field.

Addition subscriber information request message in protocol entity include：Nine integer fields and a universal field；Wherein, nine A integer field indicate respectively the addition terminal type of user, user identifier, the scheduling proxy server logged in IP Address, user's IP address of internal network, user's outer net IP address, operator identifier, area identification, network address translation Nat types, association Discuss version number；Universal field in the addition subscriber information request message indicates that registration real-time stream media protocol server generates Character string.

For example, the format of the protocol header and protocol entity in addition subscriber information request message is as shown in table 6.

P2P_PROXY_AND_TRACK_ADDUSER：

Field

Type

Byte length

P2P_HEAD	P2P_HEAD	Complex
			EndType	Int	4
P2PID	Int	4
			Scheduling broker IP	Int	4
InIP	Int	4
			OutIP	Int	4
SP	Int	2
			Region	Int	2
NAT	Int	2
			PeerID	Buffer	Complex
Version	Int	4

Table 6

In table 6, P2P_HEAD fields are protocol header, remaining field is protocol entity.Use is added in the expression of EndType fields The terminal type at family, P2PID indicate user identifier；Scheduling broker IP indicates the IP address of logged in scheduling proxy server； InIP indicates user's IP address of internal network；OutIP indicates user's outer net IP address；SP indicates operator identifier；Region indicates area Domain identifier；NAT table shows network address translation NAT types；Version presentation protocols version number；PeerID indicates registration real-time streams The character string that media protocol server generates.

In above-mentioned Fig. 2, first in the first acquisition seed resource request message and step S207 in step S204 is obtained It takes seed resource response message to be all based on the message of custom protocol, and carries the protocol header and agreement of custom protocol Body；Include message length field, action type field and/or check field in each protocol header.

Protocol entity in the described first acquisition seed resource request message includes：One for indicating file name information Universal field.Protocol entity in the described first acquisition seed resource response message includes：One indicates the logical of file name information With field, the integer field and a seed field of an expression client seed number.

For example, the format of the protocol header and protocol entity in the first acquisition seed resource request message is as shown in table 7.

P2P_PROXY_AND_CLIENT_LIVE_PEERS：

Field	P2P_HEAD	FILENAME
			Type	P2P_HEAD	Buffer
Byte length	Complex	Complex

Table 7

In table 7, P2P_HEAD fields are protocol header, and FILENAME fields are protocol entity, and the expression of FILENAME fields is wanted The type of the filename of operation, P2P_HEAD fields and FILENAME fields is respectively P2P_HEAD and Buffer, byte length Respectively Complex.

In another example the format of the protocol header and protocol entity in the first acquisition seed resource response message is as shown in table 8.

P2P_PROXY_AND_CLIENT_LIVE_PEERS_BACK：

Field	P2P_HEAD	FILENAME	PeerCount	Peer
					Type	P2P_HEAD	Buffer	Int	Peer
Byte length	Complex	Complex	4	Complex

Table 8

In table 8, P2P_HEAD fields are protocol header, remaining field is protocol entity.The expression of FILENAME fields will operate Filename, PeerCount fields indicate client seed number, peer field indicate seed field, for carry seed letter Breath, which is a composite construction field as shown in table 9.

Peer：

Field	PeerID	P2PID	Scheduling broker IP
				Type	Buffer	Int	Int
Byte length	Complex	4	4

Table 9

In table 9, peer field includes：One universal field (PeerID fields) and two integer fields (P2PID and tune Spend Agent IP)；Wherein, PeerID fields indicate the character string that seed registration real-time media stream protocol server generates, P2PID words Section and scheduling broker IP fields indicate the IP address for the scheduling proxy server that the user identifier of seed and seed are logged in respectively.

In above-mentioned Fig. 2, first in the first acquisition seed resource request message and step S206 in step S205 is obtained Seed resource response message is taken, the message of custom protocol is all based on, and carries the protocol header and agreement of custom protocol Body；Include message length field, action type field and/or check field in each protocol header；

Protocol entity in the described second acquisition seed resource request message includes：One for indicating the whole of user identifier Type-word section, a universal field for indicating the filename that need to be operated.

Protocol entity in the described second acquisition seed resource response message includes：One indicates the general of file name information Field, the seed field of a carrying seed information, two integer fields.

The protocol entity and second obtained for second in seed resource request message obtains in seed resource response message Protocol entity, including two integer fields indicate that user identifier and client seed number, the seed field are compound respectively Texture field, the seed field include：One universal field and two integer fields；Wherein, logical in the seed field The character string that seed registration real-time media stream protocol server generates, two integer words in the seed field are indicated with field Section indicates the IP address for the scheduling proxy server that the user identifier of seed and seed are logged in respectively.

For example, described second obtains format such as 10 institute of table of the protocol header and protocol entity in seed resource request message Show.

P2P_PROXY_AND_TRACK_LIVE_PEERS：

Field	P2P_HEAD	P2PID	FILENAME
				Type	P2P_HEAD	Int	Buffer
Byte length	Complex	4	Complex

Table 10

In table 10, P2P_HEAD fields are protocol header, remaining field is protocol entity.P2PID fields indicate user identifier, FILENAME fields indicate the filename that need to be operated.

In another example second obtains the format of the protocol header and protocol entity in seed resource response message, as shown in table 11.

P2P_PROXY_AND_TRACK_PEERS_BACK：

Field	P2P_HEAD	P2PID	FILENAME	PeerCount	Peer
						Type	P2P_HEAD	Int	Buffer	Int	Peer
Byte length	Complex	4	Complex	4	Complex

Table 11

In table 11, P2P_HEAD fields are protocol header, remaining field is protocol entity, in remaining field, P2PID fields Indicate that user identifier, FILENAME fields indicate the filename that need to be operated；PeerCount fields indicate the seed resource obtained Number, peer field indicate seed information：Include the character string that seed registration generates, what the user identifier and seed of seed were logged in The IP address of scheduling proxy server.

Do not include protocol entity in acquisition log-on message request message described in step S208, only includes protocol header；Step Acquisition log-on message response message described in S209 includes：Protocol header and protocol entity.The protocol entity may include：Two general Field, the two universal fields indicate the ground of scheduling proxy server log-on message and real-time media stream protocol server respectively Location.

It should be noted that scheduling proxy server log-on message is for informing that client is subsequently logging in scheduling broker clothes Required scheduling broker log-on message when business device.The address of real-time media stream protocol server is for informing that client is subsequently being noted The address of required real-time media stream protocol server when volume.

For example, obtaining the format of the protocol header in log-on message request message, as shown in table 12.

P2P_GETWAY_AND_CLIENT_REGISTER：

Field	P2P_HEAD
		Type	P2P_HEAD
Byte length	Complex

Table 12

In another example obtaining the format of the protocol header and protocol entity in log-on message response message, as shown in table 13.

P2P_GETWAY_AND_CLIENT_REGISTER_BACK：

Field	P2P_HEAD	Proxy	Rtmfp
				Type	P2P_HEAD	Buffer	Buffer
Byte length	Complex	Complex	Complex

Table 13

In table 13, P2P_HEAD fields are protocol header, and Proxy fields and Rtmfp fields are protocol entity.Proxy fields Indicate scheduling proxy server log-on message；Rtmfp fields indicate the address of real-time media stream protocol server, P2P_HEAD words The type of section is P2P_HEAD, and the type of Proxy fields and Rtmfp fields is Buffer, and the byte length of each field is Recombination length Complex.

The response message that tests the speed described in test the speed request message and step S211 described in step S210, which is all based on, to be made by oneself The message of adopted agreement, and carry the protocol header and protocol entity of custom protocol；Include message length field, behaviour in each protocol header Make type field and/or check field；The protocol entity to test the speed in request message includes：One indicates the general of random measurement data Field；The protocol entity to test the speed in response message includes：One indicates the integer field of result of testing the speed.

For example, the format of the protocol header and protocol entity in the request message that tests the speed, as shown in table 14.

P2P_GETWAY_AND_CLIENT_TEST_SPEED：

Field	P2P_HEAD	test_data
			Type	P2P_HEAD	Buffer
Byte length	Complex	Complex

Table 14

In table 14, P2P_HEAD fields are protocol header, and test_data fields are protocol entity.Test_data fields indicate Random measurement data.The type of P2P_HEAD and test_data fields is respectively P2P_HEAD and Buffer, and byte length is Complex。

For example, the format of the protocol header and protocol entity in the response message that tests the speed, as shown in Table 15.

P2P_GETWAY_AND_CLIENT_TEST_SPEED_BACK：

Field	P2P_HEAD	Speed
			Type	P2P_HEAD	Int

Byte length

Complex

4

Table 15

In table 15, P2P_HEAD fields are protocol header, and Speed fields are protocol entity, which indicates the knot that tests the speed Fruit.

In the embodiment of the present application, if after client successfully obtains resource (such as file), seed client can be become For other client downloads files, after as seed client, file is deleted by request scheduling server by exits kind Sub- client, the process detailed process is as shown in figure 3, data interaction shown in Fig. 3 may include following steps：

S301：After client sends addition user information to dispatch server, client (sender) is to scheduling broker Server (recipient) sends heartbeat detection request message.Scheduling proxy server can not be based on the heartbeat detection to client The response message of request message.

S302：If the heartbeat detection request that scheduling proxy server does not receive client transmission in set period of time disappears When breath, scheduling proxy server (sender) can send to dispatch server (recipient) and delete subscriber information request message, with So that dispatch server deletes the user information added by step S202.It, can not after dispatch server deletes user information Return to the response message based on the deletion subscriber information request message.

S303：After obtaining the file downloaded, client (sender) can be sent client to scheduling proxy server First add file information request message.

S304：Scheduling proxy server (sender) can be using the first add file information request message as the second addition text Part information request message is sent to dispatch server (recipient).

S305：Client becomes seed client in dispatch server after add file, client (sender) may be used also File request message is deleted to send first to scheduling proxy server (recipient).

S306：Scheduling proxy server (sender) can be asked the first deletion file request message as the second deletion file Message is asked to be sent to dispatch server, so that dispatch server deletes the file of addition.

In above-mentioned step S301 shown in Fig. 3, heartbeat detection request message is the message based on custom protocol, and is carried The protocol header and protocol entity of custom protocol；Include message length field, action type field and/or verification in each protocol header Field；Protocol entity in heartbeat detection request message includes：One integer field and a universal field；Wherein, the heartbeat Integer field in solicitation message indicates whether there is growth data, the heartbeat detection in the heartbeat detection request message Universal field in request message indicates growth data.

For example, the protocol header in heartbeat detection request message and protocol entity, as shown in table 16.

P2P_HEART：

Field	P2P_HEAD	Extend	ExData
				Type	P2P_HEAD	Int	Buffer
Byte length	Complex	1	Complex

Table 16

In table 16, P2P_HEAD fields are protocol header, remaining field is protocol entity.Extend is for having indicated whether expansion Data are opened up, ExData is for carrying growth data.

In above-mentioned step S302 shown in Fig. 3, it is the message based on custom protocol to delete subscriber information request message, and Carry the protocol header and protocol entity of custom protocol；Include in each protocol header message length field, action type field and/or Check field；Delete subscriber information request message in protocol entity include：The integer field of one expression user identifier.

For example, deleting the format of the protocol header and protocol entity in subscriber information request message, as shown in table 17.

P2P_PROXY_AND_TRACK_REMOVEUSER：

Field	P2P_HEAD	P2PID
			Type	P2P_HEAD	Int
Byte length	Complex	4

Table 17

In table 17, P2P_HEAD fields are protocol header, and P2PID fields are protocol entity.The P2PID expressions will delete use The user identifier at family.

In above-mentioned step S303 shown in Fig. 3, the first add file information request message is disappearing based on custom protocol Breath, and carry the protocol header and protocol entity of custom protocol；Include message length field, action type field in each protocol header And/or check field；Protocol entity in first add file information request message includes：The universal field of one expression filename With two integer fields；Wherein, two integer fields indicate the byte number downloaded from content distributing network CDN, from seed respectively The byte number of client downloads.

For example, the format of the protocol header and protocol entity in the first add file information request message, as shown in table 18.

P2P_PROXY_AND_CLIENT_ADDFILE：

Field	P2P_HEAD	FILENAME	CdnSize	PeerSize
					Type	P2P_HEAD	Buffer	Int	Int
Byte length	Complex	Complex	4	4

Table 18

In table 18, P2P_HEAD fields are protocol header, remaining field is protocol entity.FILENAME indicates the text to be operated Part name, CdnSize indicate that the byte number downloaded from content distributing network CDN, PeerSize expressions are downloaded from seed client Byte number.

In above-mentioned step S304 shown in Fig. 3, the second add file information request message is disappearing based on custom protocol Breath, and carry the protocol header and protocol entity of custom protocol；Include message length field, action type field in each protocol header And/or check field；Protocol entity in second add file information request message includes：The integer word of one expression user identifier Section, a universal field for indicating the filename that need to be operated.

For example, the format of the protocol header and protocol entity in the second add file information request message, as shown in table 19.

P2P_PROXY_AND_TRACK_ADDFILE：

Field	P2P_HEAD	P2PID	FILENAME
				Type	P2P_HEAD	Int	Buffer
Byte length	Complex	4	Complex

Table 19

In table 19, P2P_HEAD fields are protocol header, remaining field is protocol entity.P2PID indicates user identifier, FILENAME indicates the filename to be operated.

In above-mentioned step S305 shown in Fig. 3, the first deletion file request message is the message based on custom protocol, the One deletes the protocol header that file request message carries custom protocol, includes message length field and action type in protocol header Field；This first deletion file information request message in protocol entity include：The universal field of one expression file name information.

For example, first deletes the format of the protocol header and protocol entity in file information request message, as shown in table 20.

P2P_PROXY_AND_CLIENT_REMOVEFILE：

Field	P2P_HEAD	FILENAME
			Type	P2P_HEAD	Buffer
Byte length	Complex	Complex

Table 20

In table 20, P2P_HEAD fields are protocol header, and FILENAME is protocol entity.FILENAME indicates the text to be deleted Part name.

In above-mentioned step S306 shown in Fig. 3, the second deletion file request message is the message based on custom protocol, and Carry the protocol header and protocol entity of custom protocol；Include message length field, action type field and/or school in protocol header Test field；Second deletion file information request message in protocol entity include：The integer field of one expression user identifier, one Indicate the universal field for the filename that need to be operated.

For example, described second deletes the format of the protocol header and protocol entity in file information request message, as shown in table 21.

P2P_PROXY_AND_TRACK_REMOVEFILE：

Field	P2P_HEAD	P2PID	FILENAME
				Type	P2P_HEAD	Int	Buffer
Byte length	Complex	4	Complex

Table 21

In table 21, P2P_HEAD fields are protocol header, remaining field is protocol entity.P2PID indicates user identifier, FILENAME indicates the filename to be operated.

In the embodiment of the present application, it is to realize service-conformance, whether center machine can inspect periodically dispatch server normal, Abnormal dispatch server list can be then deleted if abnormal, and updates the dispatch server list of other dispatch servers, it should Monitoring and renewal process are as shown in Figure 4.

Data exchange process shown in Fig. 4, specifically comprises the following steps：

S401：Center machine (sender) sends whether the service of inspection normally checks request to dispatch server (recipient) Message (request message), to check whether dispatch server is normal.

S402：Client receives dispatch server according to the inspection response message for checking that request message returns.

S403：If inspection result is dispatch server failure, center machine (sender) (is received to scheduling proxy server Side) send the update request message (request message) for updating dispatch server list.

S404：Center machine receives the update response message that scheduling proxy server is returned according to update request message.

S405：If being that dispatch server restores normal by step S401 inspection results, center machine (sender) also can The update request message (request message) of update dispatch server list is sent to scheduling proxy server (recipient).

S406：After dispatch server restores normal, center machine (sender) sends to dispatch server (recipient) and operates The operation requests message (request message) of resource, so that dispatch server is resumed work.

S407：Center machine receives the operation response message that dispatch server is returned according to operation requests message.

In above-mentioned step S401 and S402 shown in Fig. 4, checks request message and check that response message is all based on and make by oneself The message of adopted agreement, and carry the protocol header and protocol entity of custom protocol；Include message length field, behaviour in each protocol header Make type field and/or check field；Protocol entity in the inspection request message includes：One indicates that the inspection request disappears The integer field of the sending time of breath；Protocol entity in the inspection response message includes：Two integer fields；Institute is indicated respectively It states the sending time carried in the inspection request message that dispatch server receives and starts and identify；The startup mark is used for table Show whether the dispatch server is to send to check response message for the first time after starting.

For example, checking the format of the protocol header and protocol entity in request message, as shown in table 22.

P2P_CONTROL_AND_SERVER_ALIVE：

Field	P2P_HEAD	check_sum
			Type	P2P_HEAD	Int
Byte length	Complex	8

Table 22

In table 22, P2P_HEAD fields are protocol header, and check_sum is protocol entity.The check_sum fields indicate inspection The sending time of request message is looked into, can be indicated with millisecond.

For example, checking the format of the protocol header and protocol entity of response message, as shown in table 23.

P2P_CONTROL_AND_SERVER_ALIVE_Back：

Field name	P2P_HEAD	check_sum	new_one
				Type	P2P_HEAD	Int	Int
Byte length	Complex	8	1

Table 23

In table 23, P2P_HEAD fields are protocol header, remaining field is protocol entity.Check_sum fields indicate scheduling The sending time carried in the inspection request message that server receives, new_one fields are to start to identify, and indicate the service Whether device is to send to check response message for the first time after starting.

In above-mentioned Fig. 4, update request message and update response message in step S403~S405 are all based on and make by oneself The message of adopted agreement, and carry the protocol header and protocol entity of custom protocol；Include message length field, behaviour in each protocol header Make type field and/or check field；Protocol entity in the update request message includes：One indicates that the update request disappears The integer field of the sending time of breath, a universal field for indicating updated dispatch server list；The update response Protocol entity in message includes：One indicates the transmission carried in the update request message that the scheduling proxy server receives The integer field of time.

For example, the format of the protocol header and protocol entity in update request message, as shown in table 24.

P2P_CONTROL_AND_PROXY_UPDATE_TRACK：

Field	P2P_HEAD	check_sum	Dispatch server _ key
				Type	P2P_HEAD	Int	Buffer
Byte length	Complex	8	Complex

Table 24

In table 24, P2P_HEAD fields are protocol header, remaining field is protocol entity.Wherein, check_sum fields indicate more The sending time of new request message, can be indicated with millisecond；Dispatch server _ key fields indicate updated dispatch server List.

For example, the format of the protocol header and protocol entity in update response message is as shown in Table 25.

P2P_CONTROL_AND_PROXY_UPDATE_TRACK_Back：

Table 25

In table 25, P2P_HEAD fields are protocol header, and check_sum fields are protocol entity, the check_sum field lists Show the sending time carried in the update request message that scheduling proxy server receives.

In above-mentioned Fig. 4, operation requests message and operation response message in step S406 and S407 are all based on and make by oneself The message of adopted agreement, and carry the protocol header and protocol entity of custom protocol；Include message length field, behaviour in each protocol header Make type field and/or check field；Protocol entity in operation requests message includes：Two integer fields；Described in indicating respectively The sending time and action type of operation requests message identify；Operation response message in protocol entity include：One integer field, To indicate the sending time carried in operation requests message that the dispatch server receives.

For example, the format of the protocol header and protocol entity in operation requests message, as shown in table 26.

P2P_CONTROL_AND_TRACK_DOIT：

Field	P2P_HEAD	check_sum	Op
				Type	P2P_HEAD	Int	Int
Byte length	Complex	8	1

Table 26

In table 26, P2P_HEAD fields are protocol header, remaining field is protocol entity.Check_sum fields indicate operation The sending time of request message can be indicated with millisecond；Op identifies for action type, and expression is to remove resource or start to receive The data of service broker.

For example, the format of the protocol header and protocol entity in operation response message, as shown in table 27.

P2P_CONTROL_AND_TRACK_DOIT_Back：

Field name	P2P_HEAD	check_sum
			Type	P2P_HEAD	Int
Byte length	Complex	8

Table 27

In table 27, P2P_HEAD fields are protocol header, and check_sum fields are protocol entity.Check_sum fields indicate The sending time carried in the operation requests message that dispatch server receives.

It is data processing method provided by the embodiments of the present application above, is based on same thinking, the embodiment of the present application also carries A kind of data processing system is supplied, as shown in Figure 5.

A kind of data processing system provided by the embodiments of the present application, including：

Sender 51, for sending request message；

Recipient 52, for receiving request message and according to the request message returning response message；

Wherein, the request message and response message are all based on the message of custom protocol, the request message and sound The protocol header for carrying the custom protocol in message is answered, includes message length field and action type in the protocol header Field does not include redundant data in the message based on custom protocol.

Optionally, the protocol header further includes check field.

Optionally, the request message and/or response message further include protocol entity, and the protocol entity includes universal field At least one of with other fields.

Optionally, when having elongated data in the request message and/or response message, using logical in the protocol entity The elongated data are carried with field, wherein the universal field is composite construction field.

Optionally, the custom protocol is used for point-to-point data interaction scene.

In the embodiment of the present application, data processing system shown in fig. 5 may include multiple equipment as shown in FIG. 6, specifically Including：Client 61, scheduling proxy server 62, dispatch server 63, center machine 64 and service balanced device 65, any one Equipment is recipient as long as receiving message, as long as transmission message is sender, that is, any one equipment may be both Fig. 5 Shown in sender 51, and be recipient 52 shown in fig. 5.

In conclusion a kind of data processing method of the embodiment of the present application offer and system, specifically, sending direction recipient Send request message；And receive the response message that the recipient returns according to the request message；Wherein, the request message It is all based on the message of custom protocol with response message, the self-defined association is carried in the request message and response message The protocol header of view includes message length field and action type field in the protocol header.In this way, sender and recipient it Between each message (request message or response message) for transmitting be custom protocol message, the customized protocol format Flexibly, and in agreement there is no redundant data, correspondingly, should include the agreement message in regard to not with the protocol-dependent redundancy Data, so as to effectively improve data transmission efficiency.Extended field is also remained with simultaneously, there is good autgmentability.

In conclusion a kind of data processing method provided by the embodiments of the present application and system, this method pass through sending direction Recipient sends request message；And receive the response message that the recipient returns according to the request message；Wherein, described to ask Message and response message is asked to be all based on the message of custom protocol, carrying is described certainly in the request message and response message The protocol header of agreement is defined, includes Length fields and OpType fields in the protocol header.As it can be seen that in the embodiment of the present application Request message and response message in only carry protocol header, and only include Length fields and OpType fields in the protocol header. And general head is included at least in the prior art, in the protocol header in request message and response message, request header/head response is real Body head etc., and regardless of whether need protocol entity, data volume is carried in request message and response message.Obviously, the application is real Applying does not have general head, request header/sound in the protocol header of the request message transmitted between sender and recipient or response message Answer head, these first-class redundant datas of entity, correspondingly, the just not no redundant data in request message or response message, from And data transmission efficiency can be effectively improved.

It should be understood by those skilled in the art that, the embodiment of the present invention can be provided as method, system or computer program Product.Therefore, complete hardware embodiment, complete software embodiment or reality combining software and hardware aspects can be used in the present invention Apply the form of example.Moreover, the computer which includes computer usable program code in one or more can be used in the present invention The computer program production implemented in usable storage medium (including but not limited to magnetic disk storage, CD-ROM, optical memory etc.) The form of product.

The present invention be with reference to according to the method for the embodiment of the present invention, the flow of equipment (system) and computer program product Figure and/or block diagram describe.It should be understood that can be realized by computer program instructions every first-class in flowchart and/or the block diagram The combination of flow and/or box in journey and/or box and flowchart and/or the block diagram.These computer programs can be provided Instruct the processor of all-purpose computer, special purpose computer, Embedded Processor or other programmable data processing devices to produce A raw machine so that the instruction executed by computer or the processor of other programmable data processing devices is generated for real The device for the function of being specified in present one flow of flow chart or one box of multiple flows and/or block diagram or multiple boxes.

These computer program instructions, which may also be stored in, can guide computer or other programmable data processing devices with spy Determine in the computer-readable memory that mode works so that instruction generation stored in the computer readable memory includes referring to Enable the manufacture of device, the command device realize in one flow of flow chart or multiple flows and/or one box of block diagram or The function of being specified in multiple boxes.

These computer program instructions also can be loaded onto a computer or other programmable data processing device so that count Series of operation steps are executed on calculation machine or other programmable devices to generate computer implemented processing, in computer or The instruction executed on other programmable devices is provided for realizing in one flow of flow chart or multiple flows and/or block diagram one The step of function of being specified in a box or multiple boxes.

In a typical configuration, computing device includes one or more processors (CPU), input/output interface, net Network interface and memory.

Memory may include computer-readable medium in volatile memory, random access memory (RAM) and/or The forms such as Nonvolatile memory, such as read-only memory (ROM) or flash memory (flash RAM).Memory is computer-readable medium Example.

Computer-readable medium includes permanent and non-permanent, removable and non-removable media can be by any method Or technology realizes information storage.Information can be computer-readable instruction, data structure, the module of program or other data. The example of the storage medium of computer includes, but are not limited to phase transition internal memory (PRAM), static RAM (SRAM), moves State random access memory (DRAM), other kinds of random access memory (RAM), read-only memory (ROM), electric erasable Programmable read only memory (EEPROM), fast flash memory bank or other memory techniques, read-only disc read only memory (CD-ROM) (CD-ROM), Digital versatile disc (DVD) or other optical storages, magnetic tape cassette, tape magnetic disk storage or other magnetic storage apparatus Or any other non-transmission medium, it can be used for storage and can be accessed by a computing device information.As defined in this article, it calculates Machine readable medium does not include temporary computer readable media (transitory media), such as data-signal and carrier wave of modulation.

It should also be noted that, term " comprising ", " comprising " or its any other variant are intended to nonexcludability Including so that process, method, commodity or equipment including a series of elements include not only those elements, but also wrapping Include other elements that are not explicitly listed, or further include for this process, method, commodity or equipment intrinsic want Element.In the absence of more restrictions, the element limited by sentence "including a ...", it is not excluded that wanted including described There is also other identical elements in the process of element, method, commodity or equipment.

It will be understood by those skilled in the art that embodiments herein can be provided as method, system or computer program product. Therefore, complete hardware embodiment, complete software embodiment or embodiment combining software and hardware aspects can be used in the application Form.It is deposited moreover, the application can be used to can be used which includes the computer of computer usable program code in one or more The shape for the computer program product implemented on storage media (including but not limited to magnetic disk storage, CD-ROM, optical memory etc.) Formula.

Above is only an example of the present application, it is not intended to limit this application.For those skilled in the art For, the application can have various modifications and variations.It is all within spirit herein and principle made by any modification, equivalent Replace, improve etc., it should all be included within the scope of the claims of the present application.

Claims (17)

1. a kind of data processing method, which is characterized in that including：

Sending direction recipient sends request message；And

Receive the response message that the recipient returns according to the request message；

Wherein, the request message and response message are all based on the message of custom protocol, and the request message and response disappear The protocol header of the custom protocol is carried in breath, includes message length field and action type word in the protocol header Section, and do not include in the protocol header and do not wrapped in the field that the field unrelated with current message and the protocol header are included Containing redundant content, the custom protocol is used for point-to-point data interaction scene, does not include in the message based on custom protocol Redundant data.

2. the method as described in claim 1, which is characterized in that described sender is client, and the recipient is that service is equal Weighing apparatus, the request message are to obtain log-on message request message, and the response message is to obtain log-on message response message；

It does not include protocol entity in the acquisition log-on message request message；The protocol entity obtained in log-on message response message Including：Two universal fields, described two universal fields indicate scheduling proxy server log-on message and real-time media stream respectively Agreement service device address.

3. the method as described in claim 1, which is characterized in that described sender is client, and the recipient is scheduling generation Server is managed, the request message is to log in scheduling proxy server request message, and the response message is to log in scheduling broker Server response message；

It is described log in scheduling proxy server request message in protocol entity include：Two universal fields and four integer fields；

Wherein, two universal fields indicate the character string and wanted that client registers real-time media stream protocol server generates respectively The filename of acquisition, four integer fields difference presentation protocol version number, network address translation NAT types, public network interconnection FidonetFido IP address, IP address of internal network；

It is described log in scheduling proxy server response message in protocol entity include：One integer word for indicating user identifier Section.

4. the method as described in claim 1, which is characterized in that described sender is client, and the recipient is scheduling generation Server is managed, the request message is the first acquisition seed resource request message, and the response message is the first acquisition seed money Source response message；

It is described first acquisition seed resource request message in protocol entity include：One general words for indicating file name information Section；It is described first acquisition seed resource response message in protocol entity include：The universal field of one expression file name information, one A integer field and a seed field for indicating client seed number；

Wherein, the seed field is composite construction field, for carrying seed information；The seed field includes：One logical With field and two integer fields；Wherein, the universal field in the seed field indicates that seed registers real-time media stream protocol The character string that server generates, two integer fields in the seed field indicate user identifier and the seed institute of seed respectively The internet protocol address of the scheduling proxy server of login.

5. the method as described in claim 1, which is characterized in that described sender is scheduling proxy server, the recipient For dispatch server, the request message is the second acquisition seed resource request message, and the response message is the second acquisition kind Child resource response message；

It is described second acquisition seed resource request message in protocol entity include：One integer word for indicating user identifier Section, a universal field for indicating the filename that need to be operated；

It is described second acquisition seed resource response message in protocol entity include：The universal field of one expression file name information, The seed field of one carrying seed information, two integer fields；Wherein, two integer fields indicate user identifier and visitor respectively Family end seed number, the seed field are composite construction fields, and the seed field includes：One universal field and two it is whole Type-word section；Wherein, the universal field in the seed field indicates the word that seed registration real-time media stream protocol server generates Symbol is gone here and there, and two integer fields in the seed field indicate the scheduling broker that the user identifier of seed and seed are logged in respectively The internet protocol address of server.

6. the method as described in claim 1, which is characterized in that machine centered on described sender, the recipient are that scheduling takes It is engaged in device, whether dispatch server described in machine check normally checks that request message, the response disappear centered on the request message Breath is the inspection response message that the dispatch server is returned to the center machine；

Protocol entity in the inspection request message includes：One integer word for indicating the sending time for checking request message Section；

Protocol entity in the inspection response message includes：Two integer fields, two integer fields indicate the tune respectively The sending time and startup carried in the inspection request message that degree server receives identifies；

The startup mark is for indicating whether the dispatch server is to send to check response message for the first time after starting.

7. the method as described in claim 1, which is characterized in that machine centered on described sender, the recipient are scheduling generation Server is managed, the update request of the dispatch service list centered on the request message in machine update scheduling proxy server disappears Breath, the response message are the update response message that scheduling proxy server responds the update request message；

Protocol entity in the update request message includes：The integer word of one sending time for indicating the update request message Section, a universal field for indicating updated dispatch server list；

Protocol entity in the update response message includes：One update request for indicating that the scheduling proxy server receives The integer field of the sending time carried in message.

8. the method as described in claim 1, which is characterized in that machine centered on described sender, the recipient are that scheduling takes It is engaged in device, the operation requests message of machine notice dispatch server operating resource centered on the request message；The response message is Center machine notifies dispatch server operating resource response message；

Protocol entity in the operation requests message includes：Two integer fields, two integer fields indicate the behaviour respectively Make the sending time and action type mark of request message；

Protocol entity in the operation response message includes：One integer field, to indicate that the dispatch server receives Operation requests message in the sending time that carries.

9. the method as described in claim 1, which is characterized in that described sender is client, and the recipient is that service is equal Weighing apparatus, the request message are the request message that tests the speed, and the response message is the response message that tests the speed；

Protocol entity in the request message that tests the speed includes：One universal field for indicating random measurement data；The sound that tests the speed The protocol entity in message is answered to include：One indicates the integer field of result of testing the speed.

10. the method as described in claim 1, which is characterized in that described sender is client, and the recipient is scheduling generation Server is managed, the request message is heartbeat detection request message；

Protocol entity in the heartbeat detection request message includes：One integer field and a universal field；Wherein, the heart It jumps the integer field in solicitation message and indicates whether there is growth data in the heartbeat detection request message, the heartbeat inspection The universal field surveyed in request message indicates growth data.

11. the method as described in claim 1, which is characterized in that described sender is scheduling proxy server, the recipient For dispatch server, the request message is to delete subscriber information request message；

Protocol entity in the deletion subscriber information request message includes：The integer field of one expression user identifier.

12. the method as described in claim 1, which is characterized in that described sender is client, and the recipient is scheduling generation Server is managed, the request message is the first deletion file request message；

It is described first deletion file information request message in protocol entity include：The universal field of one expression file name information.

13. the method as described in claim 1, which is characterized in that described sender is scheduling proxy server, the recipient For dispatch server, the request message is addition subscriber information request message；

Protocol entity in the addition subscriber information request message includes：Nine integer fields and a universal field；Wherein, nine A integer field indicate respectively the addition terminal type of user, user identifier, logged in scheduling proxy server it is mutual Networking protocol IP address, user's IP address of internal network, user's outer net IP address, operator identifier, area identification, network address translation NAT types, protocol version；Universal field in the addition subscriber information request message indicates registration real-time stream media protocol The character string that server generates.

14. the method as described in claim 1, which is characterized in that described sender is client, and the recipient is scheduling generation Server is managed, the request message is the first add file information request message；

Protocol entity in the first add file information request message includes：One expression filename universal field and two Integer field；Wherein, two integer fields indicate the byte number downloaded from content distributing network, are downloaded from seed client respectively Byte number.

15. the method as described in claim 1, which is characterized in that described sender is scheduling proxy server, the recipient For dispatch server, the request message is the second add file information request message；

Protocol entity in the second add file information request message includes：The integer field of one expression user identifier, one The universal field for the filename that a expression need to operate.

16. the method as described in claim 1, which is characterized in that described sender is scheduling proxy server, the recipient For dispatch server, the request message is the second deletion file information request message；

It is described second deletion file information request message in protocol entity include：The integer field of one expression user identifier, one The universal field for the filename that a expression need to operate.

17. a kind of data processing system, which is characterized in that including：

Sender, for sending request message；

Recipient, for receiving request message and according to the request message returning response message；

Wherein, the request message and response message are all based on the message of custom protocol, and the request message and response disappear The protocol header of the custom protocol is carried in breath, includes message length field and action type word in the protocol header Section, and do not include in the protocol header and do not wrapped in the field that the field unrelated with current message and the protocol header are included Containing redundant content, the custom protocol is used for point-to-point data interaction scene, does not include in the message based on custom protocol Redundant data.