import java.util.*;

 

public class Solutions {

   public static int getGreater(int a, int b) {

      if(a > b) {

          return a;

      } else {

          return b;

      }

   }

   public static void main(String args[]) {

      Scanner sc = new Scanner(System.in);

      int a = sc.nextInt();

      int b = sc.nextInt();

      System.out.println(getGreater(a, b));

   }   

}

 

import java.util.*;

public class Solutions {

   public static void printSum(int n) {

       int sum = 0;

 

      for(int i=1; i<=n; i++) {

        if(i % 2 != 0) {

            sum = sum + i;

        }

      }

 

      System.out.println(sum);

   }

   public static void main(String args[]) {

      Scanner sc = new Scanner(System.in);

 

int n = sc.nextInt();

      printSum(n);

   }   

}

 

 

import java.util.*;

public class Solutions {

   public static void main(String args[]) {

      Scanner sc = new Scanner(System.in);

      int a = sc.nextInt();

      int b = sc.nextInt();

      int c = sc.nextInt();

 

      int average = (a + b + c) / 3;

      System.out.println(average);

   }   

}

 The oneM2M IoT Standardized Architecture In an effort to standardize the rapidly growing field of machine-to-machine (M2M) communications, the European Telecommunications Standards Institute (ETSI) created the M2M Technical Committee in 2008. The goal of this committee was to create a common architecture that would help accelerate the adoption of M2M applications and devices. Over time, the scope has expanded to include the Internet of Things. One of the greatest challenges in designing an IoT architecture is dealing with the heterogeneity of devices, software, and access methods. By developing a horizontal platform architecture, oneM2M is developing standards that allow interoperability at all levels of the IoT stack. The oneM2M architecture divides IoT functions into three major domains: the application layer, the services layer, and the network layer  Applications layer: The oneM2M architecture gives major attention to connectivity between devices and their applications. This domain includes the application-layer protocols and attempts to standardize northbound API definitions for interaction with business intelligence (BI) systems. Applications tend to be industry-specific and have their own sets of data models, and thus they are shown as vertical entities.  Services layer: This layer is shown as a horizontal framework across the vertical industry applications. At this layer, horizontal modules include the physical network that the IoT applications run on, the underlying management protocols, and the hardware. Examples include backhaul communications via cellular, MPLS networks, VPNs, and so on. Riding on top is the common services layer.  Network layer: This is the communication domain for the IoT devices and endpoints. It includes the devices themselves and the communications network that links them. Embodiments of this communications infrastructure include wireless mesh technologies, such as IEEE 802.15.4, and wireless point-to-multipoint systems, such as IEEE 801.11ah.

 Communications Network Layer - Once you have determined the influence of the smart object form factor over its transmission capabilities (transmission range, data volume and frequency, sensor density and mobility), you are ready to connect the object and communicate. Compute and network assets used in IoT can be very different from those in IT environments. The difference in the physical form factors between devices used by IT and OT is obvious even to the most casual of observers. What typically drives this is the physical environment in which the devices are deployed. What may not be as inherently obvious, however, is their operational differences. The operational differences must be understood in order to apply the correct handling to secure the target assets. Access Network Sublayer - There is a direct relationship between the IoT network technology you choose and the type of connectivity topology this technology allows. Each technology was designed with a certain number of use cases in mind (what to connect, where to connect, how much data to transport at what interval and over what distance). These use cases determined the frequency band that was expected to be most suitable, the frame structure matching the expected data pattern (packet size and communication intervals), and the possible topologies that these use cases illustrate. One key parameter determining the choice of access technology is the range between the smart object and the information collector. Figure 2-9 lists some access technologies you may encounter in the IoT world and the expected transmission distances.  Range estimates are grouped by category names that illustrate the environment or the vertical where data collection over that range is expected. Common groups are as follows: * PAN (personal area network): Scale of a few meters. This is the personal space around a person. A common wireless technology for this scale is Bluetooth. * HAN (home area network): Scale of a few tens of meters. At this scale, common wireless technologies for IoT include ZigBee and Bluetooth Low Energy (BLE). * NAN (neighborhood area network): Scale of a few hundreds of meters. The term NAN is often used to refer to a group of house units from which data is collected. * FAN (field area network): Scale of several tens of meters to several hundred meters. FAN typically refers to an outdoor area larger than a single group of house units. The FAN is often seen as “open space” (and therefore not secured and not controlled). * LAN (local area network): Scale of up to 100 m. This term is very common in networking, and it is therefore also commonly used in the IoT space when standard networking technologies (such as Ethernet or IEEE 802.11) are used. Similar ranges also do not mean similar topologies. Some technologies offer flexible connectivity structure to extend communication possibilities: Point-to-point topologies Point-to-multipoint

 Internet of Things (IoT) is an ecosystem of connected physical objects that are accessible through the Internet (formal definition). So, in simple terms IOT means anything that can be connected to internet and can controlled / monitored using internet from our smart devices or PCs. The “things” specified here can be anything from small tracking chips to actual smart cars on road all these can be categorized as IOT. All things that are connected to internet are assigned with ip to it so that it can be monitored uniquely using internet. The embedded systems and technology are the objects that help in realization of successful IOT. Major Components of IOT: Things or Device - These are fitted with sensors and actuators. Sensors collect data from the environment and give to gateway where as actuators perform the action (as directed after processing of data). Gateway - The sensors give data to Gateway and here some kind pre-processing of data is even done.It also acts as a level of security for the network and for the transmitted data. Cloud - The datas after being collected at is uploaded to cloud. Cloud in simple terms is basically a set of servers connected to internet 24*7. Analytics - The data after being received in the cloud processing is done . Various algorithms are applied here for proper analysis of data .(techniques like Machine Learning etc are even applied) User Interface - User end application where user can monitor or control the data.

 IoT is a technology transition in which devices will allow us to sense and control the physical world by making objects smarter and connecting them through an intelligent network.

 

Fibre Channel Architecture:-

➢ Connections in a SAN are accomplished using FC.
➢ Fibre Channel Protocol (FCP) is the implementation of serial SCSI-3 over an FC 
network. In the FCP architecture, all external and remote storage devices attached to the 
SAN appear as local devices to the host operating system.
➢ The key advantages of FCP are as follows:
➢ Sustained transmission bandwidth over long distances.
➢ Support for a larger number of addressable devices over a network.
➢ Theoretically, FC can support over 15 million device addresses on a network.
➢ Exhibits the characteristics of channel transport and provides speeds up to 8.5 
Gb/s (8 GFC).

Fibre Channel Protocol Stack
➢ It is easier to understand a communication protocol by viewing it as a structure of 
independent layers.
➢ FCP defines the communication protocol in five layers:FC-0 through FC-4 (except FC-3 
layer, which is not implemented).
➢ In a layered communication model, the peer layers on each node talk to each other 
through defined protocols.
➢ Fig 2.9 illustrates the fibre channel protocol stack.

➢ FC-4 Upper Layer Protocol
➢ FC-4 is the uppermost layer in the FCP stack.
➢ This layer defines the application interfaces and the way Upper Layer Protocols 
(ULPs) are mapped to the lower FC layers.
➢ The FC standard defines several protocols that can operate on the FC-4 layer (see 
Fig 2.9). Some of the protocols include SCSI, HIPPI Framing Protocol, Enterprise 
Storage Connectivity (ESCON), ATM, and IP.
➢ FC-2 Transport Layer
➢ The FC-2 is the transport layer that contains the payload, addresses of the source 
and destination ports, and link control information.
➢ The FC-2 layer provides Fibre Channel addressing, structure, and organization 
of data (frames,sequences, and exchanges). It also defines fabric services, 
classes of service,flow control, and routing.
➢ FC-1 Transmission Protocol
➢ This layer defines the transmission protocol that includes serial encoding and 
decoding rules, special characters used, and error control.
➢ At the transmitter node, an 8-bit character is encoded into a 10-bit transmissions 
character.
➢ This character is then transmitted to the receiver node.
➢ At the receiver node, the 10-bit character is passed to the FC-1 layer, which 
decodes the 10-bit character into the original 8-bit character.
➢ FC-0 Physical Interface
➢ FC-0 is the lowest layer in the FCP stack.
➢ This layer defines the physical interface, media, and transmission of raw bits.
➢ The FC-0 specification includes cables, connectors, and optical and electrical 
parameters for a variety of data rates.
➢ The FC transmission can use both electrical and optical media.

 

The FC architecture supports three basic interconnectivity options:

 

1) Point-To-point,

2) Arbitrated Loop (Fc-AL),

3) FC Switched Fabric

Point-to-Point

 

Point-to-point is the simplest FC configuration — two devices are connected directly to 

each other, as shown in Fig.

 

➢ This configuration provides a dedicated connection for data transmission between nodes.

➢ The point-to-point configuration offers limited connectivity, as only two devices can 

communicate with each other at a given time.

➢ It cannot be scaled to accommodate a large number of network devices. Standard DAS uses 

point to- point connectivity.

 

Fibre Channel Arbitrated Loop

➢ In the FC-AL configuration, devices are attached to a shared loop, as shown in Fig 2.5.

➢ FC-AL has the characteristics of a token ring topology and a physical star topology.

➢ In FC-AL, each device contends with other devices to perform I/O operations. Devices on 

the loop must “arbitrate” to gain control of the loop.

➢ At any given time, only one device can perform I/O operations on the loop.

➢ FC-AL implementations may also use hubs whereby the arbitrated loop is physically 

connected in a star topology.

The FC-AL configuration has the following limitations in terms of scalability:

➢ FC-AL shares the bandwidth in the loop.

➢ Only one device can perform I/O operations at a time. Because each device in a loop 

has to wait for its turn to process an I/O request, the speed of data transmission is 

low in an FC-AL topology.

➢FC-AL uses 8-bit addressing. It can support up to 127 devices on a loop.

➢Adding or removing a device results in loop re-initialization, which can 

cause a momentary pause in loop traffic.

 

Fibre Channel Switched Fabric(FC-SW)

➢ FC-SW provides dedicated data path and scalability.

➢ The addition and removal of a device does not affect the on-going traffic between other 

devices.

➢ FC-SW is referred to as Fabric connect.

➢ A Fabric is a logical space in which all nodes communicate with one another in a network. 

This virtual space can be created with a switch or a network of switches.

➢ Each switch in a fabric contains a a unique domain identifier, which is part of the fabric’s 

addressing scheme.

➢ In a switched fabric, the link between any two switches is called an Interswitch link (ISL). 

➢ ISLs enable switches to be connected together to form a single, larger fabric. 

➢ ISLs are used to transfer host-to-storage data and fabric management traffic from one switch to 

another. 

➢ By using ISLs, a switched fabric can be expanded to connect a large number of nodes.

➢ A Fabric may contain tiers.

➢ The number of tiers in a fabric is based on the number of switches between two points that 

are farthest from each other.

 

Virtual Storage Provisioning

➢ Virtual provisioning enables creating and presenting a LUN with more capacity than 

is physically allocated to it on the storage array.

➢ The LUN created using virtual provisioning is called a thin LUN to distinguish it 

from the traditional LUN.

➢ Thin LUNs do not require physical storage to be completely allocated to them at the 

time they are created and presented to a host.

➢ Physical storage is allocated to the host “on-demand” from a shared pool of physical 

capacity.

➢ A shared pool consists of physical disks.

➢ A shared pool in virtual provisioning is analogous to a RAID group, which is a 

collection of drives on which LUNs are created.

➢ Similar to a RAID group, a shared pool supports a single RAID protection level. 

However, unlike a RAID group, a shared pool might contain large numbers of drives.

➢ Shared pools can be homogeneous (containing a single drive type) or heterogeneous 

(containing mixed drive types, such as flash, FC, SAS, and SATA drives).

➢ Virtual provisioning enables more efficient allocation of storage to hosts.

➢ Virtual provisioning also enables oversubscription, where more capacity is presented 

to the hosts than is actually available on the storage array.

➢ Both shared pool and thin LUN can be expanded non-disruptively as the storage 

requirements of the hosts grow.

➢ Multiple shared pools can be created within a storage array, and a shared pool may be 

shared by multiple thin LUNs.