China
Africa
Explore chapters and articles related to this topic
Engineered to Be Secure
Published in Larry B. Rainey, Mo Jamshidi, Engineering Emergence, 2018
These interdependent systems were not typically designed to address the ways in which they are expected to function today. The requirements were assembled independently, and each was built and fielded independently. Standard communication protocols such as File Transfer Protocol (FTP) and Transmission Control Protocol/Internet Protocol (TCP/IP) were adopted to move data from one system to another. Data encryption was an option in these communications but not a requirement. Variations in choices for security controls and differences in implementation options have provided opportunities for various type of security failures. The likelihood of failure increases when assumptions and decisions within one system are inconsistent with those of another. Good security for each component system does not guarantee good security for the composition of a system of systems.
Internetworking
Published in Paul W. Ross, The Handbook of Software for Engineers and Scientists, 2018
James Griffioen, J. Mark Pullen, Satish Chaliki
The TCP/IP protocol suite is a large set of communication and routing protocol standards that dictate how computers communicate. Although the TCP/IP protocol suite consists of many different protocols, the entire suite of protocol standards is typically referred to by the suite’s two primary protocol standards: the TCP protocol and the IP protocol. The IP protocol defines a logical or virtual network and achieves the goal of internetworking by allowing machines on different networks to communicate. The TCP protocol uses the IP protocol to transfer messages between machines. In addition, TCP provides features such as reliability and flow control that increase the scalability of communication to large networks consisting of thousands of independent networks that span large geographical areas. The TCP/IP protocol suite has been thoroughly tested, runs across almost any underlying hardware network architecture, and can be used to connect as many networks as one will ever want to connect. Many corporations have now adopted TCP/IP as the standard for their corporate networks. Consequently, new TCP/IP internets are being created daily. Some of these private internets are very large and span large geographical distances.
The Basics of Professional Networked Media
Published in Al Kovalick, Video Systems in an IT Environment, 2013
So which of the methods in Table 2.4 is the best? Well, the answer depends on your needs. FTP/TCP works quite well for short hops (roundtrip delay < than 20 Ms) within a campus environment. Very large FTP/TCP throughputs on the order of 350 Mbps and greater may be achieved over Ethernet-based LANs. FTP is the de facto standard for file transfer, and most equipment vendors support it. For wide area file distribution, FEC methods work very well and have wide industry acceptance. The proven fact that non-TCP transport layers can deliver files up to 100 faster is a huge impetus to use TCP alternatives such as UDP coupled with a powerful FEC (or with negative acknowledgments) or WAN accelerators.
Cardinal: A Lower-Length-Scale Multiphysics Simulator for Pebble-Bed Reactors
Published in Nuclear Technology, 2021
Elia Merzari, Haomin Yuan, Misun Min, Dillon Shaver, Ronald Rahaman, Patrick Shriwise, Paul Romano, Alberto Talamo, Yu-Hsiang Lan, Derek Gaston, Richard Martineau, Paul Fischer, Yassin Hassan
While MultiApp creates trees of executing applications, transfers are needed to move data between them. Transfers move data only vertically, up and down the hierarchy of applications. Many different types of transfers exist, including interpolation projection, evaluation, data copy, post-processor transfer, and scalar variable transfer. Consistent data transfers between dissimilar applications pose challenges for massively parallel code execution. To address this issue, the MWA system utilizes an ExternalMesh that is created to be compatible with the third-party application. Fields/values can then be easily moved to the ExternalProblem that uses the ExternalMesh. Built-in MOOSE transfers can communicate values with any other MOOSE/non-MOOSE application in the MultiApp hierarchy. Examples of data that can be transferred include fields, reduced values (average, minimum, maximum, etc.), and parameters. A schematic describing the solution transfer is shown in Fig. 3.
Application of the Internet of Things in the textile industry
Published in Textile Progress, 2019
Hitesh Manglani, George L. Hodge, William Oxenham
Using information available in the literature [39–42], application protocols are compared in Table 2. Each of the standards is divided into 4 categories: usage case; how it transports data; mechanism of data request and response; and finally, the mechanism to broadcast data. Prior to the comparison, it is helpful to appreciate HTTP REST, which has existed for a long time now and is quite well-established. The World Wide Web is based on the Hyper Text Transfer Protocol (HTTP). HTTP is a way to communicate data and file transfer. It is similar to hypertext documents, which include hyperlinks to other resources that the user can easily access. In a client-server model, HTTP functions as request-response protocol. For example, our web browsers are the client, and a computer hosting a website acts as a server. When a web browser submits an HTTP request to a server, the servers, in turn, respond with HTML files and other data.
Wireless Transmission and Logging of Measurement Data Through Cellular Networks
Published in NCSLI Measure, 2018
Harsshit Agrawaal, J. E. Thompson
The World Wide Web has been using HTTP (hypertext transfer protocol) for information transfer since 1990, and the version of the protocol is referred to as “HTTP/1.1”. The protocol is generally used for response and request data handling. It is a set of open-ended headers and methods that indicates the purpose of a request. A request is sent by a client to a server in the form of a method (HEAD, GET, POST, PUT, DELETE, etc.) followed by URI (uniform resource identifier), protocol version, request modifier, and client information. The GET method token was used in the code for this article for request, followed by the URI. The transfer of the resources happens using TCP (transmission control protocol). TCP manages the connection between the client and server. The GET method was chosen over POST method since the information content was not sensitive, but the code was tested for the POST and PUT methods also. HTTP request was used over TCP connection to send packets of information from client to server.