CN102685203B - The method and apparatus of transmitting data resources - Google Patents

The method and apparatus of transmitting data resources Download PDF

Info

Publication number
CN102685203B
CN102685203B CN201210054892.4A CN201210054892A CN102685203B CN 102685203 B CN102685203 B CN 102685203B CN 201210054892 A CN201210054892 A CN 201210054892A CN 102685203 B CN102685203 B CN 102685203B
Authority
CN
China
Prior art keywords
burst
capacity
option
resource
server
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
Application number
CN201210054892.4A
Other languages
Chinese (zh)
Other versions
CN102685203A (en
Inventor
李克鹏
田林
田林一
卞永刚
陈显锋
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201710132013.8A priority Critical patent/CN106850841B/en
Priority to CN201210054892.4A priority patent/CN102685203B/en
Priority to CN201710131638.2A priority patent/CN107070990B/en
Publication of CN102685203A publication Critical patent/CN102685203A/en
Application granted granted Critical
Publication of CN102685203B publication Critical patent/CN102685203B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • 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
    • 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/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

Abstract

The method and apparatus that the embodiment of the invention provides transmitting data resources in a kind of Internet of things system.Included by the method for the data resource of sliced transmission node based on lightweight application layer protocol in Internet of things system：The data resource capacity information of node is obtained, resource capacity information is data to be transmitted amount of capacity；The request message for carrying the first burst option is sent to node, wherein the first burst option includes the burst capacity recommended；Receiving node carries the response message of the second burst option, wherein the second burst option includes the burst capacity for determining；According to the burst capacity and the data resource capacity information of node that determine, the data resource of sliced transmission node.According to embodiments of the present invention, the capacity information of the data resource of the node for needing transmission can be known, and the burst capacity used when determining transmission data by burst capabilities negotiation, it is possible thereby to realize lower error rate in transmitting procedure, and can concomitantly transmit data.

Description

The method and apparatus of transmitting data resources
Technical field
The present embodiments relate to network communication field, and relate more specifically to the method for transmitting data resources and set It is standby.
Background technology
Lightweight application layer protocol (Constrained Application Protocol, referred to as " CoAP ") is mainly use In 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 small, and the host-host protocol of complexity is not supported, and message transmission rate is relatively low.CoAP provides a kind of friendship of request/response Mutual pattern, supports embedded resource discovering, including crucial Web page concepts, such as uniform resource identifier (URI) and content type. CoAP can easily translate hypertext link agreement (HTTP), for being integrated into network.Data are transmitted based on CoAP Traditional scheme in disregard calculate data resource accurate capacity, it is impossible to assess the exact number of subpackage, therefore cannot concurrently obtain Data resource, causes efficiency of transmission low.
The content of the invention
The embodiment of the invention provides a kind of method and apparatus of transmitting data resources, it would be preferable to support improved in CoAP and passed Defeated efficiency.
In an embodiment of the present invention, it is proposed that one kind is improved based on lightweight application layer protocol in Internet of things system and passed The method of defeated efficiency, can by burst come the data resource of transmission node, including：Obtain the data resource capacity letter of node Breath, resource capacity information is data to be transmitted amount of capacity；The request message for carrying the first burst option is sent to node, wherein First burst option includes the burst capacity recommended；Receiving node carries the response message of the second burst option, wherein second point Piece option include determine burst capacity, it is determined that burst capacity less than or equal to recommend burst capacity；According to dividing for determining The data resource capacity information of piece capacity and node, the data resource of sliced transmission node.
In embodiments of the present invention, there is provided one kind passes through burst in Internet of things system based on lightweight application layer protocol The method of the data resource of transmission node, receives the request message for carrying the first burst option, wherein the first burst option includes The burst capacity of recommendation；The response message for carrying the second burst option is sent, wherein the second burst option includes the burst for determining Capacity, it is determined that burst capacity less than or equal to recommend burst capacity；According to the burst capacity for determining, the data money of transmission node Source.
In embodiments of the present invention, there is provided one kind passes through burst in Internet of things system based on lightweight application layer protocol The client device of the data resource of transmission node, client device includes：Acquiring unit, the data resource for obtaining node Capacity information；Transmitting element, the request message of the first burst option is carried for sending, wherein the first burst option includes recommending Burst capacity, receiving unit, receive carry the second burst option response message, wherein the second burst option include determine Burst capacity, it is determined that burst capacity less than or equal to recommend burst capacity；Transmission unit, for according to the burst capacity for determining And the data resource capacity information of node, the data resource of sliced transmission node.
In embodiments of the present invention, there is provided one kind passes through burst in Internet of things system based on lightweight application layer protocol The server apparatus of the data resource of transmission node, server apparatus include：Receiving unit, the choosing of the first burst is carried for receiving The request message of item, wherein the first burst option includes the burst capacity recommended, transmitting element carries the second burst for sending The response message of option, wherein the second burst option include determine burst capacity, it is determined that burst capacity less than or equal to recommend Burst capacity；Transmission unit, for according to the burst capacity for determining, the data resource of transmission node.
According to embodiments of the present invention, the capacity information of the data resource of the node for needing transmission can be known, and by dividing Piece capabilities negotiation determines the burst capacity used during transmission data, it is possible thereby to lower error rate in transmitting procedure is realized, and Data can concomitantly be transmitted.
Brief description of the drawings
Technical scheme in order to illustrate more clearly the embodiments 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 invention Example is applied, for those of ordinary skill in the art, without having to pay creative labor, can also be attached according to these Figure obtains other accompanying drawings.In the accompanying drawings：
Fig. 1 is the flow chart of the method for the transmission data of an embodiment of the present invention；
Fig. 2 is the gateway of an embodiment of the present invention from the flow for implementing process of sensors for data resource Figure；
Fig. 3 is the structure chart of improved burst option in an embodiment of the present invention；
Fig. 4 is that a kind of gateway of alternate embodiment of the invention implements the flow of process from sensors for data resource Figure；
Fig. 5 is the structure chart of improved burst option in a kind of alternate embodiment of the invention；
Fig. 6 is a kind of gateway of alternate embodiment of the invention from the stream for implementing process of sensors for data resource Cheng Tu；
Fig. 7 is the structure chart of improved burst option in a kind of alternate embodiment of the invention；
Fig. 8 is the gateway of an embodiment of the present invention to the flow for implementing process of sensor transmission data resource 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 structure chart of the client device of the transmission data of an embodiment of the present invention；
Figure 13 is the structure chart of the server apparatus 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 whole embodiments.Based on this hair Embodiment in bright, the every other implementation that those of ordinary skill in the art are obtained under the premise of creative work is not made Example, belongs to the scope of protection of the invention.
CoAP is transmitted based on UDP (User Datagram Protocol, referred to as " UDP "), is Based on connectionless Message Processing pattern.Its interactive mode can be synchronous response, or asynchronous response.Message class Type can be：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 (RepresentationalState Transfer, abbreviation by declarative state " REST ") URI recognizes.The owning side that we are commonly referred to as resource is node or server, including but not limited to sensor, control Device, end points (End-point) etc., request resource side are client, including but not limited to gateway (Proxy), network side equipment.
CoAP agreements support different options (Option), are used to explain the semanteme of data in CoAP message bodies, such as Block (burst), Location (position), Token (token) option etc., different options support different functions, and can With by the function of defining new Option to extend new.
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 Hair is obtained.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, with sensor as an example, request resource side is Client, with gateway as an example.But, sensor or gateway are not used as the limitation to server or client.
Due to not knowing the precise volume of target resource, gateway exists<Get>When using Block Option in order, can only Obtain in order, i.e. choosing obtains Block 0, when waiting Block 0 to return, then obtain Block1, 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：Represent whether there be other bursts behind current slice with a bit, its value is also have behind 1 expression Burst, is do not have burst behind 0 expression, as last burst.
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.
Operation instruction for Block options is as follows：
<Get>In request, the NUM fields of Block options provide the sequence number of the burst of current request, and when burst sequence Number for 0 when, SZX be given gateway suggestion each burst capacity.<Get>In response or<Put>/<Post>In request, Whether the sequence number of the burst of the NUM field description current transmissions of Block options, M field shows there be 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 advise burst capacity, or selection one than advise burst it is small Burst, and return in the response, meanwhile, first data of burst is returned in the response.
The present invention considers that gateway knows the precise volume of target resource in advance, then gateway can choose whether to use Block Option sends the request of resource acquisition, it is also possible to realize concurrent request, i.e., while Block0 is asked, it is also possible to ask Block 1, 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 is still needed every time in transmission every time Carry M (showing whether also have burst below) and SZX (capacity of burst).
Every time in request and response, M and SZX are required for transmitting, and in fact, in addition to last burst, M 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 carried in the first secondary response is the SZX after consulting, gateway is obtained from response and asked again Middle transmission is asked, so that gateway and sensor need not all preserve state.In request response rounds once, a word is wasted altogether Section, if burst number is a lot, just it is enough for the byte of waste, and for M2M equipment, transfer resource is limited, this biography The waste of defeated resource is very considerable.Assuming that the data to be transmitted be 64M if, load (payload) capacity of each Block For the block entry numbers that 1024byte then sends are：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 use full all positions (bit), then need the data for sending The number of bag is changed to：
(1) byte：256
(2) two bytes：65280
3 structures of byte 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 256-65280*2)/(16+4080*2+61440*3)=61680/192496=32%.
Save the formula of data volume：
T is total Block quantity, and S is burst capacity (Block Size), and the percentage of the flow of saving (only compares head Domain)：
During T ＜ 16：Without saving；Both bytes；
During 16 ＜ T ＜ 256：1-T*1/ (16*1+ (T-16) * 2), simple design needs 2 bytes, and preferred scheme is only Need a byte；
During 256 ＜ T ＜ 4096：1- (256*1+ (T-256) * 2))/(16*1+ (T-16) * 2), simple design needs 2 Individual byte, preferred scheme needs 2 bytes；
During 4096 ＜ T ＜ 65256：1-(256*1+(4096-256)*2+(T-4096)*3))/(256*1+(T-256)* 2), simple design needs 3 bytes, and preferred scheme needs 2 bytes.
During T ＞ 65256, without saving, preferred scheme embodiment of the present invention and simple design are required for 3 bytes.
In simple design, during using Put/Post orders, burst capabilities negotiation lacks efficiency.In Put/Post requests In, for first burst, it is necessary to send first data of burst and the burst capacity recommended, if sensor node is selected Different burst capacity, gateway needs to be resend according to the burst capacity of sensor, then the burst number that last time sends According to being wasted.And, gateway when asking to send the big resource of capacity based on burst option using Put/Post, prior nothing Method informs sensor resource capacity information, and in transmitting procedure, sensor side receives, and side caches received resource, if passed Sensor finds insufficient memory, and resource can only send back the error status code of 413 when not being transmitted, expression The resource of request is too big, terminates this time to transmit.The part resource for transmitting before this is then useless, and transfer resource is wasted.If Gateway can inform the capacity information of the resource to be transmitted of sensor in first fragmental messages, and sensor can then compare Resource capacity information and memory capacity, if off-capacity, return to the conditional code of 413 " resource of request is too big " to tie in advance Beam resource transmission, the purpose for saving transfer resource is reached with this.
Continue to download breakpoint transmission on internet, that is, the place to have been downloaded since 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 since 2000070 bytes：
GET/down.zip HTTP/1.0
User-Agent：NetFox
Range：Bytes=2000070-
Accept：Text/html, image/gif, image/jpeg, *；Q=.2, */*；Q=.2
Wherein, RANGE：Bytes=2000070-, the meaning of this line is exactly to tell this file of sensor down.zip Passed since 2000070 bytes, byte above is without passing.
The shortcoming of this scheme is that do not have burst mechanism, and the negotiation of burst capacity is not supported, and burst sum is not supported yet Consult.The embodiment of the present invention is considered during sliced transmission, carries out the negotiation of burst capacity and/or burst sum.For this The invention provides a kind of method of data fragmentation transmission, the precise volume of target data resource can be obtained, carry out burst appearance The negotiation of amount, obtains burst sum, and carry out transmitting data resources according to burst sum.
The flow of an embodiment of the present invention is illustrated referring to Fig. 1.Fig. 1 is the flow of an embodiment of the present invention Figure.
During S110, the capacity information of the data resource of node is obtained.If gateway is from sensors for data, Then the data resource capacity information of node is preserved on a sensor.Gateway can obtain node by request message to sensor Data resource capacity information.If gateway sends data to sensor, then gateway locally has been known for the number of node According to the capacity information of resource.Obtain node data resource capacity information, be for next step carry out burst capacity negotiation and really Determine burst sum to prepare.
Then, during S120, gateway sends the request message for carrying the first burst option, wherein institute to sensor Stating the first burst option includes the burst capacity recommended.Sensor in receiving S120 send request message after, according to from Body ability, determines the burst capacity used in this transmitting data resources process, and the burst capacity that sensor determines is small In the burst capacity recommended equal to gateway.
In S130, gateway receives the response message for carrying the second burst option, wherein the second burst option is included really Fixed burst capacity, the burst capacity of the burst capacity less than or equal to the recommendation of the determination.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, the data resource capacity information of burst capacity and the node according to 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 the burst capacity for determining to be used during transmission data, it is possible thereby to lower error rate in transmitting procedure is realized, and can be simultaneously Hair ground transmission data.
Process is implemented below in conjunction with Fig. 2 explanation embodiments as shown in Figure 1.What Fig. 2 was represented is gateway from sensor The illustrated examples of data are obtained, design of the invention is only illustrated, and not as limitation of the present invention.
Data resource acquisition process shown in Fig. 2 is described in detail below：
ES210：Gateway sends resource discovering and asks to sensor, i.e., biography is obtained by Get./wellknown/core The Resources list on sensor.
ES220：Sensor returns to the Resources list, and resource indication information to gateway；Resource indication information mainly includes Addressing information (i.e. URI), resource name, resource description information, content type of resource etc..The present invention enters to resource indication information Row extension, the resource indication information of extension includes：Resource is the configured information of dynamic resource or static resource.
ES230：The Resources list that gateway is returned according to sensor, according to the configured information of resource, therefrom selection target 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 to resource content to gateway；If resource capacity is more than a capacity for transport level messages, money is returned Source capacity information.Alternatively, sensor can be used burst option, according to the burst capacity that itself determines, directly return to first Burst.The burst capacity that subsequent client and sensor root are determined therefrom that, following burst is transmitted using burst option.
In a kind of alternate embodiment of the invention, if target data resource is dynamic data resource, while returning to dynamic Data resource is indicated to gateway, and indicates gateway that money is obtained 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 to gateway, and sends carrying burst choosing The request message of item, burst capabilities negotiation is carried out with sensor device, indicates the burst capacity recommended.
ES260：Sensor determines burst capacity, and be returned to gateway according to self-ability.Alternatively, sensor Burst sum is returned simultaneously.Certainly, because gateway has obtained data resource capacity information, burst sum can also be by gateway It is determined that.It should be noted that the burst capacity that the burst capacity that sensor 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 to 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 to 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 identification is obtained successfully, and carries 2 groups of resource indication informations；
REQ：GET/sensors/firmware- asks firmware resource
RES：413“Request Entity Too Large”Size：88000.413 conditional codes show the resource of request too Greatly, its precise volume is 88000 bytes.
If data resource is the process meeting dynamic change of dynamic resource, i.e. data resource in transmission, for example, can use Following two scheme implementation treatment：
(1) when transmission data resource is started, snapshot (Snapshot) is set up to the resource, that is, caches data money this moment The capacity information in source, and this capacity information is transmitted, 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 to, indicate data resource to change, gateway needs to reacquire.
Alternatively, gateway and sensor increase authentication information in interacting message.Identity can be included in authentication information (ID), the key information (Digest) that identity-based mark and password (Password) are calculated.Identity and password can be with It is to be pre-configured with to gateway and sensor both sides.Configuration process：
For example, the algorithm of key can be：Digest=MD5 (ID：Password), i.e., ID and Password is constituted Character string carries out Hash (Hash) using MD5 algorithms, and 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 Figure 2, it is necessary to know data resource capacity information.According to this A kind of embodiment is invented, gateway can obtain the data resource capacity information for being stored in sensor using following scheme.
(1) extension link form (Link-format) keyword
In Link-format, a keyword ,-sn, or-snapshot are extended, for obtaining data recourse requests Response in, show whether resource data is snapshot data.If this parameter does not exist, or its value is 0, is shown to be static money Source, if the value of this parameter is 1, it is dynamic resource to be shown to be current data, and the data of acquisition are current snapshots.Static state money Source refers to that metastable resource, i.e. resource content will not be changed frequently in a period of time.Concrete meaning can enter in a standard Row definition.In the present invention, the immovable situation of value of resource is referred mainly to.
Also extend keyword：- asz, shows the information of the accurate capacity of resource.
Message instance：
Gateway sends the request of resource discovering to sensor：
REQ：GET/.well-known/core--- transmit a request to the URI of acquiescence, i.e. root and obtains the Resources list
Sensor sends the response of resource to gateway：
RES：200OK -- response identification is obtained successfully, and carries 2 groups of resource indication informations
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, it is necessary 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 the instruction of Size Option, sensor is also indicated with SizeOption in the response Resource capacity, especially resource are than in the case of larger, sensor should be indicated.
If resource is smaller, sensor directly returns to resource data in message body (Body), then gateway should be with resource The actual capacity of data is defined, and the resource capacity shown in Size Option can be used for verification.
If resource is larger, sensor does not return to resource data, only with the capacity of Size Option returned datas, 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 explanation embodiments as shown in Figure 1.What Fig. 3 was represented is gateway to sensor The illustrated examples of data are sent, design of the invention is only illustrated, 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 selection one to be less than or equal to The burst capacity of the burst capacity of recommendation, and return in the response, meanwhile, first burst number of burst is returned in the response According to.Therefore, when NUM fields are 0,<Get>Request has a dual semanteme, and one is to obtain first fragment data, and two are point The negotiation of piece capacity.Ambiguity of the agreement in treatment 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 When seeking middle use Block Option, if NUM fields are arranged to 0, represent that both sides only carry out the negotiation of burst capacity, and The negotiation of burst sum.I.e. sensor in the response, burst sum is returned to using NUM fields, uses SZX field Returning sensors The burst capacity of determination.M field can remove, and a Bit be saved, for NUM fields.Because requesting party, such as gateway is known Burst sum, so from the NUM fields of burst it is known that whether the burst is last burst, therefore avoid the need for again Use M field.In this case, if first fragment data of 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 be in sound Burst sum middle should be returned using two bytes or three bytes.
When Block Option are 2 bytes, it is designed to SZX fields and takes second last three of byte, table Show burst capacity；NUM fields take first character section plus second first 5 of 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 to burst sum.
Burst capacity negotiation procedure illustrated below, message instance is：
Gateway sends the request of resource acquisition to sensor：
GET 00,000 101 (NUM is that 0, SZX is 101, i.e., 5,9 powers that burst capacity is 2 are represented, i.e., 512)
The response that sensor 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 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 be rung either in request message Answer in message, in addition to the burst capacity possibility used in first burst and last burst is different, others are divided Piece capacity is entirely the same.Repeat transmission identical NUM fields mutually and waste transfer resource.
In embodiments of the present invention, gateway exists<Get>When using Block Option in the request of method, if NUM quilts 0 is set to, represents that both sides only carry out the negotiation of burst capacity, and the total negotiation of burst.I.e. sensor in the response, is used NUM fields return to total burst number, the burst capacity determined using SZX fields Returning sensor.And gateway and sensor are double Burst capacity determined by side's storage, the fragment data transmission message for after.In addition to last fragment data.Net Close follow-up<Get>In the request of method, asked current slice sequence number is only sent, have determined and keep not without sending The burst capacity of change, and sensor is in the response message, also only sends current burst sequence number and corresponding with the burst sequence number Fragment data, burst capacity is not retransmited.In this case, when NUM is 1, first burst number of burst of request is represented According to, the like.
To use<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, NUM is that 0, SZX is second byte, represents burst capacity, and TotalNumber represents burst Sum, does not use, it is not necessary to carry in request；<Get>In response, NUM is that 0, SZX represents that the burst that sensor determines holds Amount, Total Number represent burst sum.
In the prior art, the interval of burst capacity is than larger, such as 2048,1024,512, underaction.And it is actual On, 512 for a Block, smaller, can just preferably be put into a UDP bag, i.e., 1472 bytes.This Invention is improved this, in one embodiment, for SZX, can take new formula, such as：(SZX+1) * 8, then It may range from：8~2048, but successively decrease at intervals of 8.
Structure (2) and structure (3) in Fig. 3 are used for<Get>When NUM is not for 0 situation, i.e. acquisition fragment data in request 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 (NUM is that 0, SZX is 101, i.e., 5,9 powers that burst capacity is 2 are represented, i.e., 512)
The response that sensor 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).
Redesigned by Block Option, can at least be reduced in each request or response and send 4 bits Position, in the case where burst is more, can be greatly enhanced efficiency of transmission, save transfer resource, at the same also improve gateway and The treatment effeciency of sensor both sides.
Fig. 4 shows a kind of alternate embodiment of the 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 sends to sensor<GET>Request, is carried out using burst option Burst capabilities negotiation, the burst capacity for indicating gateway to recommend.In ES460, sensor is selected 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 burst capacity of the burst capacity less than or equal to gateway recommendation for determining, NUM are that 0 expression gateway requests are complete Resource, not for 0 represents the specific the NUM fragment data of gateway requests, sensor can only use SZX fields to NUM when NUM is not 0 Indicated burst capacity.
Structure (2) and structure (3) return to the burst response message of full resource for sensor to gateway, if being directed to certain The response of individual specific 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, is that 1 expression is not last burst, NUM field lists if M field represents last burst for 0 Which burst show that sensor returned is.
It is illustrated below.Message instance is：
Gateway sends the request that data resource is obtained to sensor：
CON GET 00,000,000 00000101 (NUM is that 0, SZX is 101, i.e., 5,9 powers that burst capacity is 2 are represented, I.e. 512)
The response that sensor sends to gateway：
(NUM is that 1, M is 1 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：
(NUM is that 2, M is 1 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 to the ACK to CON；
Sensor sends last burst to gateway：
CON 200 00000110 (NUM is that 3, M is 0, represents the 3rd burst for sending, and is last burst, Specific burst capacity is calculated by actual read-out data).
Embodiment according to Fig. 4, when gateway obtains complete data resource from sensor, it is only necessary to complete burst appearance The negotiation of amount, and request is obtained without sending substantial amounts of fragment data, greatly save data transfer throughput.
Fig. 6 shows another alternate embodiment of the 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 sends to sensor with embodiment illustrated in fig. 2 difference<GET>Request, request Resource is obtained, using burst option, the burst capacity for indicating gateway to recommend, the value of now NUM fields filling is 0, represents request Obtain last burst；In ES660, the request of sensor response gateway returns to the burst capacity and last point for determining 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 to the sequence number and corresponding fragment data of the burst.ES670 and ES680 can be interacted repeatedly, until fragment data is passed It is totally lost complete.
The burst option used in Fig. 6 embodiments is as shown in fig. 7, for example with two burst options of byte, only include NUM fields and SZX fields.
Below in conjunction with Fig. 6 and Fig. 7 for example, message instance is：
Gateway sends the request of resource acquisition to sensor：
(NUM is 0 to CON GET 00,000,000 00000101, represents 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 the return information of first time, gateway has been known for one and has 8 bursts, and has obtained the 8th burst Data, gateway continue to sensor send CoAP ask, can obtain successively can also concurrently obtain remaining fragment data. Following message example is first fragment data of 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 to the ACK to CON, i.e., first data of 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 aforementioned preferred embodiments can be combined 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 shows using burst option to sensor transmission data, for example, uses asset creation (Post) or update (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, the burst capacity and burst sum for indicating to recommend using burst option, burst described herein are total Number is calculated based on the burst capacity recommended and the volumeter of data resource to be sent, does not carry specific in request message body Resource data.
ES820：If sensor is ready to receive this data, it is, for example, 100 (i.e. instruction client continuation to return to conditional code Send), while returning to the burst capacity 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, returning to error code instruction client should not continue to send data.Than Such as, the lack of memory capacity of sensor then returns to 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 to the burst capacity for determining.
ES860：Gateway sends and burst sequence number to sensor successively from total up to burst from 1 according to burst sequence number The fragment data of corresponding data resource, until complete end of transmission.
ES870：Sensor returns to the message for determining to receive, wherein 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 to 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 Putting can be using the same way described in reference picture 2 with interactive mode.
In order to improve efficiency of transmission, data traffic is saved, according to another 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 to response and inform gateway Whether continuation sends data.Sensor in the response, total burst number is returned to using NUM fields, is returned using SZX fields and sensed The burst capacity that device determines.And gateway and burst capacity, the fragment data for after determined by sensor both sides storage 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, has determined and keeps constant burst capacity without sending, and sensor is in response message In, current burst sequence number and fragment data corresponding with the burst sequence number is also only sent, burst capacity is not retransmited.This In the case of, when NUM is 1, first fragment data of burst of request is represented, the like.
In the case, the design and occupation mode of burst option is 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, it is necessary to be sent again with new SZX<Put>/<Post>Request, and the burst sum for recalculating is carried, Sensor beams back response again.After<Put>/<Post>In request and response, SZX fields are no longer carried.
Redesigned by burst option, can at least be reduced in each request or response and send 4 bits, In the case that burst is more, efficiency of transmission can be greatly enhanced, transfer resource 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 client device by sliced transmission data resource of the invention.Client shown in Fig. 9 Equipment 900 includes：Acquiring unit 910, for obtaining data resource capacity information；Transmitting element 920, burst is carried for sending The request message of option, wherein the burst option includes the burst capacity recommended, receiving unit 930 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 cell 950, use In the burst capacity for preserving the determination.So as to during transmitting data resources, it is not necessary to send SZX fields every time.
Another 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 server apparatus by sliced transmission data resource of the invention.Service shown in Figure 10 Device equipment 1000 includes：Receiving unit 1010, the request message of burst option is carried for receiving, wherein the burst option bag Include the burst capacity of recommendation；Transmitting element 1020, the response message of burst option is carried for sending, wherein the burst option Including the burst capacity for determining；With transmission unit 1030, for the burst capacity according to the determination, data described in sliced transmission Resource.
According to an embodiment of the present invention, transmitting element 1020 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 cell 1040, use In the burst capacity for preserving the determination.So as to during transmitting data resources, it is not necessary to send SZX fields every time.
Another 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 obtains resource, this avoid the possibility of error, it is also possible to which burst is concomitantly asked in realization, improves request of data Efficiency, and learn that the capacity of resource also allows for distributing memory space, calculate the quantity of burst.
Redesigned by burst option, at least can less send 4 bits in each request or response, divided In the case that piece is more, efficiency of transmission can be greatly enhanced, save transfer resource, while also improving the treatment effect of both sides Rate.
In the prior art, after the request for coming from client is received, 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 a change for 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 server in the request, 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 being received 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 corresponding manner option is represented：The disposable response disposably make an immediate response, postponed, postpone Multiple responses that multiple response and cancellation are postponed.Then, in S1120, client can be received and generated according to response mode option Response message.
In the prior art, after the request for coming from client is received, 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 a change for 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, can for example be indicated using the delay of byte (Deferred) option 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：The multiple responses cancelled and postponing are represented, that is, is unsubscribed.
For the subscription on 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 retardation time of slow disposable response or the deadlines of multiple responses of postponement, i.e., more than this time after, take automatically Disappear subscription.When C is 01, T represents the retardation time of the disposable response of postponement；When C is 10, T represents that the multiple of postponement is rung The deadline answered；When T is 00 or 11, T is nonsensical, is set to 0.
For this 6 bits, the numerical value between 0~63 can be represented, it is assumed that be T, can be shown with 2 T powers This time span, in seconds, you can to represent 1~2^63 seconds.Such as：
0：2^0=1 seconds；
1：2^1=2 seconds；
2：2^2=4 seconds；
3：2^3=8 seconds
4：2^4=16 seconds；
63：2^63 seconds.
In the prior art, Max_Age fields 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 limitation, 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 of response is suitable according to the size of message identifier Sequence.
Another embodiment of the invention, it is possible to use Token (token) options indicate 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 embodiment of the invention, can alternatively or additionally increase timestamp (Timestamp) option, with Postpone option and individually or in combination indicate response mode.Specifically, client can in the request carry timestamp Option, the timestamp option includes the value of deadline, it is desirable to which server returns to response within the specified time；Service Device in the response message, carries timestamp option, shows the time of response message generation, and so, client can be based on the time Option is stabbed to judge the order of response message.
In an embodiment of the present invention, the design of the timestamp option can be represented with 1~6 byte, If the time for representing is short, with a byte, if the time is long, with 3 bytes or 6 bytes.Specific method for expressing example It is such as following two：
(1) represented with year, month, day, hour, min, second, first character section represents year, second byte representation month, the 3rd Byte representation day, the 4th byte representation hour, the 5th byte representation minute, the 6th byte representation second, for time, example Such as can 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, It is shown to be 2001, can at most represents 2063.
(2) three bytes all represent that maximum can represent 2^24-1 seconds, about 136 years with the second.
Thus, client is known that the order of the response message of return, it is to avoid mistake caused by data transfer delay.
Figure 12 is a kind of block diagram of the embodiment of client device for transmitting data resource of the invention, wherein described Client device 1200 includes：Sending module 1210, the request message of response mode option is carried for sending；And receiver module 1220, for receiving the response message generated according to the response mode option.
Process described by embodiments of the invention and feature described in reference picture 11 are applied to the client shown in Figure 12 End equipment.Specifically, for example, the response mode option carried in the request message of the transmission of sending module 1210 can be postponed Option, for example can be：The disposable response disposably make an immediate response, postponed, the multiple responses and cancellation postponement postponed Multiple responses.
According to a kind of embodiment, the response mode option carried in the request message that sending module 1210 sends can be represented The retardation time of the disposable response postponed or the deadline of multiple responses of postponement.
According to a kind of embodiment, sending module 1210 sends the request message for carrying timestamp option, and the timestamp is represented Receive the deadline of response；Receiver module 1220 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 1220 in the response message for receiving determines response The order of message.
Figure 13 is a kind of embodiment of server apparatus for transmitting data resource of the invention, wherein the server Equipment 1300 includes：Receiver module 1310, the request message of response mode option is carried for receiving；With sending module 1320, Send the response message generated according to the response mode option.
Process described by embodiments of the invention and feature described in reference picture 11 are applied to the service shown in Figure 13 Device equipment.Specifically, for example, the response mode option carried in the request message of the reception of receiver module 1310 can be postponed Option, for example can be：The disposable response disposably make an immediate response, postponed, the multiple responses and cancellation postponement postponed Multiple responses.
According to an embodiment of the present, the response mode option carried in the request message that receiver module 1310 is received The deadline of the retardation time of the disposable response of postponement or multiple responses of postponement can be represented.
According to an embodiment of the present, the postponement option in the request message that receiver module 1310 is received represents postponement Multiple responses and multiple responses for postponing between time interval, and the postponement in the response message that sending module 1320 sends Option represents the multiple responses cancelled and postponing.
Another embodiment of the invention, can carry timestamp choosing in the request message that receiver module 1310 is received , the timestamp option represents the deadline for receiving response, and can also be taken in the response message that sending module 1320 sends Band timestamp option, the timestamp option represents the generation time of response message.
Those of ordinary skill in the art are it is to be appreciated that the list of each example described with reference to the embodiments described herein Unit and algorithm steps, can be realized, with electronic hardware, computer software or the combination of the two in order to clearly demonstrate hardware With the interchangeability of software, the composition and step of each example are generally described according to function in the above description.This A little functions are performed with hardware or software mode actually, depending on the application-specific and design constraint of technical scheme.Specially Industry technical staff can realize described function to each specific application using distinct methods, but this realization is not It is considered as beyond the scope of this invention.
The method that is described with reference to the embodiments described herein can use hardware, computing device the step of algorithm Software module, or the two combination is implemented.Software module can be placed in random access memory (RAM), internal memory, read-only storage (ROM), electrically programmable ROM, electrically erasable ROM, register, hard disk, moveable magnetic disc, CD-ROM or technical field In any other form of storage medium well known to interior.
Although having shown that and describing some embodiments of the present invention, it is understood by one skilled in the art that not departing from In the case of principle of the invention and spirit, these embodiments can be carried out with various modifications, such modification should fall into the present invention In the range of.

Claims (23)

  1. It is 1. a kind of that method of the lightweight application layer protocol by sliced transmission server data resource is based in Internet of things system, It is characterised in that it includes：
    User end to server sends resource acquisition request, and the first capacity Option Field, institute are carried in the resource acquisition request State the capacity that the first capacity Option Field is used to indicate the server returned data resource；
    The client receives the resource acquisition response that the server is returned, and the second capacity is carried in the resource acquisition response Option Field, the second capacity Option Field is used to indicate the capacity of the data resource；
    The client sends the request message for carrying the first burst option to the server, wherein the first burst option Including the burst capacity recommended；
    The client receives the response message that the server carries the second burst option, wherein the second burst option bag Include the burst capacity of determination, the burst capacity of the burst capacity less than or equal to the recommendation of the determination；
    The client receives institute according to the capacity of the data resource of the burst capacity and the server of the determination, burst State the data resource of server；
    Wherein, the capacity of the data resource of the burst capacity and the server according to the determination, burst receives institute The data resource for stating server includes：
    The resource transmission message for carrying the 3rd burst option is received, wherein the 3rd burst option only includes burst sequence number, and And the resource transmission message carries the fragment data of the data resource of the server corresponding with the burst sequence number.
  2. 2. the method for claim 1, it is characterised in that the resource acquisition response also includes indicating asked service The too big conditional code of the data resource capacity of device.
  3. 3. method as claimed in claim 2, it is characterised in that the method also includes：
    The client receives the configured information for indicating static resource or dynamic data resource, if dynamic resource, then working as Preceding snapshot form represents the capacity of the data resource of the server.
  4. 4. the method for claim 1, it is characterised in that the transmission carries the request message bag of the first burst option Include：
    The request message for carrying the first burst option is sent, wherein the first burst option also data including the server The capacity of resource.
  5. 5. the method for claim 1, it is characterised in that
    The request message for sending the first burst option of carrying includes：
    The request message for carrying the first burst option is sent, wherein the first burst option includes only consulting the finger of burst capacity Show information；
    The response message for receiving the second burst option of carrying includes：
    The response message for carrying the second burst option is received, wherein the second burst option only includes the burst capacity for determining.
  6. 6. the method for claim 1, it is characterised in that
    In the request message for sending the first burst option of carrying, also carry and ask the uniform resource identifier of resource and be used for Associate the token of fragmental messages；
    In the message of the data resource for transmitting the server, only transmission associates the token of fragmental messages.
  7. 7. the method for claim 1, it is characterised in that
    The capacity of the data resource of the burst capacity and the server according to the determination, burst receives the service The data resource of device includes：
    The capacity of the data resource of burst capacity and the server according to the determination, sequentially or in parallel burst reception The data resource of the server.
  8. 8. the method for claim 1, it is characterised in that
    The request message for sending the first burst option of carrying includes：
    The request message for carrying the first burst option is sent, wherein the first burst option includes obtaining last burst The configured information of data；
    The response message for receiving the second burst option of carrying includes：
    The response message for carrying the second burst option is received, wherein the second burst option includes burst sum, and it is described Response message carries the fragment data of the data resource of the server corresponding with last burst；
    The capacity of the data resource of the burst capacity and the server according to the determination, burst receives the service The data resource of device includes：
    The burst of the data resource of the server corresponding with other burst sequence numbers is obtained according to burst capacity and burst sum Data.
  9. 9. the method for claim 1, it is characterised in that also include：
    The client sends the request message for carrying authentication information；
    The client receives the response message for carrying the information for indicating certification to pass through.
  10. 10. the method for claim 1, it is characterised in that
    The request message for carrying the first burst option is sent, wherein the first burst option includes burst sum, or
    The response message for carrying the second burst option is received, wherein the second burst option includes burst sum.
  11. A kind of 11. sides of the data resource that sliced transmission server is passed through based on lightweight application layer protocol in Internet of things system Method, it is characterised in that
    Server receives the resource acquisition request that client sends, and the first capacity option word is carried in the resource acquisition request Section, the first capacity Option Field is used to indicate the capacity of the server returned data resource；
    The server sends resource acquisition and responds to the client, and the second capacity option is carried in the resource acquisition response Field, the second capacity Option Field is used to indicate the capacity of the data resource；
    The server receives the request message for carrying the first burst option, wherein the first burst option includes that recommends divides Piece capacity,
    The server sends the response message for carrying the second burst option, wherein the second burst option includes that what is determined divides Piece capacity, the burst capacity of the burst capacity less than or equal to the recommendation of the determination；
    The server sends institute according to the capacity of the data resource of the burst capacity and the server of the determination, burst State the data resource of server；
    Wherein, the capacity of the data resource of the burst capacity and the server according to the determination, burst sends institute The data resource for stating server includes：
    The resource transmission message for carrying the 3rd burst option is sent, wherein the 3rd burst option only includes burst sequence number, and And the resource transmission message carries the fragment data of the data resource of the server corresponding with the burst sequence number.
  12. 12. methods as claimed in claim 11, it is characterised in that the capacity of the data resource according to the server for receiving is carried out Judge, if the capacity of the data resource of server is more than the memory capacity of itself, sends and indicate the data resource of server to hold The too big conditional code of amount.
  13. 13. methods as claimed in claim 11, it is characterised in that
    The request message for receiving the first burst option of carrying includes：
    The request message for carrying the first burst option is received, including the configured information of the data for obtaining last burst；
    The response message for sending the second burst option of carrying includes：
    The response message for carrying the second burst option is sent, wherein the second burst option includes burst sum, and it is described Response message carries the fragment data of the data resource of the server corresponding with last burst；
    The capacity of the data resource of the burst capacity and the server according to the determination, burst sends the service The data resource of device includes：
    The burst of the data resource of the server corresponding with other burst sequence numbers is sent according to burst capacity and burst sum Data.
  14. 14. methods as claimed in claim 11, it is characterised in that
    The request message for receiving the first burst option of carrying includes：
    The request message for carrying the first burst option is received, wherein the first burst option includes only consulting the finger of burst capacity Show information；
    The response message for sending the second burst option of carrying includes：
    The response message for carrying the second burst option is sent, wherein the second burst option only includes the burst capacity for determining.
  15. 15. methods as claimed in claim 11, it is characterised in that
    The capacity of the data resource of the burst capacity and the server according to the determination, burst sends the service The data resource of device includes：
    The capacity of the data resource of burst capacity and the server according to the determination, sequentially or in parallel burst transmission The data resource of the server.
  16. A kind of 16. visitors of the data resource that sliced transmission server is passed through based on lightweight application layer protocol in Internet of things system Family end equipment, it is characterised in that the client device includes：
    Transmitting element, is asked for sending resource acquisition to server, and the first capacity option is carried in the resource acquisition request Field, the first capacity Option Field is used to indicate the capacity of the server returned data resource；
    Receiving unit, for receiving the resource acquisition response that the server is returned, carries the second capacity in the resource response Option Field, the second capacity Option Field is used to indicate the capacity of the data resource；The transmitting element, is additionally operable to hair The request message for carrying the first burst option is sent, wherein the first burst option includes the burst capacity recommended,
    The receiving unit, is additionally operable to receive the response message for carrying the second burst option, wherein the second burst option bag Include the burst capacity of determination, the burst capacity of the burst capacity less than or equal to the recommendation of the determination；
    Transmission unit, for burst capacity and the capacity of the data resource of the server according to the determination, burst connects Receive the data resource of the server；
    Wherein, the transmission unit specifically for：
    The resource transmission message for carrying the 3rd burst option is received, wherein the 3rd burst option only includes burst sequence number, and And the resource transmission message carries the fragment data of the data resource of the server corresponding with the burst sequence number.
  17. 17. client devices as claimed in claim 16, it is characterised in that
    Burst receives the data resource of the server to the transmission unit successively or concomitantly.
  18. 18. client devices as claimed in claim 16, it is characterised in that the equipment also includes：
    Memory cell, the burst capacity for preserving the determination.
  19. 19. client devices as claimed in claim 16, it is characterised in that the equipment also includes：
    Authentication unit, for sending and receiving authentication information.
  20. A kind of 20. clothes of the data resource that sliced transmission server is passed through based on lightweight application layer protocol in Internet of things system Business device equipment, it is characterised in that the server apparatus include：
    Receiving unit, the resource acquisition request for receiving client transmission, the first capacity is carried in the resource acquisition request Option Field, the first capacity Option Field is used to indicate the capacity of the server returned data resource；
    Transmitting element, is responded for sending resource acquisition to the client, and the second capacity option is carried in the resource response Field, the second capacity Option Field is used to indicate the capacity of the data resource；
    The receiving unit, is additionally operable to receive the request message for carrying the first burst option, wherein the first burst option bag The burst capacity of recommendation is included,
    The transmitting element, is additionally operable to send the response message for carrying the second burst option, wherein the second burst option bag Include the burst capacity of determination, the burst capacity of the burst capacity less than or equal to the recommendation of the determination；
    Transmission unit, for burst capacity and the capacity of the data resource of the server according to the determination, burst hair Send the data resource of the server；
    Wherein, the transmission unit specifically for：
    The resource transmission message for carrying the 3rd burst option is sent, wherein the 3rd burst option only includes burst sequence number, and And the resource transmission message carries the fragment data of the data resource of the server corresponding with the burst sequence number.
  21. 21. server apparatus as claimed in claim 20, it is characterised in that
    The transmission unit is used for the capacity according to the burst capacity of the determination and the data resource of the server, on one's own initiative Burst sends the data resource of the server.
  22. 22. server apparatus as claimed in claim 20, it is characterised in that the server apparatus also include：
    Memory cell, the burst capacity for preserving the determination.
  23. 23. server apparatus as claimed in claim 20, it is characterised in that the server apparatus also include：
    Authentication unit, for receiving and sending authentication information.
CN201210054892.4A 2011-03-17 2012-03-02 The method and apparatus of transmitting data resources Active CN102685203B (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN201710132013.8A CN106850841B (en) 2011-03-17 2012-03-02 Method and device for transmitting data resources
CN201210054892.4A CN102685203B (en) 2011-03-17 2012-03-02 The method and apparatus of transmitting data resources
CN201710131638.2A CN107070990B (en) 2011-03-17 2012-03-02 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
CN201210054892.4A CN102685203B (en) 2011-03-17 2012-03-02 The method and apparatus of transmitting data resources

Related Child Applications (2)

Application Number Title Priority Date Filing Date
CN201710132013.8A Division CN106850841B (en) 2011-03-17 2012-03-02 Method and device for transmitting data resources
CN201710131638.2A Division CN107070990B (en) 2011-03-17 2012-03-02 Method and device for transmitting data resources

Publications (2)

Publication Number Publication Date
CN102685203A CN102685203A (en) 2012-09-19
CN102685203B true CN102685203B (en) 2017-07-07

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
CN201710131638.2A Active CN107070990B (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
CN201710131415.6A Active CN106878442B (en) 2011-03-17 2012-03-06 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

Family Applications Before (3)

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
CN201710131638.2A Active CN107070990B (en) 2011-03-17 2012-03-02 Method and device for transmitting data resources

Family Applications After (3)

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
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

Country Status (1)

Country Link
CN (7) CN102130954A (en)

Families Citing this family (39)

* Cited by examiner, † Cited by third party
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
CN107960151B (en) * 2015-05-04 2020-11-06 瑞典爱立信有限公司 Response device and request device in wireless communication system and implementation method thereof
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
WO2021126024A1 (en) * 2019-12-17 2021-06-24 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)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1905518A (en) * 2005-07-29 2007-01-31 北京航空航天大学 Method for ensuring reliable transmission of data exhange
CN101102282A (en) * 2007-08-08 2008-01-09 中兴通讯股份有限公司 A transmission and receiving method for data broadcast service
CN101729593A (en) * 2008-11-03 2010-06-09 北大方正集团有限公司 Method, system and device for uploading and receiving file

Family Cites Families (28)

* Cited by examiner, † Cited by third party
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
US7698623B2 (en) * 2004-08-13 2010-04-13 David Hedberg Systems and methods for decreasing latency in a digital transmission system
CN100349088C (en) * 2005-07-26 2007-11-14 华为技术有限公司 Digital information controlling method
PL1949584T3 (en) * 2005-10-28 2019-09-30 Viasat, Inc. Adaptive coding and modulation for broadband data transmission
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
CN101335742B (en) * 2007-06-25 2011-09-21 中兴通讯股份有限公司 Directory access system and method under lightweight directory access protocol
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
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
CN101635744B (en) * 2009-08-26 2012-08-29 华为技术有限公司 Method and system for transmitting data and relative equipment
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

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1905518A (en) * 2005-07-29 2007-01-31 北京航空航天大学 Method for ensuring reliable transmission of data exhange
CN101102282A (en) * 2007-08-08 2008-01-09 中兴通讯股份有限公司 A transmission and receiving method for data broadcast service
CN101729593A (en) * 2008-11-03 2010-06-09 北大方正集团有限公司 Method, system and device for uploading and receiving file

Also Published As

Publication number Publication date
CN102685203A (en) 2012-09-19
CN107071826A (en) 2017-08-18
CN102685204B (en) 2017-04-26
CN106850841B (en) 2020-11-17
CN106850841A (en) 2017-06-13
CN102130954A (en) 2011-07-20
CN106878442A (en) 2017-06-20
CN102685204A (en) 2012-09-19
CN107070990B (en) 2021-04-09
CN107070990A (en) 2017-08-18
CN106878442B (en) 2020-12-04
CN107071826B (en) 2020-07-07

Similar Documents

Publication Publication Date Title
CN102685203B (en) The method and apparatus of transmitting data resources
US11064330B2 (en) Methods for enabling delay-awareness in the constrained application protocol (CoAP)
CN109471744B (en) Main chain and parallel multi-sub-chain system architecture based on block chain
CA2604898C (en) System and method of message traffic optimization
US20130179557A1 (en) Method and management apparatus for performing operation on device resource
CN106411843A (en) Server initiated remote device registration
Rayes et al. IoT protocol stack: a layered view
JP7246379B2 (en) Service layer message templates in communication networks
CN108270745A (en) A kind of method for pushing of service customizing information, terminal and master control bluetooth equipment
CN108023921A (en) The cut-in method and device of a kind of third-party platform
EP1716675B1 (en) Method for inserting a new device in a community of devices
CN113056759A (en) Method and system for network devices to obtain a trusted status representation of the status of a distributed ledger technology network
CN104981791A (en) Mobile sender controlled data access and data deletion method and system
Iglesias-Urkia et al. Enhanced publish/subscribe in CoAP: describing advanced subscription mechanisms for the observe extension
Shen et al. S-SurF: an enhanced secure bulk data dissemination in wireless sensor networks
EP3026860B1 (en) Method and system for transmission management of full configuration synchronization between eml-nml
CN105681892B (en) The method, apparatus and system of differential data transmission
CN107483424B (en) Processing method and device of remote procedure call protocol
KR101028609B1 (en) Method of Secure and Efficient Networks Management Scheme based Multi RFIDs for Ubiquitous Environment.
CN109462591A (en) A kind of data transmission method, method of reseptance, apparatus and system
CN116228417B (en) Block chain-based data transaction method, device, system and medium for Internet of things
CN114189384B (en) Service processing method, device, equipment and storage medium
KR20180081331A (en) Constrained application protocol compression communication system
WO2017040940A1 (en) Improved block transfer operation in coap protocol
JP2024015458A (en) Communication devices, communication methods and communication systems

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