Abstract: Device information may be obtained using LoRaWAN communications. A device information request may be generated and transmitted by a user device and include request parameters such as a device type for which information is desired, a type of information requested, a geographic range for the request, and the like and/or combinations thereof. Device information requests may also be propagated or repeated by intermediary devices to achieve the desired request range. Accordingly, a recipient device of the original request may propagate or repeat, using LoRaWAN, a request signal if it determines that the request range has not been met. If the request range has been met, the recipient device might not repeat the request.

Abstract: Device information may be obtained using LoRaWAN communications. A device information request may be generated and transmitted by a user device and include request parameters such as a device type for which information is desired, a type of information requested, a geographic range for the request, and the like and/or combinations thereof. Device information requests may also be propagated or repeated by intermediary devices to achieve the desired request range. Accordingly, a recipient device of the original request may propagate or repeat, using LoRaWAN, a request signal if it determines that the request range has not been met. If the request range has been met, the recipient device might not repeat the request.

Abstract: A network device may establish, via a routing protocol daemon (RPD) of the network device, border gateway protocol (BGP) sockets with peer network devices and may establish a socket between the RPD and a periodic packet management daemon (PPMD) of the network device. The network device may provide file descriptors of the BGP sockets from the RPD to the PPMD, via the socket, and may provide, from the RPD and via the BGP sockets, non-keep alive protocol data units (PDUs) to the peer network devices. The network device may provide, from the PPMD and via the BGP sockets, keep alive PDUs to the peer network devices.

Abstract: Transactions may be performed using a mobile device such as a user-wearable device using LoRaWAN protocol to minimize power consumption while maximizing communication range. Transaction information may be stored in the user-wearable device and transmitted to a transaction processing device using LoRaWAN communications. Transaction information may include user-specific information, payment information, merchant information, product information, user preference information and the like. In some instances, the only communication interface (or wireless communication interface) provided in the mobile device is a LoRaWAN communication interface.

Abstract: Methods and systems are provided for validating and registering an IHS (Information Handling System) and components of the IHS for technical support. Upon delivery and initialization of an IHS, an inventory certificate that was uploaded to the IHS during factory provisioning of the IHS is retrieved. The inventory certificate includes an inventory that identifies factory-installed hardware components in the IHS. The inventory also specifies whether a registration requirement has been specified for the IHS, such as to initiate technical support. While still operating a pre-boot validation process, an inventory is collected of the detected hardware components of the IHS. Based on the inventory certificate, the validation process confirms whether a detected hardware component is a factory-installed hardware component and determines whether registration is required. If required, registration of the IHS is initiated by the validation process and initialization of the IHS continues.

Abstract: Transactions between entities may be validated using LoRaWAN communications to more quickly process those transactions. In the example of check depositing, a first entity associated with a check payee may transmit a check clearance request to a second entity associated with a check payor using LoRaWAN communications. The LoRaWAN signaling and communications may be performed between devices within LoRaWAN range. For example, a check depositing device may receive a check deposit where the payor is associated with a different financial institution or entity. Accordingly, the check depositing device may communicate with another device associated with the payor institution or entity using LoRaWAN signals to confirm check clearance.

Abstract: A network device may execute a master application shared with another network device via a session, and may receive, by a backup application replication kernel, a replicated data object. The backup application replication kernel may provide the replicated data object to a backup application, and may calculate a time delta between when the replicated data object is received and when the replicated data object is consumed by the backup application. The backup application replication kernel may determine whether the time delta exceeds a first threshold or a second threshold, and may generate a session flag based on the time delta exceeding the first threshold or the second threshold. The backup application replication kernel may provide the session flag to a master application replication kernel and to the backup application, and the master application replication kernel may provide details of the session to the master application and the backup application.

Abstract: The disclosure describes techniques that enable detection of memory leaks of software executing on devices within a computer network. An example network device includes memory and processing circuitry. The processing circuitry monitors a usage of the memory by a software component operating within the network device. The processing circuitry periodically determines a memory growth pattern score for the software component based on the usage of the memory. The processing circuitry also predicts whether the user-level process is experiencing a memory leak based on the memory growth pattern score. The processing circuitry applies confirmation criteria to current memory usage of the software component to confirm that the software component is experiencing the memory leak. When the software component is experiencing the memory leak, the processing circuitry generates an alert.

Abstract: A computerized method is provided for digitally signing a digital document related to a transaction request from a customer. The method includes receiving, by a computing device, data related to the transaction request from the customer via a web-based interface. Receipt of the transaction data initiates a request session. The method also includes recording during the request session a voice signature sample from the customer via the web-based user interface and verifying the customer for the transaction request by comparing the voice signature sample with a stored voice print of the customer. Further, a consolidated record for the transaction request is generated that includes the transaction data and the transaction result. The digital document is populated with the transaction data if the customer is verified, where the digital document is treated as being digitally signed by the customer.

Abstract: A wireless access point comprises a memory; and one or more processors operably coupled to the memory configured to: receive a first packet for an application; configure an initial packet flow for the application including a first forwarding action to send traffic for the application via a tunnel path; learn the application of the first packet; generate, based on a policy of the application, an entry in an application server address cache specifying an address of the application server and a second forwarding action to send traffic for the application via a local breakout path; receive a second packet for the application; and configure, in response to determining that a destination address of the second packet matches the entry in the application server address cache, a subsequent packet flow for the application including the second forwarding action to send traffic for the application via the local breakout path.

Abstract: Transactions between entities may be validated using LoRaWAN communications to more quickly process those transactions. In the example of check depositing, a first entity associated with a check payee may transmit a check clearance request to a second entity associated with a check payor using LoRaWAN communications. The LoRaWAN signaling and communications may be performed between devices within LoRaWAN range. For example, a check depositing device may receive a check deposit where the payor is associated with a different financial institution or entity. Accordingly, the check depositing device may communicate with another device associated with the payor institution or entity using LoRaWAN signals to confirm check clearance.

Abstract: Communication, authentication, and/or validation may be required in various types of device interactions. For example, for some types of device functions, user or device authentication may be required to confirm that the function can and should be performed. Authentication information may be communicated and authentication and/or validation may be performed using LoRaWAN signaling. LoRaWAN signaling provides low power and long-range communication capabilities to efficiently and effectively perform authentication processes. In some arrangements, LoRaWAN signals may be generated by both a first device (e.g., a user device) and a second device (e.g., a function-performing device) and subsequently compared to determine whether they correspond. This correspondence may provide the requisite authentication or validation of the first device and/or an associated user.

Abstract: Device information may be obtained using LoRaWAN communications. A device information request may be generated and transmitted by a user device and include request parameters such as a device type for which information is desired, a type of information requested, a geographic range for the request, and the like and/or combinations thereof. Device information requests may also be propagated or repeated by intermediary devices to achieve the desired request range. Accordingly, a recipient device of the original request may propagate or repeat, using LoRaWAN, a request signal if it determines that the request range has not been met. If the request range has been met, the recipient device might not repeat the request.

Abstract: Transactions may be performed using a mobile device such as a user-wearable device using LoRaWAN protocol to minimize power consumption while maximizing communication range. Transaction information may be stored in the user-wearable device and transmitted to a transaction processing device using LoRaWAN communications. Transaction information may include user-specific information, payment information, merchant information, product information, user preference information and the like. In some instances, the only communication interface (or wireless communication interface) provided in the mobile device is a LoRaWAN communication interface.

Abstract: A network device may monitor a TCP session with another network device, and may identify ingress and/or egress packets, a TCP header, and a socket of the TCP session. The network device may inspect the ingress and/or egress packets, the TCP header, and the socket to identify a zero window advertisement, details of a last quantity of packets sent or received, synchronize, finish, or reset packets sent or received, negotiated TCP options, or buffer space utilization, and may temporarily record identified data based on the inspection. The network device may detect a TCP session flap when a finish packet or a reset packet is identified and recorded, and may store, in a dead TCP session list, the identified data based on the TCP session flap being detected.

Abstract: A network device may execute a master application communicating with another network device via a session, and may receive, by a backup application replication layer, a replicated data object. The backup application replication layer may provide the replicated data object to a backup application, and may calculate a time delta between when the replicated data object is received and when the replicated data object arrives at the backup application. The backup application replication layer may determine whether the time delta exceeds a first threshold or a second threshold, and may generate a session flag based on the time delta exceeding the first threshold or the second threshold. The backup application replication layer may provide the session flag to a master application replication layer and to the backup application, and the master application replication layer may provide details of the session to the master application and the backup application.

Abstract: A confinement ring for use in a plasma processing chamber includes an upper horizontal section, a vertical section, and a lower horizontal section. The upper horizontal section extends between an upper inner radius and an outer radius of the confinement ring, The lower horizontal section extends between an lower inner radius and the outer radius of the confinement ring, and includes an extension section that extends to the lower inner radius. A top surface of the lower horizontal section provides for an angle down toward the lower inner radius. The vertical section is disposed between the outer radius and an inside radius of the confinement ring. The vertical section connects the upper horizontal section to the lower horizontal section of the confinement ring.

Abstract: A network device may execute a master application communicating with another network device via a session, and may receive, by a backup application replication layer, a replicated data object. The backup application replication layer may provide the replicated data object to a backup application, and may calculate a time delta between when the replicated data object is received and when the replicated data object arrives at the backup application. The backup application replication layer may determine whether the time delta exceeds a first threshold or a second threshold, and may generate a session flag based on the time delta exceeding the first threshold or the second threshold. The backup application replication layer may provide the session flag to a master application replication layer and to the backup application, and the master application replication layer may provide details of the session to the master application and the backup application.

Abstract: A computerized method is provided for responding to a request by a customer to enroll into a digital service. The method includes generating a personalized media clip for presentation to the enrolling customer, which comprises (i) using an artificial intelligence (AI) model to determine a plurality of relevant media objects based on data related to the request and customer data and (ii) forming a randomized composite of the plurality of relevant media objects. The method also includes providing the personalized media clip along with an instruction to the customer to record an audio description of the media clip. The method further includes generating a confidence score that measures a degree of accuracy of the audio description by the customer in relation to the personalized media clip, where enrollment of the customer into the digital service is based on at least the confidence score.

Abstract: A computing device component monitoring system includes at least one certificate generation system, and a computing device that includes a first component and that is coupled to the at least one certificate generation system via a network. The computing device receives a first component verification certificate from the at least one certificate generation system that identifies a first component lifetime after which the first component in the computing device should be replaced, and stores the first component verification certificate in a database that is accessible to the computing device. The computing device determines that the first component lifetime has been exceeded, and identifies a first component alert policy in response. The computing device generates a first component alert based on the first component alert policy.