I first heard the word Ubiquitous society in the early 21st century. It was a time when my interest in programming of network communication was increasing day by day, and at that time I just vaguely fantasized that it would be interesting to link various electric equipments. It was a time when my interest in programming of network communication was increasing day by day, and at that time I just vaguely fantasized that it would be interesting if various electric equipments were linked. And that fantasy gradually became more interesting to develop a program that various electric equipments are linked. Since then, I have repeated the develop a program and re-develop. I thought about new linking of various electric equipments, not to mention whether the style of programming suits my preference. Oh, by the way, nowadays it's not called Ubiquitous society but IoT.

IoT are no longer a concept, but a job. Various electric equipments with a communication function as standard equipment are also appearing one after another. The software development for that control are also evolving. How do you proceed with the development of software development? How do you consider communication level in the software development? If you try to make a prototype in the process, how do you make a prototype of programming? Do you use script language to develop a prototype of programming? In some cases, the program may be diverted from the systems provided, or the sample program from Internet articles and books may be diverted to make prototypes. What do you do when you get undesired results from a prototype program? Do you re-develop a prototype of programming? The amount of re-develop a prototype of programming will gradually increase. The diverted program also have unique codes, and it is troublesome to re-development them one by one for a prototype of programming. You would have wanted to develop a prototype of programming easier. How do you do the subsequent testing of software design and implementation? You may come across a situation where you have a bug and you should have tried it. If you think about the hypotheses in your head as much as possible before proceeding to designing of software, doing implementation of programming, and testing, it's best.

The Neth Communication Performer(*1) is a prototype communication tool packaging interfaces of the TCP/IP protocols. The TCP/IP protocols is an IETF communication standard such as HTTP or FTP, etc. For examining the telecommunication level of your favorite electric equipments, for examining the control level from your favorite application, we will create a scenario of your favorite interfaces of the TCP/IP protocols and support a simple prototype of programming.

(*1) Neth is a coined word that combines net of network, net of internet, and author's initial.

When a certain signal is sent to your favorite application by a certain sensor, notify a specified console, send an email to a person in charge who are at out, turn on the patorite on-site, and so on. It may be easy to use script language to develop a prototype of programming. However, when you have to send a certain signal to another system, you may be able to consider whether to send the signal by telecommunication socket of TCP or UDP. Also, if you try to switch the notification to a console terminal to web server system, the process of consideration will change from moment to moment, such as whether to have the signal send by GET method of HTTP protocol or POST method of HTTP protocol. By the way, do you know the breadboard used for making electronic circuit prototypes? Prototyping with the Neth Communication Performer is similar to the process of making a prototype while setting electronic parts such as resistor, capacitor, and diode in a combination that suits your wishes in breadboard. In other words, you can proceed with the trial production of telecommunication level using HTTP, SMTP, FTP, etc. while making a scenario.

(*2) Processing may be restricted or restricted by prohibited items in protocol, items that are generally vulnerability, and legal restrictions of each country. Also, some processes may not be provided by this tool.

The Neth Communication Performer mainly consists of the Neth Scenario function and interfaces of the TCP/IP protocols function. The concept is a star-shaped structure in which the interfaces of TCP/IP protocols are connected to radial nodes centered on the Neth Scenario function.

The main functions are as follows.

                                     ------------
                                     |Your       |
                                     |favorite   |
                                     |application|
                                     ------------
                                           A
                                           |Control
        ---Neth Communication Performer----------------------------------------
        |                                  |                                  |
 -------|  --------------                  |                  --------------  |-------
 |     ||  |    FTP     |<-----+           |           +----->|    File    |  ||     |
 |     |<->| (with TLS) |      |           |           |      | read/write |<->| *F  |
 |     ||  --------------      |           |           |      --------------  |-------
 |     ||  --------------      |           |           |      --------------  |-------
 |     ||  |    HTTP    |<--+  |           |           |  +-->| SerialComm |  ||     |
 |     |<->| (with TLS) |   |  |           V           |  |   |   RS-232C  |<->|     |
 |     ||  --------------   |  |     -------------     |  |   --------------  ||     |
 |     ||  --------------   |  +---->|           |<----+  |   --------------  || *E  |
 | *I  ||  |    SMTP    |   +------->| The Neth  |<-------+   |    USB     |  ||     |
 |     |<->| MIME/SMIME |<---------->| Scenario  |<---------->|General I/F |<->|     |
 |     ||  --------------   +------->| Function  |<-------+   --------------  |-------
 |     ||  --------------   |  +---->|           |<----+  |   --------------  |-------
 |     ||  |    POP3    |   |  |     -------------     |  |   | TCP Client |  ||     |
 |     |<->| MIME/SMIME |<--+  |                       |  +-->| (with TLS) |<->|     |
 |     ||  --------------      |                       |      --------------  ||     |
 |     ||  --------------      |                       |      --------------  || *I  |
 |     ||  |    UDP     |      |                       |      | TCP Server |  ||     |
 |     |<->|            |<-----+                       +----->| (with TLS) |<->|     |
 -------|  --------------                                     --------------  |-------
        |                                                                     |
        -----------------------------------------------------------------------

   (*I) Internet or intranet.
   (*E) Your favorite electric equipments.
   (*F) Your favorite files.

          

• The Neth Scenario function consists of a scenario that describes the record, the cooperation between the records, and the program that operates the scenario, when the record consisting of information -- depending on the protocol, it may be called header, body, and contents -- of the sender and the recipient on the telecommunication are used as the unit. Along with, the following the interfaces of TCP/IP protocols will give an operation opportunity. In addition, the information in the record are optionally transferred from the recipient to the sender according to the protoclos.
• The interfaces of TCP/IP protocols consists of based on the IETF communication convention (*3) such as FTP, HTTP, SMTP, POP3, TCP Socket Server, TCP Socket Client, UDP Socket, TLS, MIME, and MAC, and a general interface programming such as RS232C, USB of General I/F type, and File I/O. Various telecommunications and reading and writing files will be carried out by giving an operation opportunity from the above the Neth Scenario function.

(*3) I try to develop a implementation as a compliant presentation.

• Check the request and response

  If you attach your favorite application to this tool, you can check the request and response for a pre-determined the partners of telecommunication and the electric equipments.

• Send and receive messages

  You can deliver messages made from your favorite application to the recipient, or you can send a standard message to the recipient when you receive a messages from a pre-determined recipient or signals from a pre-determined electric equipments. I can do it.

• Send and receive a files

  You can deliver files made from your favorite application to the recipient, or you can send a pre-prepared file to the recipient when you receive a message from a pre-determined recipient or signals from a pre-determined electric equipments. I can do it.

• Send and receive a mails

  You can deliver mails made from your favorite application to the recipient, or you can send a pre-prepared mail to the recipient when you receive a message from a pre-determined recipient or signals from a pre-determined electric equipments. I can do it.

• link a web server

  You can update and refer pre-prepared contents on web server when you receive a message from a pre-determined recipient or signals from a pre-determined electric equipments. I can do it.

• Communicate with electric equipments

  You can send signals to a pre-determined electric equipments when you receive a message from a pre-determined recipient or signals from a pre-determined electric equipments. I can do it.

• Read and write a files

  You can record messages in a file or browse the contents of the file at that time, When you receive it from a pre-determined recipient, or signals from a pre-determined electric equipments.

• Encrypt / decrypt and communicate

  If you want to ensure the confidentiality of the messages and the contents, you can make it using the TLS.

• Electronic signature

  If you want to ensure the integrity and authenticity of the messages and the contents, you can make it using the HMAC.