Zhong Chen, 371619 Avenue V, Brooklyn, NY 11229

2019002, Jan 24, 2019

Jul 24, 2017

15/657716

- Arlington MA, US
Zhong Chen - Acton MA, US
Matthew J. Threefoot - Columbia MD, US

H04L 12/24
H04L 29/12

A network device stores capability designations associated with Internet-of-Things (IoT) devices and receives, from a customer device, one or more of the capability designations associated with a first type of IoT device. The network device receives event data generated by the first type of IoT device and maps the event data to the one or more of the capability designations. The mapping produces normalized IoT data for the first type of IoT device. The network device generates semantic information for the normalized IoT data and assembles a device model for the first type of IoT device. The device model includes the one or more of the capability designations and the semantic information.

2018021, Jul 26, 2018

Jan 20, 2017

15/410863

- Arlington VA, US
Zhong Chen - Acton MA, US
Lin Zhu - Lexington MA, US
Jianxiu Hao - Acton MA, US

H04L 29/06
H04L 9/08

A network device receives, from a node in an Internet-of-Things (IoT) network, an access request for a user authenticated via the node and identifies the access request as from either of a trusted node or an untrusted node in the IoT network. When the access request is from an untrusted node, the network device identifies a hash key for the access request, wherein the hash key is derived from an access list for the IoT network; broadcasts the hash key to other trusted nodes in the IoT network; and validates the access request based on a solution consensus from the other trusted nodes. When the access request is from a trusted node, the network device confirms mutual trust with the trusted node via an encrypted key exchange, and validates the access request based on the mutual trust with the trusted node.

2018010, Apr 12, 2018

Oct 7, 2016

15/288335

- Arlington VA, US
Jianxiu Hao - Acton MA, US
Zhong Chen - Acton MA, US
Dahai Ren - Lincoln MA, US

H04L 12/46
H04L 29/08
G06F 17/30

A network device receives a plurality of framework definitions corresponding to a respective plurality of device platforms, wherein each of the device platforms comprises at least one device. The network device generates a plurality of generalized framework definitions for each of the plurality of device platforms, wherein the plurality of generalized framework definitions comprise basic linguistic components corresponding to elements in the respective plurality of framework definitions. The network device receives data from the at least one device for each of the device platforms. The network device extracts data from the received data based on the plurality of generalized framework definitions. The network device automatically identifies contexts that include at least one device for each of the at least two device platforms based on the extracted data. The network device transmits instructions to the at least one device for each of the at least two device platforms based on one of a rule or a request associated with the identified one or more contexts.

2017035, Dec 14, 2017

Jun 13, 2016

15/180361

- Arlington VA, US
Zhong Chen - Acton MA, US
Lin Zhu - Lexington MA, US
Ming Chen - Bedford MA, US

H04L 12/26
H04L 29/08

A network device logs transmission control protocol (TCP) flow data for connections between registered devices that are registered for use of secure Internet of Things (IoT) application programming interfaces (APIs). The logging generates logged flow data. The network device receives, from a first registered device, a call validation request for an IoT API call directed to the first registered device from a second registered device. The call validation request includes packet information of the IoT API call. The network device compares the packet information with the logged TCP flow data. When the comparing indicates a match of the packet information and the logged TCP flow data, the network device sends a response to the first registered device to accept the IoT API call. Otherwise, the network device sends a response to the first registered device to reject the IoT API call.

2017035, Dec 14, 2017

Jun 13, 2016

15/180629

- Arlington VA, US
Jianxiu Hao - Acton MA, US
Zhong Chen - Acton MA, US
Matthew J. Threefoot - Columbia MD, US

H04L 29/08
H04W 60/04
H04W 4/00

A network device receives a definition for a data product of consumer Internet-of-Things (IoT) data and registers multiple machine-type communications (MTC)-devices for collection of consumer IoT data. The MTC devices provide the consumer IoT data with heterogeneous formats. The registering identifies a profile for each MTC device and particular data types authorized for collection. The network device receives consumer IoT data generated by the multiple MTC devices and extracts the particular data types from the IoT data. The network device normalizes the extracted data to include a uniform data format, and aggregates the normalized IOT data into clusters that exclude device identifiers. The network device constructs the clusters into a data portfolio that meets the definition for the data product.

2017017, Jun 15, 2017

Dec 15, 2015

14/969187

- Arlington VA, US
Jianxiu HAO - Acton MA, US
Zhong CHEN - Acton MA, US

H04L 29/06
H04L 9/32

A first device may receive a request from a second device. The request may include a device identifier associated with the second device. The request may be transmitted by the second device to obtain a signature, based on which to access a third device. The first device may determine that the device identifier is associated with a secure authentication service. The first device may generate a signature based on determining that the device identifier is associated with the secure authentication service. The first device may provide the signature to the third device. The signature may permit the third device to selectively permit or deny access by the second device based on a result of authenticating the signature. Access may be permitted when the third device successfully authenticates the signature, and access may be denied when the third device fails to authenticate the signature.

2017014, May 25, 2017

Nov 24, 2015

14/950800

- Arlington VA, US
Dongchen Wang - Concord MA, US
Ming Chen - Bedford MA, US
Zhong Chen - Acton MA, US

H04L 29/06

A method, a device, and a non-transitory storage medium provides to receive a packet from an Internet of Things (IoT) device, wherein the packet carries IoT data; determine a classification of the IoT device from which the first packet is received, in response to a receipt of the packet, wherein the classification indicates a type of IoT device; select standard data types assigned to the classification of the IoT device, in response to a determination of the classification of the IoT device; determine whether the IoT data includes all of the standard data types based on the standard data types selected; convert the IoT data into an IoT standard format in response to a determination that the IoT data includes all of the standard data types; generate another packet that includes the IoT data in the IoT standard format in response to a conversion of the IoT data; and transmit the other packet to a network device.

2017012, May 4, 2017

Oct 29, 2015

14/926234

- Arlington VA, US
Jianxiu Hao - Acton MA, US
Zhong Chen - Acton MA, US

H04L 29/06

Attributes of a session, between a source device and a verification device, for sending first verification data, such as a password and an account identifier, are determined. The verification device generates user device data based on an identifier, such as a mobile device number (MDN), for a user device associated with the account identifier. An identifier, such as an MDN, associated with the source device and an encryption key associated with the verification device are determined based on session attributes. Second verification data is generated based on the identifier associated with the source device. The second verification data is encrypted using the encryption key and forwarded to the verification device. The verification device decrypts the second verification data and compares the identifier for the user device to the identifier for the source device to determine whether the first verification data was sent from the user device.