Network System with a Plurality of Networked Devices with Various Connection Protocols

{
  "publication_number": "US2010299517A1",
  "country": "US",
  "kind": "A1",
  "title": "Network System with a Plurality of Networked Devices with Various Connection Protocols",
  "abstract": "Methods and devices for retrieving data from a variety of devices, such as biomedical devices, are disclosed. In an embodiment, a communications path is established between a device manager and a device configured to collect data from a patient. A device type associated with the device is detected. Based on the device type, connections settings required to exchange data between the device manager and the device are requested from a first server. A patient identifier is also obtained. The patient identifier is sent to a second server, which may be the same as the first server. Verification of the patient identifier is received at the device manager from the second server. Data is then received at the device manager from the device. Upon receipt, the data is either stored in a storage or the data is sent via an encrypted communication channel to a server for data format conversion.",
  "claims": [
    "1. A device manager, comprising: one or more processors; a communication interface coupled to the one or more processors; and a memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to: detect one or more devices connected to the communication interface; determine a device type associated with each of the one or more devices; receive data from the one or more devices; encrypt the data received from the one or more devices; and transmit the encrypted data to a network data storage device configured for accessibility by one or more remote terminals. 2. The device manager of claim 1, wherein the one or more processors include application programming interface (API) extensions. 3. The device manager of claim 2, wherein the API extensions include direct memory access extensions. 4. The device manager of claim 1, wherein the one or more processors are 8051 microcontrollers. 5. The device manager of claim 4, wherein the one or more processors include direct memory access extensions. 6. The device manager of claim 1, wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to detect one or more devices connected to the communication interface, wherein the one or more devices are legacy devices not initially configured for network communication. 7. The device manager of claim 6, wherein the data received from the one or more legacy devices is power consumption data. 8. The device manager of claim 7, wherein the memory for storing instructions which, when executed by the one or more processors, causes the one or more processors to convert the power consumption data into device function data. 9. The device manager of claim 8, wherein converting the power consumption data into device function data is achieved through the use an algorithm specific to the device type associated with the device. 10. The device manager of claim 1, wherein the device type is determined by receiving a transmission from the device and comparing characteristics of the transmission with known characteristics of a list of known devices. 11. The device manager of claim 10, wherein the list of known devices are categorized by characteristics and the characteristics of the transmission are compared to the categories before being compared to individual devices. 12. The device manager of claim 1, wherein the data encryption is achieved through a stream cipher encryption scheme, wherein the stream cipher encryption scheme is dependent upon the data to be encrypted. 13. The device manager of claim 1, wherein the one or more processors are virtual processors. 14. A method, comprising: detecting one or more devices connected to a communication interface; determining a device type associated with each of the one or more devices; receiving data from the one or more devices; encrypting the data received from the one or more devices; and transmitting the encrypted data to a network data storage device configured for accessibility by one or more remote terminals. 15. The method of claim 14, wherein detecting the one or more devices includes detecting one or more legacy devices not initially configured for network communication. 16. The method of claim 15, wherein receiving data from the one or more legacy devices includes receiving power consumption data. 17. The method of claim 16, further comprising converting the power consumption data into device function data. 18. The method of claim 17, wherein converting the power consumption data into device function data is achieved through the use an algorithm specific to the device type associated with the device. 19. The method of claim 14, wherein the device type is determined by receiving a transmission from the device and comparing characteristics of the transmission with known characteristics of a list of known devices. 20. The method of claim 19, wherein the list of known devices are categorized by characteristics and the characteristics of the transmission are compared to the categories before being compared to individual devices. 21. The method of claim 14, wherein encrypting the data comprises using a stream cipher encryption scheme, wherein the stream cipher encryption scheme is dependent upon the data to be encrypted. 22. A method of retrieving data from a variety of biomedical devices comprising: establishing a communications path between a device manager and a biomedical device configured to collect a data from a patient; detecting, using the device manager, a device type associated with the biomedical device; requesting from a first server, based on the device type, connection settings required to exchange data between the device manager and the biomedical device; obtaining, using the device manager, a patient identifier, the patient identifier corresponding to the patient; sending, using the device manager, the patient identifier to a second server; receiving, at the device manager, verification of the patient identifier from the second server; receiving, at the device manager, the data from the biomedical device; and either storing the data in a storage on the device manager or sending the data via an encrypted communication channel to a third server for data format conversion. 23. The method of claim 22 wherein the second server is the same as the first server."
  ],
  "description_excerpt": "In today's society, data networks are becoming more integral with everyday home, office, commercial, healthcare, and industrial life. The ability to monitor, control, and access a plurality of devices from a remote location allows for optimization of time and resources. Unfortunately, as the size, scope, and variety of devices and networks increases, the problem of compatibility and response time may become an issue in some networks and network implementations. Devices developed by various designers and manufacturers may use a variety of network and control protocols in both hardware and software, thus possibly creating issues with compatibility.\n\nThe present disclosure provides methods, devices, and systems for providing a flexible and secure data network.\n\nIn one embodiment, a method for networking devices is provided, that may comprise detecting a plurality of network devices, including a first network device and a second network device, connected to a network, determining a first communication protocol associated with the first network device based on a first network device profile, querying a database for a first configuration profile associated with the first network device profile, retrieving the first configuration profile, storing the first configuration profile, executing the stored first configuration profile for configuring a first terminal of a network communication interface for communication with the first network device using the first configuration profile ...",
  "cpc": [
    "H04L 63/0428",
    "G16H 40/67",
    "H04L 12/2809",
    "H04L 63/0823"
  ],
  "ipc": [
    "H04L 9/00"
  ],
  "assignees": [
    "Nuvon Inc"
  ],
  "inventors": [
    "Vedran JUKIC",
    "Vaghinag Hagop Zakian"
  ],
  "filing_date": "2010-03-01",
  "publication_date": "2010-11-25",
  "priority_date": "2009-05-22",
  "application_number": "US-71462110-A",
  "family_id": "43125346",
  "cited_by_count": 172,
  "citations": [
    "US6801878B1",
    "US6553336B1",
    "US6745301B2",
    "US20020184348A1",
    "US7373356B2",
    "US20050246453A1",
    "US7605695B2",
    "US8090877B2",
    "WO2010135189A2"
  ]
}