WO2017040948A1 - Activation de la flexibilité temporelle pour le transfert de blocs dans le protocole coap - Google Patents

Activation de la flexibilité temporelle pour le transfert de blocs dans le protocole coap Download PDF

Info

Publication number
WO2017040948A1
WO2017040948A1 PCT/US2016/050134 US2016050134W WO2017040948A1 WO 2017040948 A1 WO2017040948 A1 WO 2017040948A1 US 2016050134 W US2016050134 W US 2016050134W WO 2017040948 A1 WO2017040948 A1 WO 2017040948A1
Authority
WO
WIPO (PCT)
Prior art keywords
deadline
transfer process
block transfer
network
coap
Prior art date
Application number
PCT/US2016/050134
Other languages
English (en)
Inventor
Xu Li
Lijun Dong
Quang Ly
Zhuo Chen
Shamim Akbar Rahman
Guang Lu
Chonggang Wang
Original Assignee
Convida Wireless, Llc
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 Convida Wireless, Llc filed Critical Convida Wireless, Llc
Publication of WO2017040948A1 publication Critical patent/WO2017040948A1/fr

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/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • 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/04—Protocols specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • CoRE Constrained Application Protocol
  • IoT Internet of Things
  • CoAP Hypertext Transfer Protocol
  • FIG. 1 a CoAP Messages Layer for handling UDP, though with different reliability requirements than typical UDP; and a Request/Response Layer that uses Methods - GET, PUT, POST, DELETE - and Request/Response codes for handling the asynchronous nature of the network interactions.
  • both the messages layer and the request/response layer are features of the CoAP header.
  • CoAP defines four types of messages: CON, NON, ACK, and RST.
  • Confirmable message is retransmitted using a default timeout and exponential back-off between retransmissions until the recipient sends back an Acknowledgement message (ACK) with the same Message ID.
  • FIG. 2 shows an example of a CON with ACK of the same Message ID 0x7d34.
  • a Non-confirmable message does not require reliable transmission. For example, each single measurement out of a stream of sensor data can be sent as a NON. NONs are not acknowledged, but still have a Message ID for duplicate detection. An example of a NON with Message ID 0x0 laO is shown in FIG. 3. An ACK is used to acknowledge receipt of a CON.
  • a Reset message may be used when a recipient is not able to process a NON.
  • CoAP defines four methods: GET, POST, PUT, and DELETE.
  • the GET method retrieves a representation for the information that currently corresponds to the resource identified by the request Uniform Resource Identifier (URI). Upon success, a 2.05 (Content) or 2.03 (Valid) response code should be present in the response.
  • URI Uniform Resource Identifier
  • the POST method requests that the representation enclosed in the request be processed.
  • the actual function performed by the POST method is determined by the origin server and dependent on the target resource. POST usually results in a new resource being created or the target resource being updated.
  • the PUT method requests that the resource identified by the request URI be updated or created with the enclosed representation. If a resource exists at the request URI, the enclosed representation should be considered a modified version of that resource, and a 2.04 (Changed) response code should be returned. If no resource exists, then the server may create a new resource with that URI, resulting in a 2.01 (Created) response code.
  • the DELETE method requests that the resource identified by the request URI be deleted.
  • CoAP request and response semantics are carried in CoAP messages.
  • a Token is used to match responses to requests independently from the underlying messages.
  • FIG. 4 shows an example of the synchronous case.
  • the response to this request will be directly carried in the resulting ACK. This is called a "piggy-backed response.” If the CoAP Client that issued the request in a CON does not receive an ACK within an ACK timer, it will retransmit the request using an exponential back-off algorithm and double the ACK timer to wait for CoAP Server's Response. If a request is sent in a NON, then the response is sent using a new NON.
  • FIG. 5 shows an example of the asynchronous case.
  • the client when a request is carried in a CON, the client will receive an ACK without a payload. Later, when the requested content becomes available, the server will issue a new CON that includes the response to the client's initial CON request.
  • the token "0x73" is used to associate the response with the previous request.
  • CoAP defines a number of options that may be included in a message. Each Option instance in a message specifies the Option Number of the defined CoAP Option, the length of the Option Value, and the Option Value itself. Option Value can be empty, opaque, an unsigned integer, or a string. Both requests and responses may include a list of one or more Options. CoAP defines a single set of Options that are used in both requests and responses.
  • Options are either "critical” or "elective".
  • An Option is identified by an Option Number, which also provides some additional semantics information. For example, odd numbers indicate a critical Option, while even numbers indicate an elective Option. The difference between these is how an Option unrecognized by an endpoint is handled. Upon reception, unrecognized Options of class "elective” must be silently ignored. Unrecognized Options of class "critical" that occur in a CON request must cause the return of a 4.02 (Bad Option) response.
  • Unrecognized Options of class "critical" that occur in a CON response, or piggy -backed in an ACK, must cause the response to be rejected (according to RFC7252, rejecting a Confirmable message is effected by sending a matching Reset message and otherwise ignoring it).
  • Unrecognized Options of class "critical" that occur in a NON must cause the message to be rejected.
  • Table 1 displays the properties of CoAP Options using two examples defined in the current CoAP block-transfer specification: Blockl and Block2.
  • CoAP Options are maintained by an Internet Assigned Numbers Authority (IANA) registry.
  • IANA Internet Assigned Numbers Authority
  • the IANA policy for future additions to this sub-registry is split into three tiers: range [0-255] is reserved for Options defined by the IETF; range [256-2047] is reserved for commonly used Options with public specifications; and range [2048-64999] is for all other Options, including private or vendor-specific Options.
  • CoAP is a Representational State Transfer (RESTful) transfer protocol for use with constrained nodes and networks. Basic CoAP messages work well for small data transfers, such as temperature sensors, light switches, and similar building-automation devices.
  • Protocols like HTTP may rely on transport protocols like TCP to perform the low-level work
  • CoAP is based on simpler datagram transports like UDP.
  • HTTP relies on TCP to divide large payloads into multiple packets and ensure that all packets arrive and are handled in the correct order.
  • UDP has a size limit on resource
  • IP fragmentation is limited to a size of 64 KiB and is not well-suited for constrained applications and networks.
  • request-response pairs refers to the messaging paradigm of the CoAP Messages Layer: a "request message” typically refers to a CON with an included GET, PUT, or POST request; and a “response message” typically refers to a response piggy-backed in the corresponding ACK. Further, the term “payload” refers to the actual content of a single CoAP message, while the term “body” refers to the entire resource representation being transferred in block-wise fashion.
  • Blockl has two Block Options defined to enable block- wise transfers: "Blockl” and "Block2".
  • Blockl pertains to the request payload
  • Block2 Option pertains to the response payload.
  • control usage the amount of the payload that the payload will be formed in the response to the GET request.
  • Each Block Option may need to include three items of information: block size ("SZX”); whether more blocks will follow the current message's block (“M”); and the relative number of the block within a sequence of blocks with the given size (“NUM”).
  • SZX block size
  • M whether more blocks will follow the current message's block
  • NUM the relative number of the block within a sequence of blocks with the given size
  • the block size is represented as a three-bit unsigned integer, and the allowed values of SZX are [0-6].
  • the "more blocks” flag is represented as a single bit, meaning it may only have a value of 0 or 1.
  • M When a Blockl or Block2 is used for "control usage,” then M must be set to 0.
  • the block number indicates the block number being requested or provided.
  • FIG. 7 shows an example illustrating how to use Block2 in GET requests and responses.
  • the whole resource body has been retrieved from Server by using three request-response pairs in a block transfer process.
  • FIG. 7 shows Block2 usage in both the descriptive usage context and the control usage context.
  • NUM 0 indicates that the ACK payload contains the first block
  • M 1 indicates that more blocks need to be transferred
  • SZX 128 indicates that the block size is 128 bytes.
  • M has no function and is set to 0
  • SZX will likely be the size of the previous block, or SZX will be a suggested block size if the Client has not yet received any blocks.
  • FIG. 8 shows an example illustrating how to use the Blockl Option in PUT requests and responses.
  • FIG. 9 shows an example CoAP block transfer process.
  • each block is transmitted, by default, immediately one after another.
  • CoAP' s block transfer mechanism is needed when M2M/IoT applications intend to transfer large payloads using CoAP. During current block transfers, each block of data is transmitted immediately one after another regardless of any changing network conditions.
  • the current CoAP block transfer process may not function in an optimal manner, wasting time and resources.
  • the block transfer process may be executed in a more adaptive manner.
  • Embodiments disclosed herein provide modifications to the existing block transfer mechanism to minimize waste associated with excess load and congestion.
  • two new Block Options are introduced to indicate client and server time requirements with regard to the current block transfer process.
  • two other new Block Options are introduced to indicate when the next block should be transferred.
  • FIG. 1 illustrates the interaction model of the CoAP protocol
  • FIG. 2 shows an example message flow in accordance with the CoAP protocol
  • FIG. 3 shows another example message flow in accordance with the CoAP protocol
  • FIG. 4 shows another example message flow in accordance with the CoAP protocol
  • FIG. 5 shows another example message flow in accordance with the CoAP protocol
  • FIG. 6 illustrates the format of CoAP Block Options, Blockl and Block2
  • FIG. 7 shows an example message flow in accordance with using the CoAP Block2 Option
  • FIG. 8 shows an example message flow in accordance with using the CoAP Blockl Option
  • FIG. 9 shows an example message flow in accordance with the CoAP block transfer process
  • FIGs. 10A and 10B illustrate an example work flow in accordancd with one embodiment of a method for a CoAP block transfer process using CoAP Options Deadline 1, Deadline2, DeadlineForNext, and SuspendForNext;
  • FIG. 11 A is a system diagram of an example machine-to-machine (M2M), Internet of Things (IoT), or Web of Things (WoT) communication system in which one or more disclosed embodiments may be implemented;
  • M2M machine-to-machine
  • IoT Internet of Things
  • WoT Web of Things
  • FIG. 1 IB is a system diagram of an example architecture that may be used within the M2M/IoT/WoT communications system illustrated in FIG. 11 A;
  • FIG. 11C is a system diagram of an example communication network apparatus, such as an M2M/IoT/WoT device, gateway, or server that may be used within the
  • FIG. 1 ID is a block diagram of an example computing system in which a node of the communication system of FIGs. 11 A and 1 IB may be embodied; and [0048] FIG. 12 shows an example graphical user interface (GUI) in accordance with an example embodiment.
  • GUI graphical user interface
  • CoAP' s block transfer mechanism is needed when M2M/IoT applications intend to transfer large payloads using CoAP.
  • each block of data is transmitted immediately one after another until all blocks have been received. Transferring each block immediately after the previous block can become inefficient and burdensome with dynamically changing resources and networks.
  • the existing CoAP block transfer process does not consider any time-related flexibility or constraints. Such considerations become necessary when attempting to facilitate block transfers during dynamically changing network conditions. Accordingly, instead of conducting a transfer process in an "as-soon-as-possible" manner (which is the default approach adopted in the existing solution), it is desirable to allow for a block transfer process that can adaptively be suspended, resumed, or slowed as long as the process is still completed within deadlines set by both the client and server. To achieve this adaptive transferring, embodiments are proposed that allow the client and server to convey time-related flexibility and constraints (e.g., deadlines, etc.) to each other during a block transfer process.
  • time-related flexibility and constraints e.g., deadlines, etc.
  • two new block options are used to indicate the client's and server's respective deadline requirements to complete an ongoing block transfer process:
  • Deadlinel and Deadline2.
  • the Deadlinel option is used for the client's expected deadlines, while Deadline2 is used for the server's expected deadlines.
  • the Deadlinel option when the Deadlinel option is in a request message from a client, it indicates the client's expected deadline for the current block transfer process.
  • the client may proactively assert Deadlinel to the server, or the client may provide Deadlinel at the server's request.
  • Deadlinel when Deadlinel is included in a response message from a server, it indicates the server's request for the client's expected deadline for the current block transfer process; in this case, Deadlinel is set to zero.
  • the client may ignore the server's request for a deadline.
  • Deadline2 when the Deadline2 option is in a response message from a server, it indicates the server's estimated deadline for the current block transfer process.
  • Deadline2 when Deadline2 is included in a request message from a client, it indicates the client's request for the server's expected deadline for the current block transfer process; in this case, Deadline2 is set to zero.
  • both the client and server can specify their current timing needs or requirements for the block transfer process.
  • the client is able to include the deadline options in messages at any time during the block transfer process so that the client can decide how best to proceed with the rest of the block transfer process, e.g., how fast to send out subsequent request messages, when to send out, etc.
  • the specific operation behavior will depend on various scenarios and needs.
  • Exchanging deadline information also allows the client and server to negotiate a deadline favorable to both parties.
  • policies to select a deadline favorable to both parties include policies to select a deadline favorable to both parties.
  • the following policies are provided as examples only and should not be construed to be limiting of the scope of the present disclosure or claims.
  • both the client and server can indicate their own deadline requirements. If they do so, then the "coordinated deadline,” or deadline for the entire process to conclude, should be the earlier submitted deadline. This allows the client to complete the block transfer process in a time favorable to both parties.
  • the client and server may also indicate Deadlinel and Deadline2 options multiple times throughout the block transfer process, and newly received deadline values (included in either a Deadlinel or Deadline2) will override previous deadlines values if they exist.
  • the block transfer process will terminate. Therefore, if both the client and server wish to complete a block transfer process before termination and are currently unable to, they need to determine a new coordinated deadline.
  • Table 2 shows the implementation details of one embodiment of a definition for the new Deadlinel and Deadline2 CoAP Options.
  • the proposed options may be included in the No. 33 and No. 35 CoAP block options within the headers of the request and response messages, respectively. Note that assigning Nos. "33" and "35" to these new Options is presented solely for purposes of example and should not be construed to limit the Options to these specific numbers.
  • the Deadlinel and Deadline2 options proposed in the previous section may be used for indicating expected deadlines for the whole block transfer process. Instead of or in addition to those deadlines options, a client and server may wish to determine time-related constraints for transferring individual blocks during a block transfer process. In particular, the client and server may wish to set the latest time deadline for sending out the next message, or they may wish to suspend transmission of the next message for a specified amount of time. Suspending message transmission may be beneficial if either the client or server is experiencing temporary processing and/or storage capacity limitations that would hinder processing of a new message or block. For example, a server may signal a client not to transfer the next block within the next one minute because the server does not currently have enough cache space.
  • a client may signal a server not to transfer a block for a specified time because the client is about to go to sleep for that specified time.
  • Sleeping is a common operation for constrained M2M/IoT devices, yet the existing block transfer specification does not consider any sleepy-node-related issues.
  • the ability to set a deadline for a next transfer or suspend a transfer for a period of time allows the block transfer process to be executed more effectively than the current block transfer process when utilizing sleepy M2M/IoT nodes.
  • two new block options are used to set time-related constraints to individual block transfers: DeadlineForNext and SuspendForNext.
  • DeadlineForNext In one embodiment, two new block options are used to set time-related constraints to individual block transfers: DeadlineForNext and SuspendForNext.
  • DeadlineForNext may be used by either the client or server to set the deadline for the next request message.
  • SuspendForNext may be used by either the client or server to set a time interval before the next message should be sent.
  • DeadlineForNext and SuspendForNext refer to a number of block transfers, e.g., a group of the next ten blocks. Both options may also be used together to create a range of time when the next message should be sent. For example, when sending a message with DeadlineForNext indicating ten minutes from current time t and SuspendForNext indicating five minutes from current time t, the next request message should be sent between [t+5, t+10].
  • the DeadlineForNext option when the DeadlineForNext option is in a request message, having message ID N, from a client, it indicates the latest time that the client will issue the next request message, having message ID N+l . Based on this indication, the server may react accordingly. For example, if the server does not receive the next request message until after DeadlineForNext, it may plan to store the previously-received blocks in a low priority cache, i.e., the blocks may be deleted when the cache needs to be cleaned, because it believes that the current block transfer process has halted. Without such an indication, the server cannot tell if the ongoing block transfer process is halted or is simply interrupted in an intermittent manner (e.g., "Pause-and-Resume").
  • the DeadlineForNext option when the DeadlineForNext option is in a response message from a server (i.e., the response to the request message with message ID N), it indicates the latest time that the server is willing to accept the next request message (i.e., the one having message ID N+1).
  • the client may decide when to send out the next request message based on the server's indicated deadline.
  • the SuspendForNext option when the SuspendForNext option is in a request message, having message ID N, from a client, it indicates that the client will not issue the next request message, having message ID N+1, before the time indicated by SuspendForNext. Based on this indication, the server may devote its resources to other matters until needing to reallocate resources (CPU, Memory, etc.) to this block transfer process after the suspension period.
  • resources CPU, Memory, etc.
  • the SuspendForNext option when the SuspendForNext option is in a response message from a server (i.e., the response to the message with message ID N), it indicates that the server is unable to accept the next request message (i.e., the one having message ID N+1) until the time indicated by SuspendForNext.
  • the client may reschedule the transmission time for the next request message based upon the suspension time, or the client may choose to go to sleep for energy-efficient reasons until a time just before the SuspendForNext time. Once awake, the block transfer process may resume.
  • policies may include policies to resolve conflicts.
  • the following policies are provided as examples and should not be construed to be limiting of the present disclosure or claims.
  • the client initializes request messages, if the server intends to pose its own DeadlineForNext or SuspendForNext options, these options should not conflict with those posed by the client.
  • the client and server options may be able to be coordinated.
  • both client and server can indicate their own DeadlineForNext in the request/response message (say having message ID N), respectively. If so, the "coordinated deadline" for the next request message (i.e., having message ID N+1) should be the smaller one of the two expected deadlines from two sides.
  • the client and server might need to dynamically rectify or adjust values of their DeadlineForNext and SuspendForNext options to ensure the values of those options are meaningful, i.e., still valid. Any non-meaningful values will be automatically ignored.
  • Table 3 shows the implementation details of one embodiment of a definition for the new DeadlineForNext and SuspendForNext CoAP Options. The proposed options may be included in the No. 37 and No. 39 CoAP block options within the headers of the request and response messages, respectively. Note that assigning Nos. "37” and "39" to these new Options is presented solely for purposes of example and should not be construed to limit the Options to these specific numbers.
  • FIGs. 10A and 10B illustrate an example workflow in which embodiments of the Deadline 1, Deadline2, DeadlineForNext, and SuspendForNext options are employed, illustrating how those options may be employed in a communication scenario.
  • Client or Server could indicate such information during any time of a block transfer process.
  • FIGs. 10A and 10B may be performed by a client or server, such as the clients and servers illustrated in FIGs. 2-5 and 7-9, which may represent logical entities in a communication network and may be implemented in the form of software (i.e., computer-executable instructions) stored in a memory of, and executing on a processor of, an apparatus of such network, which may comprise one of the general architectures illustrated in FIGs. 11C or 1 ID as described more fully below. That is, the operations illustrated in FIGs. 10A and 10B may be implemented in the form of software (i.e., computer-executable instructions) stored in a memory of a network apparatus, such as for example the apparatus or computer system illustrated in FIGs.
  • a network apparatus such as for example the apparatus or computer system illustrated in FIGs.
  • 11C or 1 ID which computer executable instructions, when executed by a processor of the apparatus, perform the steps illustrated in the figure. It is also understood that any transmitting and receiving steps illustrated in these figures may be performed by communication circuitry (e.g., circuitry 34 or 97 of FIGs. 11C and 1 ID, respectively) of the apparatus under control of the processor of the apparatus and the computer- executable instructions (e.g., software) that it executes.
  • communication circuitry e.g., circuitry 34 or 97 of FIGs. 11C and 1 ID, respectively
  • the computer- executable instructions e.g., software
  • GUI Graphical User Interface
  • (1) users may select which options are to be used, and (2) for a given selected option to be used and because there are different usages for options depending on whether each option is included in a request or response message, users may input the maximal default values for each option for different cases based on specific needs.
  • Deadline 1 and Deadline2 it can be seen that the users only need to set the maximal default value when Deadline 1 is included in a request message and Deadline2 is included in a response message, respectively. This is because of the usages disclosed for Deadlinel and Deadline2; when Deadlinel is included in a response message and Deadline2 is included in a request message, respectively, their values are 0. Therefore, there is no need for a user to set values for those two cases.
  • users may set the maximal default values for those parameters when they are included in either a request message or a response message.
  • FIG. 11 A is a diagram of an example machine-to machine (M2M), Internet of Things (IoT), or Web of Things (WoT) communication system 10 in which one or more disclosed embodiments may be implemented.
  • M2M technologies provide building blocks for the IoT/WoT, and any M2M device, M2M gateway, M2M server, M2M service platform or other network apparatus may be a component or node of the IoT/WoT as well as an IoT/WoT service layer, etc.
  • Any of the client or server devices illustrated in any of FIGs. 2-5 or 7-10 may comprise a node (i.e., network apparatus) of a communication system such as the one illustrated in FIGs. 11A-D.
  • the M2M/ IoT/WoT communication system 10 includes a communication network 12.
  • the communication network 12 may be a fixed network (e.g., Ethernet, Fiber, ISDN, PLC, or the like) or a wireless network (e.g., WLAN, cellular, or the like) or a network of heterogeneous networks.
  • the communication network 12 may be comprised of multiple access networks that provide content such as voice, data, video, messaging, broadcast, or the like to multiple users.
  • the communication network 12 may employ one or more channel access methods, such as code division multiple access
  • the communication network 12 may comprise other networks such as a core network, the Internet, a sensor network, an industrial control network, a personal area network, a fused personal network, a satellite network, a home network, or an enterprise network for example.
  • the M2M/ IoT/WoT communication system 10 may include the Infrastructure Domain and the Field Domain.
  • the Infrastructure Domain refers to the network side of the end-to-end M2M deployment
  • the Field Domain refers to the area networks, usually behind an M2M gateway.
  • the Field Domain and Infrastructure Domain may both comprise a variety of different apparatuses (e.g., servers, gateways, device, and the like) of the network.
  • the Field Domain may include M2M gateways 14 and devices 18. It will be appreciated that any number of M2M gateway devices 14 and M2M devices 18 may be included in the M2M/ IoT/WoT communication system 10 as desired.
  • Each of the M2M gateway devices 14 and M2M devices 18 are configured to transmit and receive signals, using communications circuitry, via the communication network 12 or direct radio link.
  • a M2M gateway 14 allows wireless M2M devices (e.g. cellular and non-cellular) as well as fixed network M2M devices (e.g., PLC) to communicate either through operator networks, such as the communication network 12 or direct radio link.
  • the M2M devices 18 may collect data and send the data, via the communication network 12 or direct radio link, to an M2M application 20 or other M2M devices 18.
  • the M2M devices 18 may also receive data from the M2M application 20 or an M2M device 18.
  • M2M devices 18 and gateways 14 may communicate via various networks including, cellular, WLAN, WPAN (e.g., Zigbee, 6L0WPAN, Bluetooth), direct radio link, and wireline for example.
  • WPAN e.g., Zigbee, 6L0WPAN, Bluetooth
  • Exemplary M2M devices include, but are not limited to, tablets, smart phones, medical devices, temperature and weather monitors, connected cars, smart meters, game consoles, personal digital assistants, health and fitness monitors, lights, thermostats, appliances, garage doors and other actuator-based devices, security devices, and smart outlets.
  • the illustrated M2M service layer 22 in the field domain provides services for the M2M application 20, M2M gateways 14, and M2M devices 18 and the communication network 12. It will be understood that the M2M service layer 22 may
  • the M2M service layer 22 may be implemented by one or more nodes of the network, which may comprises servers, computers, devices, or like apparatuses.
  • the M2M service layer 22 provides service capabilities that apply to M2M devices 18, M2M gateways 14, and M2M applications 20.
  • the functions of the M2M service layer 22 may be implemented in a variety of ways, for example as a web server, in the cellular core network, in the cloud, etc.
  • M2M service layer 22' Similar to the illustrated M2M service layer 22, there is the M2M service layer 22' in the Infrastructure Domain. M2M service layer 22' provides services for the M2M application 20' and the underlying communication network 12' in the infrastructure domain. M2M service layer 22' also provides services for the M2M gateways 14 and M2M devices 18 in the field domain. It will be understood that the M2M service layer 22' may communicate with any number of M2M applications, M2M gateways and M2M devices. The M2M service layer 22' may interact with a service layer by a different service provider. The M2M service layer 22' may be implemented by one or more nodes of the network, which may comprises servers, computers, devices, virtual machines (e.g., cloud computing/storage farms, etc.) or like apparatuses.
  • nodes of the network which may comprises servers, computers, devices, virtual machines (e.g., cloud computing/storage farms, etc.) or like apparatuses.
  • the M2M service layers 22 and 22' provide a core set of service delivery capabilities that diverse applications and verticals can leverage. These service capabilities enable M2M applications 20 and 20' to interact with devices and perform functions such as data collection, data analysis, device management, security, billing, service/device discovery etc. Essentially, these service capabilities free the applications of the burden of implementing these functionalities, thus simplifying application development and reducing cost and time to market.
  • the service layers 22 and 22' also enable M2M applications 20 and 20' to communicate through various networks 12 and 12' in connection with the services that the service layers 22 and 22' provide.
  • the M2M applications 20 and 20' may include applications in various industries such as, without limitation, transportation, health and wellness, connected home, energy management, asset tracking, and security and surveillance.
  • the M2M service layer running across the devices, gateways, servers and other apparatuses of the system, supports functions such as, for example, data collection, device management, security, billing, location tracking/geofencing, device/service discovery, and legacy systems integration, and provides these functions as services to the M2M applications 20 and 20' .
  • a service layer such as the service layers 22 and 22' illustrated in FIGs. 11 A and 1 IB, may be a functional layer within a network service architecture.
  • Service layers are typically situated above the application protocol layer such as HTTP, CoAP or MQTT and provide value added services to client applications.
  • the service layer also provides an interface to core networks at a lower resource layer, such as for example, a control layer and transport/access layer.
  • the service layer supports multiple categories of (service) capabilities or functionalities including a service definition, service runtime enablement, policy management, access control, and service clustering.
  • M2M industry standards bodies, e.g., oneM2M, have been developing M2M service layers to address the challenges associated with the integration of M2M types of devices and applications into deployments such as the
  • a M2M service layer can provide applications and/or various devices with access to a collection of or a set of the above mentioned capabilities or functionalities, supported by the service layer, which can be referred to as a Common Services Entity (CSE) or Service Capability Layer (SCL).
  • CSE Common Services Entity
  • SCL Service Capability Layer
  • a few examples include but are not limited to security, charging, data management, device management, discovery, provisioning, and connectivity management which can be commonly used by various
  • the CSE or SCL is a functional entity that may be implemented by hardware and/or software and that provides (service) capabilities or
  • the Third Generation Partnership Project (3GPP) has also defined an architecture for machine-type communications (MTC).
  • MTC machine-type communications
  • SCS Service Capability Server
  • an instance of the service layer may be implemented as a logical entity (e.g., software, computer-executable instructions, and the like) executing either on one or more standalone apparatuses in the network, including servers, computers, and other computing devices or apparatuses, or as part of one or more existing apparatuses.
  • a service layer or component thereof may be implemented in the form of software running on a network apparatus (e.g., server, computer, gateway, device or the like) having the general architecture illustrated in FIG. 11C or FIG. 1 ID described below.
  • SOA Service Oriented Architecture
  • ROA Resource- Oriented Architecture
  • FIG. 11C is a block diagram of an example hardware/software architecture of an apparatus of a network, such as one of the clients or servers illustrated in FIGs. 2-5 or 7-10 which may operate as an M2M server, gateway, device, or other apparatus in an M2M network such as that illustrated in FIGs. 11 A and 1 IB.
  • the apparatus 30 may include a processor 32, non-removable memory 44, removable memory 46, a
  • the apparatus 30 may also include communication circuitry, such as a transceiver 34 and a transmit/receive element 36. It will be appreciated that the apparatus 30 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.
  • This apparatus may be a node that implements the time flexibility functionality described herein.
  • the processor 32 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of
  • the processor 32 may execute computer-executable instructions stored in the memory (e.g., memory 44 and/or memory 46) of the apparatus in order to perform the various required functions of the apparatus.
  • the processor 32 may perform signal coding, data processing, power control, input/output processing, and/or any other functionality that enables the apparatus 30 to operate in a wireless or wired environment.
  • the computer executable instructions stored in the memory of the apparatus, and executed by the processor, may further cause the apparatus to perform the operations illustrated in Figure 10 described above.
  • the processor 32 may run application-layer programs (e.g., browsers) and/or radio access-layer (RAN) programs and/or other communications programs.
  • the processor 32 may also perform security operations such as authentication, security key agreement, and/or cryptographic operations, such as at the access-layer and/or application layer for example.
  • the processor 32 is coupled to its communication circuitry (e.g., transceiver 34 and transmit/receive element 36).
  • the processor 32 may control the communication circuitry in order to cause the apparatus 30 to communicate with other apparatuses via the network to which it is connected.
  • the processor 32 may control the communication circuitry in order to perform the transmitting and receiving steps described and illustrated herein (e.g., in FIGs. 2-5 and 7-10) and in the claims. While FIG. 11C depicts the processor 32 and the transceiver 34 as separate components, it will be appreciated that the processor 32 and the transceiver 34 may be integrated together in an electronic package or chip.
  • the transmit/receive element 36 may be configured to transmit signals to, or receive signals from, other apparatuses, including M2M servers, gateways, device, and the like.
  • the transmit/receive element 36 may be an antenna configured to transmit and/or receive RF signals.
  • the transmit/receive element 36 may support various networks and air interfaces, such as WLAN, WPAN, cellular, and the like.
  • the transmit/receive element 36 may be an emitter/detector configured to transmit and/or receive IR, UV, or visible light signals, for example.
  • the transmit/receive element 36 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit/receive element 36 may be configured to transmit and/or receive any combination of wireless or wired signals.
  • the apparatus 30 may include any number of transmit/receive elements 36. More specifically, the apparatus 30 may employ MIMO technology. Thus, in an embodiment, the apparatus 30 may include two or more transmit/receive elements 36 (e.g., multiple antennas) for transmitting and receiving wireless signals.
  • the transceiver 34 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 36 and to demodulate the signals that are received by the transmit/receive element 36.
  • the apparatus 30 may have multi-mode capabilities.
  • the transceiver 34 may include multiple transceivers for enabling the apparatus 30 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.
  • the processor 32 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 44 and/or the removable memory 46.
  • the processor 32 may store session context in its memory, as described above.
  • the non-removable memory 44 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device.
  • the removable memory 46 may include a subscriber identity module (SFM) card, a memory stick, a secure digital (SD) memory card, and the like.
  • the processor 32 may access information from, and store data in, memory that is not physically located on the apparatus 30, such as on a server or a home computer.
  • the processor 32 may be configured to control lighting patterns, images, or colors on the display or indicators 42 to reflect the status of communications and to provide a graphical user interface, such as the GUI illustrated in FIG. 12 and described above.
  • the processor 32 may receive power from the power source 48, and may be configured to distribute and/or control the power to the other components in the apparatus 30.
  • the power source 48 may be any suitable device for powering the apparatus 30.
  • the power source 48 may include one or more dry cell batteries (e.g., nickel -cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.
  • the processor 32 may also be coupled to the GPS chipset 50, which is configured to provide location information (e.g., longitude and latitude) regarding the current location of the apparatus 30. It will be appreciated that the apparatus 30 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.
  • location information e.g., longitude and latitude
  • the processor 32 may further be coupled to other peripherals 52, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wired or wireless connectivity.
  • the peripherals 52 may include various sensors such as an accelerometer, biometrics (e.g., fingerprint) sensors, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.
  • biometrics e.g., fingerprint
  • a satellite transceiver for photographs or video
  • USB universal serial bus
  • FM frequency modulated
  • the apparatus 30 may be embodied in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane.
  • the apparatus 30 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of the peripherals 52.
  • FIG. 1 ID is a block diagram of an exemplary computing system 90 which may also be used to implement one or more apparatuses of a network, such as the clients or servers illustrated in FIGs. 2-5 and 7-10, which may operate as an M2M server, gateway, device, or other apparatus in an M2M network such as that illustrated in FIGs. 11 A and 1 IB.
  • Computing system 90 may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within a processor, such as central processing unit (CPU) 91, to cause computing system 90 to do work, such as, for example, performing the operations illustrated and described in FIGs. 10A and 10B and the accompanying description.
  • CPU central processing unit
  • central processing unit 91 may comprise multiple processors.
  • Coprocessor 81 is an optional processor, distinct from main CPU 91, that performs additional functions or assists CPU 91.
  • CPU 91 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computer's main data-transfer path, system bus 80.
  • system bus 80 Such a system bus connects the components in computing system 90 and defines the medium for data exchange.
  • System bus 80 typically includes data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus.
  • An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.
  • RAM random access memory
  • ROM read only memory
  • Such memories include circuitry that allows information to be stored and retrieved.
  • ROMs 93 generally contain stored data that cannot easily be modified. Data stored in RAM 82 can be read or changed by CPU 91 or other hardware devices. Access to RAM 82 and/or ROM 93 may be controlled by memory controller 92.
  • Memory controller 92 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode can access only memory mapped by its own process virtual address space; it cannot access memory within another process's virtual address space unless memory sharing between the processes has been set up.
  • computing system 90 may contain peripherals controller 83 responsible for communicating instructions from CPU 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.
  • peripherals controller 83 responsible for communicating instructions from CPU 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.
  • Display 86 which is controlled by display controller 96, is used to display visual output generated by computing system 90. Such visual output may include text, graphics, animated graphics, and video. Display 86 may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller 96 includes electronic components required to generate a video signal that is sent to display 86. For example, the display 86 may be used to display the graphical user interface illustrated in FIG. 12 and described above.
  • computing system 90 may contain communication circuitry, such as for example a network adaptor 97, that may be used to connect computing system 90 to an external communications network, such as network 12 of FIG. 11 A and FIG. 1 IB, to enable the computing system 90 to communicate with other nodes of the network.
  • the communication circuitry alone or in combination with the CPU 91, may be used to perform the transmitting and receiving steps described herein (e.g., in FIGs. 2-5 and 7-10) and in the claims.
  • any or all of the systems, methods and processes described herein may be embodied in the form of computer executable instructions (i.e., program code) stored on a computer-readable storage medium which instructions, when executed by a machine, such as an apparatus of an M2M network, including for example an M2M server, gateway, device or the like, perform and/or implement the systems, methods and processes described herein.
  • a machine such as an apparatus of an M2M network, including for example an M2M server, gateway, device or the like, perform and/or implement the systems, methods and processes described herein.
  • any of the steps, operations or functions described above may be
  • Computer readable storage media include both volatile and nonvolatile, removable and non-removable media implemented in any non-transitory (i.e., tangible or physical) method or technology for storage of information, but such computer readable storage media do not includes signals.
  • Computer readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible or physical medium which can be used to store the desired information and which can be accessed by a computer.

Abstract

Selon l'invention, des modifications sont apportées au mécanisme de transfert de blocs CoAP existant afin de minimiser les déchets associés à une charge et à un encombrement excessifs. Dans un aspect, deux nouvelles options de bloc sont introduites pour indiquer les exigences temporelles du client et du serveur en ce qui concerne le processus de transfert de bloc actuel. Dans un autre aspect, deux autres nouvelles options de bloc sont introduites pour indiquer quand le bloc suivant doit être transféré.
PCT/US2016/050134 2015-09-02 2016-09-02 Activation de la flexibilité temporelle pour le transfert de blocs dans le protocole coap WO2017040948A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201562213353P 2015-09-02 2015-09-02
US62/213,353 2015-09-02

Publications (1)

Publication Number Publication Date
WO2017040948A1 true WO2017040948A1 (fr) 2017-03-09

Family

ID=56940409

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/050134 WO2017040948A1 (fr) 2015-09-02 2016-09-02 Activation de la flexibilité temporelle pour le transfert de blocs dans le protocole coap

Country Status (1)

Country Link
WO (1) WO2017040948A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021126024A1 (fr) * 2019-12-17 2021-06-24 Telefonaktiebolaget Lm Ericsson (Publ) Observation de ressources par un client coap
US11146362B2 (en) 2017-12-15 2021-10-12 Huawei Technologies Co., Ltd. Internet of things data transmission method, device and system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2309783A1 (fr) * 2009-10-12 2011-04-13 Pantech Co., Ltd. Serveur de réseau, terminal de communication mobile et son procédé de fonctionnement
US20140155024A1 (en) * 2012-11-30 2014-06-05 International Business Machines Corporation Delayed data delivery options
US20140280885A1 (en) * 2013-03-15 2014-09-18 Hewlett-Packard Development Company, L.P. Flow control transmission
EP2800339A1 (fr) * 2012-01-30 2014-11-05 Huawei Technologies Co., Ltd Procédé d'acquisition de ressources de l'internet des objets, client et dispositif de ressources de l'internet des objets
EP2823687A1 (fr) * 2012-03-07 2015-01-14 Telefonaktiebolaget L M Ericsson (PUBL) Contrôle de l'état de connexion d'un terminal mobile basé sur une activité de communication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2309783A1 (fr) * 2009-10-12 2011-04-13 Pantech Co., Ltd. Serveur de réseau, terminal de communication mobile et son procédé de fonctionnement
EP2800339A1 (fr) * 2012-01-30 2014-11-05 Huawei Technologies Co., Ltd Procédé d'acquisition de ressources de l'internet des objets, client et dispositif de ressources de l'internet des objets
EP2823687A1 (fr) * 2012-03-07 2015-01-14 Telefonaktiebolaget L M Ericsson (PUBL) Contrôle de l'état de connexion d'un terminal mobile basé sur une activité de communication
US20140155024A1 (en) * 2012-11-30 2014-06-05 International Business Machines Corporation Delayed data delivery options
US20140280885A1 (en) * 2013-03-15 2014-09-18 Hewlett-Packard Development Company, L.P. Flow control transmission

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11146362B2 (en) 2017-12-15 2021-10-12 Huawei Technologies Co., Ltd. Internet of things data transmission method, device and system
WO2021126024A1 (fr) * 2019-12-17 2021-06-24 Telefonaktiebolaget Lm Ericsson (Publ) Observation de ressources par un client coap

Similar Documents

Publication Publication Date Title
US10425194B2 (en) Cross-layer and cross-application acknowledgment for data transmission
US11064330B2 (en) Methods for enabling delay-awareness in the constrained application protocol (CoAP)
EP3243317B1 (fr) Indication et négociation de protocole machine-machine
US10498831B2 (en) Communication sessions at a CoAP protocol layer
KR101877188B1 (ko) Ｍｑｔｔ 프로토콜을 이용한 서비스 층 상호연동
EP2957085B1 (fr) Propagation de ressources de couches de service entre domaines
EP3195572B1 (fr) Systèmes et méthodes pour permettre l'accès aux services de systèmes tiers par une couche de service
US10708885B2 (en) Methods and nodes for enabling context-awareness in CoAP
WO2018013916A1 (fr) Service d'abonnement et de notification
WO2018112327A1 (fr) Procédés de commande de simultanéité pour transfert de bloc dans une architecture de publication-abonnement coap
EP3175589A1 (fr) Gestion de ressources et de planification centralisée efficace dans des réseaux à saut de canal à synchronisation temporelle
JP7246379B2 (ja) 通信ネットワークにおけるサービス層メッセージテンプレート
WO2017044772A1 (fr) Procédés pour l'activation de messagerie coap sensible au contexte
WO2017040948A1 (fr) Activation de la flexibilité temporelle pour le transfert de blocs dans le protocole coap
WO2018132557A1 (fr) Commutation de protocole dynamique
WO2017040940A1 (fr) Opération améliorée de transfert de bloc dans un protocole coap
US9338016B2 (en) Method and apparatus for exchanging messages
FI124786B (fi) Menetelmä ja laite viestien vaihtamiseksi

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16766756

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16766756

Country of ref document: EP

Kind code of ref document: A1