CN107070990A

CN107070990A - The method and apparatus of transmitting data resources

Info

Publication number: CN107070990A
Application number: CN201710131638.2A
Authority: CN
Inventors: 李克鹏; 田林; 田林一; 卞永刚; 陈显锋
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2011-03-17
Filing date: 2012-03-02
Publication date: 2017-08-18
Anticipated expiration: 2032-03-02
Also published as: CN106850841B; CN107071826A; CN107071826B; CN102685203B; CN102130954A; CN106878442B; CN102685204B; CN102685204A; CN107070990B; CN106878442A; CN102685203A; CN106850841A

Abstract

The present embodiments relate to the method and apparatus of transmitting data resources.A kind of transmitting data resources method of node based on lightweight application layer protocol in Internet of things system, including：The request message for carrying response mode option is sent to server, wherein the response mode option represents following response mode one of which：Disposable response, multiple responses of postponement and the multiple responses for cancelling postponement disposably make an immediate response, postponed；Receive the response message generated according to the response mode option that the server is sent.According to embodiments of the present invention, by the specified response mode option in message interaction process, client can specify required response, improve CoAP interacting message efficiency.

Description

The method and apparatus of transmitting data resources

Technical field

The present embodiments relate to network communication field, and relate more specifically to the method for transmitting data resources and set It is standby.

Background technology

Lightweight application layer protocol (Constrained Application Protocol, referred to as " CoAP ") is mainly use In Internet of Things (Machine to Machine, referred to as " M2M ") scene, such as：Home controller, building automatic, intelligence The energy energy, sensor network etc..In this environment, the function of these machines is fairly simple, and general processor only has 8, Memory space is small, and the host-host protocol of complexity is not supported, and message transmission rate is relatively low.CoAP provides a kind of friendship of request/response Mutual pattern, supports embedded resource discovering, including crucial Web page concepts, such as uniform resource identifier (URI) and content type. CoAP can easily translate hypertext link agreement (HTTP), for being integrated into network.Data are transmitted based on CoAP Traditional scheme in disregard calculate data resource accurate capacity, it is impossible to assess the exact number of subpackage, therefore can not concurrently obtain Data resource, causes efficiency of transmission low.

Relatively low additionally, due to many equipment disposal abilities for using CoAP, peak transfer rate is also low, so many activating Individual connection or when handling multiple requests simultaneously, CoAP equipment is just easy to face congestion problems, leads to not after processing in time The task of continuous kainogenesis.In order to solve to define a kind of message retransmission controlling mechanism in congestion, existing CoAP agreements, as CoAP visitors When (Confirmable) message and long-time that family end equipment confirms the need for being sent to server apparatus do not meet with a response (the problems such as congestion causes), client device can retransmit the message and repeated several times after Tn seconds, be set until receiving server Response message or reach maximum number of retransmissions limitation and abandon attempting that preparation is returned；If it is x seconds and current to give tacit consent to retransmission interval Retransmitted for n-th, then Tn=x+random (0~2ⁿ), wherein random (0~2ⁿ) it is 0 to 2ⁿBetween any random integers, Therefore this method is also referred to as exponential back-off algorithm, and the time interval retransmitted every time gives server apparatus with exponential increase The looser response time.But the algorithm that prior art is used is timeslot-based, the congestion control of message level, can not be had Effect solves the other congestion problems of node level, as server because resources handling capability reaches bottleneck, or when occurring abnormal, Exponential back just seems an utterly inadequate amount, and because being the random algorithm at client ends, server is not accounted for completely yet Particular state, congestion may be further aggravated when serious.

The content of the invention

The embodiments of the invention provide a kind of method and apparatus of transmitting data resources, it would be preferable to support improves and passes in CoAP Defeated efficiency.

There is provided a kind of node based on lightweight application layer protocol in Internet of things system in embodiments of the present invention Transmitting data resources method, including：The request message for carrying response mode option is sent to server, wherein the response mode Option represents following response mode one of which：The disposable response disposably make an immediate response, postponed, the multiple sound postponed Should be with the multiple responses for cancelling postponement；Receive the response message generated according to the response mode option that the server is sent

There is provided a kind of node based on lightweight application layer protocol in Internet of things system in embodiments of the present invention Transmitting data resources method, including：The request message for the carrying response mode option that client is sent is received, wherein the response Mode option represents following response mode one of which：The disposable response disposably make an immediate response, postponed, postpone it is many Individual response and the multiple responses for cancelling postponement；The response message generated according to the response mode option is sent to client.

Lightweight application layer protocol transmission node is based in Internet of things system there is provided one kind in embodiments of the present invention Data resource client, including：Sending module, the request message of response mode option is carried for being sent to server, Wherein described response mode option represents following response mode one of which：Disposably make an immediate response, postpone it is disposable Response, the multiple responses postponed and the multiple responses for cancelling postponement；Receiving module, is generated for receiving according to response mode option Response message.

Lightweight application layer protocol transmission node is based in Internet of things system there is provided one kind in embodiments of the present invention Data resource server apparatus, including：Receiving module, for receiving asking for the carrying response mode option that client is sent Message is sought, wherein the response mode option represents following response mode one of which：One for disposably making an immediate response, postponing The response of secondary property, the multiple responses postponed and the multiple responses for cancelling postponement；Sending module, sends according to institute to the client State the response message of response mode option generation.

According to embodiments of the present invention, by the specified response mode option in message interaction process, client can be specified Required response, improves CoAP interacting message efficiency.

According to embodiments of the present invention, response mode can be indicated, and sound is received according to indicated response mode Message is answered, is so easy to requesting party to conversate processing, to improve efficiency of transmission, such as：In the feelings of indication lag response time Under condition, it is to avoid requesting party's wait-for-response message always, session can be terminated in advance after the time delay of instruction is expired；Asking When the side of asking indicates to make an immediate response, if in the customized time-out time of requesting party, it is impossible to receive response message, can also carry Preceding end session；In many secondary responses of indication lag, requesting party can preserve the information of resource subscription, multiple in order to receive The response of postponement.

Brief description of the drawings

In order to illustrate the technical solution of the embodiments of the present invention more clearly, below will be in embodiment or description of the prior art The required accompanying drawing used is briefly described, it should be apparent that, drawings in the following description are only some realities of the present invention Example is applied, for those of ordinary skill in the art, without having to pay creative labor, can also be attached according to these Figure obtains other accompanying drawings.In the accompanying drawings：

Fig. 1 is the flow chart of the method for the transmission data of an embodiment of the present invention；

Fig. 2 is the gateway of an embodiment of the present invention from the flow for implementing process of sensors for data resource Figure；

Fig. 3 is the structure chart of improved burst option in an embodiment of the present invention；

Fig. 4 is that a kind of gateway of alternate embodiment of the invention implements the flow of process from sensors for data resource Figure；

Fig. 5 is the structure chart of improved burst option in a kind of alternate embodiment of the invention；

Fig. 6 is a kind of gateway of alternate embodiment of the invention from the stream for implementing process of sensors for data resource Cheng Tu；

Fig. 7 is the structure chart of improved burst option in a kind of alternate embodiment of the invention；

Fig. 8 is that the gateway of an embodiment of the present invention sends the flow for implementing process of data resource to sensor Figure；

Fig. 9 is the block diagram of the client device of an embodiment of the present invention；

Figure 10 is the block diagram of the server apparatus of an embodiment of the present invention；

Figure 11 is the flow chart of the method for the transmission data of an embodiment of the present invention；

Figure 12 is the flow chart of the method for the transmission data of an embodiment of the present invention；

Figure 13 is the interacting message figure of an embodiment of the present invention；

Figure 14 is the interacting message figure of an embodiment of the present invention；

Figure 15 is the interacting message figure of an embodiment of the present invention；

Figure 16 is the structure chart of the client of the transmission data of an embodiment of the present invention；

Figure 17 is the structure chart of the server of the transmission data of an embodiment of the present invention.

Embodiment

Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is carried out clear, complete Site preparation is described, it is clear that described embodiment is a part of embodiment of the invention, rather than whole embodiments.Based on this hair Embodiment in bright, the every other implementation that those of ordinary skill in the art are obtained under the premise of creative work is not made Example, belongs to the scope of protection of the invention.

CoAP is transmitted based on UDP (User Datagram Protocol, referred to as " UDP "), is Based on connectionless Message Processing pattern.Its interactive mode can be synchronous response or asynchronous response.Message class Type can be：Need the message (Confirmable) confirmed, the message (Non-confirmable) that need not be confirmed, confirm to disappear Cease (Acknowledgement), reset message (Reset).A pair can be associated by message identifier (Message ID) please Summation response.

The method that CoAP is supported has four：Obtain resource (Get), more new resources (Put), establishing resource (Post) and delete Resource (Delete).Resource shifts (Representational State Transfer, abbreviation by declarative state " REST ") URI recognizes.The owning side that we are commonly referred to as resource is node or server, including but not limited to sensor, control Device, end points (End-point) etc., request resource side are client, including but not limited to gateway (Proxy), network side equipment.

The different options (Option) of CoAP agreements support, the semanteme to explain data in CoAP message bodies, such as Block (burst), Location (position), Token (token) option etc., different options support different functions, and can To extend new function by defining new Option.

CoAP supports burst option (Block Option), is mainly used in larger resource carrying out sliced transmission, with suitable Should be in the application scenarios of low-bandwidth transmission.Block options can be 1 byte, 2 bytes or 3 bytes, according to burst number Capacity required for length chosen.

The accurate capacity for calculating data resource is disregarded in traditional scheme, it is impossible to assess the exact number of subpackage, therefore can not be simultaneously Hair is obtained.It is static or dynamic also not know resource in addition.

In the following description, commonly referred to as the owning side of resource is server, with sensor as an example, request resource side is Client, example is used as using gateway.But, sensor or gateway are not used as the limitation to server or client.

Due to not knowing the precise volume of target resource, gateway exists<Get>, can only when using Block Option in order Obtain in order, i.e. choosing obtains Block 0, when waiting the Block 0 to return, then obtain Block 1, until last Block.Can not concomitantly it send<Get>Request.

The field structure of Block options generally comprises NUM fields, M field and SZX fields, wherein

NUM represents the order sequence number of burst, can be the unsigned int numeral of 4~20.0 represents first burst.

M：Represent whether there be other bursts behind current slice with a bit, its value is to also have behind 1 expression Burst, is not have burst behind 0 expression, is last burst.

SZX：For characterizing burst capacity, its calculation formula is：Burst capacity=2^ (SZX+4), i.e., 2 (SZX+4) is secondary Side.Because SZX is represented by 3 bits, its value can be 0~7, so the span of burst capacity：2^4~2^11, I.e. 16~2048.

Operation instruction for Block options is as follows：

<Get>In request, the NUM fields of Block options provide the sequence number of the burst of current request, and when burst sequence Number be 0 when, SZX provide gateway suggestion each burst capacity.<Get>In response or<Put>/<Post>In request, The sequence number of the burst of the NUM field description current transmissions of Block options, M field shows whether also have successive fragment below.

<Put>/<Post>In response, the NUM fields of Block options show the burst sequence number currently responded.

When gateway is used<Get>When method obtains first burst (Block), NUM is arranged to 0, and carries suggestion Burst capacity (i.e. SZX), sensor node can select the burst capacity for agreeing to advise, or selection one than advising that burst is small Burst, and return in the response, meanwhile, the data of first burst are returned in the response.

The present invention considers that gateway knows the precise volume of target resource in advance, then gateway can choose whether to use Block Option sends the request of resource acquisition, can also realize concurrent request, i.e., while Block 0 is asked, can also ask Block 1 is sought, without waiting.Request Block sequentially can also sweetly disposition.

In simple design, Block Option have three selections, can be a bytes, can be 2 bytes, Can be three bytes, the capacity according to resource is different, the quantity capacity of burst (Block) is different, required length is not yet Equally.Agreement is provided, in addition to last burst, and the capacity of burst must be identical, but is still needed every time in transmission every time Carry M (showing whether also have burst below) and SZX (capacity of burst).

Every time in request and response, M and SZX are required for transmitting, and in fact, in addition to last burst, M Position and SZX value are identical every time, and the transmission repeated wastes transfer resource.The purpose for repeating to send SZX assumes both sides all The SZX after consulting is not preserved, that carry in the first secondary response is the SZX after consulting, gateway is obtained from response and asked again Middle transmission is asked, so that gateway and sensor need not all preserve state.In request response rounds once, a word is wasted altogether Section, if burst number is a lot, just it is enough for the byte of waste, for M2M equipment, and transfer resource is limited, this biography The waste of defeated resource is very considerable.Assuming that if the data to be transmitted are 64M, each Block load (payload) capacity It is for the block entry numbers that 1024byte is then sent：65536.The number that the Block options then sent divide according to byte is：

(1) byte：16

(2) two bytes：4080

(3) three bytes：61440

If M and SZX can not be sent, request is 65536 bytes (byte) plus the data that response can be saved, i.e., 64K data.In addition, if the two fields should not, then NUM fields can use full all positions (bit), then need the data sent The number of bag is changed to：

(1) byte：256

(2) two bytes：65280

The structure of 3 bytes need not be now sent, therefore data can also be saved for 61440*2bytes, i.e. 60K numbers According to.Data bit 124K is then saved altogether, saves data transfer rate 0.189%.It is (16+4080*2+61440*3- that header field, which saves percentage, 256-65280*2)/(16+4080*2+61440*3)=61680/192496=32%.

Save the formula of data volume：

T is total Block quantity, and S is burst capacity (Block Size), and the percentage of the flow of saving (only compares head Domain)：

T<When 16：Without saving；Both bytes；

16<T<When 256：1-T*1/ (16*1+ (T-16) * 2), simple design needs 2 bytes, and preferred scheme is only needed Want a byte；

256<T<When 4096：1- (256*1+ (T-256) * 2))/(16*1+ (T-16) * 2), simple design needs 2 Byte, preferred scheme needs 2 bytes；

4096<T<When 65256：1- (256*1+ (4096-256) * 2+ (T-4096) * 3))/(256*1+ (T-256) * 2), Simple design needs 3 bytes, and preferred scheme needs 2 bytes.

T>When 65256, no saving, preferred scheme embodiment and simple design of the present invention are required for 3 bytes.

In simple design, during using Put/Post orders, burst capabilities negotiation lacks efficiency.In Put/Post requests In, for first burst, it is necessary to send the data of first burst and the burst capacity of recommendation, if sensor node is selected Different burst capacity, gateway needs to be resend according to the burst capacity of sensor, then the burst number that last time sends According to being wasted.Moreover, gateway using Put/Post when asking to send the big resource of capacity based on burst option, prior nothing Method informs sensor resource capacity information, in transmitting procedure, and sensor side is received, and side caches received resource, if passed Sensor finds insufficient memory, and resource can only send back the error status code of one 413 when not being transmitted, expression The resource of request is too big, terminates this time to transmit.The part resource transmitted before this is then useless, and transfer resource is wasted.If Gateway can inform the capacity information of the resource to be transmitted of sensor in first fragmental messages, and sensor can then compare Resource capacity information and memory capacity, if off-capacity, return to the conditional code of 413 " resource of request is too big ", to tie in advance Beam resource transmission, the purpose for saving transfer resource is reached with this.

Breakpoint transmission on internet, that is, to continue to download since the place that file has been downloaded.Gateway to When sensor request data, to add an information to represent the scope (Range) of request downloading data, show wherefrom Start.

Such as, gateway transmits solicited message with browser and gives Web sensors, it is desirable to since 2000070 bytes：

GET/down.zip HTTP/1.0

User-Agent:NetFox

Range:Bytes=2000070-

Accept:text/html,image/gif,image/jpeg,*；Q=.2, */*；Q=.2

Wherein, RANGE:Bytes=2000070-, the meaning of this line is exactly to tell this file of sensor down.zip Passed since 2000070 bytes, byte above is without passing.

The shortcoming of this scheme is that do not have burst mechanism, and the negotiation of burst capacity is not supported, and burst sum is not supported yet Consult.The embodiment of the present invention is considered during sliced transmission, carries out the negotiation of burst capacity and/or burst sum.For this The invention provides a kind of method of data fragmentation transmission, the precise volume of target data resource can be obtained, burst appearance is carried out The negotiation of amount, obtains burst sum, and carry out transmitting data resources according to burst sum.

The flow of an embodiment of the present invention is illustrated referring to Fig. 1.Fig. 1 is the flow of an embodiment of the present invention Figure.

During S110, the capacity information of the data resource of node is obtained.If gateway is from sensors for data, Then the data resource capacity information of node is preserved on a sensor.Gateway can obtain node by request message to sensor Data resource capacity information.If gateway sends data to sensor, then gateway locally has been known for the number of node According to the capacity information of resource.The data resource capacity information of node is obtained, is to carry out the negotiation of burst capacity and true for next step Determine burst sum to prepare.

Then, during S120, gateway sends the request message for carrying the first burst option, wherein institute to sensor State the burst capacity that the first burst option includes recommending.Sensor is after the request message sent in receiving S120, according to certainly Body ability, determines used burst capacity during this transmitting data resources, and the burst capacity that sensor is determined is small In the burst capacity recommended equal to gateway.

In S130, gateway receives the response message for carrying the second burst option, wherein the second burst option is included really Fixed burst capacity, the burst capacity of the determination is less than or equal to the burst capacity of the recommendation.Gateway is being connected to point of determination After piece capacity, according to the data resource capacity information of the node of grasp, it is determined that point of the data resource for the node that will be transmitted Piece sum.

Then, in S140, according to the burst capacity of the determination and the data resource capacity information of the node, burst Transmit the data resource.

According to embodiments of the present invention, the capacity information for the data resource for needing to transmit can be known, and pass through burst capacity Consult the burst capacity for determining to use during transmission data, it is possible thereby to lower error rate in transmitting procedure is realized, and can be simultaneously Hair ground transmission data.

Process is implemented below in conjunction with what Fig. 2 illustrated embodiment as shown in Figure 1.What Fig. 2 was represented is gateway from sensor The illustrated examples of acquisition data, design only to illustrate the invention, and not as limitation of the present invention.

Data resource acquisition process shown in Fig. 2 is described in detail below：

ES210：Gateway sends resource discovering request to sensor, i.e., biography is obtained by Get./wellknown/core The Resources list on sensor.

ES220：Sensor returns to the Resources list, and resource indication information to gateway；Resource indication information mainly includes Addressing information (i.e. URI), resource name, resource description information, content type of resource etc..The present invention enters to resource indication information Row extension, the resource indication information of extension includes：Resource is the configured information of dynamic resource or static resource.

ES230：The Resources list that gateway is returned according to sensor, according to the configured information of resource, therefrom selection target is provided Source, and according to identification marking (information of energy unique identification resource, such as resource name, URI etc.), obtain target resource.

ES240：Sensor judged target resource capacity, if resource capacity is less than transport level messages Capacity, then directly return to resource content to gateway；If resource capacity is more than the capacity of a transport level messages, money is returned Source capacity information.Alternatively, burst option can be used in sensor, according to the burst capacity that itself is determined, directly returns to first Burst.The burst capacity that subsequent client and sensor root are determined therefrom that, following burst is transmitted using burst option.

In a kind of alternate embodiment of the invention, if target data resource is dynamic data resource, while returning to dynamic Data resource is indicated to gateway, and indicates that gateway obtains money using Block options with the conditional code of 413 " request resource is too big " Source.

If data resource is dynamic resource, it indicates that what the resource capacity in information was represented is current resource snapshot (Snapshot) capacity information, sensor needs to cache this snapshot data；If static resource, it indicates that the money in information Source capacity information is accurate capacity information.If it should be appreciated by those skilled in the art that data resource is dynamic resource, passed Sensor can send the check code of resource snapshot, and gateway can subsequently retransmit new resource if necessary to fresher data Obtain request.

ES250：Gateway is according to data resource capacity information, and judgement needs to use burst option, and sends carrying burst choosing The request message of item, burst capabilities negotiation is carried out with sensor device, indicates the burst capacity recommended.

ES260：Sensor determines burst capacity, and be returned to gateway according to self-ability.Alternatively, sensor Burst sum is returned simultaneously.Certainly, because gateway has obtained data resource capacity information, burst sum can also be by gateway It is determined that.It should be noted that the burst capacity that the burst capacity that sensor is determined can only be less than or recommend equal to gateway.

ES270：Gateway is from 1 until burst sum, sends request, acquisition request and burst sequence number pair to sensor successively The fragment data for the data resource answered.

ES280：Sensor returns to the burst sequence number and data corresponding with the burst sequence number according to the burst capacity of determination The fragment data of resource, until complete end of transmission.

According to a preferred embodiment of the present invention, it can realize that parallel processing, i.e. gateway can be asked simultaneously in ES270 Multiple fragmental messages are obtained, without waiting sensor to return to the response message to previous fragment request message.

ES210 to ES240 code is, for example,：

REQ:GET/.well-known/core--- transmit a request to the URI of acquiescence, i.e. root and obtains the Resources list；

RES:200OK-- response identifications are obtained successfully, and carry 2 groups of resource indication informations；

</sensors/temp>；Ct=41；N=" TemperatureC ", -- temperature resource, content type 41 is entitled TemperatureC；

</sensors/light>；Ct=41；N=" LightLux " -- light resource, content type 41 is entitled LightLux；

</sensors/firmware>；Ct=52；N=" firmware "；Snapshot=0-- firmware resources, content class Type 52, entitled firmware, non-dynamic resource；

</sensors/log>；Ct=52；N=" log "；Snapshot=1-- firmware resources, content type 52, title For log, dynamic resource, current data is snapshot snapshot；

REQ:GET/sensors/firmware-request firmware resource

RES:413“Request Entity Too Large”Size:88000.413 conditional code shows the resource of request too Greatly, its precise volume is 88000 bytes.

If data resource is the process meeting dynamic change of dynamic resource, i.e. data resource in transmission, for example, it can use Following two scheme implementation processing：

(1) when starting transmission data resource, snapshot (Snapshot) is set up to the resource, that is, caches data money this moment The capacity information in source, and this capacity information is transmitted, regardless of follow-up change；Correspondence such scheme.

(2) if data resource is changed in transmitting procedure, sensor can be in any one acquisition data resource In the response message of request message, error code is returned, indicates that data resource has been changed, gateway needs to reacquire.

Alternatively, gateway and sensor increase authentication information in interacting message.Identity can be included in authentication information (ID), the key information (Digest) that identity-based mark and password (Password) are calculated.Identity and password can be with It is to be pre-configured with to gateway and sensor both sides.Configuration process：

For example, the algorithm of key can be：Digest=MD5 (ID:Password), i.e., ID and Password is constituted Character string carries out Hash (Hash) using MD5 algorithms, and Hash value is Digest.Sender sends ID and Digest, recipient According to the Password for receiving ID He prestoring, Digest is drawn according to same algorithm, sent with sender Digest is compared, if unanimously, certification passes through.

Gateway from sensors for data resource when, as shown in Figure 2, it is necessary to know data resource capacity information.According to this A kind of embodiment is invented, gateway can obtain the data resource capacity information for being stored in sensor using following scheme.

(1) extension link form (Link-format) keyword

In Link-format, a keyword ,-sn, or-snapshot are extended, for obtaining data recourse requests Response in, whether show resource data is snapshot data.If this parameter is not present, or its value is 0, is shown to be static money Source, if the value of this parameter is 1, it is dynamic resource to be shown to be current data, and the data of acquisition are current snapshots.Static state money Source refers to that metastable resource, i.e. resource content will not be changed frequently in a period of time.Concrete meaning can enter in a standard Row definition.In the present invention, the immovable situation of value of resource is referred mainly to.

Also extend keyword：- asz, shows the information of the accurate capacity of resource.

Message instance：

Gateway sends the request of resource discovering to sensor：

REQ:GET/.well-known/core--- transmit a request to the URI of acquiescence, i.e. root and obtains the Resources list

Sensor sends the response of resource to gateway：

RES:200OK-- response identifications are obtained successfully, and carry 2 groups of resource indication informations

</sensors/temp>；Ct=41；N=" TemperatureC ", -- temperature resource, content type 41 is entitled TemperatureC

</sensors/light>；Ct=41；N=" LightLux " -- light resource, content type 41 is entitled LightLux

</sensors/firmware>；Ct=52；N=" firmware "；Asz=65000；Snapshot=0-- firmwares Resource, content type 52, entitled firmware, non-dynamic resource, precise volume is 65000 bytes；

</sensors/log>；Ct=52；N=" log "；Asz=88000；Snapshot=1-- firmware resources, content Type 52, entitled log, dynamic resource, current data is snapshot snapshot, and its precise volume is 88000 bytes；

This response message is packaged in the message body of CoAP message, and recipient's (i.e. gateway) is according to Link-format Regulation in standard is parsed.

(2) conditional code is increased

When the data resource for receiving gateway obtains request, if resource is too big, a bag is not transmitted, sensor shape State code carrys out notification gateway, for showing, resource is too big, it is necessary to be asked with Block Option.

Such as, conditional code 413 is can specify that, for showing that current data resource capacity is excessive, gateway is indicated in the request Use Block options.Other conditional codes can be provided as needed, for representing other implications, for other purposes.

Message instance：

Gateway sends the request of resource acquisition to sensor：

GET/sensordata

Sensor sends the response of carrier state code to gateway：

ACK 413 (conditional code shows that data resource capacity is too big)

(3) increase by one shows capacity (Size) option (Option) in CoAP head field (Header)

Gateway in the request, can allow sensor returned data with capacity option (Size Option) come indication sensor The capacity of resource；Sensor in the response, the capacity of data resource is indicated with Size Option.

Either, even if gateway does not have Size Option instruction, sensor is also referred to Size Option in the response Bright resource capacity, especially resource are than in the case of larger, sensor should be indicated.

If resource is smaller, sensor directly returns to resource data in message body (Body), then gateway should be with resource The actual capacity of data is defined, and the resource capacity shown in Size Option can be used for verification.

If resource is larger, sensor does not return to resource data, only with the capacity of Size Option returned datas, simultaneously Gateway is indicated to conditional code, allows gateway to initiate new request, is asked with Block Option.

Size Option code can be 16, and data type is integer, and data length is 1~4 byte, data sheet Position is byte.Size Option are mainly used in<Get>In the response of method,<Put>/<Post>In the request of method, for table Show the capacity of resource；If in<Get>In the request of method, its value is set to 0 without actual meaning, recommendation.

Message instance：

Gateway sends the request of resource acquisition to sensor：

GET/sensordata

Sensor sends the response of carrier state code to gateway：

ACK+413+Size 51200 (50K bytes)

Process is implemented below in conjunction with what Fig. 3 illustrated embodiment as shown in Figure 1.What Fig. 3 was represented is gateway to sensor The illustrated examples of transmission data, design only to illustrate the invention, and not as limitation of the present invention.

When gateway is used<Get>When method obtains first burst (Block) data, NUM fields are arranged to 0, and take With the burst capacity (i.e. SZX) recommended, sensor can select the burst capacity for agreeing to recommend, or selection one to be less than or equal to The burst capacity of the burst capacity of recommendation, and return in the response, meanwhile, the burst number of first burst is returned in the response According to.Therefore, when NUM fields are 0,<Get>Request has a dual semanteme, and one is to obtain first fragment data, and two are point The negotiation of piece capacity.Ambiguity of the agreement in processing is so brought, and the information such as data capacity can not be carried.

The embodiment of the present invention is improved this, in an embodiment of the present invention, and gateway exists<Get>Method please When seeking middle use Block Option, if NUM fields are arranged to 0, represent that both sides only carry out the negotiation of burst capacity, and The negotiation of burst sum.I.e. sensor in the response, returns to burst sum using NUM fields, uses SZX field Returning sensors The burst capacity of determination.M field can remove, and a Bit be saved, for NUM fields.Because requesting party, such as gateway is known Burst sum, so from the NUM fields of burst it is known that whether the burst is last burst, therefore avoid the need for again Use M field.In this case, if the fragment data of first burst of acquisition request, is set to 1, successively class by NUM Push away.

It should be noted that when if gateway sends first request, it is not known that the capacity of data resource, so BlockOption can use a byte, if the data resource of sensor is larger, burst number is larger, then sensor can So that burst sum is returned using two bytes or three bytes in the response.

When Block Option are 2 bytes, it is designed to that SZX fields take last three of second byte, table Show burst capacity；NUM fields take first character section plus first 5 of second byte, represent current slice sequence number；If In NUM in the 0 corresponding response message of request, then it represents that burst sum.It will be appreciated by those skilled in the art that message mark can be used Know (Message ID) and come association request and response, that is, ask and all carry unique Transaction Identifier, such sensor in responding It is to be used to return to burst sum to be just understood that this response message.

Burst capacity negotiation procedure illustrated below, message instance is：

Gateway sends the request of resource acquisition to sensor：

GET 00,000 101 (NUM is that 0, SZX is 101, i.e., 5,9 powers that burst capacity is 2 are represented, i.e., 512)

The response that sensor is sent to gateway：

(NUM is ACK 10,000 100:10000, i.e., total burst number is that 32, SZX is 100, i.e., 4, it is 2 to represent burst capacity 8 powers, i.e., 256)

This design eliminates a bit (Bit), i.e., M to eliminating, technical advantage is to save data traffic And the change to existing design is little.In this embodiment, burst capacity (SZX) field still will be sent every time.

In the prior art, burst capacity (i.e. SZX fields) will be sent every time, still be rung either in request message Answer in message, in addition to the burst capacity possibility used in first burst and last burst is different, others point Piece capacity is entirely the same.Repeat transmission identical NUM fields mutually and waste transfer resource.

In embodiments of the present invention, gateway exists<Get>When using Block Option in the request of method, if NUM quilts 0 is set to, represents that both sides only carry out the negotiation of burst capacity, and the total negotiation of burst.I.e. sensor in the response, is used NUM fields return to total burst number, the burst capacity determined using SZX fields Returning sensor.And gateway and sensor are double Burst capacity determined by side's storage, the fragment data transmission message for after.In addition to last fragment data.Net Close follow-up<Get>In the request of method, asked current slice sequence number is only sent, has determined and keeps not without sending The burst capacity of change, and sensor is in the response message, also only sends current burst sequence number and corresponding with the burst sequence number Fragment data, burst capacity is not retransmited.In this case, when NUM is 1, the burst number of first burst of request is represented According to, the like.

To use<GET>Order illustrates above-described embodiment exemplified by sensors for data resource,

As shown in figure 3, new Block Option design is as follows：

Wherein structure (1) is used for the situation that NUM is 0：

<Get>In request, NUM is that 0, SZX is second byte, represents burst capacity, and Total Number are represented point Piece sum, request when without using, it is not necessary to carry；<Get>In response, NUM is that 0, SZX represents the burst that sensor is determined Capacity, Total Number represent burst sum.

In the prior art, the interval of burst capacity is than larger, such as 2048,1024,512, underaction.And it is actual On, 512 for a Block, smaller, can just preferably be put into a UDP bag, i.e., 1472 bytes.This Invention is improved this, in one embodiment, for SZX, can take new formula, such as：(SZX+1) * 8, then It may range from：8~2048, but successively decrease at intervals of 8.

Structure (2) and structure (3) in Fig. 3 are used for<Get>NUM is not 0 situation in request, that is, when obtaining fragment data Situation：

When NUM is less than 256, burst sequence number, i.e. structure (2) are represented with a byte；When NUM is more than 28 powers When (i.e. 256), 16 powers (i.e. 65536) less than 2, burst sequence number, i.e. structure (3) are represented using two bytes.

Because the NUM in structure (2) have to be larger than the previous bytes of the NUM fields in 0, structure (3) also greater than 0, because This can be distinguished with structure (1), for<Get>In response, the value of NUM fields and request, it can also distinguish.

Illustrated below, message instance is：

Gateway sends the request of resource acquisition to sensor：

GET 00,000,000 00000101 (NUM is that 0, SZX is 101, i.e., 5,9 powers that burst capacity is 2 are represented, i.e., 512)

The response that sensor is sent to gateway：

(NUM is that 0, Total Number are 10000 to ACK 00,000,000 00,000,100 00,000,000 00010000, i.e., Burst sum is 100 for 32, SZX, i.e., 4,8 powers that burst capacity is 2 are represented, i.e., 256).

By being redesigned to Block Option, it can at least be reduced in each request or response and send 4 bits Position, in the case where burst is more, can be greatly enhanced efficiency of transmission, save transfer resource, at the same also improve gateway and The treatment effeciency of sensor both sides.

Fig. 4 shows a kind of alternate embodiment of the present invention.In the embodiment shown in fig. 4, ES410 to ES420 and Fig. 2 institutes Show that the ES210 to ES240 of embodiment is identical, description is not repeated.

In the embodiment shown in fig. 4, in ES450, gateway is sent to sensor<GET>Request, is carried out using burst option Burst capabilities negotiation, indicates the burst capacity that gateway is recommended.In ES460, sensor selects and determines suitable burst capacity, For resource to be carried out into burst, and all fragment data active push are sent out again to gateway without gateway<GET>Request.

During Fig. 4 embodiments obtain data resource, the design of burst option is as shown in figure 5, wherein：

Structure (1) is sent for gateway to sensor<GET>Request, SZX fields represent the burst capacity that gateway is recommended, and pass Sensor final choice and burst capacity of the burst capacity less than or equal to gateway recommendation determined, NUM are that 0 expression gateway requests are complete Resource, NUM does not represent the specific the NUM fragment data of gateway requests for 0, and sensor can only use SZX fields when NUM is not 0 Indicated burst capacity.

Structure (2) and structure (3) are used for the burst response message that sensor returns to full resource to gateway, if for certain The response of individual specific fragment data request, it is not necessary to which the M field carried in burst option, structure (2) and (3) is indicated whether as most Latter burst, is that 1 expression is not last burst, NUM field lists if M field, which is 0, represents last burst Which burst show that sensor returned is.

It is illustrated below.Message instance is：

Gateway sends the request that data resource is obtained to sensor：

CON GET 00,000,000 00000101 (NUM is that 0, SZX is 101, i.e., 5,9 powers that burst capacity is 2 are represented, I.e. 512)

The response that sensor is sent to gateway：

(NUM is that 1, M is 1 to ACK 200 00000011, represents first burst sent, and not last point Piece, burst capacity is the capacity that SZX fields are specified)；

Sensor continues to send CoAP responses to gateway：

(NUM is that 2, M is 1 to CON 200 00000101, represents second burst sent, and not last point Piece, burst capacity is the capacity that SZX fields are specified)；

Gateway returns to the acknowledgement character response to CON；

Sensor sends last burst to gateway：

CON 200 00000110 (NUM is that 3, M is 0, represents the 3rd burst sent, and is last burst, Specific burst capacity is calculated by actual read-out data).

Embodiment according to Fig. 4, when gateway obtains complete data resource from sensor, it is only necessary to complete burst appearance The negotiation of amount, and request is obtained without sending substantial amounts of fragment data, greatly save data transfer throughput.

Fig. 6 shows another alternate embodiment of the present invention.In the embodiment shown in fig. 6, ES610 is to ES640 and Fig. 2 The ES210 of illustrated embodiment to ES240 is identical, therefore description is not repeated.

Fig. 6 is that, in ES650, gateway is sent to sensor with embodiment illustrated in fig. 2 difference<GET>Request, request Resource is obtained, using burst option, the burst capacity that gateway is recommended is indicated, the value of now NUM fields filling is 0, represents request Obtain last burst；In ES660, the request of sensor response gateway returns to the burst capacity and last point determined The sequence number of piece and corresponding fragment data.Due to last burst sequence number correspondence burst sum, so in ES670, net Pass just can successively or concurrently obtain the request of other fragment datas.In ES680, sensor according to the burst capacity of determination, Return to the sequence number and corresponding fragment data of the burst.ES670 and ES680 can be interacted repeatedly, until fragment data is passed It is totally lost complete.

The burst option used in Fig. 6 embodiments is as shown in fig. 7, for example with the burst option of two bytes, only include NUM fields and SZX fields.

Below in conjunction with Fig. 6 and Fig. 7 for example, message instance is：

Gateway sends the request of resource acquisition to sensor：

(NUM is 0 to CON GET 00,000,000 00000101, represents to require to obtain last burst, SZX is 101, i.e., 5,9 powers that the burst capacity recommended is 2 are represented, i.e., 512).

The response that sensor is sent to gateway：

(NUM is 1000 as 8 to ACK 00,000,000 01000101, and represent return is the 8th burst, and SZX is for 101 5,9 powers that the burst capacity determined is 2 are represented, i.e., 512)；

According to the return information of first time, gateway has been known for one and has 8 bursts, and has obtained the 8th burst Data, gateway continue to sensor send CoAP request, can obtain successively can also concurrently obtain remaining fragment data. Following message example is the fragment data of first burst of acquisition request：

CON GET 00,000,000 00001101 (NUM is 1, represents to require to obtain first burst, SZX is 101, i.e., 5, 9 powers that burst capacity is 2 are represented, i.e., 512)；

Sensor returns to the acknowledgement character response to CON, i.e., the data of first burst；

Gateway can successively or all remaining bursts of concurrent request, all data until having obtained.

Embodiment according to Fig. 6, while burst capabilities negotiation, can obtain the burst number of last burst According to, in successive fragment data acquisition, used burst capacity all same, therefore aforementioned preferred embodiments can be combined Description, gateway can not retransmit SZX fields, and only send NUM fields when sending the request for obtaining fragment data, by This can save data traffic, improve efficiency of transmission.

Fig. 8 is shown sends data using burst option to sensor, such as using asset creation (Post) or renewal (Put) embodiment when asking.It is specifically described below in conjunction with Fig. 8.

Detailed process description is as follows shown in Fig. 8：

ES810：Gateway sends asset creation (Post) to sensor or updates (Put) request message, utilizes Size options The capacity information of resource is sent, the burst capacity and burst sum for indicating to recommend using burst option, burst described herein are total Number is burst capacity based on recommendation and the volumeter of data resource to be sent is calculated, and does not carry specific in request message body Resource data.

ES820：If sensor is ready to receive this data, it is, for example, 100 (i.e. instruction client continuation to return to conditional code Send), while returning to the burst capacity determined to gateway, the burst capacity of the determination can only be less than or equal to gateway recommendation Burst capacity；If sensor is unwilling to receive this data, returns to error code and indicate that client should not continue to send data.Than Such as, the lack of memory capacity of sensor then returns to 413 " RequestEntity to store the data of indicated resource capacity Too Large " return code.

ES830：The burst capacity for the determination that gateway is returned according to sensor, judges whether the burst capacity phase with recommending Together, if identical, ES360 is jumped to；If it is not the same, the burst capacity information of the determination then returned according to sensor, and According to data resource capacity, burst sum is recalculated.

ES840：Gateway sends the burst capacity determined and the burst recalculated sum to sensor again.

ES850：Sensor returns to the burst capacity determined.

ES860：Gateway is sent and burst sequence number to sensor successively from total up to burst from 1 according to burst sequence number The fragment data of corresponding data resource, until complete end of transmission.

ES870：Sensor returns to the message for determining to receive, wherein including the burst sequence number received.

Parallel processing, i.e. gateway can be carried out according to a preferred embodiment of the present invention, in ES860 can be simultaneously to biography Sensor sends multiple fragment datas, without waiting sensor to return to the response message to previous fragmental messages.Alternatively, According to a preferred embodiment of the present invention, gateway and sensor increase authentication information in interacting message.Certification message is matched somebody with somebody Putting can be using the same way described in reference picture 2 with interactive mode.

In order to improve efficiency of transmission, data traffic is saved, according to another preferred embodiment of the invention, as above for< GET>It is such described in method, using<Put>/<Post>In the request of method, it is no longer to send first to be for 0 as NUM Fragment data, but inform the capacity and burst sum of the burst that sensor is recommended.Sensor can return to response and inform gateway Whether continuation sends data.Sensor in the response, total burst number is returned to using NUM fields, is returned and sensed using SZX fields The burst capacity that device is determined.And burst capacity, the fragment data for after determined by gateway and sensor both sides storage Transmit message.In addition to last fragment data.Gateway is follow-up<Put>/<Post>In the request of method, institute is only sent The current slice sequence number of request, has determined without transmission and keeps constant burst capacity, and sensor is in response message In, current burst sequence number and fragment data corresponding with the burst sequence number are also only sent, burst capacity is not retransmited.This In the case of, when NUM is 1, the fragment data of first burst of request is represented, the like.

In the case, the design and occupation mode of burst option are similar to shown in Fig. 3, for Fig. 3 It is bright.<Put>/<Post>In request, NUM fields are that 0, SZX fields are second bytes, represent the burst capacity recommended, Total Number represent the total number of burst to be sent；<Put>/<Post>In response, NUM fields are 0, SZX field lists Show the burst capacity that sensor is determined, Total Number are useless, it is not necessary to carry；If the SZX fields that gateway is received with What is sent is inconsistent, it is necessary to be sent again with new SZX<Put>/<Post>Request, and the burst sum that carrying is recalculated, Sensor beams back response again.After<Put>/<Post>In request and response, SZX fields are no longer carried.

By being redesigned to burst option, it can at least be reduced in each request or response and send 4 bits, In the case that burst is more, efficiency of transmission can be greatly enhanced, transfer resource is saved, while also improving gateway and sensor The treatment effeciency of both sides.

In addition, prior art is in the request of each sliced transmission, it is required for carrying the unified resource mark for asking resource Know (URI, Unified Resource Identifier), usual URI will account for ten a few to tens of bytes, the transmission repeated Transfer resource can be wasted, present invention design associates multiple requests of sliced transmission using Token (token), only at the first point Transmit URI in piece message, in follow-up sliced transmission request, it is only necessary to carry Token, due to Token be typically 1~ 8 bytes, therefore certain flow can be saved.

Fig. 9 is a kind of embodiment of client device by sliced transmission data resource of the invention.Client shown in Fig. 9 Equipment 900 includes：Acquiring unit 910, for obtaining data resource capacity information；Transmitting element 920, burst is carried for sending The request message of option, wherein the burst option includes the burst capacity recommended, receiving unit 930 receives and carries burst choosing The response message of item, wherein the burst option includes the burst capacity determined；With transmission unit 940, for according to it is described really Fixed burst capacity and the data resource capacity information, data resource described in sliced transmission.

According to a preferred embodiment of the present invention, the client device may further include memory cell 950, use In the burst capacity for preserving the determination.So as to during transmitting data resources, it is not necessary to send SZX fields every time.

According to another preferred embodiment of the present invention, the client device may further include authentication unit 960, For sending and receiving authentication information.

Figure 10 is a kind of embodiment of server apparatus by sliced transmission data resource of the invention.Serviced shown in Figure 10 Device equipment 1000 includes：Receiving unit 1010, the request message of burst option is carried for receiving, wherein the burst option bag Include the burst capacity of recommendation；Transmitting element 1020, the response message of burst option is carried for sending, wherein the burst option Burst capacity including determination；With transmission unit 1030, for the burst capacity according to the determination, data described in sliced transmission Resource.

According to an embodiment of the present invention, transmitting element 1020, which is additionally operable to send, carries disappearing for data resource capacity information Breath, in order to burst capacity and the data resource capacity information of the transmission unit 1030 according to the determination, sliced transmission institute State data resource.

According to an embodiment of the present invention, receive once ask when, transmission unit 1030 burst can be passed on one's own initiative Transmission of data, makes requests on without client device for each fragment data.

According to a kind of preferred embodiment of the invention, the server apparatus may further include memory cell 1040, use In the burst capacity for preserving the determination.So as to during transmitting data resources, it is not necessary to send SZX fields every time.

According to another preferred embodiment of the present invention, the server apparatus may further include authentication unit 1050, for sending and receiving authentication information.

According to embodiments of the present invention, gateway can know the capacity information of target resource, and whether burst is used for decision-making Mode obtains resource, this avoid the possibility of error, can also realize and concomitantly ask burst, improves request of data Efficiency, and learn that the capacity of resource also allows for distributing memory space, calculate the quantity of burst.

By being redesigned to burst option, 4 bits can be at least sent less in each request or response, divided In the case that piece is more, efficiency of transmission can be greatly enhanced, transfer resource is saved, while also improving the processing effect of both sides Rate.

In the prior art, after receiving and coming from the request of client, server can beam back response immediately, can also Ack (Acknowledgement) response message is first beamed back, shows to have received request message, present, follow-up etc. After having handled, response message is retransmited, that is, the response postponed.In addition, client can subscribe to the change of a resource, server After subscription of the client to some resource is received, once resource information changes, just notification message is beamed back to client.

Prior art can not meet following demand：

1st, client indicates server in the request, oneself needs the response of which kind of mode；

2nd, client requirements server beams back response within some defined time；

3rd, in the transmit process of notification message, because network capacity is unstable, it is logical that possible server is first sent Know message, than the message sent after server, the time for reaching client will evening.So, the resource information received after client Actually outmoded information, client, which needs a kind of mechanism, can detect the order of multiple notification messages.

Figure 11 is the flow chart of an embodiment of the present invention.In the embodiment shown in fig. 11, in S1110, client is to clothes Business device sends request message, and the request message carries response mode option, and the response mode option can be delaying response (Deferred Response) option either token (Token) option, is used to refer to server, whether client, which receives, pushes away Slow response.For example, the response mode option is represented：The disposable response disposably make an immediate response, postponed, postpone Multiple responses and the multiple responses for cancelling postponement.If response mode option is not carried, disposable response is defaulted as, server can To determine the being disposable response using disposably making an immediate response or postponing.Then, in S1120, client can be received The response message generated according to response mode option that server is sent.

In the prior art, after receiving and coming from the request of client, server can beam back response immediately, can also An Ack is first beamed back, shows to have received request message, present subsequently waits after having handled, retransmits response message, The response postponed.In addition, client can subscribe to the change of a resource, server is receiving client to some resource After subscription, once resource information changes, just notification message is beamed back to client.

In an embodiment of the present invention, it can for example be indicated using delay (Deferred) option of a byte Response mode, wherein it is possible to be represented using the first two bit (Bit), is represented with C：

C=00:Expression disposably makes an immediate response；

C=01:Represent the disposable response postponed；

C=10：The multiple responses postponed are represented, that is, are subscribed to；

C=11：Represent to cancel the multiple responses postponed, that is, unsubscribe.

The subscription on some resource initiated for client, can be unsubscribed by client, can also server Unsubscribe, such as server sends back to the response message that client one needs to confirm, client is within the predetermined time not It can confirm that, then server can consider that client loses connection, so as to unsubscribe.

Because a byte is 8 bits, unnecessary rear 6 bits (assuming that its value is T), which can be used to indicate that, to be pushed away The retardation time of slow disposable response or the deadline of multiple responses of postponement, i.e., more than this time after, take automatically Disappear subscription.When C is 01, T represents the retardation time for the disposable response postponed；When C is 10, T represents the multiple sound postponed The deadline answered；When T is 00 or 11, T is nonsensical, is set to 0.

For this 6 bits, the numerical value between 0~63 can be represented, it is assumed that be T, can with 2 T powers, to show This time span, in seconds, you can to represent 1~2^63 seconds.Such as：

0:2^0=1 seconds；

1:2^1=2 seconds；

2:2^2=4 seconds；

3:2^3=8 seconds

4:2^4=16 seconds；

…

63:2^63 seconds.

In the prior art, Max_Age fields are used for the maximum time for showing that some response can be buffered, that is, show to ring The freshness answered.The present invention extends the implication of this field, between can representing multiple responses with Max_Age fields in the request Time interval limitation, such as multiple notification messages must not be higher than this time interval, or must not be less than this time interval.

For the order of multiple responses, it can be distinguished with message identifier (Message ID).Such as, message identifier is provided Must incrementally it be generated according to the order of logical response, recipient judges that the priority of response is suitable according to the size of message identifier Sequence.

According to another embodiment of the present invention, Token (token) options can be used to indicate response mode, if Token values are 0, to represent response immediately, if Token values are not 0, then it represents that can receive the response postponed.

According to another embodiment of the present invention, it can alternatively or additionally increase timestamp (Timestamp) option, with Delay option individually or in combination indicates response mode.Specifically, client can carry timestamp in the request Option, the timestamp option includes the value of a deadline, it is desirable to which server returns to response within the specified time；Service Device in the response message, carries timestamp option, shows the time of response message generation, so, client can be based on the time Option is stabbed to judge the order of response message.

In an embodiment of the present invention, the design of the timestamp option can be represented with 1~6 byte, If the time represented is short, with a byte, if the time is long, with 3 bytes or 6 bytes.Specific method for expressing example It is such as following two：

(1) represented with year, month, day, hour, min, second, first character section represents year, second byte representation month, the 3rd Byte representation day, the 4th byte representation hour, the 5th byte representation minute, the 6th byte representation second, for time, example Such as can based on 2000, its value show 2000 after which in year, such as 0 when, be shown to be 2000, when being 1, It is shown to be 2001, can at most represents 2063.

(2) three bytes all represent that maximum can represent 2^24-1 seconds, about 136 years with the second.

Thus, client is known that the order of the response message of return, it is to avoid mistake caused by data transfer delay.

Corresponding with the embodiment shown in Figure 11, Figure 12 is the flow of the method for the embodiment of the present invention from the point of view of server side Figure.The method of the embodiment of the present invention includes：

S1210：Receive the request message for the carrying response mode option that client is sent；

S1220：The response message generated according to the response mode option is sent to client.

The scheme of the embodiment of the present invention is expanded on further with reference to specific embodiment.

Embodiment 1：

In the request message sent in step S1110, the response mode option is the disposable sound postponed Should or disposably it make an immediate response, and the request message also carries type of message configured information and time delay option. Here type of message configured information indicates that the request message is Measurement Request, and time delay option is multiple for indicating Server is within the time indicated by the time delay option, and arbitrarily one time of selection sends response message to client, To avoid multiple servers from responding to client while beaming back, network congestion is caused, and client also has little time processing.Example Such as, within the time indicated by the time delay option, multiple servers are each sent out after random delay, then to client Send response message.

For example, some building keeper sends multiple electric controllers to whole building using console (multicast gateway) (server) sends the instruction (Measurement Request) turned on light, it is desirable to which each electric controller beamed back response to be shown to be in 5 seconds It is no to have turned on light, then after each electric controller is in 5 seconds respectively through random delay, response is beamed back to console, is shown Whether turn on light.

In order to notify request message described in server to be Measurement Request, type of message configured information described here for example may be used To be default to be used to send the socket port of Measurement Request；Or the default network association for being used to send the Measurement Request Discuss IP address；Or the default port numbers for being used to send Measurement Request；Or the type of message in the request message is indicated Option.For example,

1) server opens specific socket (Socket) port, and is set to procotol (Internet Protocol, abbreviation IP) multicast reception, then client by the specific Socket ports to server send it is described request disappear Breath, to represent the request message as Measurement Request；

2) client carries default IP address, such as FF00 in the request message::/ 8 IPv6 prefix, clothes Business device is received after request message, and inspection receives the IP address of bag, if the IP address is default IP address, then it represents that should be asked It is Measurement Request to seek message, is otherwise unitcast request；

3) client by it is default be used to sending the port numbers of Measurement Request send the request message, for example： coap:// it is used for unitcast request, coapm:// being used for Measurement Request, then server can be according to the port of the request message of reception Number determine that the request message is unitcast request or Measurement Request.

4) client in request message with type of message indicate Option Field come show this request be unitcast request or Measurement Request, server judges according to this field.

According to embodiments of the present invention, said process is also applied for the scene that the request message is unitcast request.

The behavior of server is different under unicast and multicast scene, and the main distinction is, for unitcast request, time-out Afterwards, server, which is abandoned beaming back, responds to client；For Measurement Request, after time-out, server still can be beamed back and respond to client End, although response timeout, but because not every server is all overtime, so not resulting in congestion problems.

According to embodiments of the present invention, the request message also includes deadline option, to indicate server in the cut-off Response message is returned in time indicated by time option.Thus, client can be when the deadline option be indicated Between before time-out, the response message that the reception server is sent.

Embodiment 2：

In the request message sent in step S1110, response mode option is the multiple responses postponed, that is, represents client Subscribe to the data of (Observe) server in end.In this case, server sends push-notification-answer message to client.According to The embodiment of the present invention, push-notification-answer message carries most long survival time (Max-Age) option and stays the time time (Patience) to select , wherein Max-Age options are used for the most long effective time for showing the value of resource；The Patience options are used to indicate to service Device will respond after Max-Age is expired within the time indicated by the Patience options.Do not have in the value of resource In the case of change, server can use this Patience option, to postpone the transmission of response message.In this case, it is objective Family end can be judged with this, after Max-Age is expired, server will expire in the Patience times as far as possible before, sent and notified Respond to client.Therefore, client can continue to keep the subscribing relationship with the server, protect after Max-Age is expired Hold time of the time indicated by the Patience options.Client can so be avoided after Max-Age is expired, again Request message is sent to server.

Embodiment 3：

In the request message sent in step S1110, the response mode option is the multiple responses postponed, table Show the data of client subscription (Observe) server.In this case, the request that user end to server is sent disappears Breath includes retention time (Keep Alive) option.Client can according to circumstances set the value of Keep Alive options, Such as it could be arranged in this example 1000 seconds.Server is received after the request message, is replied and is confirmed to client (Acknowledgement, abbreviation ACK) message, wherein the newest value of current subscription resource is carried, while obtaining Keep Alive options, and a timer is opened at this moment, its value is the value that Keep Alive are set.

Within the time indicated described in Keep Alive options, if the resource of client subscription becomes on the server Change, then server sends third notice response to client, i.e., the third notice response that client the reception server is sent, the institute Third notice response is stated to confirm type message.

After the time indicated by Keep-Alive is overtime, server sends the 4th push-notification-answer to client, i.e., objective The 4th push-notification-answer that family end the reception server is sent, wherein the 4th push-notification-answer is to need confirmation type message.Then take Device wait client of being engaged in returns to ACK message.After server receives the ACK message from client, then illustrate that client is run Normally.Then process above can be repeated, server reopens timer, by the way that type message need not be confirmed to client Send response message.

If server does not receive the ACK message of client within a certain period of time, server will resend above-mentioned 4th push-notification-answer.If sending times reach default frequency threshold value, server is again without the return for receiving client ACK message, then server stop retransmit, while also stopping the subscribing relationship of same client.

Figure 13 is the interacting message figure of the implementation process of embodiment 3.Each message in Figure 13 is as follows：

ES1310：User end to server, which is sent, subscribes to request, wherein carrying Keep Alive options；

ES1320:Server replys ACK message to client, wherein carrying the newest value of current subscription resource, opens Timer；

ES1330：When the resource subscribed on server changes, the server sends push-notification-answer to client, should Push-notification-answer is that need not confirm type message；

ES1340：After when the timer times out, server, which is used, needs confirmation type message to send push-notification-answer, and waits client Hold the ACK message returned；

ES1350：Client-server returns to an ACK message；

ES1360：Server receives the ACK message from client, reopens timer；

ES1370：When the resource subscribed on server changes, the server sends push-notification-answer to client, should Push-notification-answer is that need not confirm type message；

ES1380：After when the timer times out, server, which is used, needs confirmation type message to send push-notification-answer, and waits client Hold the ACK message returned；

ES1390：Server does not receive the ACK message of client within a certain period of time, and server will resend above-mentioned Push-notification-answer, when sending times reach maximum, server stops weight again without the ACK message for receiving client, then server Hair, while also stopping the subscribing relationship of same client.

ES1310 to ES1390 code is, for example,：

According to embodiments of the present invention, Keep Alive options can be defined as optional option, if that is, CoAP servers are not The option is supported, the option can be ignored, by the request received without option processing.

According to embodiments of the present invention, the value of the Keep Alive options is integer type, and size can be elongated.Root According to specific needs, its size can be 4bit (bit), or 8 bit, or 12bit, and even more greatly, the embodiment of the present invention is not Limit its specific span.

Embodiment 4：

In actual applications, when server causes high load capacity because of the reason such as congestion, according to the configuration of server apparatus Strategy, in order to prevent the operations such as follow-up signaling processing from causing server apparatus thoroughly to be paralysed, server apparatus is on this time point Congestion control is opened, i.e., within ensuing certain time, any new request message received is not reprocessed.

Consider application of the embodiment of the present invention in this scene.For example, in step S1110, user end to server Request message is sent, wherein the response mode option is the disposable response postponed or disposably made an immediate response, and institute Stating request message also includes type of message configured information and deadline option, wherein the type of message configured information indicates institute Request message is stated for unitcast request, the request message is to need confirmation type message.If it will be understood by those skilled in the art that What server was received is that need not confirm type request message, then directly ignores message, any response is not replied.If now taken Business device occurs congestion and opens congestion control, then in step S1120, and server sends specific ACK to the client and disappeared Breath, wherein the specific confirmation message carries response code and delay turn-on time option, wherein the response code is for example For 5.03 " service unavailable " (service is unavailable) response codes, for representing server in the deadline The response for the request message can not be returned in time indicated by option.Or server can be first to the client ACK message is sent, then response message is sent to the client, wherein the response message carries response code and delay connects Angle of incidence option, wherein the response code represents that the server can not within the time indicated by the deadline option Return to the response for the request message.

The value of delay turn-on time option represents the specific time of delay access, and unit is, for example, the second, and maximum is for example For 2^NSecond, more than the maximum value such as being serviced device according to default value 2^MSecond is handled.When if this option value is zero or When this option is not appeared in response message, then client need not perform operation bidirectional, can attempt at any time to service Device sends request again.According to embodiments of the present invention, delay turn-on time option is optional type, i.e., can not be by CoAP clients Can directly it be ignored during identification.

Figure 14 is the interacting message figure of embodiment 4.As illustrated,

E1400：Server opens congestion control；

E1402：Client is sent to the server needs confirmation type request message；

E1404：Server sends ACK message to client, and the ACK message includes delay access option (new), response generation The load of code and sky

E1404：Client removes other request messages that the wait of caching is sent to the server immediately.

E1406：Within the time indicated by delay turn-on time option, request message is sent to server；

E1408：Server ignores the request message；

E1410：Etc. the time indicated by turn-on time option to be delayed；

E1412：Server load recovers normal；

E1414：User end to server resends the request message；

E1416：Server returns to normal ACK message.

Because the version of CoAP agreements is different, the CoAP clients actually come into operation may not upgrade in time, so that In delay access option described in None- identified.Therefore even in E1404, the ACK with delay turn-on time option is sent to Client, due to the older None- identified delay turn-on time option of client release, the client device will ignore the option (it could also be possible that other abnormal conditions cause), and may again attempt to send in E1406 and ask in ensuing random time Message is sought to the server apparatus for having met with congestion.Server apparatus can ignore the request message according to the strategy of configuration, Or sending the response message with new delay turn-on time option again, value of the new delay turn-on time option can be with Less than the value of the delay turn-on time option previously sent.

It should be noted that, all employ the sound of Piggy-backed (subsidiary formula) in the present embodiment for convenience of explanation Message is answered, i.e., each option, which is entrained in ACK message, directly to be transmitted.According to embodiments of the present invention, the sound of separate type can also be used Should, i.e. confirmation message and response message is sent in two times, and delay access option always belongs to a part for response message.

Embodiment 5：

Similar with server side generation congestion, client may also be because certain reason occurs congestion and cause high load capacity. When client causes high load capacity due to reasons such as congestions, according to the configuration strategy of client, in order to prevent at follow-up signaling The operation such as reason causes client thoroughly to be paralysed, and client opens congestion control on this time point, i.e., in ensuing one timing In, any new request message received is not reprocessed.

Consider application of the embodiment of the present invention in this scene.For example, in step S1110, user end to server The request message is sent, wherein multiple responses of the response mode option for postponement, i.e., on client subscription server Resource information.Then, in step S1120, client receives the response message of server transmission, such as in ordered resource In the case of there occurs change on the server, server is sent to client needs confirmation type response message, wherein carrying most New resource information.If now client opens congestion control, specific ACK message can be sent to server, it is described Specific confirmation message carries response code and delay turn-on time option, wherein the response code represents that the client exists The confirmation for the response message can not be returned in time indicated by the delay turn-on time option.Or client can ACK message is sent to the server with elder generation, then specific response message is sent to the client, wherein described specific Response message carries response code and delay turn-on time option, wherein the response code represents that the client is prolonged described Can not be returned in time indicated by slow turn-on time option needs the confirmation of confirmation type response message for described.In client In the case of opening congestion control, if what client received in step S1120 is that need not confirm type response message, Client directly ignores the message, and any confirmation message is not replied.

As described above, the value of delay turn-on time option represents the specific time of delay access, unit is, for example, the second, most Big value is, for example, 2^NSecond, more than the maximum value for example by client according to default value 2^MSecond is handled.If this option value is When zero or when this option is not appeared in response message, then server need not perform operation bidirectional, can taste at any time Trying to send again to client needs to confirm shape response message.According to embodiments of the present invention, delay turn-on time option is optional Type, i.e., can directly be ignored when can not be recognized by CoAP servers.

Server is received after above-mentioned specific ACK message, if it is possible to recognize the delay turn-on time option in message, then All subscription between the client of pause are pushed, and are started waiting for, that is, wait the client to recover normal.

After the time indicated by delay turn-on time option passes through, client recovers normal, the wait meter of server When also terminated, therefore server to client device retransmit need confirm response message, the normal client of load restoration A normal confirmation message can now be replied.

Figure 15 is the interacting message figure in embodiment 5.As shown in figure 16,

ES1500：User end to server, which is sent, subscribes to request；

ES1502：Server sends the response message for needing to confirm to client；

ES1504：User end to server sends ACK message；

ES1506：Client opens congestion control；

ES1508：Server sends the response message for needing to confirm to client；

ES1510：User end to server sends carrying respective code and the specific ACK of delay turn-on time option disappears Breath；

ES1512：Server suspends the resource subscribed to server push；

ES1514：Time indicated by the turn-on time option to be delayed such as server；

ES1516：Client load restoration is normal；

ES1518：Server resends the response message for needing to confirm to client；

ES1520：User end to server sends ACK message.

What deserves to be explained is, under normal circumstances, client device receives the request confirmed the need for server apparatus is pushed After message, what is all replied is ACK confirmation messages, only can just be used when client needs and notifies delay access to server Piggybacked mode carries specific response contents or separately transmission ACK and response.

Embodiment 6：

Present embodiment describes the flow that server and client side interacts：

1st, user end to server sends request, wherein carry time out option, and indicate this request be unitcast request or Measurement Request, is resource subscription request or disposable request；

2nd, server is judged according to the request received, if the request is disposable request, server continues Judgement is unitcast request or Measurement Request：

If A. the request is that unicast is disposably asked, server prejudges whether oneself can specify in time out option Time in complete client request, if prediction can not complete, beam back a conditional code (such as 5.04, Timeout, Time-out) client is given, show that the request of client can not be completed in the given time；Alternatively, server prediction itself is idle Time, or itself can complete the time of the request of client, and this predicted time is sent back to client in the response End, indicates that client after specified predicted time, sends request again；If server can be in specified time-out time It is interior to complete request, then before time-out time is expired, beam back response.

If B. the request is that multicast is disposably asked, server arbitrarily selects a time within the specified time, returns Return and respond to client.

If the 3, server judges that the request of client is to subscribe to request, server continues to judge that what is carried in the request surpasses When the time be Patience options, or Keep-alive options：

If what is carried in A. asking is Patience options, show that server needs within a specified time to beam back first Individual notification message；Server carries the information of resource in an announcement message, and Max-Age options and Patience times are selected , it is desirable to client within a specified time keeps the subscription status with server resource.

If what is carried in B. asking is Keep-alive time options, server is used within the Keep-alive times The mode of Non-confirmable message, sends a notification message to client；After the Keep-alive times are expired, use The mode of Confirmable message, sends a notification message to client.

Figure 16 is a kind of block diagram of the embodiment of the client device of transmission data resource according to the present invention, wherein described Client device 1600 includes：Sending module 1610, the request message of response mode option is carried for sending；And receiving module 1620, for receiving the response message generated according to the response mode option.

Process described by embodiments of the invention and feature described in reference picture 11 are applied to the client shown in Figure 16 End equipment.Specifically, for example, the response mode option carried in the request message that sending module 1610 is sent can be postponed Option, for example can be：The disposable response disposably make an immediate response, postponed, the multiple responses and cancellation postponement postponed Multiple responses.

According to a kind of embodiment, the response mode option carried in the request message that sending module 1610 is sent can be represented The retardation time for the disposable response postponed or the deadline of multiple responses of postponement.

According to a kind of embodiment, sending module 1610 sends the request message for carrying timestamp option, and the timestamp is represented Receive the deadline of response；Receiving module 1620 receives the response message for carrying timestamp option, and the timestamp represents response The generation time of message.Time represented by timestamp of the receiving module 1620 in the response message received determines response The order of message.

According to embodiments of the present invention, in the request message, the response mode option is the disposable sound postponed Should or disposably it make an immediate response,

The request message also carries type of message configured information and time delay option, wherein the type of message is indicated Information indicates that the request message is Measurement Request or unitcast request；

The receiving module 1620 was used within the time of time delay option instruction, the sound that the reception server is sent Answer message.

According to embodiments of the present invention, the request message also includes deadline option,

The receiving module 1620 is used for before the time time-out that the deadline option is indicated, the reception server hair The response message sent.

According to embodiments of the present invention, in the request message, the response mode option is the multiple responses postponed,

The receiving module 1620 is used to receive the push-notification-answer message that the server is sent, wherein the push-notification-answer Message carries most long survival time option and stays time time option, wherein described stay time time option to be used to indicate,

After time time-out indicated by the most long survival time option, the client is kept and the server Subscribing relationship, the retention time is the time stayed indicated by candidate item.

According to embodiments of the present invention, in the request message, the response mode option is the multiple responses postponed, institute Stating request message also includes retention time option, and the receiving module 1620 is used for the time indicated in the retention time option It is interior, the first push-notification-answer that the reception server is sent, wherein first push-notification-answer is that need not confirm type message；Described After the time time-out that retention time option is indicated, the receiving module 1620 leads to for receiving the server is sent second Know response, wherein second push-notification-answer is needs confirmation type message, the sending module 1610 is used for the server Send and confirm ACK message.

According to embodiments of the present invention, in the request message, the response mode option is the disposable sound postponed Should or disposably it make an immediate response, the request message also includes type of message configured information and deadline option, wherein institute State type of message configured information and indicate that the request message is unitcast request, the request message is to need confirmation type message；

The receiving module 1620 is used to receive the specific confirmation message that the server is sent, wherein described specific Confirmation message carries response code and delay turn-on time option, wherein the response code represents the server at described section Only the response for the request message can not be returned in the time indicated by time option；

Or

The receiving module 1620 is used to receive the confirmation message that the server is sent；

And for receiving the specific response message that the server is sent, wherein the specific response message is carried and rung Code and delay turn-on time option are answered, wherein the response code represents that the server is signified in the deadline option The response for the request message can not be returned in the time shown.

According to embodiments of the present invention, the receiving module 1620 be additionally operable to remove caching wait sent to the server Other request messages.

According to embodiments of the present invention, after the time indicated by the delay turn-on time option, the sending module 1610 are additionally operable to send the request message to the server again.

According to embodiments of the present invention, in the request message, the response mode option is the multiple responses postponed, institute The response message generated according to the response mode option for stating the reception server transmission is to need confirmation type message,

The sending module 1610 is additionally operable to send specific confirmation message to the server, wherein described specific true Recognize message and carry response code and delay turn-on time option, wherein the response code represents client in the delay access The confirmation for the response message can not be returned in time indicated by time option；

Or

The sending module 1610 is used to send confirmation message to the server；

And for sending specific response message to the server, wherein the specific response message carries response generation Code and delay turn-on time option, wherein the response code represents that the client is signified in the delay turn-on time option The confirmation for the response message can not be returned in the time shown.

According to embodiments of the present invention, the response message includes the response message generation time, and the receiving module 1220 is also Order for determining response message according to the response message generation time.

Figure 17 is a kind of embodiment of the server apparatus of transmission data resource according to the present invention, wherein the server Equipment 1700 includes：Receiving module 1710, the request message of the carrying response mode option for receiving client transmission；And hair Module 1720 is sent, the response message generated according to the response mode option is sent to client.

Process described by embodiments of the invention and feature described in reference picture 12 are applied to the service shown in Figure 17 Device equipment.Specifically, for example, the response mode option carried in the request message that receiving module 1710 is received can be postponed Option, for example can be：The disposable response disposably make an immediate response, postponed, the multiple responses and cancellation postponement postponed Multiple responses.

According to embodiments of the present invention, in the request message, the response mode option is the disposable sound postponed Should or disposably it make an immediate response, the request message also includes type of message configured information and time delay option, wherein institute State type of message configured information and indicate that the request message is Measurement Request or unitcast request；The sending module 1720 is used for In the time that the time delay option is indicated, after random delay, response message is sent to the client.

According to embodiments of the present invention, the request message also includes deadline option, and the sending module 1720 is used for Before the time time-out that the deadline option is indicated, response message is sent to the client.

The sending module 1720 is used to send push-notification-answer to the client, wherein the push-notification-answer carries most long Survival time option and time time option is stayed, wherein described stay time time option to be used to indicate,

After the time time-out indicated by the most long survival time option, the server will stay the time time described Responded in time indicated by option.

According to embodiments of the present invention, in the request message, the response mode option is the multiple responses postponed, institute Stating request message also includes retention time option, and the sending module 1720 is used for the time indicated in the retention time option It is interior, third notice response is sent to the client, wherein third notice response is that need not confirm type message；The hair Module 1720 is sent to be additionally operable to after the time time-out that the retention time option is indicated, sending the 4th to the client notifies Response, wherein the 4th push-notification-answer is to need confirmation type message；The receiving module 1710 is used to receive the client The ACK message of transmission.

The sending module 1720 is used to send specific confirmation message to client, wherein the specific confirmation message Response code and delay turn-on time option are carried, wherein the response code represents that the server is selected in the deadline The response for the request message can not be returned in time indicated by；

Or

The sending module 1720 is used to send confirmation message to client；

And for sending specific response message to client, wherein the specific response message carry response code and Postpone turn-on time option, wherein the response code represents the server in the time indicated by the deadline option It is interior to return to the response for the request message.

According to embodiments of the present invention, after the time indicated by the delay turn-on time option, the receiving module 1710 are used to receive the request message that the client is resend.

According to embodiments of the present invention, in the request message, the response mode option is the multiple responses postponed, institute It is to need confirmation type message to state the response message generated according to the response mode option sent to client, the reception mould Block 1710 is used to receive the specific confirmation message that the client is sent, wherein the specific confirmation message carries response generation Code and delay turn-on time option, wherein the response code represents that the client is signified in the delay turn-on time option The confirmation for the response message can not be returned in the time shown；

Or

The receiving module 1710 is used to receive the confirmation message that the client is sent；

And specific response message is sent for receiving the client, wherein the specific response message carries response Code and delay turn-on time option, wherein the response code represents the client in the delay turn-on time option institute The confirmation for the response message can not be returned in the time of instruction.

According to embodiments of the present invention, after the time time-out indicated by the delay turn-on time option, the transmission mould Block 1720, which is used to resend to the client, described needs confirmation type response message.

According to another embodiment of the present invention, timestamp choosing can be carried in the request message that receiving module 1710 is received , the timestamp option represents to receive the deadline of response, and can also be taken in the response message that sending module 1320 is sent Band timestamp option, the timestamp option represents the generation time of response message.

Those of ordinary skill in the art are it is to be appreciated that the list of each example described with reference to the embodiments described herein Member and algorithm steps, can be realized with electronic hardware, computer software or the combination of the two, in order to clearly demonstrate hardware With the interchangeability of software, the composition and step of each example are generally described according to function in the above description.This A little functions are performed with hardware or software mode actually, depending on the application-specific and design constraint of technical scheme.Specially Industry technical staff can realize described function to each specific application using distinct methods, but this realization is not It is considered as beyond the scope of this invention.

The method that is described with reference to the embodiments described herein can use hardware, computing device the step of algorithm Software module, or the two combination are implemented.Software module can be placed in random access memory (RAM), internal memory, read-only storage (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field In any other form of storage medium well known to interior.

Although having shown that and describing some embodiments of the present invention, it is understood by one skilled in the art that not departing from In the case of the principle and spirit of the present invention, various modifications can be carried out to these embodiments, such modification should fall into the present invention In the range of.

Claims

1. a kind of resource transmission method, it is characterised in that applied in the M2M systems based on CoAP agreements, including：

User end to server, which is sent, carries deadline option in request message, the request message, to indicate server Response message is sent within the time that the deadline option is indicated；

Client is before the time time-out that the deadline option is indicated, the response message that the reception server is sent.

2. the method as described in claim 1, it is characterised in that if the time that client is not indicated in the deadline option The response of server is inside received, then client abandons the request.

3. the method as described in claim 1-2, it is characterised in that response mode option is also carried in the request, to refer to Show the request for the response mode response client that server is indicated according to the response mode option.

4. method as claimed in claim 3, it is characterised in that the response mode includes one kind in following manner：

Disposably make an immediate response, or the disposable response postponed, or the multiple responses postponed, or cancel the multiple sound postponed Should.

5. the method as described in claim any one of 1-4, it is characterised in that

In the request message, the response mode option is the disposable response postponed or disposably made an immediate response,

The request message also carries type of message configured information and time delay option, wherein the type of message configured information It is Measurement Request or unitcast request to indicate the request message；

The response message generated according to the response mode option is received, including：

Within the time that the time delay option is indicated, the response message that the reception server is sent.

6. method as claimed in claim 5, it is characterised in that

The type of message configured information is following one of which：

The default socket port for being used to send Measurement Request；

The default network protocol IP address for being used to send Measurement Request；

The default port numbers for being used to send Measurement Request；

Type of message in the request message indicates option.

7. method as claimed in claim 4, it is characterised in that

In the request message, the response mode option is the multiple responses postponed,

The response message generated according to the response mode option that the reception server is sent, including：

The push-notification-answer message that the server is sent is received, wherein the push-notification-answer message carries most long survival time option With stay time time option, wherein it is described stay time time option be used for indicate, in the time indicated by the most long survival time option After time-out, client keeps the subscribing relationship with the server, and the retention time is the time stayed indicated by candidate item.

8. method as claimed in claim 4, it is characterised in that

The request message also includes retention time option,

Within the time that the retention time option is indicated, the first push-notification-answer that the reception server is sent, wherein described first Push-notification-answer is that need not confirm type message；

After the time time-out that the retention time option is indicated, the second push-notification-answer that the server is sent is received, its Described in the second push-notification-answer to need confirmation type message.

Sent to the server and confirm ACK message.

9. method as claimed in claim 4, it is characterised in that

The request message also includes type of message configured information and deadline option, wherein the type of message configured information It is unitcast request to indicate the request message, and the request message is to need confirmation type message；

The specific confirmation message that the server is sent is received, wherein the specific confirmation message carries response code and prolonged Slow turn-on time option, wherein the response code represents the server within the time indicated by the deadline option The response for the request message can not be returned；

Or

Receive the confirmation message that the server is sent；

The specific response message that the server is sent is received, wherein the specific response message carries response code and prolonged Slow turn-on time option, wherein the response code represents the server within the time indicated by the deadline option The response for the request message can not be returned.

10. method as claimed in claim 9, it is characterised in that

Remove other request messages that the wait of caching is sent to the server.

11. method as claimed in claim 9, it is characterised in that

After the time indicated by the delay turn-on time option, the request message is sent to the server again.

12. method as claimed in claim 4, it is characterised in that

The response message generated according to the response mode option that the reception server is sent is to need confirmation type message,

Methods described further comprises：

Specific confirmation message is sent to the server, wherein the specific confirmation message carries response code and delay connects Angle of incidence option, wherein the response code represents that client can not within the time indicated by the delay turn-on time option Return to the confirmation for the response message；

Or

Confirmation message is sent to the server；

Specific response message is sent to the server, wherein the specific response message carries response code and delay connects Angle of incidence option, wherein the response code represents the client within the time indicated by the delay turn-on time option The confirmation for the response message can not be returned.

13. the method as described in claim 1, it is characterised in that

The response message includes response message and generates the time.

14. a kind of client terminal device, including processor and memory, wherein, memory storage programmed instruction, when described program refers to When order is run by the processor, the method as described in claim any one of 1-13 is performed.