WO2017142545A1 - Services de surveillance de contexte - Google Patents

Services de surveillance de contexte Download PDF

Info

Publication number
WO2017142545A1
WO2017142545A1 PCT/US2016/018601 US2016018601W WO2017142545A1 WO 2017142545 A1 WO2017142545 A1 WO 2017142545A1 US 2016018601 W US2016018601 W US 2016018601W WO 2017142545 A1 WO2017142545 A1 WO 2017142545A1
Authority
WO
WIPO (PCT)
Prior art keywords
triggers
context
flow package
context aware
monitor service
Prior art date
Application number
PCT/US2016/018601
Other languages
English (en)
Inventor
Jonathan Gibson
Clifford A. WILKE
Paul D. Thomas
Benjamin L. REES
Original Assignee
Hewlett Packard Enterprise Development Lp
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 Hewlett Packard Enterprise Development Lp filed Critical Hewlett Packard Enterprise Development Lp
Priority to PCT/US2016/018601 priority Critical patent/WO2017142545A1/fr
Publication of WO2017142545A1 publication Critical patent/WO2017142545A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • 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/535—Tracking the activity of the user
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H04W4/029—Location-based management or tracking services

Definitions

  • the Internet of Things is a network of physical objects, devices, and machines that are embedded with electronics, software, sensors, and network connectivity to enable these devices to collect and exchange data.
  • the Internet of Things allows objects to be sensed and controlled remotely across a network infrastructure.
  • Figure 1 is a schematic diagram illustrating an example context monitoring system including an example context aware device couplable to a network in accordance with aspects of the present disclosure.
  • Figure 2 is a schematic diagram illustrating another example context monitoring system in accordance with aspects of the present disclosure.
  • Figure 3 is a schematic diagram illustrating an example context monitor service operable in the context aware devices of Figures 1 and 2 in accordance with aspects of the present disclosure.
  • Figure 4 is a schematic diagram illustrating an example flow operation in accordance with aspects of the present disclosure.
  • Figure 5 is a flow diagram illustrating an example context aware method in accordance with aspects of the present disclosure.
  • Figure 6 is a schematic diagram illustrating an example computing device that can be used to implement the method of Figure 5 and the systems of Figure 1 and 2.
  • Digital context awareness refers to technologies for detecting changes in context of a device, and providing information or services suitable for a user of the device or changing a state of a system by the system itself.
  • Digital context awareness includes a style of computing in which situational and environmental information such as about people, places, events, and things are used to anticipate and provide situation awareness and usable content and functions, for example.
  • digital context aware brings context to information in real-time through logic and techniques.
  • Digital context awareness is implemented by applying a context monitoring service for reasoning of the context.
  • Context can include many factors including presence, environmental factors, recent activity, external stimuli, security information, biometric information, personal preferences, location information, speed information, and network information, for example.
  • Context awareness can combine information about location, profile, preference, sentiment, history, and other factors. Aspects of the present disclosure provide automation through context aware systems for monitoring and controlling various context aware devices. Digital context aware monitoring works with real-time context aware information flows and aggregated and trending information flows.
  • FIG. 1 illustrates a context monitoring system 100 including an example context aware device 12, or node, according to one example of the present disclosure.
  • Context aware device 1 2 includes electronic components 14, a memory 16, and a processor 1 8.
  • Electronic components 14 can be coupled to a network 1 9.
  • a context monitor service 20 is stored on memory 16 and executed in processor 18 of context aware device 12.
  • Context monitor service 20 can perform as a service application on context aware device 12.
  • Context monitor service 20 can operate fully for partially on context aware device 12.
  • Techniques or logic can be performed on the "edge" of network 19, on context aware device 12 with having electronic components 14 that are connectable to network 19.
  • Digital context aware (i.e., "edge") devices 1 2 can implement logic to perform local monitoring and control. With digital context aware system 100, logic and techniques can occur locally at context monitor service 20.
  • Context monitor service 20 can detect and/or determine various types of information based on contextual change as described in more detail below. Data can be compiled, and logic can be performed, for example, on context aware device 12 through context monitor service 20.
  • Instructions may be stored, for example, on memory 16, such as computer-readable storage medium, which may include any electronic, magnetic, optical, or other physical storage device that store executable instructions.
  • the computer-readable storage medium is non-transitory in the sense that it does not encompass a transitory signal but instead is made up of one or more memory components configured to store the instructions which are executable on a computing system such as context aware device 12 of Figure 1 .
  • memory 16 may be, for example, random access memory (RAM), electrically-erasable programmable read-only memory (EPPROM), a storage drive, an optical disk, and any other suitable type of volatile or non-volatile memory that stores instructions to cause a programmable processor to perform the techniques described herein.
  • memory 1 6 includes a main memory, such as a RAM in which the instructions may be stored during runtime, and a secondary memory, such as a nonvolatile memory in which a copy of the instructions is stored.
  • Processor 18 can include two or more processing cores on a chip or two or more processor chips.
  • context aware device 1 2 can also have one or more additional processing or specialized processors (not shown), such as a graphics processor for general-purpose computing on graphics processor units, to perform processing functions offloaded from processor 1 8.
  • context aware device 12 can include dedicated hardware, such as one or more integrated circuits, Application Specific
  • ASICs Integrated Circuits
  • ASSPs Application Specific Special Processors
  • FPGAs Field Programmable Gate Arrays
  • Context monitor service 20 can receive sensed data 22 from context aware device 12 that context monitor service 20 resides on.
  • Sensed data 22 can be acquired, or sensed, through one or more of a variety of different sensors included on context aware device 1 2.
  • sensed data 22 can be acquired through sensors such as accelerometers, gyroscopes, magnetometer, manometer, and the like.
  • Triggers 24 initiate, or fire, to a dispatcher queue 26, with at least one trigger 24 being based on sensed data 22.
  • Triggers 24 are organized in dispatcher queue 26.
  • Triggers 24 can be organized in any manner suitable for controlling the operation of flow packages 28 (e.g., packages of execution).
  • Flow packages 28 can be programmed operations that can be executed upon the occurrence of pre-determined triggers 24. Flow packages 28 can be one or more of user based, system based, based on machine learning, based on user input, artificial intelligence, or policies, for example.
  • context monitor service 20 may comprise instructions executable by processor 18 to perform the functionalities described above.
  • the functionalities described above in relation to context monitor service 20 may be implemented at least in part in electronic circuitry.
  • the functionalities described above in relation to context monitor service 20 may be implemented via engines comprising any combination of hardware and programming to implement the functionalities of the engines.
  • the programming for the engines may be processor executable instructions stored on at least one non-transitory machine-readable storage medium and the hardware for the engines may include at least one processing resource to execute those instructions.
  • the hardware may also include other electronic circuitry to at least partially implement at least one of the engines.
  • the at least one machine-readable storage medium may store instructions that, when executed by the at least one processing resource, at least partially implement some or all of the engines.
  • the engines may include at least one machine-readable storage medium storing the instructions and the at least one processing resource to execute the instructions.
  • the instructions can be part of an installation package that, when installed, can be executed by the at least one processing resource to at least partially implement at least some of the engines of system 220.
  • the machine-readable storage medium may be a portable medium, such as a CD, DVD, or flash drive, or a memory maintained by a server from which the installation package can be downloaded and installed.
  • the instructions may be part of an application, applications, or component already installed on networking device 200 including the processing resource.
  • the machine-readable storage medium may include memory such as a hard drive, solid state drive, or the like.
  • the functionalities of any engines of system 220 may be at least partially implemented in the form of electronic circuitry.
  • FIG. 2 illustrates a context monitoring system 200 in accordance with an example of the present disclosure.
  • Context monitoring system 200 includes a local context aware device 212 and remote context aware devices 212a, 21 2b, 21 2c.
  • Local and remoted context aware devices 212, 21 2a, 212b, 212c can be similar to context aware device 12 of Figure 1 and can include any of the features and functionalities described above in relation to context aware device 20 as well as additional features and functionalities as described below. While only three remote context aware devices 212a, 21 2b, 21 2c are illustrated, it is understood that more or less remote context aware devices 21 2a... x can be included with context monitoring system 200.
  • context aware devices 212, 212a...x each include electronic components 14, memory 16, and processor 18.
  • context monitor service 20 of Figure 2 includes the features and functionalities of context monitor service 20 of Figure 1 .
  • Figure 2 illustrates additional features of context monitor service 20 including context monitor 21 and broker communicator 32, for example, as described further below.
  • the functionalities described above in relation to context monitor service 20 of device 21 2 may be implemented at least in part in electronic circuitry.
  • the functionalities described above in relation to context monitor service 20 of device 212 may be implemented via engines comprising any combination of hardware and programming to implement the functionalities of the engines, as described above.
  • a local context 23 can provide data control and communication within context aware device 212 based on events, for example, local to context aware device 212 or sensed data 22. As indicated by arrows A 1 ; local context 23 communicates with context monitor service 20. Local context 23 has a data flow within context aware device 212 similar to that of a broker 32 to remote context aware devices 2121 a, 21 2b, 21 2c further described below.
  • Sensed data 22 can be communicatively connected to context monitor service 20 as indicated by arrows A 2 .
  • Sensed data 22 can be interior or exterior to context aware device 22 and can provide direct interface into context aware device 212.
  • Context monitor service 20 can be provided on context aware device 212 and/or can be provided on one or more context aware devices 212a, 212b, 212c.
  • context aware devices 212, 21 2a, 21 2b, 212c can interconnect and interoperate within the internet infrastructure.
  • Local and remote context aware devices 212, 212a, 212b, 212c can communicate with one another and perform operations in a collaborative manner as system 200.
  • Context monitor service 20 can receive sensed data 22, from context aware device 212 that context monitor service 20 resides on, and/or receive sensed data 22 from disparate, or remote, context aware devices 212a, 212b, 212c that are the eco-system forming context monitoring system 200.
  • Context monitor system 200 can be implemented throughout an
  • Enterprise eco-system systems used in an organization
  • edge devices such as wearables and/or sensors
  • SAP Systems, Applications and Products
  • a single code base can be distributed on various disparate edge devices (e.g., 212, 212a, 212b, 21 2c) and/or in traditional enterprise environments to sense contextual changes and perform appropriate action in real-time.
  • a uniform code base can be used across multiple devices and environments.
  • Managing context and performing actions can be based on contextual changes in the Enterprise, for example, in real-time.
  • a digital context aware (DCA) context monitor 21 can be installed on any node, or device.
  • DCA context monitor 21 runs, or executes, context monitor service 20 to take local control inputs and remote control inputs as indicated by the arrows in Figure 2.
  • Context monitor service 20 is programmable, or reprogrammable, throughout the operation of context monitor 21 .
  • One form of local control inputs and/or remote control inputs is contextual changes.
  • context monitor service 20 can execute flows and/or send out local events to the device of context monitor 21 is installed on and/or send out remote events to other nodes, or devices.
  • a remote control input such as sending a control file/commands to dynamically configure or reconfigure context aware device 212 and/or remote control inputs from various remote context aware devices 212a, 212b, 212c.
  • Broker 32 communicates to remote context aware devices 212a, 212b, 212c in the eco-system of context aware system 200.
  • Broker 32 provides communication and contextual relations between each of remote context aware devices 212a, 21 2b, 21 2c and with context aware device 212.
  • Context monitoring service 20 can be controlled from local context aware device 212 on which context monitor service 20 is installed or from a remote context aware device (e.g., 21 2a, 212b, 212c).
  • Remote context communications indicated by arrows A 4 are handled via broker 32.
  • Broker 32 can be a message broker, for example.
  • FIG. 3 is a schematic diagram illustrating context monitor 21 operable in context aware devices 12 and 212, for example.
  • Context monitor 21 can include a dispatcher 42, a controller 44, and an executor 46.
  • Context monitor 21 can also include a group 48 of flow packages 28a... x and variables 50.
  • Context monitor 21 processes the local control inputs and remote control inputs and uses variables for processing purposes and/or for managing state of the system.
  • Context monitor 21 is configured through flow packages 28 and variables 50 for storage to retain information between runs of flow packages 28.
  • Context monitor 21 implements detection and monitoring of one or more of various types of context information as inputs from local and remote devices (e.g., 1 2, 212, 212a, etc.).
  • Context monitor 21 provides monitoring and automating in real-time to make systems (e.g., processes) run more efficiently and productively.
  • Triggers 24 initiate, or fire, to a dispatcher 42, with at least one trigger 24 being based on a sensed data 22 (see, e.g., Figure 2). Triggers 24 are organized in dispatcher 42. Dispatcher 42 is suitable for retrieval and execution of instructions. Triggers 24 can be organized in any manner suitable for controlling the operation of flow packages 28 (e.g., packages of execution). Triggers 24 can be fired in timed intervals, when data is sensed, or at determined manner. Organized triggers 24 are sent to controller 44, where upon executor then executes a flow package 28 through an executor 46.
  • controller 44 can enable, disable, create, or delete flow packages 28.
  • Flow packages 28 can be created, deleted, etc. through action of another flow package 28 or by from a source external to context monitor 21 (e.g., from another context monitor on a remote context aware device 212a, 21 2b, 21 2c, etc.) or locally through context aware device 212 internal by local context 23.
  • Flow packages 28 can be executed sequentially, in parallel (e.g., at the same time or staggered) or any other suitable order.
  • Executing flow package 28 can include accessing a database of variables 50.
  • Flow packages 28 can be programmed operations that can be executed upon the occurrence of pre-determined triggers 24.
  • a flow package 28 can be modified, deleted, or added in real time.
  • Control monitor 21 provides fluid control to execute and add, delete, and modify flow packages.
  • Flow packages 28 assist with the governing of the dynamic change in context.
  • the functionalities of context monitor 21 may be implemented by instructions stored on a machine-readable storage medium and executable by a processor.
  • the functionalities described above in relation to context monitor 21 may be implemented at least in part in electronic circuitry.
  • the functionalities described above in relation to context monitor 21 may be implemented via engines comprising any combination of hardware and programming to implement the functionalities of the engines, as described above.
  • FIG. 4 is an example flow package 28 operation executable in accordance with aspects of the present disclosure.
  • Triggers 24a... x e.g., temperature goes out of a predetermined range, spin cycle speed, etc.
  • Flow package 28 can have multiple triggers 24 a...x that can initiate action 60a.
  • a few examples of actions 60 can be sending a text message, or setting a variable, etc.
  • Decision 62 can be to initiate another action 62b based upon logic performed.
  • FIG. 5 is a flow diagram illustrating an example context aware method 300 in accordance with aspects of the present disclosure.
  • a context monitor service is executed on a context aware device.
  • sensed data is received.
  • triggers are initiated to a dispatcher queue, wherein at least one of the triggers is based on the sensed data.
  • the triggers are organized in the dispatcher queue.
  • operation of a flow package associated with one of the triggers is controlled.
  • the flow package is executed.
  • remote devices are communicated with.
  • the functionalities of context aware method 300 can be performed as described above in relation to any of Figures 1 -4 and also as further described below in relation to Figure 6.
  • the functionalities described above in relation to context aware method 300 can be implemented at least in part in electronic circuitry.
  • the functionalities described above in relation to context aware method 300 can be implemented via engines comprising any combination of hardware and programming to implement the functionalities of the engines, as described above.
  • Context monitor systems as described above can operate in real-time, near real-time (NRT), batch mode, or offline.
  • Real-time refers to a response of the context aware device or system responding within specified time constraints, in some examples, in the order of milliseconds or microseconds.
  • NRT refers to a time delay introduced between the occurrence of an event and use of processed data as nearly the time of the live event.
  • Batch mode refers to batching or collecting data into sets of records to process as a unit or units.
  • Single commands, multiple commands, or up to a whole file of commands, for example, can be used to prompt context monitor service into performing, or executing, actions.
  • the method can include remotely controlling operation of the flow package to create, delete, and/or modifying flow packages to make context aware system perform actions.
  • Figure 6 illustrates an example context aware system that can be employed in an operating environment and used to host or run computer programming in the form of a context monitor service 420 implementing example method 300, and other methods of the disclosure, as included on one or more computer readable storage mediums storing computer executable instructions for controlling context aware system, such as context aware device 41 2, to perform a process.
  • context aware device 412 of Figure 6 can be used to implement functionalities of context monitor service 420.
  • sensed data 422 from context aware device 412 can be acquired, or sensed, through one or more of a variety of different sensors included on context aware device 412.
  • Triggers 424 can implement the functionalities described above in relation to triggers 24, dispatcher queue 426 can implement the functionalities described above in relation to dispatcher queue 26, flow packages 428 can implement the functionalities described above in relation to flow packages 28.
  • the exemplary context aware system of Figure 6 includes a context aware device, such as context aware device 412.
  • Context aware device 412 typically includes one or more processors 418 and memory 41 6 for storing and executing context monitoring service 420.
  • Processors 418 may include two or more processing cores on a chip or two or more processor chips.
  • context aware device 412 can also have one or more additional processing or specialized processors (not shown), such as a graphics processor for general-purpose computing on graphics processor units, to perform processing functions offloaded from processor 418.
  • Memory 416 can be arranged in a hierarchy and may include one or more levels of cache.
  • Memory 41 6 can be volatile (such as random access memory (RAM)), non-volatile (such as read only memory (ROM), flash memory, etc.), or some combination of the two.
  • the context aware device 412 can take one or more of several forms of "smart" or internet couplable devices that operate in the Internet of Things. Such forms include, but are not limited to, thermostats, garage door openers, security system devices, manufacturing system devices, lighting system devices, or other, and can be a stand-alone devices or configured as part of a network, cluster, cloud services infrastructure, or other.
  • the internet includes tiers including the "cloud” and the "edge”.
  • data is transmitted to the cloud to broaden a technique or logic in order to determine an appropriate response action to the data.
  • Pulling data from node sensors can be transmitted to the cloud to perform logic and techniques, however, this uses internet bandwidth and can cause slight delays in processing, making the techniques occur near real-time instead of real-time.
  • Some environments use local area wireless computer networking technology, such as Wi-Fi®, for remote monitoring and control of nodes.
  • Context monitor service 420 can communicate from and operate within the cloud, on a server, or on the edge (e.g., the node).
  • Context aware device 41 2 may also include additional storage 408.
  • Storage 408 may be removable and/or non-removable and can include magnetic or optical disks or solid-state memory, or flash storage devices.
  • Computer storage media includes volatile and nonvolatile, removable and non- removable media implemented in any suitable method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
  • context monitor service 420 can be stored in storage 408, and at least one or more components of context monitor service 420 can be loaded and stored into memory 418 for execution on processor 418.
  • a propagating signal by itself does not qualify as storage media.
  • Context aware device 41 2 can be wirelessly or hard-wired connected to various other devices to receive and/or provide inputs and outputs.
  • Input devices 410 may include devices such as sensors, keyboard, voice input device, touch input device, or other.
  • Output devices 414 may include devices such as a display, speakers, or the like.
  • Context aware device 41 2 often includes one or more communication connections 423 that allow context aware device 412 to communicate with other context aware devices 413.
  • Example communication connections can include, but are not limited to, an Ethernet interface, a wireless interface, a bus interface, a storage area network interface, a proprietary interface.
  • Communication connections 423 can be used to couple context aware device 412 to a computer network 425 which is a collection of context aware devices and possibly other devices interconnected by
  • communications channels that facilitate communications and allows sharing of resources and information among interconnected devices.
  • Examples of computer networks include a local area network, a wide area network, the Internet, or other network.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Debugging And Monitoring (AREA)

Abstract

La présente invention porte, dans certains exemples, sur un service de surveillance de contexte pouvant être exécuté sur un dispositif en rapport avec un contexte pour recevoir des données détectées, déclencher des déclencheurs dans une file d'attente de répartiteur, au moins l'un des déclencheurs faisant appel aux données détectées, organiser les déclencheurs dans la file d'attente de répartiteur, répartir les déclencheurs organisés, commander le fonctionnement d'un progiciel de flux en réponse à un premier déclencheur parmi les déclencheurs, et exécuter le progiciel de flux en réponse à un second déclencheur parmi les déclencheurs.
PCT/US2016/018601 2016-02-19 2016-02-19 Services de surveillance de contexte WO2017142545A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2016/018601 WO2017142545A1 (fr) 2016-02-19 2016-02-19 Services de surveillance de contexte

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2016/018601 WO2017142545A1 (fr) 2016-02-19 2016-02-19 Services de surveillance de contexte

Publications (1)

Publication Number Publication Date
WO2017142545A1 true WO2017142545A1 (fr) 2017-08-24

Family

ID=59626173

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2016/018601 WO2017142545A1 (fr) 2016-02-19 2016-02-19 Services de surveillance de contexte

Country Status (1)

Country Link
WO (1) WO2017142545A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109981487A (zh) * 2019-03-27 2019-07-05 北京邮电大学 一种数据调度方法、装置、电子设备及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080133812A1 (en) * 2006-11-30 2008-06-05 Sap Ag Context based event handling and execution with prioritization and interrupt management
US20110133888A1 (en) * 2009-08-17 2011-06-09 Timothy Dirk Stevens Contextually aware monitoring of assets
KR101198437B1 (ko) * 2008-06-26 2012-11-06 노키아 코포레이션 컨텍스트 트리거형 배포 방법, 장치 및 컴퓨터 판독 가능한 저장매체
US20140006620A1 (en) * 2012-06-27 2014-01-02 International Business Machines Corporation System, method and program product for local client device context-aware shared resource and service management
US20150223009A1 (en) * 2008-10-31 2015-08-06 Qualcomm Incorporated Wake-up trigger for implementation of target actions

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080133812A1 (en) * 2006-11-30 2008-06-05 Sap Ag Context based event handling and execution with prioritization and interrupt management
KR101198437B1 (ko) * 2008-06-26 2012-11-06 노키아 코포레이션 컨텍스트 트리거형 배포 방법, 장치 및 컴퓨터 판독 가능한 저장매체
US20150223009A1 (en) * 2008-10-31 2015-08-06 Qualcomm Incorporated Wake-up trigger for implementation of target actions
US20110133888A1 (en) * 2009-08-17 2011-06-09 Timothy Dirk Stevens Contextually aware monitoring of assets
US20140006620A1 (en) * 2012-06-27 2014-01-02 International Business Machines Corporation System, method and program product for local client device context-aware shared resource and service management

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109981487A (zh) * 2019-03-27 2019-07-05 北京邮电大学 一种数据调度方法、装置、电子设备及可读存储介质
CN109981487B (zh) * 2019-03-27 2020-10-27 北京邮电大学 一种数据调度方法、装置、电子设备及可读存储介质

Similar Documents

Publication Publication Date Title
US11507430B2 (en) Accelerated resource allocation techniques
US10360069B2 (en) Automated transfer of neural network definitions among federated areas
US10740395B2 (en) Staged training of neural networks for improved time series prediction performance
US10685283B2 (en) Demand classification based pipeline system for time-series data forecasting
US10740076B2 (en) Many task computing with message passing interface
JP7086905B2 (ja) プロセス制御システムにおけるビッグデータ
US10095552B2 (en) Automated transfer of objects among federated areas
CN109564568B (zh) 用于分布式数据集索引的装置、方法和机器可读存储介质
US11086607B2 (en) Automated message-based job flow cancellation in container-supported many task computing
US10437635B2 (en) Throttling events in entity lifecycle management
US10616079B2 (en) Simplified entity lifecycle management
US20180189113A1 (en) Federated device support for generation of directed acyclic graphs
US11435726B2 (en) Contextualization of industrial data at the device level
KR20220032007A (ko) 디지털 노동력 지능형 오케스트레이션을 위한 시스템들 및 방법들
CN110622477B (zh) 物联网中基于规则的信息交换的方法和设备
US10200240B2 (en) Method for configuring an M2M system
US11675605B2 (en) Discovery, mapping, and scoring of machine learning models residing on an external application from within a data pipeline
CN108292383A (zh) 与通信相关联的任务的自动提取
US20170300804A1 (en) Software architecture for expert system
Bonnard et al. A big data/analytics platform for industry 4.0 implementation in SMEs
KR101686919B1 (ko) 빅데이터에 기반한 추론 엔진을 관리하는 방법 및 장치
WO2017142545A1 (fr) Services de surveillance de contexte
CN114047729B (zh) 天然植物加工控制方法、系统、计算机设备和存储介质
US20080208364A1 (en) Language-based organization of controller engine instances
KR102651797B1 (ko) Ai 비전문가를 위한 소프트웨어 정의 제조 기반의 머신러닝 플랫폼 시스템

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16890842

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16890842

Country of ref document: EP

Kind code of ref document: A1