H04L61/50

Automatically obtaining sensor data for machine update

A system may comprise: a reader device comprising: one or more memories; and one or more processors communicatively coupled to the one or more memories. The one or more processors may be configured to: obtain, using a wireless local area network communication, sensor data from a plurality of sensor devices associated with a machine; identify, from the sensor data, information identifying a sensor device of the plurality of sensor devices; generate sensor device information that associates the information identifying the sensor device with information identifying a component of the machine; and transmit the sensor device information to cause the machine to be updated using the sensor device information.

GENERATION OF A UNIQUE DEVICE IDENTIFIER FOR A CLIENT DEVICE IN A WIRELESS NETWORK
20220368670 · 2022-11-17 ·

To improve the network experience in a network, a unique device identifier (UDID) can be generated by a UDID generation module of a client device. The UDID generation module utilizes one or more device parameters as well as a service set identifier (SSID) as input(s) to the UDID generation module. The UDID can be reported to an access point device of the network so that the access point device can track, monitor, control, etc. the client device within the network, for example, when media access control randomization (rMAC) is utilized by the network to protect the privacy of the client device or a user of the client device. The same UDID is generated each time the client device joins the network so that the client device need not store the UDID.

GENERATION OF A UNIQUE DEVICE IDENTIFIER FOR A CLIENT DEVICE IN A WIRELESS NETWORK
20220368670 · 2022-11-17 ·

To improve the network experience in a network, a unique device identifier (UDID) can be generated by a UDID generation module of a client device. The UDID generation module utilizes one or more device parameters as well as a service set identifier (SSID) as input(s) to the UDID generation module. The UDID can be reported to an access point device of the network so that the access point device can track, monitor, control, etc. the client device within the network, for example, when media access control randomization (rMAC) is utilized by the network to protect the privacy of the client device or a user of the client device. The same UDID is generated each time the client device joins the network so that the client device need not store the UDID.

Common connection tracker across multiple logical switches

Some embodiments of the invention provide novel methods for providing a stateful service at a network edge device (e.g., an NSX edge) that has a plurality of north-facing interfaces (e.g., interfaces to an external network) and a plurality of corresponding south-facing interfaces (e.g., interfaces to a logical network). In some embodiments, each interface associated with a different bridge calls a service engine based on identifiers included in data messages received at the interface. Each data message flow is associated with a particular identifier that is associated with a particular service engine instance that provides the stateful service. In some embodiments, the interface that receives a data message identifies a service engine to provide the stateful service and provides the data message to the identified service engine. After processing the data message, the service engine provides the data message to the egress interface associated with the ingress interface.

Common connection tracker across multiple logical switches

Some embodiments of the invention provide novel methods for providing a stateful service at a network edge device (e.g., an NSX edge) that has a plurality of north-facing interfaces (e.g., interfaces to an external network) and a plurality of corresponding south-facing interfaces (e.g., interfaces to a logical network). In some embodiments, each interface associated with a different bridge calls a service engine based on identifiers included in data messages received at the interface. Each data message flow is associated with a particular identifier that is associated with a particular service engine instance that provides the stateful service. In some embodiments, the interface that receives a data message identifies a service engine to provide the stateful service and provides the data message to the identified service engine. After processing the data message, the service engine provides the data message to the egress interface associated with the ingress interface.

COMMUNICATION METHOD AND APPARATUS
20230051069 · 2023-02-16 · ·

A communication method and an apparatus are provided herein. The method includes: sending, by a mobility management entity (MME), a track area update (TAU) accept message to a user equipment (UE), the TAU accept message comprising an identifier constructed from at least a resource pool identifier (pool-ID) that identifies a resource pool in a public land mobile network (PLMN), a mobility management entity identifier (MME-ID) that uniquely identifies the MME within the resource pool, and a UE temporary identifier that uniquely identifies the UE within the MME; and receiving, by the MME, a TAU complete message from the UE.

COMMUNICATION METHOD AND APPARATUS
20230051069 · 2023-02-16 · ·

A communication method and an apparatus are provided herein. The method includes: sending, by a mobility management entity (MME), a track area update (TAU) accept message to a user equipment (UE), the TAU accept message comprising an identifier constructed from at least a resource pool identifier (pool-ID) that identifies a resource pool in a public land mobile network (PLMN), a mobility management entity identifier (MME-ID) that uniquely identifies the MME within the resource pool, and a UE temporary identifier that uniquely identifies the UE within the MME; and receiving, by the MME, a TAU complete message from the UE.

FACILITATING OVER-THE-AIR ADDRESS ROTATION

A wireless client device communicates, to an access point over a secure channel, a mapping of a dynamic device address to a stable device address. By communicating the mapping, the access point is able to determine that packets received from two different device addresses originate from a common device. The access point is then able to maintain an association between the originating device and other network resources assigned or allocated to the originating device, such as IP addresses or infrastructure station address, which is used to identify the originating device to other devices outside the network in some embodiments.

Association handling method and device

An association handling method and device are provided. The method includes: determining one or more TNL addresses of a CU; and establishing multiple TNL associations between a DU and the CU according to the one or more TNL addresses.

Association handling method and device

An association handling method and device are provided. The method includes: determining one or more TNL addresses of a CU; and establishing multiple TNL associations between a DU and the CU according to the one or more TNL addresses.