CN102685204B - Method and equipment for transmitting data resource - Google Patents
Method and equipment for transmitting data resource Download PDFInfo
- Publication number
- CN102685204B CN102685204B CN201210056456.0A CN201210056456A CN102685204B CN 102685204 B CN102685204 B CN 102685204B CN 201210056456 A CN201210056456 A CN 201210056456A CN 102685204 B CN102685204 B CN 102685204B
- Authority
- CN
- China
- Prior art keywords
- response
- message
- option
- time
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
- H04L67/1078—Resource delivery mechanisms
- H04L67/108—Resource delivery mechanisms characterised by resources being split in blocks or fragments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
- H04W28/0236—Traffic management, e.g. flow control or congestion control based on communication conditions radio quality, e.g. interference, losses or delay
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
- H04L67/1078—Resource delivery mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
- H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
- H04L67/5651—Reducing the amount or size of exchanged application data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/10—Flow control between communication endpoints
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
- H04W80/12—Application layer protocols, e.g. WAP [Wireless Application Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention relates to a method for transmitting a data resource and equipment for transmitting the data resource. The method for transmitting the data resource in an internet of things system based on a node of a lightweight application layer protocol comprises the steps of: sending a request message with a response mode option to a server, wherein the response mode option shows one of the following response modes: once immediate response, delayed once response, delayed multi-response, and cancelling of delayed multi-response; and receiving the response message transmitted by the server and produced according to the response mode option. According to the method and the equipment for transmitting data resource, the response mode option can be specified in the message interaction process; the client can specify the response as required, thereby improving the message interaction efficiency of CoAP.
Description
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 used
In the scene of Internet of Things (Machine to Machine, referred to as " M2M "), 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 little, does not support the host-host protocol of complexity, and message transmission rate is relatively low.CoAP provides a kind of friendship of request/response
Mutually 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 in.Based on CoAP transmission datas
Traditional scheme in disregard calculate data resource accurate capacity, it is impossible to assess the exact number of subpackage, therefore cannot concurrently obtain
Data resource, causes efficiency of transmission low.
Relatively low additionally, due to many equipment disposal abilities using CoAP, peak transfer rate is also low, so many activating
Individual connection or while when processing multiple requests, CoAP equipment is just easy to face congestion problems, after leading to not process in time
Continue de novo task.In order to solve congestion, a kind of message retransmission control mechanism is defined in existing CoAP agreements, when CoAP it is objective
When (Confirmable) message and long-time that family end equipment confirms to the needs that server apparatus send does not meet with a response
(the problems such as congestion causes), client device can retransmit the message and repeated several times after the Tn seconds, set until receiving server
Response message or reach maximum number of retransmissions restriction and abandon attempting that preparation is returned;If acquiescence retransmission interval is x seconds and current
Retransmit for n-th, then Tn=x+random (0~2n), wherein random (0~2n) it is 0 to 2nBetween arbitrary random integers,
Therefore the method is also referred to as exponential back-off algorithm, and the time interval retransmitted every time gives server apparatus with exponential increase
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 increased when serious.
The content of the invention
Embodiments provide a kind of method and apparatus of transmitting data resources, it would be preferable to support improve in CoAP and pass
Defeated efficiency.
In embodiments of the present invention, there is provided a kind of node that lightweight application layer protocol is based in Internet of things system
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 sends
In embodiments of the present invention, there is provided a kind of node that lightweight application layer protocol is based in Internet of things system
Transmitting data resources method, including:The request message of the carrying response mode option that client sends 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
Multiple responses that individual response and cancellation are postponed;The response message generated according to the response mode option is sent to client.
In embodiments of the present invention, there is provided one kind is based on lightweight application layer protocol transmission node in Internet of things system
Data resource client, including:Sending module, for sending the request message for carrying response mode option to server,
Wherein described response mode option represents following response mode one of which:Disposably make an immediate response, postpone it is disposable
Multiple responses that response, the multiple responses postponed and cancellation are postponed;Receiver module, generates for receiving according to response mode option
Response message.
In embodiments of the present invention, there is provided one kind is based on lightweight application layer protocol transmission node in Internet of things system
Data resource server apparatus, including:Receiver module, for receiving asking for the carrying response mode option that client sends
Message is sought, wherein the response mode option represents following response mode one of which:One for disposably making an immediate response, postponing
Multiple responses that the response of secondary property, the multiple responses postponed and cancellation are postponed;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 the interacting message efficiency of CoAP.
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 process, 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, can in advance terminate session after the time delay for indicating is expired;Asking
When the side of asking indicates to make an immediate response, if in the self-defining time-out time of requesting party, it is impossible to receive response message, it is also possible to carry
Front 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.
Description of the drawings
In order to be illustrated more clearly that the technical scheme of the embodiment of the present invention, below will be in embodiment or description of the prior art
The required accompanying drawing for using 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 be with 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 flow process for implementing process of the gateway of an embodiment of the present invention from 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 the flow process that a kind of gateway of alternate embodiment of the invention implements 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 stream for implementing process of the gateway of alternate embodiment of the invention from 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 the flow process for implementing process that the gateway of an embodiment of the present invention sends 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.
Specific 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 the embodiment of whole.Based on this
Embodiment in bright, the every other enforcement 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:The message (Confirmable) for confirming, the message (Non-confirmable) that need not be confirmed, confirmation is needed to disappear
Breath (Acknowledgement), replacement 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 to be recognizing.It is node or server, including but not limited to sensor, control that we are commonly referred to as the owning side of resource
Device, end points (End-point) etc., request resource side is client, including but not limited to gateway (Proxy), network equipment.
CoAP agreements support different options (Option), to explain CoAP message bodies in data semanteme, 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 for 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 cannot be simultaneously
Send out and obtain.Do not know that resource is static or dynamic in addition yet.
In the following description, commonly referred to as the owning side of resource is server, and, request resource side is with sensor as an example
Client, with gateway as an example.But, either gateway is not used as the restriction to server or client to sensor.
Precise volume due to not knowing target resource, gateway exists<Get>Used in order during Block Option, can only
In order obtaining, i.e. choosing obtains Block 0, when waiting Block 0 to return, then obtains Block 1, until last
Block.Can not concomitantly 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:Represented with a bit and whether also have behind current slice other bursts, its value is also have behind 1 expression
Burst, is without burst, as last burst behind 0 expression.
SZX:For characterizing burst capacity, its computing 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.
It is as follows for the operation instruction of Block options:
<Get>In request, the NUM fields of Block options provide the sequence number of the burst of current request, and when burst sequence
Number for 0 when, SZX be given 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 of current response.
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 agree to suggestion burst capacity, or select one than suggestion burst it is little
Burst, and return in the response, meanwhile, the data of first burst are returned in the response.
The present invention considers that gateway knows in advance the precise volume of target resource, then gateway can choose whether to use Block
Option is sending the request of resource acquisition, it is also possible to realize concurrent request, i.e., while Block 0 is asked, it is also possible to please
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 specifies, in addition to last burst, the capacity of burst must be identical, but still needs every time in transmission every time
Carry M positions (showing whether also have burst below) and SZX (capacity of burst).
Every time in request and response, M positions and SZX positions are required for transmission, and in fact, in addition to last burst, M
The value of position and SZX is every time identical, and the transmission for repeating wastes transfer resource.The purpose for repeating to send SZX assumes both sides all
The SZX after consulting is not preserved, that what is carried in the first secondary response is the SZX after consulting, gateway is obtained from response and asked again
Middle transmission is asked, so as to 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, and for M2M equipment, transfer resource is limited, this biography
The waste of defeated resource is very considerable.Assume that the data to be transmitted are load (payload) capacity of each Block if 64M
It is for the block entry numbers that 1024byte then sends:65536.The number that the Block options for then sending divide according to byte is:
(1) byte:16
(2) two bytes:4080
(3) three bytes:61440
If M and SZX can not send, 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 then need the data for sending with full all positions (bit)
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 saves percentage ratio
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 ratio 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, preferred version only to need
Want a byte;
256<T<When 4096:1- (256*1+ (T-256) * 2))/(16*1+ (T-16) * 2), simple design needs 2
Byte, preferred version 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, preferred version to need 2 bytes.
T>When 65256, without saving, preferred version embodiment of the present invention and simple design are required for 3 bytes.
In simple design, using during Put/Post orders, burst capabilities negotiation lacks efficiency.Please in Put/Post
In asking, for first burst, the data for sending first burst and the burst capacity recommended are needed, if sensor node choosing
Different burst capacity is selected, gateway needs to be resend according to the burst capacity of sensor, then the burst that last time sends
Data are wasted.And, gateway when the big resource of capacity is sent based on burst option using Put/Post requests, in advance
Sensor resource capacity information cannot be informed, in transmitting procedure, sensor side receives, and side caches received resource, if
Sensor finds insufficient memory, and resource can only send back the error status code of 413, table when not being transmitted
Show that the resource of request is too big, terminate this time to transmit.The part resource for transmitting before this is then useless, and transfer resource is wasted.Such as
Fruit gateway can inform the capacity information of the resource to be transmitted of sensor in first fragmental messages, and sensor then can compare
Compared with resource capacity information and memory capacity, if off-capacity, the conditional code of 413 " resource of request is too big " is returned in advance, come
Ending resource is transmitted, and the purpose for saving transfer resource is reached with this.
Breakpoint transmission on the Internet, that is, start to continue to download where having downloaded from file.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 from the beginning of 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
Start to pass from 2000070 bytes, byte above is without passing.
The shortcoming of this scheme is that do not have burst mechanism, does not support the negotiation of burst capacity, does not also support burst sum
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, can obtain the precise volume of target data resource, burst appearance is carried out
The negotiation of amount, obtains burst sum, and carries out transmitting data resources according to burst sum.
The flow process of an embodiment of the present invention is illustrated referring to Fig. 1.Fig. 1 is the flow process 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 the negotiation and really for carrying out burst capacity 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.After the request message that sensor sends in S120 is received, according to certainly
Body ability, determines the burst capacity used in this transmitting data resources process, and the burst capacity that sensor determines is little
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 dividing for determination
After piece capacity, according to grasp node data resource capacity information, it is determined that the data resource of the node that will be transmitted point
Piece sum.
Then, in S140, according to the burst capacity and the data resource capacity information of the node of the determination, burst
Transmit the data resource.
According to embodiments of the present invention, the capacity information of the data resource for needing transmission can be known, and by burst capacity
Consult to determine the burst capacity used during transmission data, it is possible thereby to lower error rate in transmitting procedure is realized, and can be simultaneously
Send out ground transmission data.
Process is implemented below in conjunction with Fig. 2 explanations embodiment as shown in Figure 1.What Fig. 2 was represented is gateway from sensor
Obtain the illustrated examples of 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 to sensor sends resource discovering request, i.e., biography is obtained by Get./wellknown/core
The Resources list on sensor.
ES220:Sensor to gateway returns the Resources list, and resource indication information;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 money
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 resource content to gateway;If resource capacity is returned more than the capacity of a transport level messages
Resource capacity information.Alternatively, sensor can use burst option, according to the burst capacity that itself determines, directly return first
Individual burst.The burst capacity that subsequent client and sensor root are determined therefrom that, using burst option following burst is transmitted.
In a kind of alternate embodiment of the invention, if target data resource is dynamic data resource, while returning 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:According to data resource capacity information, judgement needs to use burst option gateway, and sends carrying burst choosing
The request message of item, with sensor device burst capabilities negotiation is carried out, and indicates the burst capacity recommended.
ES260:Sensor determines burst capacity according to self-ability, and is returned to gateway.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 determines 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 of the data resource answered.
ES280:Sensor returns the burst sequence number and data corresponding with the burst sequence number according to the burst capacity for determining
The fragment data of resource, until complete end of transmission.
A kind of preferred embodiment of the invention, can realize that parallel processing, i.e. gateway can be asked simultaneously in ES270
Multiple fragmental messages are obtained, without waiting sensor to return the response message to previous fragment request message.
The code of ES210 to ES240 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, title
For 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 asked 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, can adopt
Following two scheme enforcements are processed:
(1) when starting to transmit data resource, snapshot (Snapshot) is set up to the resource, that is, caches the data money this moment
The capacity information in source, and this capacity information is transmitted, no matter 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, indicate that data resource is 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., to ID and Password compositions
Character string carries out Hash (Hash) using MD5 algorithms, and the value of Hash is Digest.Sender sends ID and Digest, recipient
According to the Password for receiving ID He prestore, Digest is drawn according to same algorithm, with sender's transmission
Digest is compared, if unanimously, certification passes through.
Gateway from sensors for data resource when, as shown in Fig. 2 needing 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, show whether 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 a period of time interior metastable resource, i.e. resource content will not be changed frequently.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, and for showing, resource is too big, needs to be asked with Block Option.
Such as, conditional code 413 is can specify that, it is excessive for showing current data resource capacity, indicate gateway in the request
Use Block options.Other conditional codes can as needed be specified, 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) option (Option) for showing capacity (Size) is increased in the head field (Header) of CoAP
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.
Or, even if gateway does not have an instruction of Size Option, 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 less, sensor directly returns 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 resource data, only with the capacity of Size Option returned datas, while
Gateway is indicated to conditional code, allows gateway to initiate new request, asked with Block Option.
The code of Size Option 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 Fig. 3 explanations embodiment as shown in Figure 1.What Fig. 3 was represented is gateway to sensor
Send the illustrated examples of 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
Burst capacity (i.e. SZX) with recommending, sensor can select the burst capacity for agreeing to recommend, or selecting one is 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 is to carry out point
The negotiation of piece capacity.Ambiguity of the agreement in process is so brought, and the information such as data capacity cannot be carried.
The embodiment of the present invention is improved this, and in an embodiment of the present invention, gateway exists<Get>Method please
Used in asking during 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 burst sum, using SZX field Returning sensors using NUM fields
It is determined that burst capacity.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
Using 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.
If it should be noted that when gateway sends first request, it is not known that the capacity of data resource, so Block
Option can use a byte, if the data resource of sensor is larger, burst number is larger, then sensor can ring
Two bytes or three bytes are total to return burst used in answering.
When Block Option are 2 bytes, it is designed to last three that SZX fields take 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 the corresponding response message of request that NUM is 0, 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
Just it is understood that this response message is for returning burst sum.
Burst capacity negotiation procedure illustrated below, message instance is:
Gateway sends the request of resource acquisition to sensor:
GET 00,000 101 (it is 101 that NUM is 0, SZX, i.e., 5,9 powers that burst capacity is 2 are represented, i.e., 512)
The response that sensor sends to gateway:
(NUM is ACK 10,000 100:10000, i.e., total burst number is 100 for 32, SZX, i.e., 4, represent that burst capacity is 2
8 powers, i.e., 256)
This design eliminates a bit (Bit), i.e., M positions 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 send every time.
In the prior art, burst capacity (i.e. SZX fields) will send every time, still ring either in request message
In answering 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 field mutually and waste transfer resource.
In embodiments of the present invention, gateway exists<Get>Used in the request of method during Block Option, if NUM quilts
0 is set to, represents that both sides only carry out the negotiation of burst capacity, and the negotiation of burst sum.I.e. sensor in the response, is used
NUM fields return 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, and do not send and have determined and keep not
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, do not retransmit burst capacity.In this case, when NUM is 1, the burst number of first burst of request is represented
According to, the like.
To adopt<GET>Order illustrates above-described embodiment from as a example by sensors for data resource,
As shown in figure 3, the design of new Block Option is as follows:
Wherein structure (1) is for situation that NUM is 0:
<Get>In request, it is second byte that NUM is 0, SZX, represents burst capacity, and Total Number are represented point
Piece sum, does not use, it is not necessary to carry in request;<Get>In response, NUM is that 0, SZX represents the burst that sensor determines
Capacity, Total Number represent burst sum.
In the prior art, the interval of burst capacity is than larger, such as and 2048,1024,512, underaction.And it is actual
On, 512 for a Block, smaller, in can just being preferably 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 is used for<Get>NUM situations not for 0 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 8 powers of the NUM more than 2
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 0, the previous byte of the NUM fields in 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 is also possible to distinguish.
Illustrated below, message instance is:
Gateway sends the request of resource acquisition to sensor:
GET 00,000,000 00000101 (it is 101 that NUM is 0, SZX, i.e., 5,9 powers that burst capacity is 2 are represented, i.e.,
512)
The response that sensor sends 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 redesigning to Block Option, 4 bits of transmission can be at least reduced in each request or in responding
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 to sensor sends<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) sends for gateway to sensor<GET>Request, SZX fields represent the burst capacity that gateway is recommended, and pass
Sensor final choice and determine burst capacity less than or equal to gateway recommend burst capacity, NUM be 0 represent gateway requests it is complete
Resource, NUM does not represent the concrete 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) return the burst response message of full resource for sensor to gateway, if being directed to certain
The response of individual concrete fragment data request, it is not necessary to carry burst option, the M field in structure (2) and (3) is indicated whether as most
Latter burst, if M field represents last burst for 0, be 1 expression be not last burst, NUM field lists
Which burst show that sensor returned is.
It is illustrated below.Message instance is:
Gateway to sensor sends the request that data resource is obtained:
CON GET 00,000,000 00000101 (it is 101 that NUM is 0, SZX, i.e., 5,9 powers that burst capacity is 2 are represented,
I.e. 512)
The response that sensor sends to gateway:
(it is 1 that NUM is 1, M to ACK 200 00000011, represents first burst for sending, and not last point
Piece, burst capacity is the capacity that SZX fields are specified);
Sensor continues to send CoAP responses to gateway:
(it is 1 that NUM is 2, M to CON 200 00000101, represents second burst for sending, and not last point
Piece, burst capacity is the capacity that SZX fields are specified);
Gateway returns the ACK to CON;
Sensor to gateway sends last burst:
CON 200 00000110 (it is 0 that NUM is 3, M, represents the 3rd burst for sending, and is last burst,
Concrete 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 kind of alternate embodiment of the present invention.In the embodiment shown in fig. 6, ES610 to ES640 and Fig. 2
The ES210 to ES240 of illustrated embodiment is identical, therefore description is not repeated.
Fig. 6 is that, in ES650, gateway to sensor sends 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, the burst capacity and last point for determining is returned
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 for determining,
Return 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 adopted 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.
Illustrate below in conjunction with Fig. 6 and Fig. 7, message instance is:
Gateway sends the request of resource acquisition to sensor:
(NUM is 0 to CON GET 00,000,000 00000101, represents and requires to obtain last burst, and SZX is 101, i.e.,
5,9 powers that the burst capacity recommended is 2 are represented, i.e., 512).
The response that sensor sends 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 for determining is 2 are represented, i.e., 512);
According to primary return information, 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 and requires to obtain first burst, and SZX is 101, i.e., 5,
9 powers that burst capacity is 2 are represented, i.e., 512);
Sensor returns the ACK to CON, the i.e. data of first burst;
Gateway can successively or all remaining bursts of concurrent request, until having obtained all of data.
Embodiment according to Fig. 6, while burst capabilities negotiation, can obtain the burst number of last burst
According to, in successive fragment data acquisition, the burst capacity all same for being used, therefore can be with reference to aforementioned preferred embodiments
Description, gateway can not retransmit SZX fields, and only send NUM fields when the request for obtaining fragment data is sent, by
This can save data traffic, improve efficiency of transmission.
Fig. 8 to show and send data to sensor using burst option, 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) or updates (Put) request message to sensor, using Size options
The capacity information of resource is sent, burst capacity and the burst sum for indicating to recommend using burst option, burst described herein is total
Number is calculated based on the volumeter of the burst capacity and data resource to be sent recommended, does not carry concrete 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 conditional code
Send), while returning the burst capacity for determining 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 error code and indicate that client should not continue to send data.Than
Such as, the lack of memory capacity of sensor then returns 413 " Request Entity to store the data of indicated resource capacity
The return code of Too Large ".
ES830:The burst capacity of the determination that gateway is returned according to sensor, judges whether and the burst capacity phase recommended
Together, if identical, ES360 is jumped to;If it is not the same, the burst capacity information of the determination for then being returned according to sensor, and
According to data resource capacity, burst sum is recalculated.
ES840:Gateway sends the burst capacity for determining and the burst for recalculating sum to sensor again.
ES850:Sensor returns the burst capacity for determining.
ES860:Gateway sends and burst sequence number successively from total up to burst from 1 according to burst sequence number to sensor
The fragment data of corresponding data resource, until complete end of transmission.
ES870:Sensor is returned and determines the message for receiving, wherein comprising the burst sequence number for receiving.
A kind of preferred embodiment of the invention, parallel processing, i.e. gateway can be carried out in ES860 can be simultaneously to biography
Sensor sends multiple fragment datas, without waiting sensor to return the response message to previous fragmental messages.Alternatively,
A kind of preferred embodiment of the invention, gateway and sensor increase authentication information in interacting message.Certification message is matched somebody with somebody
Put the same way that can be adopted with interactive mode with reference to described in Fig. 2.
In order to improve efficiency of transmission, data traffic is saved, according to another kind preferred embodiment of the invention, as above for<
GET>It is such described in method, using<Put>/<Post>No longer it is to send first for 0 when NUM is in the request of method
Fragment data, but inform the capacity and burst sum of the burst that sensor is recommended.Sensor can return response and inform gateway
Whether continuation sends data.Sensor in the response, using NUM fields total burst number is returned, and is returned using SZX fields and is sensed
The burst capacity that device determines.And gateway and burst capacity determined by sensor both sides storage, the fragment data for after
Transmission 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, and do not send and have determined and keep 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, do not retransmit burst capacity.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 of burst option and occupation mode are similar to shown in Fig. 3, for Fig. 3
It is bright.<Put>/<Post>In request, NUM fields are second bytes for 0, SZX fields, represent the burst capacity recommended,
Total Number represent burst sum number to be sent;<Put>/<Post>In response, NUM fields are 0, SZX field lists
Show the burst capacity that sensor determines, Total Number are useless, it is not necessary to carry;If the SZX fields that gateway is received with
What is sent is inconsistent, and needs are sent again with new SZX<Put>/<Post>Request, and the burst sum for recalculating is carried,
Sensor beams back again response.After<Put>/<Post>In request and response, SZX fields are no longer carried.
By redesigning to burst option, 4 bits of transmission can be at least reduced in each request or in responding,
In the case that burst is more, efficiency of transmission can be greatly enhanced, transfer resource be 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 for repeating
Transfer resource can be wasted, present invention design associates multiple requests of sliced transmission using Token (token), only at the first point
URI is transmitted in piece message, in follow-up sliced transmission request, it is only necessary to carry Token, 1 is typically due to Token~
8 bytes, therefore certain flow can be saved.
Fig. 9 is a kind of embodiment of the client device by sliced transmission data resource of the present invention.Client shown in Fig. 9
Equipment 900 includes:Acquiring unit 910, for obtaining data resource capacity information;Transmitting element 920, for sending burst is carried
The request message of option, wherein the burst option includes the burst capacity recommended, receiving unit 930 is received and carries burst choosing
The response message of item, wherein the burst option includes the burst capacity for determining;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.
A kind of preferred embodiment of the invention, the client device may further include memory element 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.
Another kind of preferred embodiment of the invention, the client device may further include authentication ' unit 960,
For sending and receiving authentication information.
Figure 10 is a kind of embodiment of the server apparatus by sliced transmission data resource of the present invention.Service shown in Figure 10
Device equipment 1000 includes:Receiving unit 1010, for receiving the request message for carrying burst option, wherein the burst option bag
Include the burst capacity of recommendation;Transmitting element 1020, for sending the response message for carrying burst option, wherein the burst option
Including the burst capacity for determining;With transmission unit 1030, for according to the burst capacity of the determination, data described in sliced transmission
Resource.
According to an embodiment of the present invention, transmitting element 1020 is additionally operable to send and carries disappearing for data resource capacity information
Breath, in order to transmission unit 1030 according to the burst capacity and the data resource capacity information of 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 element 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.
Another kind of preferred embodiment of the 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 this avoid the probability of error obtaining resource, it is also possible to which burst is concomitantly asked in realization, improve request of data
Efficiency, and learn that the capacity of resource also allows for distributing memory space, calculate the quantity of burst.
By redesigning to burst option, 4 bits at least can be less sent in each request or in responding, divided
In the case that piece is more, efficiency of transmission can be greatly enhanced, save transfer resource, while also improving the process effect of both sides
Rate.
In the prior art, after receiving and coming from the request of client, server can immediately beam back response, it is also possible to
Ack (Acknowledgement) response message is first beamed back, shows to have received request message, present, follow-up etc.
After having processed, 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 certain 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 in the request server, oneself needs the response of which kind of mode;
2nd, client requirements server beams back response within the time that certain specifies;
3rd, in the transmit process of notification message, because network capacity is unstable, it is logical that possible server first sends
Know message, than the message sent after server, the time for reaching client will evening.So, the resource information for receiving after client
Actually outmoded information, client needs a kind of mechanism and 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 or token (Token) option, are used to refer to server, and whether client 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 that multiple responses and cancellation are postponed.If response mode option is not carried, disposable response is defaulted as, server can
To determine being to adopt the disposable response for 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 sends.
In the prior art, after receiving and coming from the request of client, server can immediately beam back response, it is also possible to
An Ack is first beamed back, shows to have received request message, present is subsequently waited after having processed, and retransmits response message,
The response postponed.In addition, client can subscribe to the change of a resource, server is receiving client to certain resource
After subscription, once resource information changes, just notification message is beamed back to client.
In an embodiment of the present invention, for example can 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, is subscribed to;
C=11:Represent and cancel the multiple responses postponed, that is, unsubscribe.
For the subscription with regard to certain resource that client is initiated, can be unsubscribed by client, it is also possible to server
Unsubscribe, such as server sends back to the response message that client one needs to confirm, client is within the predetermined time not
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) can be used to indicate that and push away
The deadline of multiple responses of the retardation time or postponement of slow disposable response, i.e., more than this time after, take automatically
Disappear subscription.When C is 01, T represents the retardation time of the disposable response of postponement;When C is 10, T represents multiple sound of postponement
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 for T, can be shown with 2 T powers
This time span, in seconds, you can to represent 1~2^63 seconds.Such as:
0:The 2^0=1 seconds;
1:The 2^1=2 seconds;
2:The 2^2=4 seconds;
3:The 2^3=8 seconds
4:The 2^4=16 seconds;
…
63:The 2^63 seconds.
In the prior art, Max_Age fields show to ring for showing the maximum time that certain response can be buffered
The freshness answered.The present invention extends the implication of this field, can be represented between multiple responses with Max_Age fields in the request
Time interval restriction, such as multiple notification messages must not be spaced higher than this time, or must not be spaced less than this time.
For the order of multiple responses, can be distinguished with message identifier (Message ID).Such as, it is stipulated that message identifier
Must incrementally be generated according to the order of logical response, recipient judges that the priority for responding is suitable according to the size of message identifier
Sequence.
Another kind of embodiment of the invention, it is possible to use Token (token) options indicating response mode, if
Token values represent response immediately for 0, if Token values are not 0, then it represents that can receive the response postponed.
Another kind of embodiment of the invention, can alternatively or additionally increase timestamp (Timestamp) option, with
Postpone option individually or in combination to indicate response mode.Specifically, client can in the request carry timestamp
Option, the timestamp option includes the value of a deadline, it is desirable to which server returns response within the specified time;Service
Device in the response message, carries timestamp option, shows the time that response message is generated, and so, client can be based on the time
Stab option 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 for representing is short, with a byte, if the time is long, with 3 bytes or 6 bytes.Concrete 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 moon, 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 be based on 2000, its value shows which afterwards in 2000 in year, such as 0 when, be shown to be 2000, when being 1,
Calendar year 2001 is shown to be, at most can be represented 2063.
(2) three bytes all represent with the second, and maximum can represent the 2^24-1 seconds, about 136 years.
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 process 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 of the carrying response mode option that client sends;
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 make an immediate response, and the request message also carries type of message configured information and option time delay.
Here type of message configured information indicates that the request message is Measurement Request, and time delay, option was multiple for indicating
Server selects a time to send response message to client within the time indicated by option time delay, arbitrarily,
To avoid multiple servers from responding to client while beaming back, network congestion, and client is caused also to have little time to process.Example
Such as, within the time indicated by option time delay, multiple servers are each after random delay, then send out to client
Send response message.
For example, certain building manager sends the multiple electric controllers to whole building using control station (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 control station, show
Whether turn on light.
In order to notify that request message described in server is Measurement Request, type of message configured information described here for example may be used
Being the default socket port for sending Measurement Request;Or the default network for sending the Measurement Request is assisted
View IP address;Or the default port numbers for sending 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::The prefix of/8 IPv6, clothes
Business device is received after request message, checks the IP address for receiving bag, if the IP address is default IP address, then it represents that should
Ask message to be Measurement Request, be otherwise unitcast request;
3) client by it is default for sending the port numbers of Measurement Request sending 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 for receiving
Number determining 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 is abandoned beaming back and responds to client;For Measurement Request, after time-out, server still can be beamed back and respond to client
End, although response timeout, but due to not every server it is all overtime, so not resulting in congestion problems.
According to embodiments of the present invention, the request message also includes option deadline, to indicate server in the cut-off
Response message is returned in time indicated by time option.Thus, client can be when option deadline be indicated
Between time-out before, the reception server send response message.
Embodiment 2:
In the request message sent in step S1110, response mode option is the multiple responses postponed, that is, represent 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 of the value for showing resource;The Patience options are used to indicate 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 postpone the transmission of response message with this Patience option.In this case, visitor
Family end can be judged with this, and after Max-Age is expired, server will send and notify as far as possible before the Patience times expire
Respond to client.Therefore, client can continue to keep the subscribing relationship with the server after Max-Age is expired, protect
The time of holding is 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 step S1110 send the request message in, the response mode option be postpone multiple responses, table
Show the data of client subscription (Observe) server.In this case, the request that user end to server sends disappears
Breath includes retention time (Keep Alive) option.Client can according to circumstances arrange the value of Keep Alive options,
Such as could be arranged in this example 1000 seconds.Server is received after the request message, is replied to client and is confirmed
(Acknowledgement, abbreviation ACK) message, wherein the newest value of current subscription resource is carried, while obtaining Keep
Alive options, and an intervalometer is opened at this moment, its value is the value that Keep Alive are arranged.
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 sends, the institute
Third notice response is stated for type message need not be confirmed.
After the time time-out for pressing Keep-Alive instructions, server to client sends the 4th push-notification-answer, i.e. visitor
The 4th push-notification-answer that family end the reception server sends, wherein the 4th push-notification-answer is to need confirmation type message.Then take
Business device waits client to return ACK message.After server is received from the ACK message of client, then client operation is illustrated
Normally.Then process above can be repeated, server reopens intervalometer, by the way that type message need not be confirmed to client
Send response message.
If within a certain period of time server does not receive the ACK message of client, 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 for realizing process of embodiment 3.Each message in Figure 13 is as follows:
ES1310:User end to server sends subscribes to request, wherein carrying Keep Alive options;
ES1320:Server to client replys ACK message, wherein carrying the newest value of current subscription resource, opens
Intervalometer;
ES1330:When the resource subscribed on server changes, the server to client sends push-notification-answer, should
Push-notification-answer is need not to confirm type message;
ES1340:After when the timer times out, server is adopted needs confirmation type message to send push-notification-answer, and waits client
The ACK message that end returns;
ES1350:Client-server returns an ACK message;
ES1360:Server receives the ACK message from client, reopens intervalometer;
ES1370:When the resource subscribed on server changes, the server to client sends push-notification-answer, should
Push-notification-answer is need not to confirm type message;
ES1380:After when the timer times out, server is adopted needs confirmation type message to send push-notification-answer, and waits client
The ACK message that end returns;
ES1390:Server does not receive within a certain period of time the ACK message of client, and server will resend
Push-notification-answer is stated, when sending times reach maximum, server stops again without the ACK message for receiving client, then server
Retransmit, while also stopping the subscribing relationship of same client.
The code of ES1310 to ES1390 is, for example,:
REQ:GET/resource-URI/observe=0/keep-alive=1000--- transmit a request to be needed to subscribe to
Resource URI, carry and subscribe to sign observe options and Keep Alive options;
RES:ACK/payload--- first replys ACK, and the newest data of resource are carried in payload;
RES:When resource has renewal, server adopts the message back push-notification-answer of non-acknowledgement to NON/payload---;
RES:CON/payload--- has been crossed after the intervalometer of Keep Alive options setting, and server is adopted to be needed to confirm
Type message back push-notification-answer;
REQ:ACK/--- clients reply ACK message
RES:When resource has renewal, server adopts the message back push-notification-answer of non-acknowledgement to NON/payload---;
RES:CON/payload--- has been crossed after the intervalometer of Keep Alive options setting, and server is using disappearing for confirming
Breath replys push-notification-answer;
RES:CON/payload--- does not receive within a certain period of time the ACK message of client, resends above-mentioned disappearing
Breath;
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, the request for receiving is processed by the not option.
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 concrete 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 thus results in high load capacity because of originals such as congestions, according to the configuration of server apparatus
Strategy, in order to prevent the operations such as follow-up signaling process from causing server apparatus thoroughly to be paralysed, server apparatus are on this time point
Congestion control is opened, i.e., in ensuing certain hour, does not reprocess any new request message for receiving.
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 of postponement or disposably makes an immediate response, and institute
Stating request message also includes type of message configured information and option deadline, wherein the type of message configured information indicates institute
It is unitcast request to state request message, and 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 need not to confirm type request message, then directly ignore message, does not reply any response.If now taken
There is congestion and open congestion control in business device, then in step S1120, server sends specific ACK and disappears to the client
Breath, wherein the specific confirmation message carries response code and postpones turn-on time option, wherein the response code is for example
For 5.03 " service unavailable " (service unavailable) response code, for representing server in the deadline
The response of the request message cannot be returned in time indicated by option.Or server can 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 cannot within the time indicated by option deadline
It is returned for the response of the request message.
The value for postponing turn-on time option represents the concrete time for postponing to access, and unit is, for example, the second, and maximum is for example
For 2NSecond, more than the maximum value such as being serviced device according to default value 2MSecond is processed.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 again request.According to embodiments of the present invention, it is optional type to postpone turn-on time option, i.e., cannot be by CoAP clients
Can directly be ignored during identification.
Figure 14 is the interacting message figure of embodiment 4.As illustrated,
E1400:Server opens congestion control;
E1402:Client sends to the server needs confirmation type request message;
E1404:Server to client sends ACK message, and the ACK message accesses option (new), response generation comprising delay
The load of code and sky
E1405:Client removes immediately other request messages that the wait of caching sends to the server.
E1406:Within the time postponed indicated by turn-on time option, to server request message is sent;
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 normal ACK message.
Because the version of CoAP agreements is different, the CoAP clients for actually coming into operation may not upgrade in time, so that
Option is accessed in delay described in None- identified.Even if therefore in E1404, being sent to the ACK for postponing turn-on time option
Client, because the older None- identified of client release postpones turn-on time option, 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 for previously having sent.
It should be noted that explaining for convenience in the present embodiment, the sound of Piggy-backed (subsidiary formula) is all employ
Message is answered, i.e., each option is entrained in ACK message and directly transmits.According to embodiments of the present invention, it is also possible to using the sound of separate type
Should, that is, confirm that message and response message send at twice, postpone to access the part that option always belongs to response message.
Embodiment 5:
Similar with server side generation congestion, client is likely to cause high load capacity because congestion certain reason occurs.
When client thus results in high load capacity due to originals 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
It is interior, do not reprocess any new request message for receiving.
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 the response mode option is the multiple responses postponed, 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 sends 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
It is specific to confirm that message carries response code and postpones turn-on time option, wherein the response code represents that the client exists
The confirmation of the response message cannot be returned in the time postponed indicated by 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 postpones turn-on time option, wherein the response code represents that the client is prolonged described
The confirmation for needing confirmation type response message cannot be returned in the late time indicated by turn-on time option.In client
In the case of opening congestion control, if what client received in step S1120 is need not to confirm type response message,
Then client directly ignores the message, does not reply any confirmation message.
As described above, the value for postponing turn-on time option represents the concrete time for postponing to access, unit is, for example, the second, most
Big value is, for example, 2NSecond, more than the maximum value for example by client according to default value 2MSecond is processed.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 be sent again to client needs to confirm shape response message.According to embodiments of the present invention, it is optional to postpone turn-on time option
Type, i.e., can directly be ignored when cannot 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
Suspend all of subscription between the client to push, start waiting for, that is, wait the client to recover normal.
After the time indicated by turn-on time option that postpones 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 15,
ES1500:User end to server sends 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 that the needs of server apparatus push confirm
After message, what is all replied is that ACK confirms message, only just can be used when client needs and notifies and postpone and access to server
The mode of piggybacked carries concrete response contents or separately transmits ACK and response.
According to embodiments of the present invention, by the specified response mode option in message interaction process, client can be specified
Required response, improves the interacting message efficiency of CoAP.
Embodiment 6:
Present embodiment describes the flow process 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 for receiving, 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 the request of client, if prediction can not be completed, beam back a conditional code (such as 5.04, Timeout,
Time-out) client is given, show the request that can not in the given time complete client;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 in the response client
End, indicates client after specified predicted time, and request is sent again;If server can be in specified time-out time
Request is inside completed, then before time-out time is expired, beams 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 in an announcement message the information of resource, 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 of the invention, wherein described
Client device 1600 includes:Sending module 1610, for sending the request message for carrying response mode option;And receiver module
1620, for receiving the response message generated according to the response mode option.
The process described by embodiments of the invention and feature with reference to described in Figure 11 is 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 sends can be postponed
Option, for example can be:Disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed is postponed
Multiple responses.
According to a kind of embodiment, the response mode option carried in the request message that sending module 1610 sends can be represented
The deadline of multiple responses of the retardation time or postponement of the disposable response postponed.
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;Receiver 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 receiver module 1620 in the response message for receiving 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 make an immediate response,
The request message also carries type of message configured information and option time delay, wherein the type of message is indicated
Information indicates that the request message is Measurement Request or unitcast request;
The receiver module 1620 was used within the time of option time delay instruction, the sound that the reception server sends
Answer message.
According to embodiments of the present invention, the request message also includes option deadline,
The receiver module 1620 was used for before the time time-out that option deadline is indicated, the reception server is sent out
The response message for sending.
According to embodiments of the present invention, in the request message, the response mode option is the multiple responses postponed,
The receiver module 1620 is used to receive the push-notification-answer message that the server sends, wherein the push-notification-answer
Message carries most long survival time option and stays time time option, wherein described stay time time option for indicating,
After time time-out indicated by the most long survival time option, the client keeps 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 be postpone multiple responses, institute
Stating request message also includes retention time option, and the receiver 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 sends, wherein first push-notification-answer is need not to confirm type message;Described
After the time time-out that retention time option is indicated, the receiver module 1620 is used to receive the server sends second
Push-notification-answer, wherein second push-notification-answer is to need confirmation type message, the sending module 1610 is for the service
Device sends and confirms 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 make an immediate response, the request message also includes type of message configured information and option deadline, 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 receiver module 1620 is used to receive the specific confirmation message that the server sends, wherein described specific
Confirm that message carries response code and postpones turn-on time option, wherein the response code represents the server at described section
The response of the request message only cannot be returned in the time indicated by time option;
Or
The receiver module 1620 is used to receive the confirmation message that the server sends;
And for receiving the specific response message that the server sends, wherein the specific response message is carried and rung
Answer code and postpone turn-on time option, wherein the response code represents the server in the option deadline indication
The response of the request message cannot be returned in the time shown.
According to embodiments of the present invention, the receiver module 1620 be additionally operable to remove caching wait send 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 be postpone multiple responses, 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 to carry response code and postpone turn-on time option, wherein the response code represents that client postpones to access described
The confirmation of the response message cannot 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 the client in the delay turn-on time option institute
The confirmation of the response message cannot be returned in the time of instruction.
According to embodiments of the present invention, the response message includes that response message generates the time, and the receiver module 1220 is also
For determining the order of response message according to the response message generation time.
Figure 17 is a kind of embodiment of the server apparatus of transmission data resource of the invention, wherein the server
Equipment 1700 includes:Receiver module 1710, for receiving the request message of the carrying response mode option of client transmission;With send out
Module 1720 is sent, the response message generated according to the response mode option is sent to client.
The process described by embodiments of the invention and feature with reference to described in Figure 12 is applied to the service shown in Figure 17
Device equipment.Specifically, for example, the response mode option carried in the request message that receiver module 1710 is received can be postponed
Option, for example can be:Disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed is 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 make an immediate response, the request message also includes type of message configured information and option time delay, 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 option time delay is indicated, after random delay, to the client response message is sent.
According to embodiments of the present invention, the request message also includes option deadline, and the sending module 1720 is used for
Before the time time-out that option deadline is indicated, to the client response message is sent.
According to embodiments of the present invention, in the request message, the response mode option is the multiple responses postponed,
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 for indicating,
After the time time-out indicated by the most long survival time option, the server will stay the time time described
Respond in time indicated by option.
According to embodiments of the present invention, in the request message, the response mode option be postpone multiple responses, 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 need not to confirm type message;Described
Send module 1720 to be additionally operable to after the time time-out that the retention time option is indicated, send the 4th to the client and notify
Response, wherein the 4th push-notification-answer is to need confirmation type message;The receiver module 1710 is used to receive the client
The ACK message of transmission.
According to embodiments of the present invention, in the request message, the response mode option is the disposable sound postponed
Should or disposably make an immediate response, the request message also includes type of message configured information and option deadline, 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 sending module 1720 is used to send specific confirmation message to client, wherein the specific confirmation message
Carry response code and postpone turn-on time option, wherein the response code represents that the server is selected in the deadline
The response of the request message cannot 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 option deadline
The interior response that cannot be returned for the request message.
According to embodiments of the present invention, after the time indicated by the delay turn-on time option, the receiver module
1710 are used to receive the request message that the client resends.
According to embodiments of the present invention, in the request message, the response mode option be postpone multiple responses, 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 sends, wherein the specific confirmation message carries response generation
Code and delay turn-on time option, wherein the response code represents the client in the delay turn-on time option indication
The confirmation of the response message cannot be returned in the time shown;
Or
The receiver module 1710 is used to receive the confirmation message that the client sends;
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 of the response message cannot 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 is used to be resend to the client described needs confirmation type response message.
Another kind of embodiment of the invention, in the request message that receiver module 1710 is received timestamp can be carried
Option, the timestamp option represents the deadline for receiving response, and can also in the response message that sending module 1320 sends
Timestamp option is carried, 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 with reference to the embodiments described herein description
Unit and algorithm steps, can with electronic hardware, computer software or the two be implemented in combination in, in order to clearly demonstrate hardware
With the interchangeability of software, according to function the composition and step of each example have been generally described 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 use different methods to realize described function to each specific application, but this realization is not
It is considered as beyond the scope of this invention.
Can be with hardware, computing device with reference to the method for the embodiments described herein description or the step of algorithm
Software module, or the combination of the two is implementing.Software module can be placed in random access memory (RAM), internal memory, read only memory
(ROM), electrically programmable ROM, electrically erasable ROM, depositor, 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 without departing from
In the case of the principle and spirit of the present invention, these embodiments can be carried out with various modifications, such modification should fall into the present invention
In the range of.
Claims (24)
1. it is a kind of in Internet of things system based on lightweight application layer protocol node transmitting data resources method, its feature exists
In,
The request message for carrying response mode option is sent to server, wherein the response mode option represents following responder
Formula one of which:It is multiple that disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed is postponed
Response;
Receive the response message generated according to the response mode option that the server sends;
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 sends, including:
The push-notification-answer message that the server sends is received, wherein the push-notification-answer message carries most long survival time option
With stay time time option, wherein described stay time time option for indicating, 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 described staying indicated by time time option
Time.
2. it is a kind of in Internet of things system based on lightweight application layer protocol node transmitting data resources method, its feature exists
In,
The request message for carrying response mode option is sent to server, wherein the response mode option represents following responder
Formula one of which:It is multiple that disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed is postponed
Response;
Receive the response message generated according to the response mode option that the server sends;
In the request message, the response mode option is the multiple responses postponed,
The request message also includes retention time option,
The response message generated according to the response mode option that the reception server sends, including:
Within the time that the retention time option is indicated, the first push-notification-answer that the reception server sends, wherein described first
Push-notification-answer is need not to confirm type message;
After the time time-out that the retention time option is indicated, the second push-notification-answer that the server sends is received, its
Described in the second push-notification-answer to need confirmation type message;
Send to the server and confirm ACK message.
3. it is a kind of in Internet of things system based on lightweight application layer protocol node transmitting data resources method, its feature exists
In,
The request message for carrying response mode option is sent to server, wherein the response mode option represents following responder
Formula one of which:It is multiple that disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed is postponed
Response;
Receive the response message generated according to the response mode option that the server sends;
In the request message, the response mode option is the disposable response of postponement or disposably makes an immediate response,
The request message also includes type of message configured information and option deadline, wherein the type of message configured information
Indicate that the request message is unitcast request, the request message is to need confirmation type message;
The response message generated according to the response mode option that the reception server sends, including:
The specific confirmation message that the server sends is received, wherein the specific confirmation message carries response code and prolongs
Slow turn-on time option, wherein the response code represents the server within the time indicated by option deadline
The response of the request message cannot be returned for;
Or
The confirmation message that the server sends is received, and receives the specific response message that the server sends, wherein
The specific response message carries response code and postpones turn-on time option, wherein the response code represents the service
Device cannot be returned for the response of the request message within the time indicated by option deadline.
4. method as claimed in claim 3, it is characterised in that
Remove other request messages that the wait of caching sends to the server.
5. method as claimed in claim 3, 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.
6. it is a kind of in Internet of things system based on lightweight application layer protocol node transmitting data resources method, its feature exists
In,
The request message for carrying response mode option is sent to server, wherein the response mode option represents following responder
Formula one of which:It is multiple that disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed is postponed
Response;
Receive the response message generated according to the response mode option that the server sends;
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 sends is to need confirmation type message,
Methods described is further included:
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 cannot within the time indicated by the delay turn-on time option
It is returned for the confirmation for needing confirmation type message;
Or
Send to the server and confirm message, and specific response message is sent to the server, wherein described specific
Response message carry response code and postpone turn-on time option, wherein the response code represents the client described
The confirmation for needing confirmation type message cannot be returned in postponing the time indicated by turn-on time option.
7. it is a kind of in Internet of things system based on lightweight application layer protocol node transmitting data resources method, its feature exists
In,
The request message of the carrying response mode option that client sends is received, wherein the response mode option represents following sound
Answer mode one of which:What disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed was postponed
Multiple responses;
The response message generated according to the response mode option is sent to client;
In the request message, the response mode option is the multiple responses postponed,
It is described that the response message generated according to the response mode option is sent to client, including:
Push-notification-answer is sent to the client, wherein the push-notification-answer carries most long survival time option and stays the time time to select
, wherein described stay time time option for indicating, and after the time time-out indicated by the most long survival time option, clothes
Business device will respond within the time stayed indicated by time time option.
8. it is a kind of in Internet of things system based on lightweight application layer protocol node transmitting data resources method, its feature exists
In,
The request message of the carrying response mode option that client sends is received, wherein the response mode option represents following sound
Answer mode one of which:What disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed was postponed
Multiple responses;
The response message generated according to the response mode option is sent to client;
In the request message, the response mode option is the multiple responses postponed,
The request message also includes retention time option,
It is described that the response message generated according to the response mode option is sent to client, including:
Within the time that the retention time option is indicated, third notice response is sent to the client, wherein the described 3rd
Push-notification-answer is need not to confirm type message;
After the time time-out that the retention time option is indicated, to the client the 4th push-notification-answer, wherein institute are sent
The 4th push-notification-answer is stated to need confirmation type message;
Receive the confirmation ACK message that the client sends.
9. it is a kind of in Internet of things system based on lightweight application layer protocol node transmitting data resources method, its feature exists
In,
The request message of the carrying response mode option that client sends is received, wherein the response mode option represents following sound
Answer mode one of which:What disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed was postponed
Multiple responses;
The response message generated according to the response mode option is sent to client;
In the request message, the response mode option is the disposable response of postponement or disposably makes an immediate response,
The request message also includes type of message configured information and option deadline, wherein the type of message configured information
Indicate that the request message is unitcast request, the request message is to need confirmation type message;
The response message generated according to the response mode option sent to client, including:
Specific confirmation message is sent to client, wherein when the specific confirmation message carries response code and postpones access
Between option, wherein the response code represents that server cannot be returned within the time indicated by option deadline
The response of the request message;
Or
Send to client and confirm message, and specific response message is sent to client, wherein the specific response disappears
Breath carries response code and postpones turn-on time option, wherein the response code represents the server in the deadline
The response of the request message cannot be returned in time indicated by option.
10. method as claimed in claim 9, it is characterised in that
After the time indicated by the delay turn-on time option, the request that the reception client resends disappears
Breath.
A kind of 11. transmitting data resources methods of the node that lightweight application layer protocol is based in Internet of things system, its feature
It is,
The request message of the carrying response mode option that client sends is received, wherein the response mode option represents following sound
Answer mode one of which:What disposable response, multiple responses of postponement and the cancellation disposably make an immediate response, postponed was postponed
Multiple responses;
The response message generated according to the response mode option is sent to client;
In the request message, the response mode option is the multiple responses postponed,
The response message generated according to the response mode option sent to client is to need confirmation type message,
Methods described is further included:
The specific confirmation message that the client sends is received, wherein the specific confirmation message carries response code and prolongs
Slow turn-on time option, wherein the response code represent the client indicated by the delay turn-on time option when
It is interior to be returned for the confirmation for needing confirmation type message;
Or
The confirmation message that the client sends is received, and receives the specific response message that the client sends, wherein
The specific response message carries response code and postpones turn-on time option, wherein the response code represents the client
Holding cannot be returned for the confirmation for needing confirmation type message within the time indicated by the delay turn-on time option.
12. methods as claimed in claim 11, it is characterised in that
After the time time-out indicated by the delay turn-on time option, the response message resend to the client is
It is described to need confirmation type message;
Receive the confirmation message that the client sends.
A kind of 13. clients of the data resource that lightweight application layer protocol transmission node is based in Internet of things system, it is special
Levy and be, including:
Sending module, for sending the request message for carrying response mode option to server, wherein the response mode option
Represent following response mode one of which:The disposable response disposably make an immediate response, postponed, the multiple responses postponed and
Cancel the multiple responses postponed;
Receiver module, for receiving the response message that the server is generated according to the response mode option;
In the request message, the response mode option be postpone multiple responses, the receiver module specifically for:
The push-notification-answer message that the server sends is received, wherein the push-notification-answer message carries most long survival time option
With stay time time option, wherein described stay time time option for indicating, 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 described staying indicated by time time option
Time.
A kind of 14. clients of the data resource that lightweight application layer protocol transmission node is based in Internet of things system, it is special
Levy and be, including:
Sending module, for sending the request message for carrying response mode option to server, wherein the response mode option
Represent following response mode one of which:The disposable response disposably make an immediate response, postponed, the multiple responses postponed and
Cancel the multiple responses postponed;
Receiver module, for receiving the response message generated according to the response mode option that the server sends;
In the request message, the response mode option is the multiple responses postponed, and the request message also includes keeping
Time option, the receiver module specifically for:
Within the time that the retention time option is indicated, the first push-notification-answer that the reception server sends, wherein described first
Push-notification-answer is need not to confirm type message;
After the time time-out that the retention time option is indicated, the second push-notification-answer that the server sends is received, its
Described in the second push-notification-answer to need confirmation type message;
The sending module, is additionally operable to send confirmation ACK message to the server.
A kind of 15. clients of the data resource that lightweight application layer protocol transmission node is based in Internet of things system, it is special
Levy and be, including:
Sending module, for sending the request message for carrying response mode option to server, wherein the response mode option
Represent following response mode one of which:The disposable response disposably make an immediate response, postponed, the multiple responses postponed and
Cancel the multiple responses postponed;
Receiver module, for receiving the response message generated according to the response mode option that the server sends;
In the request message, the response mode option is the disposable response of postponement or disposably makes an immediate response,
The request message also includes type of message configured information and option deadline, wherein the type of message configured information is indicated
The request message is unitcast request, the request message to need confirmation type message, the receiver module specifically for:
The specific confirmation message that the server sends is received, wherein the specific confirmation message carries response code and prolongs
Slow turn-on time option, wherein the response code represents the server within the time indicated by option deadline
The response of the request message cannot be returned for;
Or
The confirmation message that the server sends is received, and receives the specific response message that the server sends, wherein
The specific response message carries response code and postpones turn-on time option, wherein the response code represents the service
Device cannot be returned for the response of the request message within the time indicated by option deadline.
16. clients as claimed in claim 15, it is characterised in that remove that the wait of caching sent to the server its
His request message.
17. clients as claimed in claim 15, it is characterised in that the sending module specifically for:
After the time indicated by the delay turn-on time option, the request message is sent to the server again.
A kind of 18. clients of the data resource that lightweight application layer protocol transmission node is based in Internet of things system, it is special
Levy and be, including:
Sending module, for sending the request message for carrying response mode option to server, wherein the response mode option
Represent following response mode one of which:The disposable response disposably make an immediate response, postponed, the multiple responses postponed and
Cancel the multiple responses postponed;
Receiver module, for receiving the response message generated according to the response mode option that the server sends;
In the request message, the response mode option is the multiple responses postponed, the root of the reception server transmission
According to the response mode option generate response message be to need confirmation type message, the sending module specifically for:
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 cannot within the time indicated by the delay turn-on time option
It is returned for the confirmation for needing confirmation type message;
Or
Send to the server and confirm message, and specific response message is sent to the server, wherein described specific
Response message carry response code and postpone turn-on time option, wherein the response code represents the client described
The confirmation for needing confirmation type message cannot be returned in postponing the time indicated by turn-on time option.
A kind of 19. servers of the data resource that lightweight application layer protocol transmission node is based in Internet of things system, it is special
Levy and be, including:
Receiver module, for receiving the request message of the carrying response mode option of client transmission, 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;
Sending module, the response message generated according to the response mode option is sent to the client;
In the request message, the response mode option be postpone multiple responses, the sending module specifically for:
Push-notification-answer is sent to the client, wherein the push-notification-answer carries most long survival time option and stays the time time to select
, wherein described stay time time option for indicating, and after the time time-out indicated by the most long survival time option, clothes
Business device will respond within the time stayed indicated by time time option.
A kind of 20. servers of the data resource that lightweight application layer protocol transmission node is based in Internet of things system, it is special
Levy and be, including:
Receiver module, for receiving the request message of the carrying response mode option of client transmission, 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;
Sending module, for sending the response message generated according to the response mode option to client;
In the request message, the response mode option is the multiple responses postponed, and the request message also includes keeping
Time option, the sending module specifically for:
Within the time that the retention time option is indicated, third notice response is sent to the client, wherein the described 3rd
Push-notification-answer is need not to confirm type message;
After the time time-out that the retention time option is indicated, to the client the 4th push-notification-answer, wherein institute are sent
The 4th push-notification-answer is stated to need confirmation type message;
The receiver module, is additionally operable to receive the confirmation ACK message that the client sends.
A kind of 21. servers of the data resource that lightweight application layer protocol transmission node is based in Internet of things system, it is special
Levy and be, including:
Receiver module, for receiving the request message of the carrying response mode option of client transmission, 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;
Sending module, for sending the response message generated according to the response mode option to client;
In the request message, the response mode option is the disposable response of postponement or disposably makes an immediate response,
The request message also includes type of message configured information and option deadline, wherein the type of message configured information is indicated
The request message is unitcast request, the request message to need confirmation type message, the sending module specifically for:
Specific confirmation message is sent to client, wherein when the specific confirmation message carries response code and postpones access
Between option, wherein the response code represents that server cannot be returned within the time indicated by option deadline
The response of the request message;
Or
Send to client and confirm message, and specific response message is sent to client, wherein the specific response disappears
Breath carries response code and postpones turn-on time option, wherein the response code represents the server in the deadline
The response of the request message cannot be returned in time indicated by option.
22. servers as claimed in claim 21, it is characterised in that in the time indicated by the delay turn-on time option
Afterwards, the receiver module is additionally operable to receive the request message that the client resends.
A kind of 23. servers of the data resource that lightweight application layer protocol transmission node is based in Internet of things system, it is special
Levy and be, including:
Receiver module, for receiving the request message of the carrying response mode option of client transmission, 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;
Sending module, for sending the response message generated according to the response mode option to client;
In the request message, the response mode option is the multiple responses postponed, the basis sent to client
The response message that the response mode option is generated is to need confirmation type message, and the receiver module is additionally operable to receive the client
The specific confirmation message that end sends, wherein the specific confirmation message carries response code and postpones turn-on time option,
Wherein described response code represents that the client cannot return pin within the time indicated by the delay turn-on time option
To the confirmation for needing confirmation type message;
Or
The confirmation message that the client sends is received, and receives the specific response message that the client sends, wherein
The specific response message carries response code and postpones turn-on time option, wherein the response code represents the client
Holding cannot be returned for the confirmation for needing confirmation type message within the time indicated by the delay turn-on time option.
24. servers as claimed in claim 23, it is characterised in that in the time indicated by the delay turn-on time option
After time-out, the response message that the sending module is additionally operable to be resend to the client is described to need confirmation type message;
The receiver module is additionally operable to receive the confirmation message that the client sends.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201710131415.6A CN106878442B (en) | 2011-03-17 | 2012-03-06 | Method and device for transmitting data resources |
CN201210056456.0A CN102685204B (en) | 2011-03-17 | 2012-03-06 | Method and equipment for transmitting data resource |
CN201710132014.2A CN107071826B (en) | 2011-03-17 | 2012-03-06 | Method and device for transmitting data resources |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2011100645493A CN102130954A (en) | 2011-03-17 | 2011-03-17 | Method and device for transmitting data resources |
CN2011100645493 | 2011-03-17 | ||
CN201110064549.3 | 2011-03-17 | ||
CN201210056456.0A CN102685204B (en) | 2011-03-17 | 2012-03-06 | Method and equipment for transmitting data resource |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710132014.2A Division CN107071826B (en) | 2011-03-17 | 2012-03-06 | Method and device for transmitting data resources |
CN201710131415.6A Division CN106878442B (en) | 2011-03-17 | 2012-03-06 | Method and device for transmitting data resources |
Publications (2)
Publication Number | Publication Date |
---|---|
CN102685204A CN102685204A (en) | 2012-09-19 |
CN102685204B true CN102685204B (en) | 2017-04-26 |
Family
ID=44268843
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2011100645493A Pending CN102130954A (en) | 2011-03-17 | 2011-03-17 | Method and device for transmitting data resources |
CN201710132013.8A Active CN106850841B (en) | 2011-03-17 | 2012-03-02 | Method and device for transmitting data resources |
CN201210054892.4A Active CN102685203B (en) | 2011-03-17 | 2012-03-02 | The method and apparatus of transmitting data resources |
CN201710131638.2A Active CN107070990B (en) | 2011-03-17 | 2012-03-02 | Method and device for transmitting data resources |
CN201710132014.2A Active CN107071826B (en) | 2011-03-17 | 2012-03-06 | Method and device for transmitting data resources |
CN201210056456.0A Active CN102685204B (en) | 2011-03-17 | 2012-03-06 | Method and equipment for transmitting data resource |
CN201710131415.6A Active CN106878442B (en) | 2011-03-17 | 2012-03-06 | Method and device for transmitting data resources |
Family Applications Before (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2011100645493A Pending CN102130954A (en) | 2011-03-17 | 2011-03-17 | Method and device for transmitting data resources |
CN201710132013.8A Active CN106850841B (en) | 2011-03-17 | 2012-03-02 | Method and device for transmitting data resources |
CN201210054892.4A Active CN102685203B (en) | 2011-03-17 | 2012-03-02 | The method and apparatus of transmitting data resources |
CN201710131638.2A Active CN107070990B (en) | 2011-03-17 | 2012-03-02 | Method and device for transmitting data resources |
CN201710132014.2A Active CN107071826B (en) | 2011-03-17 | 2012-03-06 | Method and device for transmitting data resources |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201710131415.6A Active CN106878442B (en) | 2011-03-17 | 2012-03-06 | Method and device for transmitting data resources |
Country Status (1)
Country | Link |
---|---|
CN (7) | CN102130954A (en) |
Families Citing this family (39)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103227803A (en) * | 2012-01-30 | 2013-07-31 | 华为技术有限公司 | Internet of thing resource obtaining method, client and internet of thing resource devices |
CN103780483A (en) * | 2012-10-26 | 2014-05-07 | 中兴通讯股份有限公司 | Method, system and device for obtaining resource information of terminal device of Internet of Thingss |
CN103428273B (en) * | 2013-07-18 | 2016-12-28 | 北京百度网讯科技有限公司 | The method and apparatus of response inquiry is carried out in asynchronous system is mutual |
WO2015070441A1 (en) * | 2013-11-15 | 2015-05-21 | 华为技术有限公司 | M2m network and application, common services entity, and information reply method |
CN104468594B (en) * | 2014-12-15 | 2018-04-27 | 北京奇安信科技有限公司 | The method, apparatus and system of a kind of request of data |
CN104580396B (en) * | 2014-12-19 | 2018-07-20 | 华为技术有限公司 | A kind of method for scheduling task, node and system |
WO2016178623A1 (en) * | 2015-05-04 | 2016-11-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Delayed response to requesting device |
CN106658348A (en) * | 2015-10-28 | 2017-05-10 | 西安中兴新软件有限责任公司 | Method and device for managing monitoring resources and CSE |
CN106817314B (en) * | 2015-12-02 | 2020-03-20 | 中国电信股份有限公司 | Big data acquisition method, device and system |
CN105868029A (en) * | 2015-12-11 | 2016-08-17 | 鼎点视讯科技有限公司 | Consistency fault-tolerance processing method and system |
CN107222450A (en) * | 2016-03-21 | 2017-09-29 | 中兴通讯股份有限公司 | A kind of network node and realize the method and apparatus communicated between network node |
CN106303059A (en) * | 2016-08-24 | 2017-01-04 | 努比亚技术有限公司 | Electronic equipment and information processing method |
CN106331117B (en) * | 2016-08-26 | 2019-05-03 | 中国科学技术大学 | A kind of data transmission method |
CN106790603A (en) * | 2016-12-29 | 2017-05-31 | 东软集团股份有限公司 | The method of interacting message, apparatus and system |
US10191825B2 (en) * | 2017-03-01 | 2019-01-29 | Wipro Limited | System and method for testing a device using a light weight device validation protocol |
CN107105035A (en) * | 2017-04-24 | 2017-08-29 | 常州信息职业技术学院 | A kind of smart home supervising device and monitoring system |
CN108809858B (en) * | 2017-04-28 | 2020-11-10 | 华为技术有限公司 | Network congestion control method, equipment and system |
CN109586855A (en) * | 2017-09-29 | 2019-04-05 | 西安中兴新软件有限责任公司 | A kind of mobile unit data transmission method and device |
CN109729039B (en) * | 2017-10-27 | 2022-05-13 | 中兴通讯股份有限公司 | Negotiation fragmentation method and device of link management protocol |
CN107864135A (en) * | 2017-11-07 | 2018-03-30 | 山东网智物联网科技有限公司 | The realization device of Internet of Things communication means, device and Internet of Things Network Communication |
CN109936588B (en) * | 2017-12-15 | 2021-08-31 | 华为技术有限公司 | Internet of things data transmission method, equipment and system |
CN108599904B (en) * | 2018-03-21 | 2021-09-28 | 中兴通讯股份有限公司 | Data transmission method and device |
CN108834110B (en) * | 2018-05-30 | 2021-05-25 | 上海顺舟智能科技股份有限公司 | Data transmission control method and system of zigbee network |
CN108900370B (en) * | 2018-06-08 | 2021-12-17 | 努比亚技术有限公司 | Long connection multiple timeout judging method, device and computer readable storage medium |
CN110636551B (en) * | 2018-06-25 | 2022-05-17 | 上海华为技术有限公司 | Method and device for avoiding message fragmentation |
CN110875952A (en) * | 2018-09-04 | 2020-03-10 | 中国移动通信有限公司研究院 | Data response processing method and equipment based on Internet of things and storage medium |
CN110881021B (en) * | 2018-09-06 | 2022-06-03 | 中国移动通信有限公司研究院 | MSRP fragment processing method and device, network equipment and storage medium |
CN109787884B (en) * | 2019-01-02 | 2021-03-12 | 中国联合网络通信集团有限公司 | Message pushing method and device |
KR102622252B1 (en) * | 2019-05-27 | 2024-01-08 | 삼성에스디에스 주식회사 | Apparatus and method for transmitting contents |
EP4079009A4 (en) * | 2019-12-17 | 2022-11-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Observation of resources by a coap client |
CN111083161A (en) * | 2019-12-27 | 2020-04-28 | 中消云(北京)物联网科技研究院有限公司 | Data transmission processing method and device and Internet of things equipment |
CN111259371B (en) * | 2020-01-13 | 2023-08-18 | 平安科技(深圳)有限公司 | Internet of things equipment authentication method, electronic device and storage medium |
CN112187931A (en) * | 2020-09-29 | 2021-01-05 | 中国平安财产保险股份有限公司 | Session management method, device, computer equipment and storage medium |
CN112367387A (en) * | 2020-10-30 | 2021-02-12 | 湖北亿咖通科技有限公司 | Internet of vehicles communication method and system |
CN112541788B (en) * | 2020-12-11 | 2023-11-17 | 江西蔚乐科技有限公司 | Advertisement request method based on COAP protocol |
CN114125746B (en) * | 2021-11-19 | 2022-08-16 | 山东华科信息技术有限公司 | Dynamic CoAP mode selection method and device based on UCB |
CN114363831B (en) * | 2021-12-02 | 2023-05-26 | 北京万集科技股份有限公司 | Method, apparatus and computer readable storage medium for transmitting V2X message |
CN114884913A (en) * | 2022-01-10 | 2022-08-09 | 中国移动通信有限公司研究院 | Message interaction method and device, electronic equipment, message server and storage medium |
CN115103005A (en) * | 2022-06-14 | 2022-09-23 | 北京京东乾石科技有限公司 | Request response method and device, electronic equipment and storage medium |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101102282A (en) * | 2007-08-08 | 2008-01-09 | 中兴通讯股份有限公司 | A transmission and receiving method for data broadcast service |
CN101335742A (en) * | 2007-06-25 | 2008-12-31 | 中兴通讯股份有限公司 | Directory access system and method under lightweight directory access protocol |
CN101635744A (en) * | 2009-08-26 | 2010-01-27 | 华为技术有限公司 | Method and system for transmitting data and relative equipment |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5909542A (en) * | 1996-11-20 | 1999-06-01 | Cfi Proservices, Inc. | Distributed computing system for executing intercommunicating applications programs |
US6680921B1 (en) * | 1999-06-18 | 2004-01-20 | Telefonaktiebolaget Lm Ericsson (Publ) | Estimation of time stamps in real-time packet communications |
US7239648B1 (en) * | 2001-11-27 | 2007-07-03 | Marvell International Ltd. | Extension mode for wireless lans complying with short interframe space requirement |
US20030202487A1 (en) * | 2002-04-26 | 2003-10-30 | Harris John M. | Method and apparatus for reducing call setup time |
US9886309B2 (en) * | 2002-06-28 | 2018-02-06 | Microsoft Technology Licensing, Llc | Identity-based distributed computing for device resources |
KR20040087161A (en) * | 2003-04-04 | 2004-10-13 | 엘지전자 주식회사 | File content management method for mobile communication terminal |
WO2006020934A2 (en) * | 2004-08-13 | 2006-02-23 | Conexant Systems, Inc. | Systems and methods for decreasing latency in a digital transmission system |
CN100349088C (en) * | 2005-07-26 | 2007-11-14 | 华为技术有限公司 | Digital information controlling method |
CN1905518B (en) * | 2005-07-29 | 2010-12-01 | 北京航空航天大学 | Method for ensuring reliable transmission of data exchange |
US7689162B2 (en) * | 2005-10-28 | 2010-03-30 | Viasat, Inc. | Adaptive coding and modulation flow control and traffic shaping systems and methods |
CN100461673C (en) * | 2005-12-02 | 2009-02-11 | 华为技术有限公司 | Data-bag interacting method and personal field network communication apparatus |
CN100490380C (en) * | 2005-12-26 | 2009-05-20 | 北大方正集团有限公司 | Light distributed file storage system file uploading method |
CN101155054A (en) * | 2006-09-28 | 2008-04-02 | 华为技术有限公司 | Method and device for automatic detection and calculation of PCE path between autonomous system domains |
JP2008271312A (en) * | 2007-04-23 | 2008-11-06 | Matsushita Electric Ind Co Ltd | Radio packet communication apparatus |
US20080275808A1 (en) * | 2007-05-01 | 2008-11-06 | Instinet Europe Limited | Anonymous block trade matching system |
CN101374020B (en) * | 2007-08-20 | 2012-11-14 | 中兴通讯股份有限公司 | Centralized bandwidth distribution method for relay network |
CN101150506B (en) * | 2007-08-24 | 2011-07-06 | 华为技术有限公司 | Content acquisition method, device and content transmission system |
CN101471992B (en) * | 2007-12-24 | 2012-05-09 | 联想(北京)有限公司 | Mobile terminal and method for receiving or sending business information, and push-pull server |
CN101217402B (en) * | 2008-01-15 | 2012-01-04 | 杭州华三通信技术有限公司 | A method to enhance the reliability of the cluster and a high reliability communication node |
CN101222395B (en) * | 2008-02-03 | 2010-10-27 | 华为技术有限公司 | Method, system and device for implementing selection of network guiding configuration information |
CN101635703A (en) * | 2008-07-24 | 2010-01-27 | 北京启明星辰信息技术股份有限公司 | Method for detecting WEB service abnormality |
CN101729593A (en) * | 2008-11-03 | 2010-06-09 | 北大方正集团有限公司 | Method, system and device for uploading and receiving file |
CN101741701B (en) * | 2008-11-12 | 2012-01-11 | 中兴通讯股份有限公司 | Synchronous dispatching method and synchronous dispatching device |
CN101867882B (en) * | 2009-04-14 | 2015-10-21 | 中兴通讯股份有限公司 | Message sends and message feedback preprocess method |
KR20100127189A (en) * | 2009-05-25 | 2010-12-03 | 엘지전자 주식회사 | Bandwidth request procedure and mobile station for the same |
CN101945427B (en) * | 2009-07-03 | 2012-11-14 | 深圳市融创天下科技股份有限公司 | Efficient streaming media transmission method |
CN101789958B (en) * | 2009-12-30 | 2013-06-05 | 中兴通讯股份有限公司 | Method, system and equipment of data synchronization based on equipment management service |
US10448390B2 (en) * | 2014-12-19 | 2019-10-15 | Qualcomm Incorporated | Transmission techniques for enabling an immediate response |
-
2011
- 2011-03-17 CN CN2011100645493A patent/CN102130954A/en active Pending
-
2012
- 2012-03-02 CN CN201710132013.8A patent/CN106850841B/en active Active
- 2012-03-02 CN CN201210054892.4A patent/CN102685203B/en active Active
- 2012-03-02 CN CN201710131638.2A patent/CN107070990B/en active Active
- 2012-03-06 CN CN201710132014.2A patent/CN107071826B/en active Active
- 2012-03-06 CN CN201210056456.0A patent/CN102685204B/en active Active
- 2012-03-06 CN CN201710131415.6A patent/CN106878442B/en active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101335742A (en) * | 2007-06-25 | 2008-12-31 | 中兴通讯股份有限公司 | Directory access system and method under lightweight directory access protocol |
CN101102282A (en) * | 2007-08-08 | 2008-01-09 | 中兴通讯股份有限公司 | A transmission and receiving method for data broadcast service |
CN101635744A (en) * | 2009-08-26 | 2010-01-27 | 华为技术有限公司 | Method and system for transmitting data and relative equipment |
Also Published As
Publication number | Publication date |
---|---|
CN106850841A (en) | 2017-06-13 |
CN106878442A (en) | 2017-06-20 |
CN102130954A (en) | 2011-07-20 |
CN102685204A (en) | 2012-09-19 |
CN107070990A (en) | 2017-08-18 |
CN102685203A (en) | 2012-09-19 |
CN107071826B (en) | 2020-07-07 |
CN106878442B (en) | 2020-12-04 |
CN102685203B (en) | 2017-07-07 |
CN107070990B (en) | 2021-04-09 |
CN106850841B (en) | 2020-11-17 |
CN107071826A (en) | 2017-08-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN102685204B (en) | Method and equipment for transmitting data resource | |
KR100781911B1 (en) | Downloading web pages | |
US11064330B2 (en) | Methods for enabling delay-awareness in the constrained application protocol (CoAP) | |
Lindgren et al. | Probabilistic routing protocol for intermittently connected networks | |
US6807578B2 (en) | Nack suppression for multicast protocols in mostly one-way networks | |
US10498831B2 (en) | Communication sessions at a CoAP protocol layer | |
CN100403716C (en) | Server device, method for controlling a server device, and method for establishing a connection using the server device | |
US7509394B2 (en) | Method for controlling flow of radius protocol | |
KR20080040671A (en) | Range extension between two wireless devices | |
CN104967613B (en) | The system and method that data are transmitted under a kind of mobile network environment | |
Rahman et al. | Performance evaluation of video streaming application over CoAP in IoT | |
EP3360374B1 (en) | Network node, wireless device and methods performed thereby for the network node to provide information to the wireless device | |
CN113992307A (en) | Data message transmission method and device, electronic equipment and computer storage medium | |
WO2015106524A1 (en) | Method, apparatus and server for notifying/sending usage of service package | |
Chakravarthi et al. | M2M Communication Protocols | |
CN112468513A (en) | Terminal management communication protocol architecture of enterprise network | |
KR100921491B1 (en) | Message transmission method without loss in ring-type communication network | |
Gómez Montenegro et al. | Constrained Application Protocol (CoAP) over Bundle Protocol (BP) | |
GB2385499A (en) | Network transport protocol | |
CN116016396A (en) | Processing method, processing device, processing equipment and medium for resending message | |
CN117812165A (en) | Cross-regional quotation transmission method, device, equipment and storage medium | |
CN117956045A (en) | Communication system and method based on UDP protocol | |
CN114900488A (en) | Data transmission method, computer readable storage medium and device | |
CN107637051A (en) | Querying by group response transactions are supported in lower floor | |
Ergin et al. | ONE: Adaptive One-to-N Error Recovery in Wireless Sensor Networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |