Transmission of lost data blocks

By introducing multicast repair function and transmission window management into network devices of IoT devices, the problem of low multicast transmission efficiency and reliability in OTA firmware updates is solved, and efficient and reliable data transmission is achieved.

CN118947101APending Publication Date: 2024-11-12TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094450.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-03-31
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

During the OTA firmware update process of IoT devices, multicast transmission is prone to errors and lacks standardized retransmission methods, resulting in low transmission efficiency and reliability.

Method used

By introducing multicast repair functions in network devices, the transmission window management (including retransmission window, correction window and finalization stage) is used to determine the transmission strategy of data blocks, and dynamically determine the unicast or multicast transmission method to improve transmission Reliability and efficiency.

Benefits of technology

It realizes efficient and reliable transmission of large data objects in IoT devices, reduces the number of transmissions and the consumption of network resources, and improves the success rate of firmware updates.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118947101A_ABST
    Figure CN118947101A_ABST
Patent Text Reader

Abstract

A method, network device and computer program in a communication network (100) for assisting an application server (130) using a restricted application protocol, CoAP, in communication of a data object (600) to a client device (110), where the data object comprises data blocks (601-609). The network device is operable to notify a multicast repair function. The network device is operable to receive at least one indication of at least one lost data block from a client device that does not successfully receive the data block within a transmission window. The network device is operable to decide to send and initiate a transmission of one or more lost data blocks via unicast, multicast, or both unicast and multicast. A computer program product is also disclosed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The invention relates to a network device for use in a communication network, a method performed by the network device, a corresponding computer program and a corresponding computer program product. Background Art

[0002] Devices in the massive IoT device category typically send information in an energy-efficient manner and often over long distances and with poor transmission capabilities. These devices use RESTful (representational state transfer) protocols, such as Constrained Application Protocol (CoAP), to communicate with low computational overhead. The communication is typically accomplished using an application server that coordinates a group of such massive IoT devices simultaneously.

[0003] In order to keep such devices (also called endpoints) updated in terms of software, large firmware updates are often sent from application servers to these endpoints where the software is installed. Such updates are often referred to as over-the-air (OTA) firmware updates. Current methods of using larger data objects with CoAP as specified by the CoAP block-by-block protocol (see, e.g., RFC7959) simply involve breaking up the larger data object into multiple blocks of a specific size. This transmission is often done via unicast transmission from an application server to a single device or multicast transmission from an application to some devices in the network. In OTA firmware updates, the multicast option is used to update most, if not all, devices at the same time.

[0004] US10447816 B2 discloses a data collector that sends an announcement of a firmware update to multiple endpoints. At the time indicated by the announcement, the data collector multicasts the firmware update multiple times. Then, the data collector receives indications from multiple endpoints that all blocks of the multicast firmware update were not successfully received. In response, the data collector sends the missing blocks to the multiple endpoints according to the indication.

[0005] Depending on the circumstances, these transmissions may be error-prone and thus require retransmissions. Additionally, in RESTful protocols, multicast transmissions lack confirmation of successful transmissions from each individual device to prevent overwhelming the application server with a large number of confirmations. CoAP lacks a standardized method for requesting retransmissions of potentially lost blocks. Summary of the invention

[0006] The object of the present invention is to achieve a reduction in the number of transmissions required to successfully transmit OTA firmware in a network using a RESTful protocol.

[0007] According to a first aspect of the present invention, there is a network device in a communication network, the network device having a processor circuit and a storage unit storing instructions. The network device is configured to assist the task of an application server in the communication of a data object to a client device using a restricted application protocol CoAP, wherein the data object includes a data block. The network device is operable to notify the client device of a multicast repair function enabled by the network device. The network device is operable to receive at least one indication of at least one lost data block from a client device that has not successfully received all data blocks of the data object within at least one transmission window of an earlier transmission in a communication associated with the client device. The network device is operable to decide to send one or more lost data blocks to the client device via unicast or multicast or both unicast and multicast. The network device is operable to initiate the transmission of one or more lost data blocks according to the decision. In this way, a solution is achieved for using CoAP to achieve efficient and reliable transmission of large data objects to multiple client devices by using a limited repair capability in the case of continuous failure to repair.

[0008] In an embodiment of the first aspect, the network device is operable to determine one or more transmission windows corresponding to one or more lost data blocks of the client device. The transmission window is or includes a retransmission window, which defines how long the client device should wait to receive the one or more lost data blocks before indicating that the one or more data blocks have been lost. The transmission window is or includes a correction window, which defines how long the client device should wait after communicating that the one or more lost data blocks are lost before reporting an error in the communication of the one or more data blocks. The transmission window is or includes a finalization phase, which defines how long the communication should remain open. In this way, a reliable and efficient solution to the transmission of data objects is achieved.

[0009] In an embodiment of the first aspect, the transmission window or one of the transmission windows is or includes a finalization phase, and the network device is operable to end communication of the data object once the finalization phase has elapsed, thereby achieving efficient cessation of transmission of the data object.

[0010] In an embodiment of the first aspect, the network device is operable to initiate transmission of information indicating one or more transmission windows and / or one or more transmission window lengths, thereby enabling flexible transmission windows and transmission window lengths between transmissions of data objects.

[0011] In an embodiment of the first aspect, the network device is operable to determine one or more lengths of one or more transmission windows, the one or more lengths being defined by the number of blocks or the time length, thereby achieving flexibility in the length of data blocks of the data object.

[0012] In an embodiment of the first aspect, the network device is operable to decide to send the lost data blocks to the client device via unicast or multicast or both unicast and multicast based on the number of unsuccessful transmissions of the lost data blocks within one or more transmission windows. This enables retransmission flexibility depending on the difficulty of the initial transmission and subsequent retransmissions. This allows more reliable transmission via unicast at the expense of resources, or lower cost multicast transmission, or even more reliable transmission by providing both unicast and multicast transmissions with diversity.

[0013] In an embodiment of the first aspect, the network device is operable to use the number of lost blocks of a data object for each of the client devices to decide to send the lost data blocks to the client devices via unicast or multicast or both unicast and multicast. This enables retransmission flexibility depending on the difficulty of previous transmissions across both a single client device and multiple client devices. This allows more reliable transmission via unicast at the expense of resources, or a lower cost multicast transmission, or an even more reliable transmission via both unicast and multicast transmissions (which provides diversity for those client devices that may need it).

[0014] In an embodiment of the first aspect, the network device is operable to collect network information. The network information includes: the number of client devices to which the data object is to be transmitted; mobility characteristics of at least one client from a plurality of clients; the number of client devices belonging to a cell; radio resource allocation of the cell; network resource allocation for the cell; available bandwidth in the cell; and / or at least one radio parameter derived from reference and probing channels for each client device. This enables a changing transmission configuration to cope with different network conditions. This is achieved by adjusting session information to cope with better or worse network conditions.

[0015] In an embodiment of the first aspect, the network device is operable to assign the client device to one or more of: a multicast session, a unicast session, or both a unicast session and a multicast session. The session includes at least: a start time; an indication of a multicast repair function; and information indicating the length of a transmission window of the client device belonging to the session. This enables updating the transmission configuration for each data object individually. This allows optimizing the configuration for the data object, the network information, and the client device.

[0016] In an embodiment of the first aspect, the network device is operable to assign the client device to one or more of the following based on network information or the number of lost blocks in one or more transmission windows of each client device: a multicast session, a unicast session, or both a multicast session and a unicast session. The sessions are distinguished by: which data blocks will be sent in the session; when the data blocks are sent; the transmission window length; the network settings; and / or the transmission settings. This enables the transmission configuration to be adjusted individually for each data object and client device. This allows the configuration to be optimized for the data object, the network information, and the client device.

[0017] In an embodiment of the first aspect, the network device is operable to initiate transmission of information indicating one or more sessions assigned to a client device. The network device is operable to initiate transmission of information for initializing the one or more sessions. In this way, a manner in which data objects for updating each client device are to be sent is achieved. This allows for more efficient transmission to each client device and to groups of client devices.

[0018] In an embodiment of the first aspect, a network device is operable to determine a length of a transmission window for a session. The length of the transmission window for the session is determined based on: the number of lost blocks in one or more transmission windows from a previous multicast or unicast session to which the client device was previously assigned; the number of blocks in a data object; the number of client devices; and / or collected network information. In this way, a more efficient transmission window length and a more reliable repair function are achieved. This allows for a more efficient use of network resources compared to endlessly repairing lost multicast transmissions and restarting transmission of data objects when repair is possible and uses few network resources.

[0019] In an embodiment of the first aspect, the transmission window is or one of the transmission windows includes a finalization phase. The network device is operable to initiate release of the session for the client device once the finalization phase of the client device and of the session has passed. This achieves an equal repair opportunity for each data block in the data object. This allows for more efficient use of network resources.

[0020] In an embodiment of the first aspect, the network device is operable to use the collected network information to decide to send the missing data blocks to the client device via unicast and / or multicast, thereby achieving more reliable transmission of the data object by allowing more reliable transmission of the missing data blocks when the network information indicates poor network conditions.

[0021] In an embodiment of the first aspect, the network device is operable to use the collected network information to decide whether to first send a data block of the data object to the client device via multicast or unicast before any retransmission, thereby achieving more efficient transmission of the data object by more reliably sending the data block via unicast from the beginning when the network information indicates poor network conditions.

[0022] In an embodiment of the first aspect, the network device is operable to decide to stop transmission of lost data blocks. The decision is based on: the data block is lost by the client device in one or more of the associated transmission windows; and / or collected network information. In this way, network resources are saved because data blocks with particularly poor transmission success rates or with poor network conditions are considered failed and new more reliable sessions are created, rather than wasting network resources on data blocks that are unlikely to be successfully sent.

[0023] According to a second aspect of the present invention, there is provided a method performed in a network device for assisting retransmission of lost data blocks from a multicast transmission of a data object from an application server to a client device using a constrained application protocol CoAP. The method includes notifying a client device of a multicast repair function enabled by the network device. The method includes receiving at least one indication of at least one lost data block from a client device that did not successfully receive all data blocks of the data object within at least one transmission window of an earlier transmission in a communication associated with the client device. The method includes deciding to send one or more lost data blocks to the client device via unicast or multicast or both unicast and multicast. The method includes initiating transmission of the one or more lost data blocks based on the decision.

[0024] In an embodiment of the second aspect, the method includes one or more transmission windows corresponding to one or more lost data blocks of the client device. The transmission window is or includes a retransmission window, which defines how long the client device should wait to receive the one or more lost data blocks before indicating that the one or more data blocks have been lost. The transmission window is or includes a correction window, which defines how long the client device should wait after communicating that the one or more lost data blocks are lost before reporting an error in the communication of the one or more data blocks. The transmission window is or includes a finalization phase, which defines how long the communication should remain open.

[0025] In an embodiment of the second aspect, the transmission window or one of the transmission windows is or includes a finalization phase.The method comprises ending the communication of the data object once the finalization phase has elapsed.

[0026] In an embodiment of the second aspect, the method comprises initiating transmission of information indicating one or more transmission windows and / or a length of the one or more transmission windows.

[0027] In an embodiment of the second aspect, the method comprises determining one or more lengths of one or more transmission windows, the one or more lengths being defined by a number of blocks or a time length.

[0028] In an embodiment of the second aspect, the method includes deciding to send the missing data blocks to the client device via unicast or multicast or both unicast and multicast based on a number of unsuccessful transmissions of the missing data blocks within one or more transmission windows.

[0029] In an embodiment of the second aspect, the method includes using the number of missing blocks of the data object for each of the client devices to decide to send the missing data blocks to the client devices via unicast or multicast or both unicast and multicast.

[0030] In an embodiment of the second aspect, the method includes facilitating multiple application servers communicating with multiple groups of client devices for purposes of multicast and unicast transmissions.

[0031] In an embodiment of the second aspect, the method comprises collecting network information. The network information comprises: a number of client devices to which the data object is to be transmitted; a mobility characteristic of at least one client from a plurality of clients; a number of client devices belonging to a cell; a radio resource allocation of the cell; a network resource allocation for the cell; an available bandwidth in the cell; and / or for each client device, at least one radio parameter derived from a reference and a probing channel.

[0032] In an embodiment of the second aspect, the method includes assigning a client device to one or more of: a multicast session, a unicast session, or both a multicast session and a unicast session. A session includes at least: a start time; an indication of a multicast repair function; and information indicating a length of a transmission window for a client device belonging to the session.

[0033] In an embodiment of the second aspect, the method includes assigning the client device to one or more of: a multicast session, a unicast session, or both a multicast session and a unicast session based on network information or a number of lost blocks in one or more transmission windows of each client device. The sessions are distinguished by: which data blocks are to be sent in the session; when the data blocks are to be sent; the transmission window length; the network settings; and / or the transmission settings.

[0034] In an embodiment of the second aspect, the method includes initiating transmission of information indicating one or more sessions assigned to the client device.The method includes initiating transmission of information for initializing the one or more sessions.

[0035] In an embodiment of the second aspect, the method includes determining a length of a transmission window for a session. The determination of the length of the transmission window for the session is based on: a number of lost blocks in one or more transmission windows from a previous multicast or unicast session to which the client device was previously assigned; a number of blocks in a data object; a number of client devices; and / or collected network information.

[0036] In an embodiment of the second aspect, the transmission window is or one of the transmission windows includes a finalization phase.The method includes initiating a release of the session for the client device once the finalization phase of the client device and of the session has elapsed.

[0037] In an embodiment of the second aspect, the method includes using the collected network information to decide to send the missing data blocks to the client device via unicast and / or multicast.

[0038] In an embodiment of the second aspect, the method includes using the collected network information to decide to initially send data chunks of the data object to the client device via multicast or unicast.

[0039] In an embodiment of the second aspect, the method includes deciding not to send the lost data block. The decision is based on: the data block is lost by the client device in one or more of the associated transmission windows; and / or collected network information.

[0040] According to a third aspect of the present invention, a computer program is provided. The computer program includes computer-readable instructions for assisting an application server in communicating with multiple clients using a constrained application protocol CoAP, and the computer-readable instructions are executed on a processing circuit of a network device. The computer-readable instructions cause the network device to notify a client device of a multicast repair function enabled by the network device. The computer-readable instructions cause the network device to receive at least one indication of at least one lost data block from a client device that has not successfully received all data blocks of a data object within at least one transmission window of an earlier transmission in a communication associated with the client device. The computer-readable instructions cause the network device to decide to send one or more lost data blocks to the client device via unicast or multicast or both unicast and multicast. The computer-readable instructions cause the network device to initiate the transmission of one or more lost data blocks according to the decision.

[0041] In an embodiment of the third aspect, a computer program is provided. The computer program includes computer-readable instructions running on a processing circuit of a network device. The computer-readable instructions cause the network device to perform a method according to the second aspect, including any one of the embodiments of the second aspect.

[0042] According to a fourth aspect of the present invention, there is provided a computer program product. The computer program product comprises a computer program according to the third aspect of the present invention. The computer program product comprises a computer readable storage medium on which the computer program is stored. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate various embodiments.

[0044] Figure 1 is a diagram illustrating functional units of a network according to an embodiment.

[0045] Figure 2 is a signaling diagram illustrating a procedure according to an embodiment.

[0046] Figure 3 is a flow chart illustrating the process of an intelligent agent according to an embodiment.

[0047] Figure 4 is a flow chart illustrating a process of an application server according to an embodiment.

[0048] Figure 5 is a flow chart illustrating a process of a client device according to an embodiment.

[0049] Figure 6 is a schematic diagram of a data object according to an embodiment.

[0050] Figure 7 is a schematic diagram of data objects in a data block being transmitted over time according to an embodiment.

[0051] Figure 8a , Figure 8b , Figure 8c is a signaling diagram illustrating a procedure according to an embodiment.

[0052] Fig. 9 is a diagram showing functional units of an application server according to an embodiment.

[0053] Fig.10 is a diagram showing functional modules of an application server according to an embodiment.

[0054] Fig.11 is a diagram showing functional units of a client device according to an embodiment.

[0055] Fig.12 is a diagram showing functional modules of a client device according to an embodiment.

[0056] Fig.13 is a diagram showing functional units of an intelligent agent according to an embodiment.

[0057] Fig.14is a diagram showing functional modules of an intelligent agent according to an embodiment; and

[0058] Fig.15 One example of a computer program product comprising computer readable means according to an embodiment is shown. DETAILED DESCRIPTION

[0059] The present invention will now be described more fully herein with reference to the accompanying drawings, in which certain embodiments of the invention are shown. However, the present invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided by way of example so that this disclosure will be comprehensive and complete and will fully convey the scope of the invention to those skilled in the art.

[0060] Aspects of the present invention provide methods for transmitting large data files (such as firmware in the present embodiment) in a communication network including multiple devices. In some embodiments, one or more of these devices may be referred to as user equipment (UE). In some embodiments, the communication network may include multiple devices connected in a machine-to-machine (M2M) deployment. In order to update these devices, a lightweight protocol such as a constrained application protocol (CoAP) is used to connect these devices to the network via an application server, and the application server may include an intelligent proxy network device to assist in communication. The CoAP protocol is a RESTful protocol that is typically used to connect simpler devices that lack more complex capabilities such as computers or smart phones to a network. The CoAP protocol has the ability to simultaneously communicate between multiple devices using multicast capabilities. These devices are hereinafter referred to as client devices.

[0061] The client device in this embodiment is a device having the capability of communicating using the CoAP protocol in a communication network, hereinafter referred to as a network.

[0062] The data objects in this embodiment are objects that have enough data to necessitate the need to break the object into smaller data chunks in accordance with the CoAP chunk-by-chunk protocol [RFC7959]. These data objects may be firmware updates or other large files that should be sent to the client device.

[0063] The application server in this embodiment is a server that hosts an application program that uses the CoAP protocol to communicate in a network.

[0064] The smart agent in this embodiment is a network device that assists the application server. The smart agent can be a part of the application server. The smart agent can also be located outside the application server, somewhere else in the network but communicating with the application server. The smart agent can assist multiple application servers.

[0065] Figure 1 A currently disclosed embodiment of a communication network 100 is schematically shown in which an access point 105 uses wireless radio frequency communication and is connected to multiple client devices 110 using CoAP. The access point is part of a cellular network 115. The cellular network can be, but is not limited to, an LTE or 5G NR wireless communication network. Each access point is connected to a network device 120, also referred to herein as an intelligent agent, via the cellular network and continues to be connected to a core network 125. The intelligent agent determines how to repair packets for multiple client devices. The core network 125 can be, but is not limited to, a fourth generation or fifth generation 3GPP core network. The core network is connected to an application server 130 using the CoAP protocol. The application server receives information from and sends information to client devices in the communication network via a communication network consisting of a core network, an intelligent agent, a cellular network, and access points. Although in Figure 1 In the embodiment, the intelligent proxy is a discrete network device to which multiple application servers are connected, but in other embodiments the intelligent proxy may be located / hosted by the application server or another communication device, such as in the access point 105, the core network 125, or a discrete node in the network ( Figure 1 (not shown in the figure). Examples of these client devices may be wireless devices connected in an M2M deployment consisting of M2M devices. The client devices may be stationary or mobile and may be connected to the communication network directly or via an edge node such as a gateway.

[0066] Figure 2 A signaling diagram illustrating an embodiment of the present disclosure is shown. The network device 120 is referred to as an intelligent agent. Figure 2 8, the application server 130 (labeled AS in the figure) starts with a first step 205 in which the application server indicates to the intelligent agent that a large data object should be sent to one or more client devices in the communication network 100. An example of this step 205 can be found in step 801 of FIG. 8.

[0067] Then, in a second step 210, the cellular network may send information about network information to the intelligent agent. The network information may include, but is not limited to, the number of client devices marked to receive the data object, mobility characteristics from at least one of the plurality of client devices, cell conditions (such as the number of devices), radio resource allocations, network resource allocations, available bandwidth, received signal strength and reliability of recent communication exchanges, and radio parameters for each client device (such as power usage mode and coverage extension level). The information may also include the number of client devices to which the data object will be transmitted; the number of client devices belonging to the cell; the radio resource allocation of the cell; the network resource allocation for the cell; the available bandwidth in the cell; and / or, for each client device, at least one radio parameter derived from the reference and probing channels. Indicates to the cellular network and, in turn, to the client device that it can assist the application server in providing the ability to retransmit blocks lost during a potential transmission of the data object. Prior to or during step 210, network information may be collected from records of previous transmissions, other network devices, and the client device itself. An example of this step 210 may be found in step 803 of FIG. 8 .

[0068] Then, in a third step 215, the proxy server notifies one or more of the plurality of client devices 110 via the cellular network 115 that the network device 120 and the application server 130, referred to as the smart proxy, have the ability to retransmit any blocks lost during a potential multicast transmission of the data object. In other words, the proxy server notifies the client device of a multicast repair function enabled by the proxy server. An example of this step may be sending multicast session information to the cellular network and the client device, such as in step 805 of FIG. 8 . The smart proxy may then notify the cellular network of an initial transmission configuration in which some client devices may be marked as being sent data objects via multicast and other client devices may be indicated as being sent data objects via unicast. This may be done after receiving the network information in order to determine the initial transmission configuration, or based on a determination made for the initial transmission based on other preset parameters (such as data object size, number of client devices, quality of service requirements) or network information from step 210 that has been provided to the smart proxy from another source. The initial transmission configuration is shared with the cellular network and the client device in the form of session information. The session may be a session for multicast transmission, unicast transmission and / or a combination of multicast transmission and unicast transmission. The client device may belong to one, more than one, all or none of the sessions created and initiated by the intelligent agent. The session and the associated session information must contain the start time, the indication of the multicast repair function, and the information indicating the length of the transmission window of the client device belonging to the session. The session and the associated session information may also be distinguished in terms of which blocks are sent, when to send blocks, the transmission window length, the network settings and / or the transmission settings. The intelligent agent may also send information about the retransmission window 715, the correction window 725, the finalization phase 735 or a combination thereof for use by the application server and the client device. The intelligent agent may also initiate the transmission of information indicating the length of one or more transmission windows and / or one or more transmission windows. The intelligent agent may initiate the transmission of information indicating one or more sessions assigned to one or more client devices. This information may be shared in the session information, or may be known by the client device before step 205. The retransmission window is used to indicate to the client device how long the client device should wait to receive at least one indication of at least one lost data block before indicating that a data block from a data object transmitted from an initial multicast or unicast transmission has been lost. Once a data block or a series of blocks has been lost, the client device will thereby notify the application server of the potential lost data blocks. In other words, the retransmission window defines how long the client device should wait to receive one or more lost data blocks before indicating that one or more data blocks have been lost.The second is the correction window, which is used to inform the client device how long it should wait for the retransmission of a new block after notifying the application server of the loss of a block and before notifying the application server of errors in the transmission. The finalization phase is a period of time after the correction window that allows the client device to transmit to the application server a final list of lost blocks about which blocks were lost from the transmission that included the last retransmission window.

[0069] In a fourth step 220, the intelligent agent will initiate a session to the cellular network. This is done by initiating the transmission of information for initializing one or more sessions. An example of this step can be found in step 812 of Figure 8. In a fifth step 225, the cellular network will then establish a session with the client device indicated by the intelligent agent via the session information. An example of this step can be found in step 813 of Figure 8.

[0070] In a sixth step 230, the application server transmits the data object or a reference to the data object to the intelligent agent. In one embodiment, the intelligent agent segments the data object into data chunks and prepares them for transmission via the cellular network. In another embodiment, when the cellular network requires the data chunks, the intelligent agent retrieves the data chunks from the application server using the references. The intelligent agent may receive the data object from a source different from the application server. An example of this step may be found in steps 808 and 809 of FIG. 8 .

[0071] Once the client device has been notified of the multicast repair capability, and may have received the initial transmission configuration before initiating and establishing a session or in conjunction with the initiation and establishment of a session, the intelligent proxy will begin the transmission of the data object. In the seventh step 235, the intelligent proxy initiates the transmission of the data object to the client device via the cellular network. This can be done via a multicast session as shown in sub-step 235a. Depending on the initial transmission configuration in the session initiated from the intelligent proxy, the application server can also initiate the transmission of the data object to one or more client devices via unicast in sub-step 235b. In both steps 235a and 235b, these transmissions are completed in a series of blocks, which divide the data object into one or more fragments according to the CoAP block-by-block protocol. Examples of these steps can be found in step 815 of Figure 8.

[0072] During or after the transmission, the client device then keeps track of which chunks have been received from the application server in an eighth step 240. An example of this step can be found in step 822 of FIG.

[0073] Once the initial transmission from the smart agent via the cellular network is completed, in the ninth step 245, the client device then creates a list of lost data blocks by comparing the blocks successfully received within one or more transmission windows with the total number of blocks assumed to be received from the smart agent during the one or more transmission windows. This can also be done by comparing the numbering of the blocks and checking for any discontinuities in the numbering. In this context, a missing data block can be a data block that is simply not received or a data block that is not received in its entirety. Once the list is created, in step 245, the client device then sends the list of missing blocks to the cellular network and on to the smart agent. The smart agent will thereby receive at least one indication of at least one lost data block from a client device that did not successfully receive all data blocks of a data object within at least one transmission window of an earlier transmission in the communication associated with the client device. An example of this step can be found in step 817 of Figure 8.

[0074] Optionally, once the list of lost blocks has been created and sent, the cellular network may update the previously collected network information in a tenth step 250 and may send any updated network information to the intelligent agent. The type of network information will be the same as described in step 210. This may also include any transmission parameters or statistics from the multicast and / or unicast transmissions of steps 240a and / or 240b. The intelligent agent receives the updated network information. An example of this step may be found in step 819 of FIG. 8 .

[0075] Here, in the eleventh step 255, the intelligent agent decides whether to end the session and stop the transmission of the data object to the client device after receiving a list of lost blocks from each of the multiple client devices in the network and receiving updated network information from the cellular network. An example of this step can be found in step 823 of Figure 8. This may be the result of all or most of the blocks including the data object being lost, or the result of the unicast message reporting the lost block not being successfully received. This may also be due to changes in network information, such as a significant decrease in channel quality or many client devices being disconnected from the session or cellular network. In addition, in the eleventh step 255, the intelligent agent decides whether to send the lost block to the client device via unicast or multicast or both. In other words, the intelligent agent will decide whether to send one or more lost data blocks to the client via unicast or multicast or both multicast and unicast, or to completely stop the transmission for the lost data blocks. The intelligent agent can also end the further transmission of the data blocks in the data object. The decision can be based on the number of unsuccessful transmissions of the lost data blocks within one or more transmission windows. The intelligent agent can use the collected network information to decide to send the lost data blocks to the client device via unicast and / or multicast. This decision may be based on information collected in step 245 and optionally in step 250, and is described in more detail in method 300. This decision allows for an improvement in retransmission efficiency and potentially reduces the number of packets sent over the communications network, thereby reducing network resources used. This, combined with the lower overhead of the CoAP protocol, allows for a reduction in network resources when sending large data objects to many devices (such as in firmware updates), compared to other application protocols (RESTful or otherwise). Additionally, multicast repair may also reduce the time required to send large data objects when compared to unicasting the lost data blocks sequentially to each device, particularly in situations where there are many devices missing similar blocks.

[0076] The decision notifies the transmission configuration, and the intelligent agent can then proceed to indicate the new transmission configuration to the cellular network. This can be completed in step 260 by initiating the transmission of one or more lost data blocks according to the decision, or can be completed in advance in a discrete transmission. The transmission configuration can be to send the lost blocks to at least one client device that has not successfully received all blocks of the data object in multiple client devices via unicast, multicast, or a mixture of the two, or to stop the transmission and report failure. An example of this transmission configuration is that the first data block is unicast to some or all client devices, while the second data block is multicast to half of the client devices, and the third data block is both multicast to the same client device and unicast to different client devices to ensure successful transmission. In some embodiments, this update of the transmission configuration can be completed by updating the session.

[0077] The intelligent agent will then initiate transmission of one or more of the missing data blocks in a twelfth step 260 based on the decision in step 255. This can be through multicasting of the missing data blocks to multiple client devices in step 260a, or unicasting in step 260b, or both multicasting and unicasting based on the transmission configuration in the session. Examples of this step can be found in 817, 824, and 825 of Figure 8.

[0078] The system may then loop back to step 240, where the client device tracks which chunks were received by the transmission in step 260, passes through steps 245 to 260, and then repeats the loop until, in a thirteenth step 265, the client device indicates that it has received all of the chunks sent, or one or more transmission windows expire. Expiration of a window will cause the intelligent agent to determine that the transmission has failed and abandon further transmissions to the one or more client devices that lost chunks, such as was done in step 255. An example of this step can be found in steps 820 and 827 of FIG. 8 .

[0079] The decision to stop transmitting the lost data blocks can be based on data blocks being lost by the client device in one or more of the associated transmission windows, and / or network information collected. This determination is made by considering various factors. Examples of these factors can be the number of blocks of data objects lost by each client device, the number of client devices in the communication network, the quality of the radio channels between the client devices, any network devices between the client devices, the application server and the intelligent agent, any excess capacity in various control channels in the network, and / or the mobility of the client devices.

[0080] Once the intelligent agent has stopped transmitting due to success or failure, in the fourteenth step 270, the intelligent agent will then release the session with the cellular network and then with the client device. In the current embodiment, once the finalization phase has passed, the intelligent agent ends the communication of the data object. Once the finalization phase of one or more client devices, which also belongs to the session, has passed, the intelligent agent completes this by initiating the release of the session for one or more client devices. An example of this step can be found in step 833 of Figure 8. Then, in the fifteenth step 275, the intelligent agent will report to the application server the status of whether the transmission is successful or failed for each of the one or more client devices, and possibly the degree of failure represented by the number of lost blocks or retries required for successful transmission. An example of this step can be found in steps 835 and 839 of Figure 8.

[0081] Figure 3A flow chart is shown that illustrates an example of a method 300 performed by a network device 120 referred to as a smart proxy for reducing the use of radio resources in a radio network 100 for large data transfers between an application server 130 and a plurality of client devices 110 while using the CoAP protocol. These steps may be related to Figure 2 The steps shown in the signaling diagram of are complementary. These radio resources may be, but are not limited to, air time, power usage, network bandwidth, or any combination thereof.

[0082] exist Figure 3 In the method 300, the intelligent agent begins with a first step 305 by receiving an indication of a data object DO suitable for multicast and ready to be sent to a group of client devices from one or more application servers. The intelligent agent also receives network information from the cellular network. The information may include, but is not limited to, the number of client devices marked to receive the data object by unicast or multicast, mobility characteristics from at least one of the plurality of client devices, cell conditions (such as the number of devices), radio resource allocations, network resource allocations, available bandwidth, received signal strength and reliability of recent communication exchanges, and radio parameters for each client device (such as power usage mode and coverage extension level). The information may also include the number of client devices to which the data object is to be transmitted; the number of client devices belonging to the cell; the radio resource allocation of the cell; the network resource allocation for the cell; the available bandwidth in the cell; and / or, for each client device, at least one radio parameter derived from reference and probing channels. Indicate to the cellular network, and in turn to the client device, that it can assist the application server in providing the ability to retransmit blocks lost during potential transmission of the data object.

[0083] In a second step 310, the collected network information can then be used to decide who will be the first instance of the transmission of the data block of the data object initially, in other words, to send the data object to the client device via multicast or unicast with a block containing a portion of the data object. The decision is used to determine the initial transmission configuration. The decision can be based on the number of unsuccessful transmissions of lost data blocks within one or more transmission windows, the number of unsuccessful transmissions derived from the previous transmission of the data object, or the like. The decision can also be based on the number of lost data blocks of the data object for each client device in the client device from the previous transmission of the data object, or the like. The decision can be made using default settings or by using the information to influence the optimization algorithm. The decision can also group the client devices together in different multicast groups and individual unicast client devices. These groups and individual client devices are distinguished by, for example, which blocks are sent, network settings and / or transmission settings. These network settings can include, for example, coverage extension levels, power usage patterns and / or mobility characteristics. Transmission settings can include, for example, transmission power, bandwidth used and / or repetition of blocks sent.

[0084] An example of determining the initial transmission configuration may be that the intelligent agent decides that if the client device is at the most extreme coverage extension level, the intelligent agent will always recommend a secondary unicast transmission to the client device immediately following the multicast transmission to increase the redundancy level, thereby improving the reliability of the transmission. Another example may be that if the mobility characteristics change so that the multicast transmission of the new application server will have better reliability, the intelligent agent switches the client device to the multicast transmission of a different application server. Another example of this determination will be that the intelligent agent considers the sleep mode or other power usage mode of the client device. Considering that the client device may be an IoT or other low-capability device, the client device may be in sleep mode when a data object can be sent. Therefore, a client device in sleep mode will miss any unicast or multicast transmission sent by the application server. To avoid this situation, the intelligent agent can then create several multicast sessions, which group the client devices into, for example, 3 different groups, so that the client device can receive the initial multicast transmission when all client devices in each group are awake, and then can receive subsequent multicast retransmissions when all client devices in each group wake up again.

[0085] The intelligent agent may also determine one or more lengths of transmission windows for data chunks corresponding to data objects associated with the client device as part of the initial transmission configuration. The transmission windows may be or include a retransmission window 715, a correction window 725, and a finalization phase 735, or a mixture of all three. These windows are Figure 7305. This is accomplished using the information received in step 305. In another embodiment, the client device already has preset values ​​for the retransmission window, the correction window, and the finalization phase. In another embodiment, the client device has multiple preset values ​​for one or more windows, and the intelligent agent can specify which preset values ​​to use. One or more lengths of one or more transmission windows can be defined by the number of blocks, the number of data blocks, or the length of time. The determination of the length of the transmission window for a session can be based on the number of lost blocks in one or more transmission windows of a previous multicast or unicast session to which the client device was previously assigned, the number of data blocks in a data object, the number of client devices in the session and / or associated with the transmission window, and / or collected network information.

[0086] An example of determining the window lengths for the retransmission window and the correction window may be that if the number of users exceeds a predetermined number, the intelligent agent extends these window lengths, and for each doubling of devices, the intelligent agent extends the window by half to allow the application server time to resend lost blocks to all possible devices. Another example may be that when the client devices are far away or in poor coverage, the intelligent agent sets short window lengths of three blocks and nine blocks, respectively, because it is expected that the client device may fail to transmit, and the application server should quickly switch to a more reliable high-power unicast transmission in the event of a failure or report a complete failure and avoid unnecessary transmission of data objects. An example of determining the window length for the finalization phase may be that the correction window is particularly long, necessitating the need for a longer finalization time period.

[0087] The initial transmission configuration may include information describing a multicast or unicast session in detail, including one or more or all of the client devices that will receive data objects from the application server. The client device will be assigned to the session, whereby the session will include a start time, an indication of a multicast repair function, and information indicating the length of the transmission window of the client device that belongs to the session. The initial transmission configuration may also include information for multiple multicast and / or unicast sessions of a group of client devices that will receive data objects from the application server. The client device will be assigned to one or more of the following based on network information or the number of lost blocks in one or more transmission windows of each client device: a multicast session, a unicast session, or both a multicast session and a unicast session. Different assigned sessions will be distinguished by: which blocks will be sent in the session, when the blocks are sent, the transmission window length, network settings, and / or transmission settings.

[0088] In a third step 315, the intelligent agent may notify the client device of the multicast repair capability via the cellular network and assign the client device to one or more of the sessions. This may be accomplished by the intelligent agent initiating transmission of information indicating one or more sessions assigned to the client device and / or initiating transmission of information for initializing one or more sessions. The intelligent agent may also initiate transmission of information indicating one or more transmission windows and / or the length of one or more transmission windows.

[0089] In a fourth step 320, the intelligent proxy initiates transmission of information for initializing one or more sessions to the cellular network and, in turn, to the client device and sends the information.

[0090] In a fifth step 325, the intelligent agent receives the data object from the application server. In other embodiments, the intelligent agent may receive the data object in a single data block or a group of data blocks during transmission to the client device. Alternatively, the intelligent agent may also receive the data object from some other storage medium connected to the intelligent agent over a network.

[0091] In a sixth step 330, the intelligent proxy will initiate transmission of the data block to the cellular network for transmission to the client device in the network according to the transmission configuration of the session.

[0092] In a seventh step 335, the intelligent agent may receive a list of blocks that the client device failed to receive via the cellular network. In other words, the intelligent agent will receive at least one indication of at least one missing data block from a client device that did not successfully receive all data blocks of the data object within at least one transmission window of an earlier transmission in a communication associated with the client device.

[0093] In an eighth step 340, the intelligent agent may also receive updated network information from the application server with updated information of the same nature as in step 305. The network information may be updated with information collected from other network transmissions and / or the multicast transmission initiated in step 330.

[0094] In a ninth step 345, the intelligent agent checks whether there are any chunks that the client device is still missing from the transmission.

[0095] If there are windows in use, the intelligent agent may also check in a tenth step 350 whether the correction phase or (if used) the finalization phase has passed. And if so, the communication of the data object is terminated. If there are no lost blocks or all windows have passed, the intelligent agent may also check in an eleventh step 355 whether there are any new, previously unsent blocks in the data object that still must be sent to the client device. If there are no lost blocks or the window has passed, and there are no additional new blocks to be sent, the intelligent agent will move to step 375. However, if there are lost blocks and the window has not passed, or there are new blocks to be sent, the intelligent agent may move to step 360, or in other embodiments, directly to step 375 if the received network information indicates a poor transmission environment or other problems that necessitate the termination of the transmission.

[0096] In the twelfth step 360, the intelligent agent will decide to send one or more lost data blocks to the client device via unicast or multicast or both unicast and multicast. This can also be described as determining the transmission configuration by deciding to send the lost blocks to each client device via multicast or unicast or both. The intelligent agent can use the information collected from steps 315, 355 and possible 360 ​​(such as collected network information) to make a decision. The decision can also be based on the number of unsuccessful transmissions of lost data blocks within one or more transmission windows and / or the number of unsuccessful transmissions of lost data blocks for each data object of each client device in the client device. The determination can be made using default settings or by using the information to influence the optimization algorithm. The determination can also group the client devices together into different multicast groups and individual unicast client devices on a per-data-block basis. These groups and individual client devices are distinguished by, for example, which blocks are sent, network settings and / or transmission settings. These network settings can include, for example, coverage extension levels, power usage patterns and / or mobility features. Transmission settings can include, for example, transmission power, bandwidth used and / or repetition of blocks sent.

[0097] An example of this determination would be that client devices that share a lost block are given a multicast retransmission, and client devices that individually have lost data blocks receive a unicast transmission. For example, when only one of the plurality of client devices (client device A) loses data block 3 out of a total of 5 sent data blocks, and 3 of the plurality of client devices, C, D, and E, all lose data block 4 out of a total of 5 sent data blocks, the intelligent agent sends data block 3 to client device A via unicast, since no other client device lost data block 3, and sends data block 4 to client devices C, D, and E via multicast, since client devices C, D, and E share a common lost data block.

[0098] Another example of this determination would be if a majority of a plurality of client devices lost multiple consecutive blocks, the intelligent agent would determine, based on the possibility given the poor performance of the initial transmission, indicating that client devices that successfully transmitted may have received corrupted data blocks or no data blocks at all, that such blocks are to be multicast to all client devices and that client devices at the outermost coverage extension level may additionally receive unicast transmissions which act as a type of redundancy to ensure successful reception.

[0099] Another example of this determination may be to abandon the session entirely due to poor transmission conditions (such as abnormally high path loss) as indicated by the collected network data. This would motivate the intelligent agent to notify the application server of the failure and may initiate a new session or multiple new sessions from step 320 and restart the process with new sessions and window lengths appropriate to the network conditions.

[0100] In making the determination of which transmission method to use when sending the missing data blocks to the client device, the intelligent agent may also use various optimization algorithms widely utilized in the prior art, which may include but are not limited to multi-objective programming, vector optimization, multi-criteria optimization, multi-attribute optimization, or Pareto optimization. These may utilize the above-mentioned inputs to help make the determination.

[0101] In another embodiment, the intelligent agent may also decide to determine the length of a transmission window for a session, where the determination of the length of the transmission window for the session may be based on the number of lost blocks in one or more transmission windows from a previous multicast or unicast session to which the client device was previously assigned, the number of data blocks in a data object, the number of client devices in the session and / or associated with the transmission window, and / or collected network information.

[0102] Once the transport configuration is determined, the session or sessions will be updated accordingly.

[0103] Once the intelligent proxy has determined the transmission configuration, in a thirteenth step 365, the cellular network is then initiated by the intelligent proxy to transmit one or more of the missing data blocks via multicast or unicast, or not at all, depending on the decision / transmission configuration in step 360 and the subsequent updates to the session made in step 360. The intelligent proxy will then return to step 345 and loop again until the method reaches step 375.

[0104] In a fourteenth step 375, the intelligent proxy will then initiate a release and release the session for the client device. This may be done after the finalization phase of the client device and pertaining to the session has passed. In a final fifteenth step 380, the transmission status is reported to the application server. The transmission status may include information indicating a successful transmission or a transmission failure on a per-client device and per-data-block basis. For example, the status may indicate that data block 4 out of 5 data blocks needed to be retransmitted 3 times to a certain client device before successful reception of the data block. This information may allow for improved transmission of large data objects for future multicast session setups.

[0105] Figure 4 A flowchart is shown that illustrates an example of a method 400 performed by an application server 130 during the transfer of a data object using CoAP as in the present disclosure. The steps of the method 400 may be similar to Figure 2 The steps shown in the signaling diagram of and the steps of the method described in 300 are complementary. The application server may be a network device.

[0106] exist Figure 4 In the method 400, the application server begins with a first step 410 by communicating to the network device 120, referred to as the smart agent, and in turn to the client device, that the application server has the ability to retransmit blocks lost during potential transmission of the data object. In the present embodiment, this is accomplished by providing a uniform resource locator (URL) at the application server to the smart agent, which can receive requests for the lost blocks.

[0107] In a second step 420, the application server sends the data object to the intelligent agent for subsequent transmission to the client device.

[0108] In a third step 430, the application server receives from the intelligent proxy information about the status of the transmission of the data object for each created multicast session, and which client devices in each session successfully received the data object, partially received the data object, or failed to receive the data object. In the present embodiment, this is done towards the URL defined by the application server in step 410 for transmitting the data object.

[0109] Figure 5 A flow chart is shown that illustrates an example of a method 500 performed by a client device during the transfer of a data object using CoAP as in the present disclosure. The steps of method 300 may supplement the steps of method 500, enabling multiple client devices to communicate with a smart proxy in the manner described in method 300. The client device may be a network device or an endpoint device.

[0110] exist Figure 5In the method 500, in a first step 510, the client device receives an indication from the application server that the application server is capable of multicast repair. This can be received in the form of information related to one or more sessions created for the client device. The client device receiving the data object will then track the chunks of the data object received from the multicast transmission. As part of the session information, the client device may also receive a transmission window length. The transmission window length may include one or a combination of a retransmission window 715, a correction window 725, and / or a finalization phase 735.

[0111] In a second step 515, the client device may join the session at a time defined by the session.

[0112] In a third step 520, the client device then receives the data chunks sent from the intelligent proxy and then in a fourth step 530, a list of received data chunks will be created.

[0113] In a fifth step 540, if any block of the data object fails to be received by the client device or is received by the client device in a corrupted state, the client device will detect and record the lost block by using the list of received data blocks from step 520. The client device will then make a request for these blocks to the intelligent proxy in a sixth step 550 and receive from the intelligent proxy in a seventh step 560 any retransmitted data blocks sent by the cellular network within the time limit defined by the correction window. The client device then repeats steps 530 to 560 until an eighth step 570, in which the transmission is deemed completed or failed by the client device, or (if applicable) the time for the correction window or the window length of the finalization phase has expired and the entire transmission is also deemed to have failed, and an indication of this situation is sent to the intelligent proxy. Finally, in a ninth step 580, the session is dropped.

[0114] Figure 6 A diagram illustrating an example of a data object 600 for an embodiment of the present disclosure is shown. The data object includes 9 data blocks 601 to 609. In order for a data object to be usable, it must contain all of its constituent blocks. In other embodiments, a data object may have duplicate blocks or blocks that serve diversity or error correction purposes (such as error correction parity data in the event of a lost data block). An example of a data object may be a firmware update for a client device. In the current embodiment, the data object is sent using the CoAP block-by-block protocol.

[0115] Figure 7 Figures illustrating examples of embodiments of the present disclosure are shown. Figure 7, a retransmission window 715, a correction window 725, and a finalization phase 735 are shown along a line with arrows, which represent time and direction of time, respectively. The retransmission window and the correction window can be defined by the number of blocks sent or a set length of time. However, if the blocks are poorly received by the client device, the finalization phase must be a set length of time, which will allow the transmission to eventually stop. The network device 120 is referred to as an intelligent agent.

[0116] Figure 7 The embodiment depicts a block-based length definition, where the time length of the finalization phase is equal to the time required to send the correction window and the retransmission window. Each vertical dashed line indicates a time slot of sufficient length for sending three data blocks, and corresponds to an example length of the retransmission window for three data blocks. In some embodiments, the retransmission window can set a random length to the retransmission window, where the length is a range of blocks from 0 to an integer set by the intelligent agent, or a time limit from zero to a value set by the intelligent agent. Data object 600 is sent using the CoAP block-by-block protocol. Blocks with solid outlines are successfully received blocks, such as blocks 601 and 603. Blocks with dashed outlines, such as 602 and 604, are blocks that have been lost or blocks that have been received but damaged. Blocks with dashed outlines below these, such as 602 and 604, are blocks that the receiver requests retransmission and are to be retransmitted in subsequent windows in the current embodiment. In other embodiments, the retransmitted blocks can be retransmitted in a later window instead of in an immediately subsequent window, or in a dedicated window for retransmission.

[0117] Retransmission window 715 starts from the beginning of the transmission of the data object and ends after three blocks, possibly with a margin. In other embodiments, these retransmission windows may not directly follow each other, but have a regular or scheduled interval between them. In this interval, the client device 110 tracks all blocks received, and if a data block (e.g., data block 602) is lost or damaged (such as 602 or 604), the client device 110 will notify the proxy server of the lost or damaged data block in the second retransmission window after the first retransmission window has expired. The client device also requests retransmission of the data block lost in the second retransmission window, as can be seen for data block 602a. Then, the client device will wait for the third retransmission window, in which data block 602b, i.e., a retransmission of data block 602, is sent. The number of these back and forth cycles is limited by the correction window 620, which determines when the client device can no longer request a retransmission, but must indicate the failure of receiving a packet. The correction window starts from the beginning of the transmission of the data object and ends after the length of 4 retransmission windows in this example. The correction window should have a length that is at least a multiple of the retransmission window. If the client device 110 receives a missing data block, such as data block 604c, the transmission of data block 604 is determined to be successful. However, in Figure 7 In the embodiment of the present invention, the client device still loses data block 602b, allowing one or more requests for data block 602 in the form of data block 602c before the correction window 620 is passed. If the client device loses data block 602d, then due to the correction window, the client device will not be able to request a retransmission of data block 602, and the proxy server will be notified that the client device has failed to receive data block 602 and therefore failed to receive the data object in its entirety. In some embodiments, the intelligent proxy will receive an indication that the transmission has completely failed. In other embodiments, the intelligent proxy will receive a report indicating which data block has failed to be received, and may attempt to send the data block as a separate data object in a different multicast or unicast session.

[0118] The correction window is critical because in some embodiments retransmissions may take up space for new data blocks in the transmitted data object, and without a correction window, if all blocks are requested for retransmission, the transmission may never end. Once all data blocks of a data object have been sent at least once, the intelligent agent will initiate a finalization phase. This can be done by, for example, repeatedly sending the last data block of the data object (data block 609) at a low frequency or sending a dedicated message or any data block of the data object. In this example, this is three repetitions over subsequent retransmission windows. This notifies the client device that no new data blocks will be sent and only corrections will be processed.

[0119] The finalization time period allows all correction windows associated with their respective data blocks to expire, and allows the intelligent agent to retransmit any lost blocks when allowed. An example of this would be if data block 609 was consistently lost, whereby the last possible opportunity to receive a retransmission of data block 609 would be in the first time slot of the third row. Therefore, the finalization time period should be the length of the correction time period plus additional time for initiating the finalization phase. These three windows allow the multicast retransmission functionality of the present embodiment to not permanently take over the network, which might otherwise attempt to retransmit lost blocks before receiving the entire data object, or repeatedly attempt to retransmit lost blocks until the retransmission is successful (which might never happen).

[0120] FIG8 shows a signaling diagram illustrating an embodiment of the present disclosure. This embodiment may correspond to and be described in more detail Figure 2 The network device 120 is part of the embodiment described in , but the two embodiments should not necessarily be considered as the same embodiment of the present disclosure. The network device 120 is called an intelligent agent.

[0121] Starting with a first step 801, the smart agent receives an indication of a data object (DO) to be sent to a client device in a data block (DB) from an application server (AS). This is achieved by the smart agent receiving a PUT object delivery service URL including a DO reference 800, which is sent from the IoT-AS-ObjectHandler to the Object-Delivery-Service and has a payload {data-object-reference, device-group-descriptor}. In a second step 802, the smart agent accepts the PUT object by notifying the AS of an acceptance with a payload {service-request-id}, and in a third step 803, the smart agent receives network information of the collected device group from the cellular network. The information may also include the number of client devices to which the data object will be transmitted; the number of client devices belonging to the cell; the radio resource allocation of the cell; the network resource allocation for the cell; the available bandwidth in the cell; and / or, for each client device, at least one radio parameter derived from the reference and sounding channels. Indicates to the cellular network, and in turn to the client device, that it can assist the application server in providing the ability to retransmit blocks lost during potential transmission of the data object.

[0122] Then, in a fourth step 804, the intelligent agent determines the number of multicast (MC) sessions, the characteristics of the multicast sessions, and any subgroups of devices, all based on the collected network information. This is used to assign the client device to one or more of the following: a multicast session, a unicast session, or both a multicast session and a unicast session, the session including a start time, an indication of a multicast repair function, and information indicating the length of the transmission window of the client device belonging to the session. The length of the transmission window of the session can be based on the number of lost blocks in one or more transmission windows of a previous multicast or unicast session to which the client device was previously assigned, the number of data blocks in a data object, the number of client devices in the session and / or associated with the transmission window, and / or the collected network information. The session will be assigned to the session based on the number of lost blocks in multiple transmission windows of the network information or each client device. The session will be distinguished by: which blocks will be sent in the session, when the blocks are sent, the transmission window length, the network settings, and / or the transmission settings. As part of this step, the intelligent agent also determines one or more transmission windows corresponding to the data blocks of the data object associated with the client device. The intelligent agent also determines one or more lengths of one or more transmission windows, the one or more lengths being defined by the number of blocks or the length of time.

[0123] In a fifth step 805, the intelligent proxy initiates transmission of information indicating one or more sessions assigned to one or more client devices by unicasting to each client device when the (UC) client device will next be reachable, and communication details about the multicast session, the multicast session being defined using the following example message:

[0124] CoAP.REQ:PUT multicast-session-object-id {session parameters:

[0125] -Session start time

[0126] -Retransmission-Service-URL

[0127] -Retransmission window size

[0128] -Correction window factor

[0129] - Finalization phase size

[0130] -…}

[0131] This is used to initiate the transmission of information indicating one or more transmission windows and / or the length of one or more transmission windows. Wherein the session start time is the time at which the multicast transmission is assumed to start, the retransmission service URL is the URL to which the client device will also send a list of lost packets, the retransmission window size defines the size of the retransmission window (RW), the correction window (CW) factor defines the size of the correction window to be expressed in terms of the retransmission window, the finalization phase (FP) size defines the size of the finalization phase, and the ellipsis contains any other necessary parameters for fully defining the multicast session of the client device. These details are used to inform the client device of the multicast repair function implemented by the intelligent proxy. In the sixth step 806, the client device will store the session information from the CoAP.REQ:PUT message in step 805, and the session information is a wake-up timer for the multicast session so that the client device will join the session and listen to the transmission at the appropriate time. Once this step is completed, the client device will confirm the successful establishment of the session with the message CoAP.ACK:800OK in the seventh step 807. Then, in the eighth step 808, the intelligent agent will use the message GET Data-Object-Reference to request the data object DO from the application server, and in the ninth step 809, the application server will send the intelligent agent an 800OK{data object} message containing DO. Then, the intelligent agent will store DO in the tenth step 810.

[0132] From here, for each multicast session determined by the intelligent agent in step 804, steps 811 to 834 will loop once. The steps for describing a single loop of a single multicast session will be described in detail. An embodiment will include multiple loops for multiple multicast sessions. In the eleventh step 811, the multicast session wake-up timer for the client device will expire, and the client device will be ready to receive data associated with the data object. Then, in the twelfth step 812, the intelligent agent will initiate the transmission of information for initializing one or more sessions by sending a message with parameters to the cellular network, which is a multicast session with predetermined parameters from step 804. In the thirteenth step 813, the cellular network will receive the initialization message and establish a multicast session for the intelligent agent, the cellular network, and the client device. Then, in the fourteenth step 814 repeated for each client device, the client device will join the multicast session.

[0133] Now, all is set to start the transmission of the data object, and in the fifteenth step 815, the intelligent agent will multicast the data blocks in the first retransmission window. This is done in the current embodiment according to the format used in the standard RFC7959 using the Block1 / 2 format. However, alternative methods of multicasting and unicasting data blocks according to the CoAP standard should be readily apparent to those skilled in the art. One such alternative would be CoAP with Quick-Block1 proposed by the IETF memorandum draft-ietf-core-new-block-01. Then, in the sixteenth step 816, the client device will collect a list of missing data blocks from this first multicast transmission. This begins a loop from the second to the final retransmission window for steps 817 to 827 within the correction window. Some of these steps in the loop rely on certain criteria, so that all steps and their corresponding criteria will be as described in the process of the first loop for steps 817 to 823 and the last loop for steps 824 to 826.

[0134] If there are missing data blocks from the previous retransmission window recorded by the client device, the seventeenth step 817 and the eighteenth step 818 are triggered. In step 817, the intelligent proxy receives a unicast report of missing data blocks from the client device using the message CoAP.REQ:PUT retransmission-service-URL{list of missing blocks}. The unicast report includes at least one indication of at least one missing data block from the client device that did not successfully receive all data blocks of the data object within at least one transmission window of an earlier transmission in the communication associated with the client device. Then in step 818, the intelligent proxy sends an acknowledgment to the client device using the message CoAP.ACK:800OK.

[0135] In an embodiment where the intelligent proxy has the ability to preemptively close a session based on the network information, a nineteenth step 819 and a twentieth step 820 are performed. The intelligent proxy receives collected network information having the same characteristics as the network information collected in step 803, but updated to be as recent as possible. Then, in step 820, if it is determined that the network information indicates a network condition that is unfavorable to further transmission (such as a client device disconnecting from the network, channel conditions becoming sufficiently poor, or a number of unsuccessful transmissions of lost data blocks within one or more transmission windows), the intelligent proxy closes the current multicast session.

[0136] In an embodiment of the present invention where there is a dedicated space for retransmission of previously transmitted lost data blocks, the twenty-first step 821, the twenty-second step 822, and the twenty-third step 823 are always run in a loop. If the number of blocks comprising the data object is less than the length of the correction window, these steps are skipped. In step 821, the intelligent agent multicasts the latest data blocks of the data object. In step 821, the client device checks the list of any lost data blocks from multicast in step 819. Then in step 823, the intelligent agent decides to send one or more lost data blocks recorded from step 817 to the client device via unicast, multicast, or both unicast and multicast. The decision can be based on the number of unsuccessful transmissions of one or more of the lost data blocks within one or more transmission windows. The decision can also be based on the number of lost data blocks of the data object of each client device in the client device. The intelligent agent can also make a decision using the collected network information.

[0137] If there are lost data blocks from the previous retransmission window within the correction window, the twenty-fourth step 824 and the twenty-fifth step 825 are triggered. In step 824, the intelligent agent sends one or more lost data blocks to the client multicast according to the decision, and thereby to the multicast session and all client devices belonging to it. In step 825, the intelligent agent sends one or more lost data blocks via unicast according to the decision made in step 823. Sending the lost data blocks to the selected client devices via unicast depends on whether there is a limited number of client devices that have lost data blocks, whether there is a need for more reliable unicast transmission, or whether there is a need for diversity in the transmission of data blocks to client devices. An example of this decision can be found in method 200.

[0138] In the event that the lost data block is successfully retransmitted from the intelligent proxy to the client device via the cellular network, a twenty-sixth step 826 enables the client device to repair any incomplete data block ranges in the data object using the lost data block. The client device may also repair any individual lost blocks if the retransmission of the lost data block is able to successfully send enough data to repair the lost data block.

[0139] If there are still lost or damaged data blocks after the correction window for lost or damaged blocks has passed, steps 827 to 830 are triggered. In the twenty-seventh step 827, the intelligent agent can receive an optional report of a data object compilation failure in the form of a message CoAP.REQ:PUT retransmission-service-URL{error: object compilation failed}. Then in the twenty-eighth step 828, the intelligent agent stores the ID of any client device that reports an object compilation failure indicating that all blocks have not been received. In the twenty-ninth step 829, the intelligent agent sends an acknowledgment to the client device in the form of a message CoAP.ACK:800OK. Then, in the thirtieth step 830, the client device stops the object download and then leaves the multicast session.

[0140] Once the final data block in the data object has been sent, the finalization phase begins. This allows the remaining blocks to complete their respective correction windows and notifies the client device that no new blocks are being sent. The beginning of this phase begins with the thirty-first step 831 and the thirty-second step 832. In step 831, the intelligent agent multicasts the last data block of the data object at a low frequency to indicate the end of the data object and the beginning of the finalization phase. In step 832, the client device identifies the finalization phase from the low data throughput and is prepared to strictly receive and repair the blocks that have been sent. From here, steps 817 to 830 are repeated for data blocks that have a "correction window" time remaining in the finalization phase. The retransmission window in this phase is called the finalization window. This means that the finalization phase consists of n plus one finalization window, where n is the length of the correction window.

[0141] Once the finalization phase is completed, the intelligent agent initiates the release of the session for one or more client devices in the thirty-third step 833. This is done after the finalization phase of the client device and belonging to the session has passed. This is done by sending a message including an indication of ending the current multicast session to the cellular network. In other words, once the finalization phase has passed, the intelligent agent ends the communication of the data object. After receiving the indication, the cellular network will then release the intelligent agent and any still connected client devices from the multicast session in the thirty-fourth step 834. Then, in the thirty-fifth step 835, the intelligent agent sends a PUT object delivery service URL (800) message to the application server, from the object-delivery-service to the IoT-AS-object handler, with a payload {error report: list of failed client devices}. Then, in the thirty-sixth step 836, the application server then stores a list of all failed client devices for the multicast session for further processing, which may include scheduling future transmissions of data objects. Then, at the end of the loop for a particular multicast session that starts at step 811, the intelligent agent receives a confirmation message in the form of 800OK in the thirty-seventh step 837.

[0142] Once all multicast sessions have been completed, the smart agent deletes the data object obtained from the application server and stored in step 810 in a thirty-eighth step 838. In a thirty-ninth step 839, the smart agent sends a PUT IoT-AS-object-handler URL message from the object-delivery-service to the IoT-AS-object handler with a payload {request=service-request-id that was executed successfully or executed with an exception or failure (error-description)}, which is a report on how the transmission of the data object was performed. The method ends with a final fortieth step 840, in which the smart agent receives a confirmation from the application server that "it received the performance report sent in step 839".

[0143] Fig. 9 is a block diagram of an application server 130 according to some embodiments. Fig. 9As shown, the application server 130 may include: a processing circuit 810, which may include one or more processors (e.g., a general-purpose microprocessor and / or one or more processors, such as an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), etc.); a communication interface 820 for communicating with other devices connected to the network 100; and a storage medium 830, which may include one or more non-volatile storage devices and / or one or more volatile storage devices (e.g., a random access memory (RAM)). In an embodiment where the application server includes a processing circuit, a computer program product may be provided. The computer program product 1510 includes a computer-readable medium 1520, such as, but not limited to, a storage medium, a magnetic medium (e.g., a hard disk), an optical medium, a memory device, etc. The storage medium may contain a computer program 1530a, which contains computer-readable instructions 1540a, which, when executed by the processor circuit, cause the processor circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processor circuit may be defined to include a storage medium, so that a separate storage medium is not required.

[0144] Fig.10 is a diagram illustrating functional units of an application server 130 according to some embodiments. Fig. 9 As shown, the application server includes multiple functional modules: an indication module configured to perform step 410; a sending module configured to perform step 420; and a receiving module configured to perform step 330. In general, each functional module can be implemented in hardware or software. Preferably, one or more or all functional modules can be implemented by a processing circuit (possibly in cooperation with a communication interface and / or a storage medium). Therefore, the processing circuit can be arranged to retrieve instructions from the storage medium to perform any steps of the application server 130 as disclosed herein.

[0145] Fig.11 is a block diagram of a client device 110 according to some embodiments. Fig.11As shown, the client device 110 may include: a processing circuit 1110, which may include one or more processors (e.g., a general-purpose microprocessor and / or one or more processors such as an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.); a communication interface 1120 for communicating with other devices connected to the network 100; and a storage medium 1130, which may include one or more non-volatile storage devices and / or one or more volatile storage devices (e.g., a random access memory (RAM)). In embodiments where the client device includes a programmable processor, a computer program product may be provided. The computer program product 1510 includes a computer-readable medium 1520, such as, but not limited to, a storage medium 1130, a magnetic medium (e.g., a hard disk), an optical medium, a memory device, etc. The storage medium may include a computer program 1530b, which includes computer-readable instructions 1540b, which, when executed by the processor circuit 1110, cause the processor circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processor circuit 1110 may be defined to include a storage medium, so that a separate storage medium is not required.

[0146] Fig.12 is a diagram illustrating functional units of a client device 110 according to some embodiments. Fig.12 As shown, the client device includes multiple functional modules: a receiving module configured to perform step 510; a joining module configured to perform step 515; a receiving module configured to perform step 520; a creating module configured to perform step 530; a creating module configured to perform step 540; a sending module configured to perform step 550; a receiving module configured to perform step 560; a notification module configured to perform step 570; and a discarding module configured to perform step 580. In general, each functional module can be implemented in hardware or software. Preferably, one or more or all functional modules can be implemented by a processing circuit (possibly in cooperation with a communication interface and / or a storage medium). Therefore, the processing circuit can be arranged to retrieve instructions from the storage medium to perform any steps of the client device 110 as disclosed herein.

[0147] Fig.13 is a block diagram of a network device 120 according to some embodiments. Fig.13As shown, the intelligent agent 120 may include: a processing circuit 1310, which may include one or more processors (e.g., a general-purpose microprocessor and / or one or more processors such as an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.); a communication interface 1320 for communicating with other devices connected to the network 100; and a storage medium 1330, which may include one or more non-volatile storage devices and / or one or more volatile storage devices (e.g., a random access memory (RAM)). In an embodiment where the network device includes a programmable processor 1310, a computer program product may be provided. The computer program product includes a computer-readable medium 1520, such as, but not limited to, a storage medium 1330, a magnetic medium (e.g., a hard disk), an optical medium, a memory device, etc. The storage medium may contain a computer program 1530c, which contains computer-readable instructions 1540c, which, when executed by the processor circuit 1310, cause the processor circuit to perform operations according to the embodiments disclosed herein. According to other embodiments, the processor circuit 1310 may be defined to include a storage medium, so that a separate storage medium is not required.

[0148] Fig.14 is a diagram illustrating functional units of a network device 120 according to some embodiments. Fig.14 As shown, the client device includes multiple functional modules: a receiving module configured to perform step 305; a determining module configured to perform step 310; a notifying module configured to perform step 315; an initiating module configured to perform step 320; a receiving module configured to perform step 325; an initiating module configured to perform step 330; a receiving module configured to perform step 335; a receiving module configured to perform step 340; an are module configured to perform step 345; a have module configured to perform step 350; a determining module configured to perform step 355; an initiating module configured to perform step 360; a do module configured to perform step 370; a releasing module configured to perform step 375; and a reporting module configured to perform step 380. In general, each functional module can be implemented in hardware or software. Preferably, one or more or all functional modules can be implemented by a processing circuit (possibly in cooperation with a communication interface and / or a storage medium). Thus, the processing circuitry may be arranged to retrieve instructions from the storage medium to perform any of the steps of the network device 120 as disclosed herein.

[0149] Fig.15 FIG. 1 is a diagram showing an embodiment of the present invention. Fig.15As shown, the computer program product 1510 includes a computer readable medium 1520 storing computer programs 1530a, 1530b, 1530c, and the computer programs 1530a, 1530b, 1530c include computer readable instructions 1540a, 1540b, 1540c. The computer readable medium can be, but is not limited to, storage media 930, 1130, 1330, magnetic media (e.g., hard disk), optical media, memory devices (e.g., random access memory, flash memory), etc.

[0150] In addition, although various embodiments of the present disclosure are described herein, it should be understood that they are presented only by way of example, and not by way of limitation. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above exemplary embodiments. In addition, unless otherwise indicated herein or contradictory to the context, any combination of the above elements with all possible variations thereof is included by the present disclosure.

[0151] Additionally, although the processes described above and shown in the accompanying drawings are shown as a sequence of steps, this is for illustrative purposes only. Therefore, it is conceivable that some steps may be added, some steps may be omitted, the order of the steps may be rearranged, and some steps may be performed in parallel.

Claims

1. A network device (120) for use in a communication network (100) and configured to assist an application server (130) in communicating a data object (600) to a client device (110) using a constrained application protocol CoAP, wherein: The data object includes a data block (601-609), and the network device includes: a processor circuit and a storage unit storing instructions that, when executed by the processor circuit, render the network device operable to: Notifying the client device (215, 315, 805) of a multicast repair function enabled by the network device; receiving (245, 330, 817) at least one indication of at least one missing data block from a client device among the client devices that did not successfully receive all of the data blocks of the data object within at least one transmission window (715, 725, 735) of an earlier transmission in a communication associated with the client device; Deciding (255, 360, 823) to send one or more missing data blocks to the client device via unicast or multicast or both unicast and multicast; and Based on the determination, transmission of the one or more missing data blocks is initiated (260, 365, 824, 825).

2. The network device according to claim 1, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: Determining (310, 804) one or more transmission windows corresponding to data chunks of the data object associated with the client device, the transmission windows being or comprising: a retransmission window (715) that defines how long the client device should wait to receive one or more lost data blocks before indicating that one or more data blocks have been lost; a correction window (725) that defines how long the client device should wait after communicating that the one or more lost data blocks are lost before reporting an error in communication of the one or more data blocks; and / or The finalization phase (735) defines how long the communication should remain open.

3. The network device according to claim 2, wherein: The transmission window or one of the transmission windows is or includes the finalization phase, and the instructions, when executed by the processing circuitry, cause the network device to become operable to: Once the finalization phase has passed, the communication of the data object is terminated (270, 350, 833).

4. The network device according to any one of claims 1 to 3, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: Transmission of information indicating one or more transmission windows and / or lengths of the one or more transmission windows is initiated (215, 315, 805).

5. The network device according to any one of claims 1 to 4, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: One or more lengths of the one or more transmission windows are determined (310, 804), the one or more lengths being defined by a number of data blocks or a time length.

6. The network device according to any one of claims 1 to 5, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: Based on the number of unsuccessful transmissions of the lost data blocks within the one or more transmission windows, a decision is made (255, 360, 823) to send the lost data blocks to the client device via unicast or multicast or both unicast and multicast.

7. The network device according to any one of claims 1 to 6, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: Using the number of missing data blocks of the data object for each of the client devices, it is determined (310, 360, 823) to send the missing data blocks to the client devices via unicast or multicast or both unicast and multicast.

8. The network device according to any one of claims 1 to 7, comprising: Connections used to facilitate communication between multiple application servers and groups of client devices for the purposes of multicast and unicast transmissions.

9. The network device of any one of claims 1-8, wherein the instructions, when executed by the processor circuit, cause the network device to become operable to collect (210, 250, 305, 340, 803, 819) network information, the network information comprising: the number of client devices to which the data object is to be transmitted; mobility characteristics of at least one client from the plurality of clients; the number of client devices belonging to the cell; Radio resource allocation for cells; Network resource allocation for cells; The available bandwidth in the cell; and / or For each client device, at least one radio parameter is derived from the reference and probing channels.

10. The network device according to claim 9, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: Assigning (310, 804) the client device to one or more of: a multicast session, a unicast session, or both a multicast session and a unicast session, the session comprising: Start time; indication of multicast repair functionality; and Information indicating the length of the transmission window of the client device belonging to the session.

11. The network device according to any one of claims 9 and 10, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: Based on network information or a number of lost data blocks in one or more transmission windows of each client device, the client devices are assigned (310, 804) to one or more of: a multicast session, a unicast session, or both a multicast session and a unicast session, the sessions being distinguished by: which data blocks are to be sent in said session; When the data block is sent; Transmission window length; Network settings; and / or Transfer settings.

12. The network device according to any one of claims 1 to 11, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: initiating (215, 315, 805) transmission of information indicative of one or more sessions assigned to the client device; and / or Transmission of information for initializing one or more sessions is initiated (220, 320, 812).

13. The network device according to any one of claims 10 to 12, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: Determining (310, 360, 804) a length of a transmission window for the session, the determination being based on: a number of lost data blocks from one or more transmission windows of a previous multicast or unicast session to which the client device was previously assigned; the number of data blocks in the data object; The number of client devices; and / or Network Information Collected.

14. The network device according to any one of claims 10 to 13, wherein: The transmission window is or one of the transmission windows includes the finalization phase, and the instructions, when executed by the processing circuitry, cause the network device to become operable to: Once the finalization phase of the client device and of the session has passed, a release of the session is initiated (270, 375, 833) for the client device.

15. The network device according to any one of claims 9 to 14, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: The collected network information is used to decide (255, 360, 823) to send the missing data blocks to the client device via unicast and / or multicast.

16. The network device according to any one of claims 9 to 15, wherein: The instructions, when executed by the processor circuit, cause the network device to become operable to: The collected network information is used to decide (310, 804) to first send the data chunks of the data object to the client device via multicast and / or unicast prior to any retransmission.

17. The network device according to any one of claims 1 to 16, wherein: The instructions, when executed by the processing circuit, cause the network device to be operable to: A decision (265) is made to stop transmission of the lost data block based on the following information: The data block is lost by the client device within one or more associated transmission windows; and / or Network Information Collected.

18. A method performed by a network device for facilitating retransmission of lost data blocks from a multicast transmission of a data object from an application server to a client device using a constrained application protocol CoAP, the method comprising: Notifying the client device (215, 315, 805) of a multicast repair function enabled by the network device; receiving (245, 330, 817) at least one indication of at least one missing data block from a client device among the client devices that did not successfully receive all of the data blocks of the data object within at least one transmission window (715, 725, 735) of an earlier transmission in a communication associated with the client device; Deciding (255, 360, 823) to send one or more missing data blocks to the client device via unicast or multicast or both unicast and multicast; as well as Based on the determination, transmission of the one or more missing data blocks is initiated (260, 365, 824, 825).

19. The method according to claim 18, comprising: determining (310, 804) one or more transmission windows corresponding to the one or more lost data blocks of the client device, the transmission windows being or comprising: a retransmission window (715) that defines how long the client device should wait to receive one or more lost data blocks before indicating that one or more data blocks have been lost; a correction window (725) that defines how long the client device should wait after communicating that the one or more lost data blocks are lost before reporting an error in communication of the one or more data blocks; and / or The finalization phase (735) defines how long the communication should remain open.

20. The method according to claim 19, wherein: The transmission window or one of the transmission windows is or includes the finalization phase, and the method comprises: Once the finalization phase has passed, the communication of the data object is terminated (270, 350, 833).

21. The method according to any one of claims 18 to 20, comprising: Transmission of information indicating one or more transmission windows and / or lengths of the one or more transmission windows is initiated (215, 315, 805).

22. The method according to any one of claims 18 to 21, comprising: One or more lengths of the one or more transmission windows are determined (310, 804), the one or more lengths being defined by a number of data blocks or a time length.

23. The method according to any one of claims 18 to 22, comprising: Based on the number of unsuccessful transmissions of the lost data blocks within the one or more transmission windows, a decision is made (255, 360, 823) to send the lost data blocks to the client device via unicast or multicast or both unicast and multicast.

24. The method according to any one of claims 18 to 23, comprising: Using the number of missing data blocks for the data object of each of the client devices, it is determined (310, 360, 823) to send the missing data blocks to the client devices via unicast or multicast or both unicast and multicast.

25. The method according to any one of claims 18 to 24, comprising: Facilitates multiple application servers to communicate with multiple groups of client devices for the purposes of multicast and unicast transmissions.

26. The method according to any one of claims 18 to 25, comprising: Collect (210, 250, 305, 340, 803, 819) network information, the network information including: the number of client devices to which the data object is to be transmitted; mobility characteristics from at least one of the client devices; the number of client devices belonging to the cell; Radio resource allocation for cells; Network resource allocation for cells; The available bandwidth in the cell; and / or For each client device, at least one radio parameter is derived from the reference and probing channels.

27. The method according to claim 26, comprising: Assigning (310, 804) the client device to one or more of: a multicast session, a unicast session, or both a multicast session and a unicast session, the session comprising at least: Start time; indication of multicast repair functionality; and Information indicating the length of the transmission window of the client device belonging to the session.

28. The method according to any one of claims 26 or 27, comprising: Based on network information or a number of lost data blocks in one or more transmission windows of each client device, the client devices are assigned (310, 804) to one or more of: a multicast session, a unicast session, or both a multicast session and a unicast session, wherein the unicast and multicast sessions are distinguished by: which data blocks are to be sent in said session; When the data block is sent; Transmission window length; Network settings; and / or Transfer settings.

29. The method according to any one of claims 18 to 28, comprising: initiating (215, 315, 805) transmission of information indicative of one or more sessions assigned to the client device; and / or Transmission of information for initializing one or more sessions is initiated (220, 320, 812).

30. The method according to any one of claims 26 to 29, comprising: Determining (310, 360, 804) a length of a transmission window for the session, the determination being based on: a number of lost data blocks from one or more transmission windows of a previous multicast or unicast session to which the client device was previously assigned; the number of data blocks in the data object; The number of client devices; and / or Network Information Collected.

31. The method according to any one of claims 27 to 30, wherein: The transmission window or one of the transmission windows includes or comprises the finalization phase, the method comprising: Once the finalization phase for the client device belonging to the session has passed, a release of the session is initiated (270, 375, 833) for the client device.

32. The method according to any one of claims 26 to 31, comprising: The collected network information is used to decide (255, 360, 823) to send the missing data blocks to the client device via unicast and / or multicast.

33. The method according to any one of claims 26 to 32, comprising: The collected network information is used to decide (310, 804) to first send the data chunks of the data object to the client device via unicast and / or multicast prior to any retransmission.

34. The method according to any one of claims 18 to 33, comprising: A decision (265) is made to stop transmission of the lost data block based on the following information: The data block is lost by the client device in one or more associated transmission windows; and Network Information Collected.

35. A computer program comprising computer readable instructions for facilitating an application server to communicate with a plurality of clients using a constrained application protocol, CoAP, which when executed on processing circuitry of a network device causes the network device to: Notifying the client device (215, 315, 805) of a multicast repair function enabled by the network device; receiving (245, 330, 817) at least one indication of at least one missing data block from a client device among the client devices that did not successfully receive all of the data blocks of the data object within at least one transmission window (715, 725, 735) of an earlier transmission in a communication associated with the client device; Deciding (255, 360, 823) to send one or more missing data blocks to the client device via unicast or multicast or both unicast and multicast; and Based on the determination, transmission of the one or more missing data blocks is initiated (260, 365, 824, 825).

36. A computer program comprising computer readable instructions for assisting an application server in communicating with a plurality of clients using a constrained application protocol CoAP, the computer readable instructions when executed on a processing circuit of a network device causing the network device to perform the method according to any one of claims 19-34.

37. A computer program product comprising a computer program according to claim 35 or 36 and a computer readable storage medium on which the computer program is stored.