Patent Description:
A similar method is for example disclosed in document <NPL>).

In some implementations, a method may include providing, to a network device, a subscribe request that includes a request for sensor data based on an event, and receiving, based on the subscribe request, sensor data packets, wherein each of the sensor data packets includes the sensor data for one or more elements of the network device, a header extension that includes a respective group identifier for a respective group of sensor data, and final packet information indicating whether the sensor data packet is a final one for the respective group. The method may include storing the sensor data packets until the final packet information of one of the sensor data packets indicates that the one of the sensor data packets is a final sensor data packet for the respective group of sensor data, and identifying a complete set of the sensor data packets when the final packet information of the one of the sensor data packets indicates that the one of the sensor data packets is the final sensor data packet for the respective group of sensor data. The method may include performing one or more actions based on the complete set of the sensor data packets.

In some implementations, a device may include one or more memories, and one or more processors to provide, to a network device, a subscribe request that includes a request for sensor data based on an event, and receive, based on the subscribe request, sensor data packets, wherein each of the sensor data packets includes the sensor data for one of a plurality of interfaces of the network device, a header extension identifying a respective group identifier and final packet information indicating whether the sensor data packet is a final one for a group of sensor data associated with the respective group identifier. The one or more processors may store the sensor data packets until the final packet information of one of the sensor data packets indicates that the one of the sensor data packets is a final sensor data packet for the respective group identifier, and may identify a complete set of the sensor data packets when the final packet information of the one of the sensor data packets indicates that the one of the sensor data packets is the final sensor data packet for the group of sensor data. The one or more processors may analyze the complete set of the sensor data packets to generate at least one result, and may perform one or more actions based on the at least one result.

In some implementations, a computer-readable medium may store a set of instructions that includes one or more instructions that, when executed by one or more processors of a device, cause the device to provide, to a network device, a subscribe request that includes a request for sensor data based on an event, wherein the subscribe request causes the network device to install software-defined sensors that collect the sensor data associated with a plurality of elements of the network device. The one or more instructions may cause the device to receive, based on the subscribe request, sensor data packets, wherein each of the sensor data packets includes the sensor data for one of the plurality of elements of the network device, a header extension identifying a respective group identifier and final packet information indicating whether the sensor data packet is a final one for a group of sensor data associated with the respective group identifier. The one or more instructions may cause the device to store the sensor data packets until the final packet information of one of the sensor data packets indicates that the one of the sensor data packets is a final sensor data packet for the group of sensor data. The one or more instructions may cause the device to identify a complete set of the sensor data packets when the final packet information of the one of the sensor data packets indicates that the one of the sensor data packets is the final sensor data packet for the group of sensor data, and perform one or more actions based on the complete set of the sensor data packets. A computer readable medium may include non-transitory type media such as physical storage media including storage discs and solid state devices. A computer readable medium may also or alternatively include transient media such as carrier signals and transmission media. A computer-readable storage medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

A telemetry collector device may utilize a subscribe request (e.g., a remote procedure call (RPC) request) to cause a target device (e.g., a network device) to install software-defined sensors that collect sensor data (e.g., data associated with operation of the network device) with a particular frequency (e.g., periodically, when a change occurs, based on a threshold, and/or the like). For example, the software-defined sensors may collect sensor data identifying routes associated with the network device, a temperature of the network device, throughput of ports of the network device, input bytes of the network device, output bytes of the network device, neighbor routes associated with the network device, processor utilization by the network device, and/or the like. The network device may provide the sensor data to the collector device at a configured reporting interval that is based on the particular frequency. The network device may include thousands, tens of thousands, and/or the like interfaces, and a wrap may occur when the sensor data is received from all of the elements of the network device.

However, for software-defined sensors that are configured for periodic sampling or for software-defined sensors that inherently support only periodic sampling, there is no defined method for the collector device to identify, during real-time, whether the network device has reported all of the sensor data for a wrap. Identifying the wrap as early as possible may enable the collector device to take an appropriate action for the network device. Current techniques for determining that the network device has reported all of the sensor data for a wrap require the collector device to cache sensor data from a previous wrap until a next wrap is completed. Such techniques cause the collector device to expend significant memory resources (e.g., for storing the sensor data) and processing resources (e.g., for comparing the sensor data to determine completion of a wrap). Thus, current techniques for collecting sensor data and/or for determining that the network device has reported all of the sensor data for a wrap waste computing resources (e.g., processing resources, memory resources, communication resources, and/or the like), network resources, and/or the like associated with storing sensor data, comparing the sensor data to determine completion of a wrap, delayed detection of completion of a wrap, delayed performance of actions in response to analysis of a wrap, and/or the like.

Some implementations described herein relate to a collector device that provides real-time detection of completion of collected sensor data of a network device (e.g., sensor data for a wrap). For example, the collector device may provide, to a network device, a subscribe request that includes a request for sensor data based on an event. The collector device may receive, based on the subscribe request, sensor data packets from the network device. Each of the sensor data packets may include the sensor data for one of a plurality of elements of the network device and a header extension identifying a respective group identifier for a respective group of sensor data and final packet information indicating whether the sensor data packet is a final one for the respective group. The collector device may store the sensor data packets until the final packet information of one of the sensor data packets indicates that the one of the sensor data packets is a final sensor data packet for the respective group of sensor data. The collector device may identify a complete set of the sensor data packets when the final packet information of the one of the sensor data packets indicates that the one of the sensor data packets is the final sensor data packet for the respective group of sensor data. The collector device may perform one or more actions based on the complete set of the sensor data packets.

In this way, the collector device provides real-time detection of completion of collected sensor data of a network device. The collector device may provide, in headers of sensor data packets, an end of wrap identifier (e.g., final packet information) that identifies completion of a wrap. The collector device may store the sensor data and may determine that the sensor data is complete when the end of wrap identifier is received in one of the sensor data packets. Once the sensor data is determined to be complete, the collector device may perform actions based on the complete sensor data, such as addressing errors, generating alarms, performing traffic engineering, performing load balancing, and/or the like. This, in turn, conserves computing resources, networking resources, and/or the like that would otherwise have been wasted in storing sensor data, comparing the sensor data to determine completion of a wrap, delayed detection of completion of a wrap, delayed performance of actions in response to analysis of a wrap, and/or the like.

<FIG> are diagrams of an example <NUM> associated with providing real-time detection of completion of collected sensor data of a network device. As shown in <FIG>, example <NUM> includes a collector device associated with a network that includes multiple network devices. The collector device may include a server device, a cloud-based device, and/or the like that receives information from the network devices, as described herein. Each of the network devices may include a router, a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, and/or the like. Although <FIG> describe the collector device interacting with a single network device, in some implementations, the collector device may interact with the other network devices in a similar manner.

As shown in <FIG>, and by reference number <NUM>, the collector device provides, to a network device, a subscribe request that includes a request for sensor data over a time period. In some implementations, the collector device provides the subscribe request to the network device via an RPC network management interface protocol. The collector device may provide the subscribe request to the network device to cause the network device to generate and/or install software-defined sensors that collect sensor data associated with one or more of a plurality of elements (e.g., one or more interfaces, one or more resources, one or more hardware components, and/or the like) of the network device.

In some implementations, the subscribe request may include information identifying a mode associated with the software-defined sensors. The mode may indicate an interval at which the software-defined sensors collect the sensor data. For example, the mode may be a periodic mode (e.g., the software-defined sensors collect the sensor data periodically), an on-change mode (e.g., the software-defined sensors collect the sensor data based on a change in the sensor data), a target-defined mode (e.g., the network device determines a frequency at which the software-defined sensors collect the sensor data), and/or the like.

As shown in <FIG>, the collector device receives the subscribe request and generates and/or installs the software-defined sensors to collect the sensor data based on receiving the subscribe request. In some implementations, the software-defined sensors may be configured to collect the sensor data based on the mode indicated in the subscribe request. For example, the software-defined sensors may be configured to collect the sensor data periodically (e.g., based on an expiration of a time period), based on a satisfaction of a threshold by the sensor data, based on an occurrence of a change in the sensor data, based on a frequency determined by the network device, and/or the like.

For each wrap, the network device may generate a plurality of sensor data packets. A sensor data packet, of the plurality of sensor data packets, may include sensor data and a header extension. The sensor data may include data associated with an element of the network device, data obtained by a software-defined sensor, and/or the like. For example, the sensor data may include data identifying a route associated with the network device, a temperature of the network device, a throughput of a port of the network device, an input byte of the network device, an output byte of the network device, a neighbor route associated with the network device, a processor utilization by the network device, data associated with unicast packets generated by the network device, and/or the like.

The header extension may include information identifying a group identifier identifying a wrap associated with the sensor data and final packet information associated with the sensor packet. In some implementations, the header extension is included in a GNMI extension and/or the group identifier includes a wrap number. For example, as shown in <FIG>, the header extension includes information indicating that the group identifier for sensor data <NUM> is <NUM> (e.g., groupID=<NUM>, as shown in <FIG>).

The final packet information may include information indicating whether a sensor data packet is a final (e.g., last) sensor data packet for the wrap identified by the group identifier. For example, the final packet information may include a variable that is set to a first value (e.g., <NUM>, true, and/or the like) when the sensor data packet is the final sensor data packet for the wrap identified by the group identifier. The variable may be set to a second value (e.g., <NUM>, false, and/or the like) when the sensor data packet is not the final sensor data packet for the wrap identified by the group identifier.

As shown in <FIG>, the network device provides the plurality of sensor data packets to the collector device. The network device may provide the plurality of sensor data packets to the collector device based on a reporting frequency determined based on the mode associated with the software-defined sensors. For example, the collector device may periodically provide the plurality of sensor data packets to the collector device based on the software-defined sensors being configured to periodically collect the sensor data.

As shown by reference number <NUM>, the collector device receives, based on the subscribe request, the plurality of sensor data packets from the network device. In some implementations, the collector device receives the plurality of sensor data packets via a RPC network management interface protocol.

As shown in <FIG>, and by reference number <NUM>, the collector device stores the sensor data packets until the final packet information of one of the sensor data packets indicates that the sensor data packet is a final sensor data packet for the group identifier. For example, the collector device may analyze the final packet information of a sensor data packet and may determine whether the variable included in the final packet information is set to the first value or the second value. The collector device may store the sensor data packet in a memory (e.g., a cache) associated with the collector device. The collector device may determine that the sensor data packet is a final sensor data packet for the group identified by the group identifier when the variable is set to the second value.

As shown in <FIG>, and by reference number <NUM>, the collector device identifies a complete set of the sensor data packets when the final packet information of one of the sensor data packets indicates that the sensor data packet is a final sensor data packet for the group identifier. The collector device may analyze the stored sensor data associated with the wrap identified by the group identifier based on determining that the final packet information indicates that the sensor data packet is the final sensor data packet for the group. The collector device may determine one or more actions to be performed by the collector device and/or another device (e.g., the network device) based on analyzing the stored sensor data.

As shown in <FIG>, and by reference number <NUM>, the collector device performs the one or more actions based on the complete set of sensor data packets. In some implementations, the one or more actions include the collector device identifying an error in the network device based on the complete set of sensor data packets and automatically correcting the error and/or generating an alarm. For example, the collector device may identify a software issue and/or a hardware issue associated with the network device based on analyzing the stored sensor data. The collector device may automatically perform one or more actions to correct the software issue and/or the hardware issue and/or may generate an alarm to notify a user (e.g., a technician) of the software issue and/or the hardware issue. Alternatively, and/or additionally, the one or more actions include the collector device causing an autonomous vehicle and/or a technician to be dispatched to service the network device. For example, the collector device may generate the alarm and/or provide a notification to an autonomous vehicle and/or a user device associated with a technician to cause the autonomous vehicle and/or the technician to be dispatched to a location of the network device to address the software issue and/or the hardware issue.

In some implementations, the one or more actions include the collector device performing traffic engineering on the network device based on the complete set of sensor data packets. For example, the collector device may determine one or more performance characteristics associated with a network path based on analyzing the stored sensor data. The collector device may determine a link weight associated with the network path based on the one or more performance characteristics. The collector device may provide information identifying the link weight to the network device. The network device may utilize the link weight for determining routing information for routing data packets through a network. In this way, the collector device may automatically determine optimized link weights for the network device.

In some implementations, the one or more actions include the collector device performing load balancing on the network device based on the complete set of sensor data packets. The collector device may determine respective loads associated with one or more ports, one or more interfaces, and/or the like of the network device based on analyzing the stored sensor data. The collector device may perform load balancing on the network device based on the respective loads.

In some implementations, the one or more actions include the collector device identifying a network attack on the network device based on the complete set of sensor data packets and mitigating the network attack. The collector device may determine an occurrence of a particular type of network attack (e.g., a denial of service attack) on the network device based on analyzing the stored sensor data. The collector device may provide information associated with the particular type of network attack to the network device and/or to a security device (e.g., a firewall) associated with the network device and/or cause the network device and/or the security device to perform one or more security actions to mitigate the particular type of network attack.

In this way, the collector device provides real-time detection of completion of collected sensor data of a network device. The collector device may provide, in headers of sensor data packets, an end of wrap identifier that identifies completion of a wrap. The collector device may store the sensor data and may determine that the sensor data is complete when the end of wrap identifier is received in one of the sensor data packets. Once the sensor data is determined to be complete, the collector device may perform actions based on the complete sensor data, such as addressing errors, generating alarms, performing traffic engineering, performing load balancing, and/or the like. This, in turn, conserves computing resources, networking resources, and/or the like that would otherwise have been wasted in storing sensor data, comparing the sensor data to determine completion of a wrap, delayed detection of completion of a wrap, delayed performance of actions in response to analysis of a wrap, and/or the like.

<FIG> is a diagram of an example environment <NUM> in which systems and/or methods described herein may be implemented. As shown in <FIG>, environment <NUM> may include a collector device <NUM>, a group of network devices <NUM> (shown as network device <NUM>-<NUM> through network device <NUM>-N), and a network <NUM>. Devices of environment <NUM> may interconnect via wired connections, wireless connections, or a combination of wired and wireless connections.

Collector device <NUM> includes one or more devices capable of receiving, generating, storing, processing, providing, and/or routing information, as described elsewhere herein. Collector device <NUM> may include a communication device and/or a computing device. For example, collector device <NUM> may include a server, such as an application server, a client server, a web server, a database server, a host server, a proxy server, a virtual server (e.g., executing on computing hardware), a data center server, or a server in a cloud computing system. In some implementations, collector device <NUM> includes computing hardware used in a cloud computing environment.

Network device <NUM> includes one or more devices capable of receiving, processing, storing, routing, and/or providing traffic (e.g., a payload packet, an application, etc.) in a manner described herein. For example, network device <NUM> may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router, a provider core router, etc., a virtual router, and/or the like). Additionally, or alternatively, network device <NUM> may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, a data center server, etc.), a load balancer, and/or a similar device.

In some implementations, network device <NUM> may be a physical device implemented within a housing, such as a chassis. In some implementations, network device <NUM> may be a virtual device implemented by one or more computer devices of a cloud computing environment or a data center. In some implementations, network device <NUM> may be an edge network device in network <NUM>. In some implementations, network device <NUM> may be an intermediary network device in network <NUM> (i.e., a network device between two or more edge network devices).

Network <NUM> includes one or more wired and/or wireless networks. For example, network <NUM> may include a cellular network (e.g., a fifth generation (<NUM>) network, a fourth generation (<NUM>) network, such as a long-term evolution (LTE) network, a third generation (<NUM>) network, a code division multiple access (CDMA) network, a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, a cloud computing network, or the like, and/or a combination of these or other types of networks.

The number and arrangement of devices and networks shown in <FIG> are provided as one or more examples.

<FIG> is a diagram of example components of a device <NUM>, which may correspond to collector device <NUM> and/or network device <NUM>. In some implementations, collector device <NUM> and/or network device <NUM> may include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include a bus <NUM>, a processor <NUM>, a memory <NUM>, a storage component <NUM>, an input component <NUM>, an output component <NUM>, and a communication component <NUM>.

Bus <NUM> includes a component that enables wired and/or wireless communication among the components of device <NUM>. Processor <NUM> includes a central processing unit, a graphics processing unit, a microprocessor, a controller, a microcontroller, a digital signal processor, a field-programmable gate array, an application-specific integrated circuit, and/or another type of processing component. Processor <NUM> is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor <NUM> includes one or more processors capable of being programmed to perform a function. Memory <NUM> includes a random-access memory, a read only memory, and/or another type of memory (e.g., a flash memory, a magnetic memory, and/or an optical memory).

Storage component <NUM> stores information and/or software related to the operation of device <NUM>. For example, storage component <NUM> may include a hard disk drive, a magnetic disk drive, an optical disk drive, a solid-state disk drive, a compact disc, a digital versatile disc, and/or another type of non-transitory computer-readable medium. Input component <NUM> enables device <NUM> to receive input, such as user input and/or sensed inputs. For example, input component <NUM> may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system component, an accelerometer, a gyroscope, and/or an actuator. Output component <NUM> enables device <NUM> to provide output, such as via a display, a speaker, and/or one or more light-emitting diodes. Communication component <NUM> enables device <NUM> to communicate with other devices, such as via a wired connection and/or a wireless connection. For example, communication component <NUM> may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and/or an antenna.

Device <NUM> may perform one or more processes described herein. For example, a non-transitory computer-readable medium (e.g., memory <NUM> and/or storage component <NUM>) may store a set of instructions (e.g., one or more instructions, code, software code, and/or program code) for execution by processor <NUM>. Processor <NUM> may execute the set of instructions to perform one or more processes described herein. In some implementations, execution of the set of instructions, by one or more processors <NUM>, causes the one or more processors <NUM> and/or the device <NUM> to perform one or more processes described herein. In some implementations, hardwired circuitry may be used instead of or in combination with the instructions to perform one or more processes described herein.

<FIG> is a diagram of example components of a device <NUM>. Device <NUM> may correspond to network device <NUM>. In some implementations, network device <NUM> may include one or more devices <NUM> and/or one or more components of device <NUM>. As shown in <FIG>, device <NUM> may include one or more input components <NUM>-<NUM> through <NUM>-B (B ≥ <NUM>) (hereinafter referred to collectively as input components <NUM>, and individually as input component <NUM>), a switching component <NUM>, one or more output components <NUM>-<NUM> through <NUM>-C (C ≥ <NUM>) (hereinafter referred to collectively as output components <NUM>, and individually as output component <NUM>), and a controller <NUM>.

Controller <NUM> may perform one or more processes described herein. Controller <NUM> may perform these processes in response to executing software instructions stored by a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

<FIG> is a flowchart of an example process <NUM> for providing real-time detection of completion of collected sensor data of a network device. In some implementations, one or more process blocks of <FIG> may be performed by a device (e.g., collector device <NUM>). In some implementations, one or more process blocks of <FIG> may be performed by another device or a group of devices separate from or including the device, such as a network device (e.g., network device <NUM>). Additionally, or alternatively, one or more process blocks of <FIG> may be performed by one or more components of device <NUM>, such as processor <NUM>, memory <NUM>, storage component <NUM>, input component <NUM>, output component <NUM>, and/or communication component <NUM>. Additionally, or alternatively, one or more process blocks of <FIG> may be performed by one or more components of device <NUM>, such as input component <NUM>, switching component <NUM>, output component <NUM>, and/or controller <NUM>.

As shown in <FIG>, process <NUM> may include providing, to a network device, a subscribe request that includes a request for sensor data based on an event (block <NUM>). For example, the device may provide, to a network device, a subscribe request that includes a request for sensor data based on an event, as described above. In some implementations, the device may provide the subscribe request to the network device via a remote procedure call network management interface protocol.

The subscribe request may cause the network device to install software-defined sensors that collect sensor data associated with one or more of the plurality of interfaces of the network device. The event may include an expiration of a time period (e.g., periodically), a satisfaction of a threshold by the sensor data, and/or an occurrence of a change in the sensor data.

As further shown in <FIG>, process <NUM> may include receiving, based on the subscribe request, sensor data packets, wherein each of the sensor data packets includes the sensor data for one of a plurality of interfaces of the network device and a header extension identifying a respective group identifier for a respective group of sensor data and a final packet information indicating whether the sensor data packet is a final one for the respective group (block <NUM>). For example, the device may receive, based on the subscribe request, sensor data packets, as described above. In some implementations, each of the sensor data packets includes the sensor data for one of a plurality of interfaces of the network device and a header extension identifying a respective group identifier for a respective group of sensor data and final packet information indicating whether the sensor data packet is a final one for the respective group.

In some implementations, the device receives the sensor data packets via a remote procedure call network management interface protocol. In some implementations, a respective group of sensor data is received from all of a plurality of interfaces of the network device. The sensor data may include data identifying a route associated with the network device, a temperature of the network device, a throughput of a port of the network device, an input byte of the network device, an output byte of the network device, a neighbor route associated with the network device, a processor utilization by the network device, and/or a unicast packet generated by the network device.

As further shown in <FIG>, process <NUM> may include storing the sensor data packets until the final packet information of one of the sensor data packets indicates that the one of the sensor data packets is a final sensor data packet for the respective group of sensor data (block <NUM>). For example, the device may store the sensor data packets until the final packet information of one of the sensor data packets indicates that the one of the sensor data packets is a final sensor data packet for the respective group of sensor data, as described above.

As further shown in <FIG>, process <NUM> may include identifying a complete set of the sensor data packets when the final packet information of the one of the sensor data packets indicates that the one of the sensor data packets is the final sensor data packet for the respective group of sensor data (block <NUM>). For example, the device may identify a complete set of the sensor data packets when the final packet information of the one of the sensor data packets indicates that the one of the sensor data packets is the final sensor data packet for the respective group of sensor data, as described above.

As further shown in <FIG>, process <NUM> may include performing one or more actions based on the complete set of the sensor data packets (block <NUM>). For example, the device may perform one or more actions based on the complete set of the sensor data packets, as described above. In some implementations, the device may perform the one or more actions in near real-time relative to identifying the complete set of the sensor data packets. In some implementations, the one or more actions include analyzing the complete set of the sensor data packets to generate at least one result and performing the one or more actions based on the at least one result.

In some implementations, the one or more actions include causing an autonomous vehicle to be dispatched to service the network device, causing a technician to be dispatched to service the network device, performing traffic engineering on the network device based on the at least one result, and/or performing load balancing on the network device based on the at least one result. In some implementations, the one or more actions include identifying an error associated with the network device based on the at least one result and automatically causing the error to be corrected and/or generating an alarm based on the error. Alternatively, and/or additionally, the one or more actions may include identifying a network attach on the network device based on the at least one result and performing an action to mitigate the network attack.

Modifications may be made in light of the above disclosure or may be acquired from practice of the implementations.

Although particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of various implementations.

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items, and may be used interchangeably with "one or more. " Further, as used herein, the article "the" is intended to include one or more items referenced in connection with the article "the" and may be used interchangeably with "the one or more. " Furthermore, as used herein, the term "set" is intended to include one or more items (e.g., related items, unrelated items, a combination of related and unrelated items, and/or the like), and may be used interchangeably with "one or more. " Where only one item is intended, the phrase "only one" or similar language is used. Also, as used herein, the terms "has," "have," "having," or the like are intended to be open-ended terms. Further, the phrase "based on" is intended to mean "based, at least in part, on" unless explicitly stated otherwise. Also, as used herein, the term "or" is intended to be inclusive when used in a series and may be used interchangeably with "and/or," unless explicitly stated otherwise (e.g., if used in combination with "either" or "only one of").

Claim 1:
A method, comprising:
sending, by a device (<NUM>), a request to subscribe to receive one or more packets associated with one or more sensors;
receiving, by the device and based on sending the request, the one or more packets associated with the one or more sensors,
wherein a packet of the one or more packets includes an extension, associated with the packet, comprising a group identifier associated with a sensor, of the one or more sensors, and information indicating whether the packet is a final packet related to a group identified by the group identifier;
identifying, by the device, a set of the one or more packets when a particular extension of a particular packet of the one or more packets indicates that the particular packet is a final packet related to a particular group associated with the one or more sensors; and
performing, by the device and based on the set of the one or more packets, one or more actions.