Scheme Design for Communication between Network Port and Serial Port Based on ARM

11 - FTP Software TCP/IP Internetworking Products

Chapter 11 - Managing Windows 2000 Network Services Fast Track

Early data networks were based on point-to-point or multipoint topologies. They were often of a star structure with a central processing unit (CPU) at the star's hub. Terminals in this network were “dumb” terminals and relied on the CPU's processing power for nearly all network activity. When the personal computer (PC) gained wide acceptance, distributed processing became the rule. As a result, data networks and data networking became much more complex. We now see complex multiple star, mesh, and tree like networks where many of the nodes have multiple inlets and outlets. Data rates were based on the limitations of the analog network. In the period of the 2nd edition of this book, this roughly equated to 9600 bps. Today, it is common to have 56-kbps access lines to a larger network where the basic channel data rate is 64 kbps. We can bring together these basic building blocks of 64 kbps to form aggregate channels of 128, 256, and 384 kbps up to 1.536 Mbps or 1.984 Mbps. Data protocols instilled order out of contentious chaos in data network operation. These protocols, applying to wide area networks (WANs), are the principal thrust of the chapter. Most are based on shipping user data in packets or frames. We discuss the transport of user data in cells in Chapter 28. Most packet networks are based on CCITT Rec. X.25. If we widen the definition of packet networks to include the transmission control protocol/internet protocol (TCP/IP), certainly X.25 will have a competitor. Both TCP/IP and X.25 have a comparatively high latency (latency is the time it takes from initiation to completion of a data transaction). Frame relay was introduced in the same period. This is a comparatively low latency system. This section provides design data and brief descriptions of wide area data networking as a whole with hypothetical reference circuits, the archetypical data link layer protocol, high-level data link control (HDLC), X.25 and its companion, link access protocol B-layer (LAPB), TCP/IP family of protocols, frame relay family of protocols, and a brief description of SMDS (switched multimegabit data service). Variants of LAPD are discussed in the frame relay section of this chapter. Keywords: enterprise networks; universal application; high-level data-link control; packet-switched; virtual connections; transmission control protocol; internet protocol; ISO transport protocol; frame relay; switched multimegabit data service; internetworking; ITU-T rec X.75; data network management

The transmission of huge amounts of data generated from various sensors is the basis and prerequisite for the analysis and prediction of the marine ecosystem. The special geographical conditions of the ocean determine that its data transmission is different from the common terrestrial data transmission. In this study, a marine environmental monitoring network architecture is proposed to collect environmental data from marine ecosystems using a heterogeneous network constructed by a multi-hop network and a satellite network. Considering the characteristics of satellite networks, such as high bandwidth delay product (BDP), long latency and high bit error rate, this work proposes a transmission scheme that improves the transmission performance of Transmission Control Protocol/Internet Protocol (TCP/IP)-based Internet networks over satellite networks. The improved scheme increases the monitoring data transmission rate, distinguishes between random data loss and congested data loss, rationalizes the threshold in fast recovery, and improves the overall transmission performance of the marine environmental monitoring network. The experimental results show that the proposed scheme can greatly improve the transmission performance of the monitoring network compared with traditional transmission protocols. The network model proposed in this study makes full use of current advanced network technologies, including multi-hop networks, wireless sensor networks, and satellite networks to expand the monitoring area at sea. This study provides a useful reference for the network model and data transmission for ocean monitoring.

Early data networks were based on point‐to‐point or multipoint topologies. They were often of a star structure with a central processing unit (CPU) at the star's hub. Terminals in this network were “dumb” terminals and relied on the CPU's processing power for nearly all network activity.When the personal computer (PC) gained wide acceptance, distributed processing became the rule. As a result, data networks and data networking became much more complex. We now see complex multiple star, mesh, and tree like networks where many of the nodes have multiple inlets and outlets.Data rates were based on the limitations of the analog network. In the period of the 2nd edition of this book, this roughly equated to 9600 bps. Today, it is common to have 56‐kbps access lines to a larger network where the basic channel data rate is 64 kbps. We can bring together these basic building blocks of 64 kbps to form aggregate channels of 128, 256, and 384 kbps up to 1.536 Mbps or 1.984 Mbps.Data protocols instilled order out of contentious chaos in data network operation. These protocols, applying to wide area networks (WANs), are the principal thrust of the chapter. Most are based on shipping user data in packets or frames. We discuss the transport of user data in cells in Chapter 28.Most packet networks are based on CCITT Rec.X.25. If we widen the definition of packet networks to include the transmission control protocol/internet protocol (TCP/IP), certainly X.25 will have a competitor. Both TCP/IP and X.25 have a comparatively high latency (latencyis the time it takes from initiation to completion of a data transaction). Frame relay was introduced in the same period. This is a comparatively low latency system.This section provides design data and brief descriptions of wide area data networking as a whole with hypothetical reference circuits, the archetypical data link layer protocol, high‐level data link control (HDLC), X.25 and its companion, link access protocol B‐layer (LAPB), TCP/IP family of protocols, frame relay family of protocols, and a brief description of SMDS (switched multimegabit data service). Variants of LAPD are discussed in the frame relay section of this chapter.

In this paper, Transmission Control Protocol/Internet Protocol (TCP/IP) over Stream Control Transmission Protocol (SCTP)/IP parallel transmission system is proposed to realize large TCP/IP throughput. The proposed system enables SCTP/IP connection between switches by protocol stacking. The proposed system is implemented on a software switch to evaluate its performance. The evaluation result indicates that proposed system can achieve 90% throughput compared with serial transmission when the delay difference among parallel routes is 20msec.

Many current implementations of protocols such as the Transmission Control Protocol/Internet Protocol (TCP/IP) are inefficient because data are often accessed more frequently than necessary. Three techniques that reduce the need for memory bandwidth are proposed. The techniques are copy-on-write, page remapping, and single-copy. Afterburner, a network-independent card that provides the services that are necessary for a single-copy protocol stack, is described. The card has 1 MByte of local buffers and provides a simple interface to a variety of network link adapters, including HIPPI and asynchronous transfer mode (ATM). Afterburner can support transfers to and from the link adapter card at rates up to 1 Gbit/s. An implementation of TCP/IP that uses the features provided by Afterburner to reduce the movement of data to a single copy is discussed. Measurements of the end-to-end performance of Afterburner and the single-copy implementation of TCP/IP are presented.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

The authors describe a connection-oriented transport-level protocol (local network transport protocol, LNTP) specifically designed for use on LANs (local area networks). The fundamental philosophy in the design of LNTP is simplicity. Features irrelevant to the LAN environment are not included, resulting in a simpler and more efficient protocol. LNTP uses a simple but effective two-region flow control mechanism which is activated only when the traffic intensity exceeds some value. This eliminates control packets during normal operation and increases concurrency between sender and receiver. LNTP runs under 4.2 BSD UNIX in place of TCP/IP (transmission control protocol/internet protocol). Detailed comparisons between LNTP and TCP/IP show that LNTP is several times faster, although end-to-end throughput rates are only 30% faster because of the overhead attributed to Ethernet and UNIX layers. However, the reduced CPU cycles as well as the increased network throughput indicate that LNTP is a viable replacement for TCP/IP. >

In previous chapters, the local applications and services of UNIX in individual computers have been introduced. This chapter will present the remote and network functions and services of UNIX in servers and workstations. After explanation of general concepts about the Internet and computer networking, Transmission Control Protocol/Internet Protocol (TCP/IP) suit will be presented, and contents associated with layers of TCP/IP model from down to up will be discussed. Finally, we will explain how to use some commands in the application layer of the TCP/IP model, such as telnet, ping, ftp, etc.

At the same time, technological and technical development of telecommunication networks enables implementation of various solutions in order to significantly improve PS monitoring and management system. Each element of the PS can be monitored to a greater or lesser extent, and management functions must be enabled for certain elements. Transfer of information from and to PS elements should be fast, reliable and protected. The final goal is to realize a fully automated process of keeping values of the system and individual elements of the system parameters within the given, previously defined, limits. This paper presents design concept of the telecommunication network for the entire PS which contains electrical energy sources, transmission capacities, substations and consumers. The hardware part of the network consists components implemented on the central locations, primary and redundant links, as well as network devices in PS nodes and at consumers. Monitoring and management of the network is carried out within the network management system (NMS), while software configurations of the network devices are such that they enable implementation of best-practice solutions in the data transmission and protection. The infrastructure for transmission of information between PS elements and NMS is defined by the the Transmission Control Protocol/Internet Protocol (TCP/IP) architecture and IEC 61850 standard. Data exchange between distributed and central locations, as well as between PS nodes and central locations is done using the Internet of Things (IoT) technology on the distributed locations and in the PS nodes or by using directly communication between devices at distributed locations and in the PS nodes and central locations if hardware configuration of that devices includes network interface card (NIC).

Chapter 2 - Microsoft TCP/IP 2000

Chapter 3 - The Internet and TCP/IP

Chapter 3 - MCSA/MCSE 70-291: The Dynamic Host Configuration Protocol

Significant progress has been made over the last decades in understanding the physiological and neural bases of cognitive processes and behavior. The advent of new and improved sensors enables monitoring the human body and brain activity in natural environments, with cost-effective, mobile and wearable form factor systems. As neuroimaging and brain sensing technologies are further developed, there's an expanding interest for using multiple systems concurrently on i) the same brain: multimodal/hybrid measurements for better identification of neurophysiological markers, and ii) multiple brains: hyperscanning for novel investigations of brain functions during social interactions. Particularly for functional neuroimaging, such as Functional Near Infrared Spectroscopy (fNIRS) and Electroencephalography (EEG), precise time synchronization of experimental events with acquired datasets is necessary for proper analysis and interpretation of results. However, there are currently no standards for interoperability and neuroimaging systems have many different designs and interfaces. Furthermore, it is often cumbersome to come up with a custom solution to each new research setup based on the devices involved. The original NeuroHub, a plug-and-play time synchronization device developed at Drexel University, attempted to alleviate some of the complications associated with custom setups and time synchronization. The original NeuroHub relayed any incoming signal to one of its four serial ports, TTL port, and parallel port, to all other ports on the device and can be connected to multiple sending/listening devices or computers. Although one or more of these legacy ports are present in various neuroimaging systems, modern computing systems require more sophisticated alternatives. This thesis proposes a solution and improvement to the original NeuroHub, by incorporating time synchronization over a network as an information transfer layer. The network solution enables more flexible experimental configurations and expands the compatible plug-and-play system range. Moreover, this new approach eliminates the need for multiple wires, while still being able to service large number of clients. The new NeuroHub is also able to directly interface with typical RS-232 serial ports and offers the best of both worlds - ability to interface with network and legacy hardware ports for complete customizability, flexibility and backward compatibility. The new NeuroHub network module consists of a Raspberry Pi Model 1B fitted with a serial port add-on board. The device transmits any event markers received from either networked or serial ports and relays them to the other opened ports. Verification testing confirmed that the device transmits with 100% accuracy and the latency to send a byte from one computer to the other via the network module was minimal, ranging from sub-millisecond speeds to 7 ms depending on the use of serial ports, baud-rate, and configuration order. The new NeuroHub network module was tested in Brain Compute Interface (BCI) setups using OpenViBE as a stimulus presenter and EEG data recording, with COBI Studio as the fNIRS data recording software to receive markers all through NeuroHub. This simple use case demonstrates the utility of the new NeuroHub for simplification of complex functional neuroimaging, neuroergonomics and BCI research experimental setups.

Given the current expansion of cloud computing, the expected advent of the Internet of Things, and the requirements of future fifth‐generation network infrastructures, significantly larger pools of computational and storage resources will soon be required. This emphasizes the need for more scalable data centers that are capable of providing such an amount of resources in a cost‐effective way. A quick look into today's commercial data centers shows that they tend to rely on variations of well‐defined leaf‐spine/Clos data center network (DCN) topologies, offering low latency, ultrahigh bisectional bandwidth, and enhanced reliability against concurrent failures. However, DCNs are typically restricted by the use of the Transmission Control Protocol/Internet Protocol (TCP/IP) suite, thus suffering limited routing scalability. In this work, we study the benefits that replacing TCP/IP with the recursive internetwork architecture (RINA) can bring into commercial DCNs, focusing on forwarding and routing scalability. We quantitatively evaluate the benefits that RINA solutions can yield against those based on TCP/IP and highlight how, by deploying RINA, topological routing solutions can improve even more the efficiency of the network. To this goal, we propose a rule‐and‐exception forwarding policy tailored to the characteristics of several DCN variants, enabling fast forwarding decisions with merely neighbors' information. Upon failures, few exceptions are necessary, whose computation can also profit from the known topology. Extensive numerical results show that the proposed policy requirements depend mainly on the number of neighbors and concurrent failures in the DCN rather than its size, dramatically reducing the amount of forwarding and routing information stored at DCN nodes.