US20220006876A1 - Universal convertor, feeders and pushers for connectivity of industrial internet of things - Google Patents

Universal convertor, feeders and pushers for connectivity of industrial internet of things Download PDF

Info

Publication number
US20220006876A1
US20220006876A1 US17/478,553 US202117478553A US2022006876A1 US 20220006876 A1 US20220006876 A1 US 20220006876A1 US 202117478553 A US202117478553 A US 202117478553A US 2022006876 A1 US2022006876 A1 US 2022006876A1
Authority
US
United States
Prior art keywords
data
converter
dictionary
feeder
universal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US17/478,553
Other languages
English (en)
Inventor
Yussif ALSANAH
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Siraj Technologies Ltd
Original Assignee
Siraj Technologies Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Siraj Technologies Ltd filed Critical Siraj Technologies Ltd
Priority to US17/478,553 priority Critical patent/US20220006876A1/en
Assigned to SIRAJ TECHNOLOGIES LTD. reassignment SIRAJ TECHNOLOGIES LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ALSANAH, Yussif
Publication of US20220006876A1 publication Critical patent/US20220006876A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H04L67/2823—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/565—Conversion or adaptation of application format or content
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y40/00—IoT characterised by the purpose of the information processing
    • G16Y40/10—Detection; Monitoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • H04L67/18—
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/52—Network services specially adapted for the location of the user terminal

Definitions

  • the disclosed embodiments generally relates to systems having a plurality of data generating elements, and more particularly to systems including components that enable the transfer of data from the data generating elements to a cloud-based central processing element, and more particularly by using a series of elements including building blocks that convert protocols and data formats.
  • a system may include a plurality of end-point equipment that may have one or more data generating elements associated thereto. Such data generating elements may be generating data respective of such end-point equipment.
  • the data may be collected for the purpose of monitoring and/or controlling particular end-point equipment.
  • a sensor may be connected to a motor to check the number of Revolutions-Per-Minute (RPM) every predetermined period of time.
  • RPM Revolutions-Per-Minute
  • the data collected by the sensor may be used to make determinations respective of the motor.
  • the data provided by such a sensor has two aspects to it. That is, the sensor typically provides the data in a particular data format. Also, the data is transferred from the sensor onwards using a particular protocol.
  • Such a protocol may be a communication protocol, such as Ethernet or Internet protocols, Bluetooth®, WiFi®, serial or parallel protocols, and the like.
  • memory transfer protocols may also be used. That is, data is placed in a particular location in a memory unit and then used by another element for processing purposes.
  • a system 105 comprises an industrial system 130 that may be equipped with a plurality of Data Generating Elements (DGEs) 140-1 through 140-N (collectively described as DGE 140 or DGEs 140 hereinafter), where N is an integer number.
  • the DGEs 140 may be sensors, time stamp devices, and any other kind of elements that generate data respective of the industrial system 130 .
  • the data collected by each of the DGEs 140 is transferred via a gateway 150 to a network 110 , which is connected to one or more Cloud Service Providers (CSPs) 120 .
  • CSPs Cloud Service Providers
  • CSPs 120 - 1 through 120 -M (collectively described as CSP 120 or CSPs 120 hereinafter), where M is an integer.
  • each DGE 140 In order for each DGE 140 to operate in conjunction with the respective CSP 120 , each has to have a corresponding adaptor to properly function.
  • the adaptors 155 (e.g., adaptors 155 - 1 through 155 -N, which will be collectively described as adapter 155 or adapters 155 hereinafter), may be part of the gateway 150 that connects between the DGEs 140 and the network 110 .
  • the network 110 may be wired or wireless, and may include but is not limited to Local Area Network (LAN), Wide Area Network (WAN), Metro Area Network (MAN), Worldwide Web (WWW), the Internet, and any combinations thereof.
  • the adaptors 155 may interact with three DGEs 140 , DGE 140 - 1 , DGE 140 - 2 and DGE- 140 - 3 , with each DGE 140 having its particular characteristics.
  • DGE 140 - 1 and DGE 140 - 3 may provide a data format of 32-bit time stamp
  • DGE 140 - 2 may provide a data format of 64-bit time stamp.
  • DGEs 140 - 1 and 140 - 2 operate using a TCP/IP communication protocol
  • DGE 140 - 3 operates using a Structured Query Language database (SQL-DB) protocol.
  • SQL-DB Structured Query Language database
  • FIG. 2A shows the different conversions used in an adaptor 155 - 1 , operative in conjunction with a DGE 140 - 1 .
  • the adaptor 155 - 1 includes convert 32-bit time stamp data, convert Message Queuing Telemetry Transport (MQTT) data, convert data to net protocol, and finally provide access to the gateway 150 using TCP/IP.
  • MQTT Message Queuing Telemetry Transport
  • FIG. 2B shows the different conversions used in adaptor 155 - 2 , operative in conjunction with DGE 140 - 2 , that includes convert 64-bit time stamp data, convert Simple (or Streaming) Text Oriented Message Protocol (STOMP) data, convert data to net protocol, and finally provide access to the gateway 150 using TCP/IP.
  • FIG. 2C shows the conversions used in adaptor 155 - 3 , operative in conjunction with DGE 140 - 3 that converts the 32-bit data time stamp and then provides access to the gateway 150 on an SQL-DB protocol.
  • the number of resulting adaptor configuration possibilities is 200 million or more. This makes the manual solution for development of adaptors expensive, inefficient, and time consuming.
  • Certain embodiments disclosed herein include a method for data conversion.
  • the method includes receiving a data from a feeder, the feeder configured to provide the data from data generating element, generating a schema in response to the received data; merging the generated schema with a previously generated schema to update a dictionary, and deploying the dictionary within a universal converter, upon determining that the dictionary is unchanged, and a learning conducted by a learning machine satisfies a predetermined value.
  • Certain embodiments disclosed herein also include a system for data conversion system.
  • the system includes a data generating element configured to generate data, and a container configured to the data generating element, the container enabling the generated data to be delivered to a computing component and including a feeder configured to accept the generated data and transfer the generated data to the converter in a first data format of a plurality of data formats, a converter coupled to the feeder and configured to convert the first data format to the second data format, and a pusher coupled to the converter, and configured to transfer data in a second format from the plurality of data formats provided by the converter to a service provider.
  • a universal converter system including a processing circuitry, and a memory, the memory containing instructions that, when executed by the processing circuitry, configure the system to receive a data from a feeder, the feeder configured to provide the data from a data generating element, generate a schema in response to the received data, merge the generated schema with a previously generated schema to update a dictionary, and deploy the dictionary within a universal converter, upon determining that the dictionary is deployable, and a learning period by a learning machine is sufficiently long.
  • FIG. 1 is a schematic diagram of a system for transmission of data from an industrial system through a data generating elements each element connected by a hard-coded adaptor to the cloud.
  • FIG. 2A is a schematic diagram of adaptor conversion in a first exemplary case.
  • FIG. 2B is a schematic diagram of adaptor conversion in a second exemplary case.
  • FIG. 2C is a schematic diagram of adaptor conversion in a third exemplary case.
  • FIG. 3 is a schematic diagram of system for transmission of data from an industrial system through a gateway configured using a plurality of building blocks according to an embodiment.
  • FIG. 4 is a schematic diagram of a system adapted for transmission of data from an industrial system and configured with a plurality of feeders and pushers that connect through a universal converter according to an embodiment.
  • FIG. 5 is a flowchart for generating a dictionary for a universal converter according to an embodiment.
  • DGE Data Generating Elements
  • a universal converter converts data formats, from a plurality of DGEs, to a plurality of other standard data formats useable by the processing elements on the cloud.
  • the universal includes, after a period of learning of the language communicated by the DGEs, an industrial system that performs the learning period until such time that a long enough period passes without new learning to be conducted. Thereafter the universal converter is used between feeders and pushers to perform the necessary data format conversions using a learned dictionary.
  • IOT Internet of Things
  • IOT Industrial IOT
  • a first type of building blocks used are data feeders, referred to shortly herein as feeders.
  • the feeders are responsible for the access to the data.
  • a feeder may include, but is not limited to, a file feeder, a Transmission Control Protocol/Internet Protocol (TCP/IP) feeder, an Interlayer Collaboration Protocol (ILC) feeder, and (Structured Query Language (SQL) feeder, a Peripheral Component Interconnect (PCI) feeder, and the like.
  • a second type of building blocks is the data converters, or converters as used herein for short.
  • a converter may include, but is not limited to, a 32-bit time stamp, a 64 bit time stamp, a Mudbus, an MQTT, a Streaming Text Oriented Messaging Protocol (STOMP), and the like.
  • a third type of building blocks is the data pusher, or the pusher for short. These are building blocks that enable the interface to a particular Cloud Service Provider (CSP) 120 , for example a pusher that pushes the data to.
  • CSP Cloud Service Provider
  • An adaptor includes building blocks, each adaptor includes one feeder, one or more converters and one pusher. Furthermore, building blocks may be shared. That is, a building block may be used by more than one DGE or more than one other building block. For example, a TCP/IP feeder building block may be used by two or more DGEs that interface using this protocol. A 32-bit time stamp converter may be used by both an SQL-DB feeder as well as an MQTT converter.
  • FIG. 3 is an example block diagram 300 of a system 305 configured for transmission of data from an industrial system 130 through a gateway 350 that uses a plurality of building blocks according to an embodiment. Similar elements in FIG. 3 that are previously shown in FIG. 1 , and which have the same function are not described herein again.
  • FIG. 3 includes two CSPs 121 - 2 (which will be collectively referred to CSP 120 or CSPs 120 ), three DGEs 141 - 3 (which will be collectively referred to DGE 140 or DGEs 140 ).
  • the adaptors (e.g., adaptors 155 - 1 through 155 -N of the gateway 150 previously shown in FIG. 1 ) are replaced by a container 360 having therein a plurality of building blocks.
  • the plurality of building blocks includes various adaptors that are explained herein, using certain building blocks for more than one adaptor.
  • the gateway 350 may include a processing unit 352 and a memory 354 attached thereto, where the memory contains instructions therein that when executed by the processing unit realize the container 360 described herein.
  • a first adaptor is achieved for a Data Generating Element (DGE) 140 - 1 that provides a 32-bit time stamp using a Transmission Control Protocol/Internet Protocol (TCP/IP) protocol, the data of which is to be handled by a first Cloud Service Provider (CSP) 120 - 1 (where the CSP can also be known as a cloud processing element).
  • a TCP-IP feeder 310 is configured to connect DGE 140 - 1 to a network protocol converter 312 .
  • the network protocol converter 312 is further configured to connect to a Messaging and Queuing Telemetry Transport (MQTT) converter 314 , which in turns connects to a 32-bit time stamp converter 316 .
  • MQTT Messaging and Queuing Telemetry Transport
  • the 32-bit time stamp converter 316 connects to a second CSP pusher 318 .
  • a second adaptor is achieved for a DGE 140 - 2 that provides a 64-bit time stamp using a TCP/IP protocol, the data of which is to be handled by the first CSP 120 - 1 .
  • a TCP-IP feeder 310 connects DGE 140 - 2 to the net protocol converter 312 .
  • the net protocol converter 312 is configured to connect to a Streaming Text Oriented Messaging Protocol (STOMP) converter 13 , which in turn connects to a 64-bit time stamp converter 315 .
  • STOMP Streaming Text Oriented Messaging Protocol
  • the 64-bit time stamp converter 315 connects to a first CSP pusher 317 .
  • a third adaptor is achieved for DGE 140 - 3 that provides a 32-bit timestamp to be handled by a second CSP 120 - 2 .
  • An SQL-DB feeder 311 connects to DGE 140 - 3 and transfers data to the 32-bit time stamp converter 316 .
  • the 32-bit time stamp converter 316 connects to the second CSP pusher 318 .
  • a data converter system includes a data generating element that generates data, and a container configured to communicate with the data generating element.
  • the container enables the generated data to be delivered to the computing component and includes a feeder, a converter coupled to the feeder, and a pusher coupled to the converter.
  • the feeder is configured to accept the generated data and transfer the generated data to the converter in a first data format of a plurality of data formats.
  • the pusher is configured to transfer data in a second format from the plurality of data formats provided by the converter to a service provider.
  • the converter is configured to convert the first data format to the second data format.
  • the number of converters may grow exponentially as there are many possible permutations as each manufacturer of the DGE 140 may be using proprietary data formats. Therefore, the number of converters that may be needed to serve all the different permutations of pushers and feeders may be infinite. Therefore, coverage of the different permutations can be low, and it is impractical to expect hand-tailored development of converters for the container 360 . As such it would be advantageous not to have any converter at all by providing a universal converter as will be described in the exemplary FIG. 4 below.
  • FIG. 4 is an example schematic diagram 400 of a system 405 adapted for transmission of data from an industrial system and configured with a gateway 450 that includes a plurality feeders and pushers that connect through a universal converter according to an embodiment. Compared to FIG. 3 , similar components of FIG. 4 are similarly marked.
  • FIG. 4 additionally includes a universal converter 441 that provides an interface between a plurality of feeders, (e.g., feeders 310 and 311 ), and a plurality of pushers, (e.g., pushers 317 and 318 ).
  • a dictionary 443 is also included within the universal converter 441 .
  • the gateway 450 may include a processing unit 452 and a memory 454 attached thereto, where the memory contains instructions therein that when executed by the processing unit realize the container 460 described herein.
  • the universal converter 441 is created by initial automated learning of the inputs received from the DGEs 140 , selecting the necessary feeders and pushers, and creating the universal converter 441 based on further automated learning.
  • the generated universal converter 441 is configured to convert an input from a feeder, for example feeder 311 , to an output for a pusher, for example pusher 317 .
  • the conversion may be performed, for example, by processing sets of rules that include the universal converter 441 , by a matrix that converts the input to a desired output, by logic in the form of hardware, software, firmware or combination thereof, by a neural network tuned by the learning process, and by other options.
  • an error signal 442 may be generated to provide an error notification. This can happen in cases where a particular input is not recognized by the universal converter 441 or, if any one of the pushers provides an error notification. In such cases the error signal 442 is generated. Such errors may occur as a result of a data format that is received from any one of the feeder blocks 310 / 311 , but not recognized by the universal converter 441 or the dictionary 443 that has not been updated to recognize the data format.
  • Such errors may further occur upon providing a data format from the universal converter 441 to any one of the pushers 417 / 418 , and receiving a notification that the data format is unrecognized by the intended pusher 417 / 418 .
  • the error signal 442 may be processed by the industrial system 130 , by a CSP 120 , or by any other processing means that is adapted to handle error cases. Such an error signal 442 may provide an alert to an operator of the system 400 . Alternatively, the error signal 442 may cause the initiation of another learning phase to enhance the universal converter 441 (e.g., by updating the dictionary 443 ), so that in the future the universal converter 441 may be capable of handling the particular case that caused the error signal 442 in the first place.
  • the generation of a universal converter 441 is performed by listening to the outputs of the plurality of feeders 310 / 311 that provide a plurality of data formats after protocol adaptation.
  • This raw data is provided to a learning machine (not shown) that is configured to listen to the language.
  • a dictionary 443 that provides the ability to convert the non-standard data formats to standard data formats that may be used by the pushers 317 / 318 .
  • the universal converter 42 may accept data formats at its inputs, and output therefrom a normalized data format.
  • the learning machine is configured to recognize time series data that are typically characterized by at least three elements: an Identification (ID) that identifies the source of the data, a timestamp, and a data value (e.g., time, temperature, current, voltage, etc.). These and other data may be provided by the DGEs 140 to the universal converter 441 through the feeders 310 / 311 .
  • the values are then provided to the learning machine as vectors of numbers that are used to generate a dictionary 443 so that the resultant dictionary 443 can predict a proper output from a format that was not known previously to the converter 441 .
  • the learning machine may analyze certain characteristics of data values to interpret the data. For example, a sequence of data values that monotonously increases may provide an indication that this is a timestamp, an identification number may be repeated ever so often to indicate data coming from a particular DGE 140 , and a value that changes over time but relatively slowly may be indicative of data provided by a temperature sensor. Therefore the learning machine may learn from both the structure and the values of the data provided to it. In some cases, textual data is provided which enables the learning machine to better analyze the data provided.
  • the dictionary 443 is generated that provides the necessary translation from the data received to a normalized data structure.
  • the learning machine listen to a sufficient number of variants of the data structure so as to ensure proper understanding of the data structure. This is because a data structure may have different appearances, for example, the data structure may provide multiple samples but the number of samples may be different each time.
  • a data structure may be able to provide samples from one or more DGEs 140 and therefore, while using the same data structure, its appearance may be different. Therefore, the learning machine may cover as many as possible permutations of the data structure appearance so that the dictionary 443 can consistently predict the output of the normalized data format.
  • FIG. 5 is an example flowchart 500 for generating a dictionary 443 for a universal converter 441 according to an embodiment.
  • an output from one or more feeders is received by a learning machine.
  • one or more schemas are generated by the learning machine in response to the received data formats.
  • the generated one or more schemas are merged with previously generated schemas so as to generate an updated dictionary 443 .
  • S 540 it is checked whether the dictionary 443 has changed. If the dictionary has changed (i.e., it is not yet stable enough or includes enough schema or data to account for different schema permutations to be deployed for the purpose of being used by the universal converter), execution continues with S 510 ; otherwise, upon determining that the dictionary is unchanged, or is stable enough to be deployed, the flowchart 500 continues with S 550 .
  • a dictionary that changes often is typically an indication of a dictionary that cannot be used consistently and therefore more learning is required before it can be put to effective use.
  • S 550 it is checked whether learning by the learning machine has been sufficiently long (i.e., satisfies a predetermined criteria or value). This may be achieved, for example, by the passage of at least a predetermined period of time, a predetermined number of data units received from the feeders, or a predetermined number of feeders providing data. If it is determined in S 550 that the check was not long enough based on the parameters checked then execution continues with S 510 ; otherwise execution continues with S 560 .
  • the dictionary 443 is deployed, for example by replacing a previously installed dictionary 443 within the converter 441 or installing the initial dictionary 443 for use by the converter 441 .
  • data format may be converted to normalized data formats.
  • the learning machine may be reactivated to allow for additional learning and updating of the dictionary 443 . According to tests performed, the learning of 10,000 formats by the learning machine provided a dictionary 443 with a 99.98% accuracy of translation.
  • the various embodiments disclosed herein can be implemented as hardware, firmware, software, or any combination thereof.
  • the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium consisting of parts, or of certain devices and/or a combination of devices.
  • the application program may be uploaded to, and executed by, a machine comprising any suitable architecture.
  • the machine is implemented on a computer platform having hardware such as one or more central processing units (“CPUs”), a memory, and input/output interfaces.
  • CPUs central processing units
  • the computer platform may also include an operating system and microinstruction code.
  • a non-transitory computer readable medium is any computer readable medium except for a transitory propagating signal.
US17/478,553 2019-03-18 2021-09-17 Universal convertor, feeders and pushers for connectivity of industrial internet of things Abandoned US20220006876A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/478,553 US20220006876A1 (en) 2019-03-18 2021-09-17 Universal convertor, feeders and pushers for connectivity of industrial internet of things

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201962819959P 2019-03-18 2019-03-18
US201962819956P 2019-03-18 2019-03-18
PCT/US2020/023329 WO2020191028A1 (fr) 2019-03-18 2020-03-18 Convertisseur universel, dispositifs d'alimentation et poussoirs destinés à la connectivité de l'internet des objets industriel
US17/478,553 US20220006876A1 (en) 2019-03-18 2021-09-17 Universal convertor, feeders and pushers for connectivity of industrial internet of things

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2020/023329 Continuation WO2020191028A1 (fr) 2019-03-18 2020-03-18 Convertisseur universel, dispositifs d'alimentation et poussoirs destinés à la connectivité de l'internet des objets industriel

Publications (1)

Publication Number Publication Date
US20220006876A1 true US20220006876A1 (en) 2022-01-06

Family

ID=72521193

Family Applications (1)

Application Number Title Priority Date Filing Date
US17/478,553 Abandoned US20220006876A1 (en) 2019-03-18 2021-09-17 Universal convertor, feeders and pushers for connectivity of industrial internet of things

Country Status (2)

Country Link
US (1) US20220006876A1 (fr)
WO (1) WO2020191028A1 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7440967B2 (en) * 2004-11-10 2008-10-21 Xerox Corporation System and method for transforming legacy documents into XML documents
EP2154641A1 (fr) * 2008-08-14 2010-02-17 Crossgate AG Procédé et dispositif de conversion de messages entre plusieurs formats de données
CA3128629A1 (fr) * 2015-06-05 2016-07-28 C3.Ai, Inc. Systemes et procedes de traitement de donnees et d'applications ia d'entreprise

Also Published As

Publication number Publication date
WO2020191028A1 (fr) 2020-09-24

Similar Documents

Publication Publication Date Title
US20170339056A1 (en) Remote vehicle data collection system
US10237712B2 (en) In-field wireless access to smart instruments using Bluetooth low energy
US7062580B2 (en) Logic arrangement, system and method for configuration and control in fieldbus applications
EP2684336B1 (fr) Procédé et appareil pour des communications sans fil dans un environnement de contrôle ou de surveillance de processus
WO2017099940A1 (fr) Appareil et procédé d'utilisation d'une passerelle sécurisée de bord d'internet des objets
KR20130021652A (ko) 복수의 서로 다른 차량 진단 프로토콜을 표준 진단 프로토콜로 변환하는 인터페이스 장치 및 그 방법
CN103428627A (zh) 物联网系统中数据的传送方法、物联网系统及相应装置
CN112187922A (zh) 一种基于mqtt通信协议的智能物联网关机
US20190025790A1 (en) Generic Shadowing in Industrial Process Plants
JP2018180705A (ja) 異常検知システム、半導体装置の製造システムおよび製造方法
CN108536435A (zh) 一种自动生成can通信代码的方法
CN109150610A (zh) 基于规则适配的网络事件采集方法
EP3480916B1 (fr) Procédé, dispositif et programme informatique pour configurer un dispositif électronique intelligent
JP2013073503A (ja) 分散監視制御装置及び分散監視制御装置における制御方法
CN111970230A (zh) 基于云端识别的工业现场协议自动解析的方法及系统
US20220006876A1 (en) Universal convertor, feeders and pushers for connectivity of industrial internet of things
US20200228478A1 (en) Electronic message control
CN115794106A (zh) 一种轨道交通二进制协议数据配置式解析的方法及系统
US10218573B2 (en) System and method for discovering configurations of legacy control systems
Silva et al. Universal parser for wireless sensor networks in industrial cyber physical production systems
CN114793188A (zh) 一种智能网关数据采集推送方法
EP2091211A1 (fr) Procédé de conversion générique entre des données de serveur et des données de client
CN117044177A (zh) 使用便携式设置设备将设备调试到过程自动化系统
CN107368340A (zh) 一种软件自动安装方法及装置
KR20170127348A (ko) 반도체 제조 설비와 외부 분석 시스템 간의 데이터 연결 시스템 및 방법

Legal Events

Date Code Title Description
AS Assignment

Owner name: SIRAJ TECHNOLOGIES LTD., ISRAEL

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALSANAH, YUSSIF;REEL/FRAME:057519/0391

Effective date: 20210916

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION