WO2018046108A1 - Module et procédé de communication - Google Patents

Module et procédé de communication Download PDF

Info

Publication number
WO2018046108A1
WO2018046108A1 PCT/EP2016/071436 EP2016071436W WO2018046108A1 WO 2018046108 A1 WO2018046108 A1 WO 2018046108A1 EP 2016071436 W EP2016071436 W EP 2016071436W WO 2018046108 A1 WO2018046108 A1 WO 2018046108A1
Authority
WO
WIPO (PCT)
Prior art keywords
microcontroller
communications module
sensor
module
sensor systems
Prior art date
Application number
PCT/EP2016/071436
Other languages
English (en)
Inventor
Marcus GÅRDMAN
Cristian Norlin
Niclas JONASSON
Athanasios KARAPANTELAKIS
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
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 Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2016/071436 priority Critical patent/WO2018046108A1/fr
Publication of WO2018046108A1 publication Critical patent/WO2018046108A1/fr

Links

Classifications

    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/61—Installation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G06F8/656—Updates while running
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Definitions

  • the present invention relates to a communications module and method, and in particular a communications module and method for interfacing between one or more repository units and one or more microcontroller-sensor systems, for example for handling configuration and/or update information.
  • microcontrollers and sensors exist. For every type of sensor (ranging from those monitoring environmental qualities such as temperature sensors, to actuators such as DC motors, servos but also communication sensors), different communication protocols can exist between such sensors and their associated microcontrollers.
  • FIG. 1 shows an example of such microcontroller-sensor systems 101 .
  • Each microcontroller-sensor system 101 comprises a microcontroller 102 and one or more associated sensors 103.
  • a first microcontroller 102i is associated with three sensors 103n , 103i2 and 103i3, which together form a microcontroller-sensor system 1011.
  • a second microcontroller 1022 is associated with a single sensor 10321, which together form another microcontroller-sensor system 1012, and so on.
  • Different communication protocols may exist between the microcontroller 102i and its associated sensors 103n , 103i2 and 103i3, compared to that of microcontroller 1022 and its associated sensor 10321.
  • the microcontroller 102i may use different communication protocols between two or more of its own associated sensors 103n , 103i2 and 103i3.
  • microcontroller-sensor systems This means that operations such as the mass updating of software or firmware for microcontroller-sensor systems (MSSs) is a process that involves a large operational expense, either requiring a local update of a particular microcontroller-sensor system, for example through serial connection, or replacement of a microcontroller-sensor system with new hardware.
  • MMSs microcontroller-sensor systems
  • a communications module comprising a first interface module for interfacing with one or more microcontroller-sensor systems, MSSs, wherein a microcontroller-sensor system comprises a microcontroller and at least one associated sensor.
  • the communications module comprises a second interface module for interfacing with one or more repository units.
  • a method in a communications module for interfacing between one or more repository units and one or more microcontroller- sensor systems.
  • the method comprises detecting one or more microcontroller-sensor systems in a vicinity of the communications module using a first interface module.
  • the method comprises communicating with one or more repository units using a second interface module to obtain configuration and/or update data for the one or more detected microcontroller-sensor systems.
  • the method comprises communicating the obtained configuration and/or update data to the one or more microcontroller-sensor systems using a third interface unit.
  • a microcontroller-sensor system for use with a communications module as described herein.
  • the microcontroller-sensor system comprises a microcontroller and at least one sensor associated with the microcontroller, and an electronic or visual tag for identifying the microcontroller and/or at least one sensor to the communications module.
  • Figure 1 shows examples of microcontroller-sensor systems
  • Figure 2 shows an example of a communications module according to an embodiment
  • Figure 3 shows an example of an application of a communications module according to an embodiment
  • Figure 4 shows an example of a signalling flow according to an embodiment
  • Figure 5 shows an example of a signalling flow according to another embodiment
  • Figure 6 shows an example of a signalling flow according to another embodiment
  • Figure 7 shows an example of a method according to an embodiment
  • Figure 8 shows an example of a wireless network node according to an embodiment
  • FIGS. 9A to 9D show examples of different configurations. Detailed description
  • a communications module for interfacing between one or more microcontroller-sensor systems, MSSs, and one or more repository units.
  • References herein to a repository unit are intended to include a module or node, either network based or cloud based (or a combination of both), which is configured to handle configuration and/or update information, including for example software or firmware, for microcontrollers and/or sensors.
  • a repository unit may also include compiler functionality, for example to compile source code into software binaries on request, prior to sending to a communications module.
  • a repository unit may consist of a software repository (for example a software version control system known as GIT, a subversion, a Web Distributed Authoring and Versioning extension of the Hypertext Transfer Protocol - WEBDAV/HTTP, etc.), a compiler, an interface to the communications module and an interface to a software designer (who updates/creates new software/firmware for microcontrollers and/or sensors).
  • a repository unit may retrieve code from a software repository and compile it to the architecture of the microcontroller of the MSS the communications module is coupled to. Subsequently, a compiled binary may be sent to the communications module.
  • FIG 2 shows an example of a communications module 105 according to an embodiment.
  • the communications module 105 comprises a first interface module 106 for interfacing with one or more microcontroller-sensor systems, MSSs, (not shown in detail), wherein a microcontroller-sensor system comprises a microcontroller and at least one associated sensor.
  • the communications module 105 comprises a second interface module 107 for interfacing with one or more repository units (not shown in detail).
  • this enables, for example, mass updates to be performed to various MSSs, including different microcontroller-sensor systems, via the communications module 105.
  • Such an embodiment also enables a MSS to be configured by the communications module 105, for example when a new MSS is installed in the vicinity of the communications module 105. In this way a MSS does not necessarily have to be pre-configured prior to installation, with the communications module 105 taking care of this upon detection, or being informed, about the presence of a new MSS.
  • the first interface module 106 may be adapted to receive identifier information from a microcontroller and/or one or more sensors associated with a microcontroller of a MSS. This identifier information can be used by the communications module 105, as described in greater detail later, to establish which types of microcontroller-sensor systems are in the vicinity of the communications module 105, such that the communications module 105 can then communicate with different microcontroller- sensor systems according to their particular communication protocols, while also being able to communicate with one or more repository units to obtain configuration data such as software or firmware relating to configuration information, or update information, relating to one or more different microcontroller-sensor systems.
  • the communications module 105 comprises a processing unit 108 for detecting the type of microcontroller and/or the type of one or more sensors associated with a microcontroller of a MSS, using the received identifier information.
  • the identifier information may comprise a model type or a serial number of a microcontroller and/or sensor.
  • the processing unit 108 is able to identify the type of MSS that it needs to communicate with, and select an appropriate communication protocol for doing so. This may involve consulting a database to obtain the relevant information. Part or whole of such a database may either be located within the communications module 105 itself, or located elsewhere, for example in another network node or nodes, or in a cloud based functional unit.
  • the first interface module 106 is adapted to communicate with the one or more microcontrollers and/or one or more associated sensors of the MSSs using wireless communication.
  • the wireless communication may comprise short-range radio communication, such as radio frequency identification (RFID) communication, or near field communication (NFC), Bluetooth communication or some other form of wireless or optical communication technique.
  • RFID radio frequency identification
  • NFC near field communication
  • the communications module 105 is able to detect or determine which MSSs are in the vicinity of the communications module, for example within a particular threshold distance (for example either a physical distance or signalling distance), and act as an interface between such MSSs and one or more repository units.
  • the communications module 105 may interface with a plurality of repository units.
  • the first interface module 106 comprises an RFID unit for communicating with one or more RFID units located on the one or more microcontrollers and/or associated sensors of the MSSs.
  • the RFID unit of the first interface module 106 may comprise an RFID reader for communication with one or more passive or active RFID tags located on the one or more microcontrollers and/or associated sensors of the MSSs.
  • the communications module 105 is able to identify one or more MSSs in the vicinity of the communications module using some form of short range radio communication technique that does not require prior knowledge of what type of communication protocol should be used to communicate with the MSSs.
  • the first interface module 106 of the communications module is coupled to an imaging unit for imaging visual identification tags located on the one or more microcontrollers-sensor systems.
  • the imaging unit may include, for example, image recognition technology.
  • the visual identification tags may comprise, for example, Quick Response (QR) codes to be imaged by the imaging unit coupled to the communications module 105, thus enabling the type of microcontroller/sensor to be detected by optical means.
  • QR Quick Response
  • the communications module 105 is able, either proactively or reactively, to communicate with one or more repository units for obtaining data relating to the one or more MSSs identified by the communications module 105, for example configuration or update data. It is noted that in the embodiments described herein, other forms of data may be obtained from the one or more repository units.
  • the communications module 105 may comprise a third interface module 109 for communicating data with the one or more MSSs.
  • the third interface module 109 may comprise a wireless link for communicating data between the communications module 105 and the one or more MSSs.
  • the communications module 105 may be adapted, for example in response to a trigger signal, to detect one or more microcontroller-sensor systems using the first interface module 106, communicate with one or more repository units via the second interface unit 107, for example to obtain configuration and/or update data for the one or more detected microcontroller-sensor systems, and communicate the obtained configuration and/or update data to the one or more microcontrollers using the third interface unit 109.
  • a trigger signal may be received, for example, in response to a power-up of the communications module, or in response to an update message received from one or more repository units, or in response to a new microcontroller-sensor system being detected in the vicinity of the communications module.
  • a communications module 105 is able to provide data communication functionality via the third interface module 109, which may include for example the communications module 105 programming a microcontroller to interface with sensors the microcontroller is connected to, and offer update functionality to the microcontroller-sensor system in case a software update becomes available.
  • an updating process can cover uploading of a newer version of the microcontroller software ("push") or updating upon detection of new sensor hardware (“pull").
  • Figure 3 shows further details of an application of a communications module 105 according to an embodiment.
  • the communications module 105 of Figure 3 provides an interface between one or more microcontroller-sensor systems 101 (only one shown for clarity) and one or more repository units 1 10 (again, only one shown for clarity).
  • the microcontroller-sensor system 101 comprises a microcontroller 102 connected to one or a plurality of sensors 103 (only one sensor 103 shown for clarity).
  • the microcontroller 102 comprises an RFID unit 1 13
  • the sensor 103 comprises an RFID unit 1 14.
  • the RFID units 1 13, 1 14 contain static information relating to the model of the microcontroller and sensor, respectively. For example, this information could be a sensor model or serial number or alphanumeric identifier, or some other type of identifier.
  • the microcontroller 102 and sensor 103 may communicate over one or more I/O channels 1 15, which may comprise physical or wireless channels, or a combination of both.
  • the I/O channels 1 15 may comprise for example a serial communications link, or a universal serial bus (USB).
  • the communications module 105 comprises a first interface module 106 for interfacing with the microcontroller-sensor system 101 .
  • the first interface module 106 comprises a RFID reader.
  • the RFID reader 106 may communicate with the microcontroller 102 and/or the sensor 103, using RF communication links 1 16 and 1 17, respectively.
  • the RFID units 1 13 and 1 14 of the respective microcontroller 102 and one or more associated sensors 103 comprise passive RFID tags, which the RFID reader 106 of the communications module 105 can communicate with using the communication links 1 16, 1 17.
  • the communication module 105 can identify the microcontroller 102 and sensors 103 directly, i.e. by interrogating the passive RFID tags 1 13, 1 14.
  • the RFID unit 1 13 of the microcontroller 102 comprises a RFID reader while the RFID unit 1 14 of an associated sensor 103 comprises a passive RFID tag.
  • the microcontroller 102 can detect the sensors 103 it is attached to using its RFID reader 1 13 (i.e. that communicates with one or more passive RFID tags 1 14 mounted on one or more respective sensors 103), and report this to the communications module 105, for example via communication between the RFID reader 106 of the communications module 105 and the RFID reader 1 13 of the microcontroller
  • the communications module 105 may, in some examples, still have the option of communicating directly with the sensors 103 (whereby the RFID reader 106 of the communications module 105 interrogates the passive RFID tags 1 14 of the sensors
  • the communications module 105 also comprises a second interface module 107 for interfacing with one or more repository units 1 10. Communication between the second interface module 107 and the one or more repository units 1 10 may be over a long- range radio communications link 1 18, for example a cellular 3G or LTE communications link.
  • the one or more repository units 1 10 may in turn receive software update information or configuration information 1 19 from another node. For example, when a user submits new code on a repository unit 1 10, then there is an update operation. This may comprise, for example, committing new code in Subversion or GIT repositories. Subsequently, this can be used to trigger an update operation on a MSS, as will be described in greater detail below.
  • the communications module 105 comprises a third interface module 109 for communicating data with the microcontroller-sensor system 101.
  • Such data communication over signalling link 1 1 1 may comprise control and/or user plane signalling.
  • the communications module 105 is able to detect one or more microcontroller-sensor systems using the first interface module 106, communicate with one or more repository units via the second interface unit 107, for example to obtain configuration and/or update data for the one or more detected microcontroller-sensor systems, and communicate the obtained configuration and/or update data to the one or more microcontrollers using the third interface unit 109.
  • Figure 3 also shows the microcontroller 102 coupled to a power source, for example a battery, which in this example is also used to power the communications module via a power connection 120. It is noted, however, that the communications module 105 and microcontroller 102 may be powered from separate sources.
  • the communications module 105 comprises a mobile device which can be powered on site, and in such a case the communications module 105 can be used to bootstrap multiple MSSs.
  • a drone may be equipped with a cellular communications device, moving around in a large area (e.g. a forest or field). To save power, the drone can be controlled to turn on its communications module when it reaches the next MSS. The drone may be controlled to continuously patrol a certain route with waypoints between MSSs, and perform bootstrapping/update operations periodically.
  • the microcontroller 102 of the MSS 101 may comprise an application programming interface (API) that is configured to provide the following functionality: ⁇ INSTALL new microcontroller software, which accepts requests to install a new version of software for the microcontroller.
  • API application programming interface
  • a microcontroller comes pre-programmed with a basic set of functionality, and in order to support new functionality, the new software binary is uploaded and the microcontroller is instructed to reboot. Further details are provided in Figure 4 below.
  • UPDATE microcontroller software which accepts requests to update a version of software running on the microcontroller.
  • the update functionality may be different than the first install functionality in case the current execution state of the microcontroller needs to be saved in order to resume after the update takes effect. Further details are provided in Figure 5 below.
  • Such an API can be implemented, for example, using a full Transmission Control Protocol/Internet Protocol, TCP/IP, stack (e.g. using Hypertext Transport Protocol, HTTP, REST as the application layer of the stack).
  • the API can be exposed by the microcontroller 102 to other entities over similar I/O channels 1 15 as the sensors 103 (e.g. serial, USB, etc.) or by other means (e.g. wirelessly using Bluetooth or WiFi, etc.), depending on the capabilities of the microcontroller 102.
  • the communications module 105 via its second interface module 107, interfaces with one or more repository units 1 10.
  • a repository unit 1 10 may contain software for various MSS, microcontroller and sensor models. Since the one or more repository units 1 10 can be anywhere in the Internet and the MSSs 101 and communications module 105 deployed anywhere in an area, the communications module 105 may use, for example, long-range radio communication (e.g. including but not limited to 3G, LTE) for communicating with the one or more repository units 1 10 over the link 1 18.
  • long-range radio communication e.g. including but not limited to 3G, LTE
  • the communications module 105 interfaces with the microcontroller 102 in two ways.
  • the communications module 105 interfaces with the microcontroller 102 using RFID in order to receive identifier information, e.g. information about the microcontroller model as well as the sensor models it is connected to in the microcontroller-sensor system 101.
  • identifier information e.g. information about the microcontroller model as well as the sensor models it is connected to in the microcontroller-sensor system 101.
  • the RFID reader 106 of the communications module 105 is adapted, upon bootstrap of the system, to activate all passive RFID tags in the system, and collect all information on sensor-microcontroller identifiers they transmit. This process may be triggered by a "bootstrap trigger".
  • the bootstrap trigger can be automated, for example once the communications module 105 is connected to some source of power source (for example from the microcontroller 102 as shown in Figure 3, or an external power source), or the bootstrap signal can be manual, for example activated by a user pressing a bootstrap trigger input 121 (e.g. button) on the communications module 105.
  • the RFID reader 106 on the communications module 105 can be configured to remain active after the initial setup, for example for the purpose of detecting changes in hardware of the system (e.g. addition of a new MSS, or new sensor or microcontroller within an existing MSS).
  • the communications module 105 interfaces with the microcontroller 102 using communication over the communications link 1 1 1 via the third interface module 109.
  • such communication may involve installing or updating software in the microcontroller 102.
  • the communications module 105 can ask one or more repository units 1 10 for software to run on the microcontroller (based on the types of sensors and the model of the microcontroller).
  • the communications module 105 uses the INSTALL function of the API described above to install software on the microcontroller 102. This is described further in Figure 4 below.
  • the communications module 105 detects through the RFID interface that a change has occurred in the system setup (e.g. a new MSS, microcontroller or sensor has been added), then it instructs for new software from the one or more repository units 1 10 and subsequently uses the UPDATE function of the API described above to update the software on the microcontroller. This is described further in Figure 5 below.
  • a repository unit 1 10 receives notification of an update relating to a MSS, microcontroller or sensor, such as a software update for the code of a microcontroller, then the repository unity 1 10 notifies the communication module 105 about this update. Subsequently, the communications module 105 uses the INFORM function of the API described above to get the version of software currently running on the microcontroller, and performs a comparison with the software version received in the notification of the software repository. If the latter is a more recent version than the former, the communications module 105 issues an UPDATE request towards the microcontroller to update its software. This is described further in Figure 6 below.
  • Figure 4 shows an example of a signalling flow according to an embodiment, for example involving system bootstrapping and the INSTALL function noted above.
  • Figure 4 shows an example of the messages that may be transmitted between the communications module 105, a repository unit 1 10, the microcontroller 102 and sensors 103.
  • the communications module 105 seeks identifier information from the microcontroller 102 and sensor(s) 103. For example, the communications module 105 transmits a "Get Microcontroller Model” message 402 to the microcontroller 102, and the microcontroller 102 responds with its microcontroller identifier information 403, "MCJD". Likewise, the communications module 105 transmits a "Get Sensor Models" message 404 to the one or more sensors 103 (only one shown for clarity), and the sensors 103 respond with a list of sensor identifier information 405, "Nst[sensorlD]".
  • the information above is obtained via the first interface module 106 of the communications module 105, for example using RFID, NFC, Bluetooth, optical, or some other form of short-range radio communication.
  • the communications module 105 is then adapted to interface with one or more repository units 1 10 (for example using the second interface module 107 shown in Figures 2 and 3).
  • the communications module 105 sends a message 406 requesting software for the identified microcontroller and/or sensor(s), such message including the identifier information previously received at the communications module 105, e.g. a message "GET_Software[MC_ID, list[sensorlD]]".
  • one or more repository units 1 10 return a message 407 containing software relating to the microcontroller and/or sensor(s), for example a "Software_Binaries" message.
  • This message may comprise configuration software or firmware relating to the microcontroller and/or sensor(s).
  • the communications module 105 is then adapted to perform an INSTALL procedure as noted earlier, by sending an install message 408 to the microcontroller 102, for example by sending a "INSTALL[Software_Binaries]" message.
  • the microcontroller 102 may send an acknowledgement signal 409, confirming that the INSTALL message has been safely received, or that the installation procedure has been successful.
  • Figure 4 shows an example of how a microcontroller-sensor system can be configured using a communication module 105 following a bootstrap trigger, by installing software or firmware onto a microcontroller and/or sensors of a microcontroller-sensor system.
  • Figure 5 shows an example of a signalling flow according to another embodiment, for example where the communications module detects a change in a MSS setup, and involving an UPDATE function as noted above.
  • Figure 5 shows an example of the messages that may be transmitted between the communications module 105, a repository unit 1 10, the microcontroller 102 and sensors 103.
  • the communication module 105 may be configured to periodically perform a check operation 501 , to determine whether there have been any changes to the network, for example changes in hardware involving the addition of a new microcontroller-sensor system, or additional microcontrollers or sensors per se, in the vicinity of the communications module 105.
  • the communications module 105 seeks identifier information from one or more microcontrollers 102 and sensor 103. For example, the communications module 105 transmits a "Get Microcontroller Model" message 502 to one or more microcontrollers 102 (only one shown for clarity), and the microcontrollers 102 respond with their respective microcontroller identifier information 503, "MCJD".
  • this may involve the use of RFID or optical (or other means) for detecting identifier information relating to the microcontrollers.
  • this would automatically detect any microcontroller RFID tags that are within range of the RFID reader of the communication module 105.
  • the communications module 105 transmits a "Get Sensor Models" message 504 to the one or more sensors 103 (only one shown for clarity), and the sensors 103 respond with a list of sensor identifier information 505, "Nst[sensorlD]".
  • this would automatically detect any sensor RFID tags that are within range of the active RFID reader of the communication module 105.
  • the sensor identifier information may be obtained via an associated microcontroller, for example if a microcontroller is aware of this information.
  • steps 504 and 505 of Figure 5 may be omitted in such embodiments.
  • the communications module 105 then performs a comparison, step 506, to determine whether the list of detected microcontrollers and sensors is the same as a list previously generated from a previous iteration of this loop.
  • the communications module 105 may comprise a memory for storing information relating to microcontroller-sensor systems it is currently interfacing with.
  • the procedure 507 is performed. This is similar to that of Figure 4 above, whereby the communications module 105 is then adapted to interface with one or more repository units 1 10 (for example using the second interface module 107 shown in Figures 2 and 3).
  • the communications module 105 sends a message 508 requesting software for the identified microcontroller and/or sensor(s), such message including the identifier information previously received at the communications module 105, e.g. a message "GET_Software[MC_ID, list[sensorlD]]".
  • the communications module 105 may either request software for just newly detected MSSs, or for all MSSs currently detected in the setup (e.g. in order to obtain most up- to-date software for any existing MSSs).
  • one or more repository units 1 10 return a message 509 containing software relating to the microcontroller and/or sensor(s), for example a "Software_Binaries" message.
  • This message may comprise configuration software or firmware relating to the microcontroller and/or sensor(s).
  • the communications module 105 is then adapted to perform an UPDATE procedure as noted earlier, by sending an UPDATE message 510 to the microcontroller 102, for example by sending a "UPDATE[Software_Binaries]" message.
  • the microcontroller 102 may send an acknowledgement signal 51 1 , confirming that the UPDATE message has been safely received, or that the update procedure has been successful.
  • Figure 5 shows an example of how a communications module 105 can detect changes to MSS setup, and how the microcontroller-sensor systems can be configured using a communication module 105 following such a change.
  • Figure 6 shows an example of a signalling flow according to another embodiment, for example where the communications module is informed of an update from a repository unit, and involving an INFORM function as noted above.
  • Figure 6 shows an example of the messages that may be transmitted between the communications module 105, a repository unit 1 10, the microcontroller 102 and sensors 103.
  • a repository unit 1 10 sends an update message 601 to the communication module 105, e.g. a "Update in code [Lates /ersion]" message.
  • the communications module 105 is configured to send an INFORM request message 602 to a microcontroller 102 it is interfaced with, seeking information about the version of software currently running on the microcontroller 102.
  • the microcontroller 102 returns a message 603 informing the communications module about the version of software it currently has installed, e.g. a "lnstalled_version" message.
  • the communications module 105 then performs a check to determine whether the microcontroller has the latest version of software already installed. If so, no further action is required. If not, the procedure 606 is performed. This is similar to that of Figures 4 and 5 above, whereby the communications module 105 is then adapted to interface with one or more repository units 1 10 (for example using the second interface module 107 shown in Figures 2 and 3).
  • the communications module 105 sends a message 607 requesting software for the identified microcontroller and/or sensor(s), such message including the identifier information previously received at the communications module 105, e.g. a message "GET_Software[MC_ID, list[sensorlD]]".
  • the communications module 105 requests software where it has been determined in step 605 that a microcontroller is not currently running the most recent version of software.
  • a repository unit 1 10 returns a message 608 containing software relating to the microcontroller and/or sensor(s), for example a "Software_Binaries" message.
  • This message may comprise configuration software or firmware relating to the microcontroller and/or sensor(s).
  • the communications module 105 is then adapted to perform an UPDATE procedure as noted earlier, by sending an UPDATE message 609 to the microcontroller 102, for example by sending a "UPDATE[Software_Binaries]" message.
  • the microcontroller 102 may send an acknowledgement signal 610, confirming that the UPDATE message has been safely received, or that the update procedure has been successful.
  • Figure 6 shows an example of how a communications module 105 is informed of an update from a repository unit.
  • the communications module 105 may comprise a memory for storing information relating to microcontroller-sensor systems it is currently interfacing with, and the current versions of software installed in such microcontroller-sensor systems. In such embodiments the INFORM procedure of Figure 6 may be omitted if desired.
  • Figure 7 shows an example of a method in a communications module according to an embodiment, for interfacing between one or more repository units and one or more microcontroller-sensor systems.
  • the method comprises detecting one or more microcontroller-sensor systems in a vicinity of the communications module using a first interface module, step 701.
  • the method comprises communicating with one or more repository units using a second interface module to obtain configuration and/or update data for the one or more detected microcontroller-sensor systems, step 703.
  • the method further comprises communicating the obtained configuration and/or update data to the one or more microcontroller-sensor systems using a third interface module, step 705.
  • the step of detecting may comprise receiving identifier information from a microcontroller and/or one or more sensors associated with a microcontroller.
  • the method may comprise detecting the type of microcontroller and/or the type of one or more sensors associated with the microcontroller using the received identifier information.
  • the step of detecting may comprise communicating with the one or more microcontroller-sensor systems using short-range radio communication, or radio frequency identification, RFID, communication, or near field communication, NFC, or Bluetooth communication, in order to obtain the identifier information.
  • the step of detecting comprises controlling an RFID reader to communicate with one or more passive RFID tags located on one or more microcontrollers and/or associated sensors.
  • the step of detecting may comprise receiving the identifier information from an imaging unit for imaging visual identifier information, for example QR codes, on the one or more microcontroller-sensor systems.
  • the method may further comprise the step of receiving a trigger signal in response to a power-up of the communications module, or in response to an update message received from one or more repository units, or in response to a new microcontroller- sensor system being detected in the vicinity of the communications module, and performing the detecting step in response to receiving the trigger signal.
  • a microcontroller-sensor system for use with a communications module as described herein.
  • the microcontroller-sensor system comprises a microcontroller, at least one sensor associated with the microcontroller, and an electronic or visual tag for identifying the microcontroller and/or at least one sensor to the communications module.
  • FIG. 8 shows an example of a wireless network node 800 according to another embodiment, for interfacing between one or more repository units and one or more microcontroller-sensor systems.
  • the wireless network node 800 comprises a processor 801 and a memory 803, said memory 803 containing instructions executable by said processor 801.
  • the wireless network node 800 is operative to: detect one or more microcontroller-sensor systems in a vicinity of the communications module using a first interface module; communicate with one or more repository units using a second interface module to obtain configuration and/or update data for the one or more detected microcontroller-sensor systems; and communicating the obtained configuration and/or update data to the one or more microcontroller-sensor systems using a third interface module.
  • the first interface module is a type of interface module that is capable of obtaining identifier information relating to one or more MSSs without having specific knowledge of a particular type of communication protocol used by a MSS, e.g. by using a standardised RFID link, with the third interface module then being used to communicate user and/or control plane signalling with the MSS, once the type of MSS has been determined from the identifier information.
  • the embodiments can be deployed wirelessly in the field, which can be particularly advantageous for remote sensor deployments (for example in remote areas such as forests, fields, etc.), where wireline communication is impossible. This applies to lifecycle operations, i.e. bootstrapping, updating during operation and decommissioning.
  • the embodiments described above also have an advantage of enabling the functionality of a MSS to be repurposed during its lifetime.
  • Figures 9A to 9D provide examples of different applications of a communications module 105.
  • Figure 9A relates to an example whereby a communications module 105 is configured to interface between a single microcontroller-sensor system 101 and a plurality of repository units 1 10i to 1 10M.
  • the plurality of repository units 1 10i to 1 10M may contain software or firmware relating to a plurality of sensors (not shown) associated with the MSS 101 , and/or the microcontroller of the MSS 101.
  • the communications module 105 may comprise a second interface module 107 as described in the embodiments above. It is noted that, in such embodiments having two or more repository units, a second interface module 107 of the communications module 105 may comprise a single interface module which is capable of communicating with multiple repository units, or two or more separate interface modules for interfacing with two or more repository units.
  • Figure 9B relates to an example whereby a communications module 105 is configured to interface between a single microcontroller-sensor system 101 and a single repository unit 1 10, whereby the repository unit 1 10 contains software or firmware relating to the MSS 101 , including the microcontroller and/or one or more sensors of the MSS 101 .
  • Figure 9C relates to an example whereby a communications module 105 is configured to interface between a plurality of microcontroller-sensor systems (MMSs) 1011 to 101 N and a single repository unit 1 10, whereby the repository unit 1 10 contains software or firmware relating to the plurality of MSSs 1011 to 101 N, including the microcontrollers and/or one or more sensors of the MSSs 1011 to 101 N.
  • MMSs microcontroller-sensor systems
  • Figure 9D relates to an example whereby a communications module 105 is configured to interface between a plurality of microcontroller-sensor systems (MMSs) 1011 to 101 N and a plurality of repository units 1 10i to 1 10M, whereby the plurality of repository units 1 10i to 1 10M contain software or firmware relating to the plurality of MSSs 1011 to 101 N, including the microcontrollers and/or one or more sensors of the MSSs 1011 to 101 N.
  • MMSs microcontroller-sensor systems

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Health & Medical Sciences (AREA)
  • Arrangements For Transmission Of Measured Signals (AREA)

Abstract

Un module de communication (105) comprend un premier module d'interface (106) conçu pour réaliser une interface avec un ou plusieurs systèmes à capteur de microcontrôleur (MSS, "microcontroller-sensor system"), un MSS comprenant un microcontrôleur et au moins un capteur associé. Le module de communication (105) comprend un second module d'interface (107) conçu pour réaliser une interface avec une ou plusieurs unités de référentiel.
PCT/EP2016/071436 2016-09-12 2016-09-12 Module et procédé de communication WO2018046108A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/071436 WO2018046108A1 (fr) 2016-09-12 2016-09-12 Module et procédé de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2016/071436 WO2018046108A1 (fr) 2016-09-12 2016-09-12 Module et procédé de communication

Publications (1)

Publication Number Publication Date
WO2018046108A1 true WO2018046108A1 (fr) 2018-03-15

Family

ID=56920709

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2016/071436 WO2018046108A1 (fr) 2016-09-12 2016-09-12 Module et procédé de communication

Country Status (1)

Country Link
WO (1) WO2018046108A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080150698A1 (en) * 2006-12-26 2008-06-26 G2 Microsystems, Inc. Radio frequency identification tag with passive and active features
EP2741055A2 (fr) * 2012-12-07 2014-06-11 General Electric Company Partage des informations associées à des dispositifs de génération de puissance par l'intermédiaire d'un système de fichiers sur un réseau
WO2016054177A1 (fr) * 2014-09-30 2016-04-07 Tego, Inc. Systèmes et procédés de gestion d'informations rfid

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080150698A1 (en) * 2006-12-26 2008-06-26 G2 Microsystems, Inc. Radio frequency identification tag with passive and active features
EP2741055A2 (fr) * 2012-12-07 2014-06-11 General Electric Company Partage des informations associées à des dispositifs de génération de puissance par l'intermédiaire d'un système de fichiers sur un réseau
WO2016054177A1 (fr) * 2014-09-30 2016-04-07 Tego, Inc. Systèmes et procédés de gestion d'informations rfid

Similar Documents

Publication Publication Date Title
US9929906B2 (en) Data collection system having EIR terminal interface node
US10880404B2 (en) On-vehicle control device and on-vehicle control device information update system
US8677343B2 (en) Centrally coordinated firmware upgrade model across network for minimizing uptime loss and firmware compatibility
CN111886845B (zh) 在通信互连装置网络中执行空中下载（ota）升级的方法和装置
KR101845290B1 (ko) 장치 관리 명령을 통한 펌웨어 갱신 방법 및 장치
US20180198848A1 (en) Dynamic mesh system
KR101525811B1 (ko) 무선 센서 네트워크에서의 펌웨어 업그레이드를 위한 분산처리 시스템 및 그 방법
CN105389249B (zh) 异常日志生成配置方法及异常日志生成配置装置
CN112256294A (zh) 终端应用的部署方法、云平台、系统及存储介质
CN112661065A (zh) 用于物料搬运车辆网络的系统和方法
US20070236345A1 (en) Wireless sensor node executable code request facilitation method and apparatus
CN101854623B (zh) 一种m2m终端远程升级的系统和方法
CN105049502A (zh) 一种云端网络管理系统中设备软件更新的方法和装置
CN112733062A (zh) 一种物联应用管理系统及方法
EP3350962B1 (fr) Gestion de communication entre un dispositif m2m et un serveur m2m
US10085147B2 (en) Configuring network access parameters
CN104079425A (zh) 一种用于匹配设备的方法、装置和系统
WO2018046108A1 (fr) Module et procédé de communication
JP5966664B2 (ja) 位置情報管理システム、無線端末制御方法及び管理サーバ
EP2919415B1 (fr) Procédé, appareil et système d'indication en ligne
US20240323257A1 (en) System and method for tag-gateway communications
EP4231551A1 (fr) Système informatique et procédé de réglage
KR102685751B1 (ko) 클라우드 컴퓨팅 기반의 스마트 팩토리 시스템
KR20150019152A (ko) 펌웨어 관리 방법 및 장치
JP6334476B2 (ja) 通信システム

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: 16763825

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: 16763825

Country of ref document: EP

Kind code of ref document: A1