Professional Documents
Culture Documents
ABSTRACT
Cloud communications and cloud-based computing (here referring to the different types of services and applications being delivered in the internet cloud, and the fact that, in many cases, the devices used to access these services and applications do not require any special applications) are seemingly on a steep growth curve. With the need to reduce costs, the explosion of communications capabilities, and the increasing demand for mobile access to services, the service delivery move to the cloud enables faster growth and improved management and scalability. Cloud provides data independency and remote desktop applications. In the paper Infrastructure as a service (IAAS), Software as a Service (SAAS) and implementing the new concept of Communication as a Service (CAAS) in the cloud is explained. Paper contains the concept of client server architecture where the database of the client is stored on the server and the client would get the available software as a service. At the client side, the client can access the cloud server with browser via Internet with proper Authentication thereby performing different tasks In the new concept of Communication as a service the client can send email, chat with their friends, send texts and voice over internet protocol (VoIP). Communications as a Service (CaaS) is an outsourced enterprise communications solution that can be leased from a single vendor. Such communications can include voice over IP (VoIP or Internet telephony), instant messaging (IM), collaboration and videoconference applications using fixed and mobile devices. CaaS has evolved along the same lines as Software as a Service (SaaS).
150
Gurudatt Kulkarni, Maheshchandra Jadhav , Sadanand Bhuse, Hemant Bankar & Autade Sushma
151
Platform as a Service This layer refers to software and product development tools (e.g. application servers, database servers, portal servers, middleware, etc) which clients purchase so they can build and deploy their own applications, thus providing a much increased flexibility and control to the consumer. However, there may sometimes be a certain amount of dependence upon the infrastructures and platform providers. The services, here, are intended to support the software services top layer of the pyramid. The customers are looking to buy time and cost savings in deploying their applications. Typical offerings include runtime environment for application code, Cloud Services, Compute power, storage, and networking infrastructure. This level of services may be regarded as a developer level layer. The pricing structure is often along the lines of: Compute usage per hour; data transfer per GB; IO requests per million; storage per GB; data storage requests per thousand. All charges are per each billing period. Google App Engine, Heroku, Mosso and Engine Yard are examples of PaaS products and providers.
Infrastructure as a Service[5] This layer is essentially hardware (e.g. visualized servers, storage, network devices, etc) and hardware services to enable Cloud Platforms and Applications to operate. These services support the software services top layer of the pyramid. Customers get full control over server infrastructure and that sometimes comes with a price premium. Here, customers are looking to buy computing, without making upfront investment. Since, the infrastructure is offered on a pay-for what-you-use basis, it is sometimes referred to as utility computing, as there is similarity with the provision and use of services such as electricity and gas. The pricing structure is often similar to the provision for PaaS. Amazon EC2, IBM BlueHouse, VMWare, GoGrid, RightScale and Linode are some of the IaaS products and providers.
Communication-as-a-Service[6] The heart of the project lies in the communication as a service, where the user on the cloud can directly communicate with the other user. The user can even communicate with other people from the cloud via E-mails, Texts, Voice and Video Calls, chat box etc. This facility is developed from the point of view of the user. It helps the user to share their thoughts with other people, without logging in the other website or service providers. Thus from the cloud website alone the user can have the multiple options to communicate with the other users. The communication mode would be anonymous and authenticated. The API of the email clients and chat rooms would be provided for the communication. This project is mainly built up for the educational use so according to the criteria, facilities would be provided. The APIs are build on the java platform with the object oriented concepts and are the part of SAAS. The chat application is developed on the basis of the concept of Remote method invocation (RMI) and Ajax.
152
Gurudatt Kulkarni, Maheshchandra Jadhav , Sadanand Bhuse, Hemant Bankar & Autade Sushma
agreement (SLA). A CaaS model allows a CaaS providers business customers to selectively deploy communications features and services throughout their company on a pay-as-you-go basis for service(s) used. CaaS is designed on a utilitylike pricing model that provides users with comprehensive, flexible, and (usually) simple-to-understand service plans. According to Gartner, the CaaS market is expected to total $2.3 billion in 2011, representing a compound annual growth rate of more than 105% for the period. CaaS service offerings are often bundled and may include integrated access to traditional voice (or VoIP) and data, advanced unified communications functionality such as video calling, web collaboration, chat, real time presence and unified messaging, a handset, local and long-distance voice services, voice mail, advanced calling features (such as caller ID, three way and conference calling, etc.) and advanced PBX functionality. A CaaS solution includes redundant switching, network, POP and circuit diversity, customer premises equipment redundancy, and WAN fail-over that specifically addresses the needs of their customers. All VoIP transport components are located in geographically diverse, secure data centers for high availability and survivability. CaaS service offerings are often bundled and may include integrated access to traditional voice (or VoIP) and data, advanced unified communications functionality such as video calling, web collaboration, chat, real time presence and unified messaging, a handset, local and long-distance voice services, voice mail, advanced calling features (such as caller ID, three way and conference calling, etc.) and advanced PBX functionality. A CaaS solution includes redundant switching, network, POP and circuit diversity, customer premises equipment redundancy, and WAN fail-over that specifically addresses the needs of their customers. All VoIP transport components are located in geographically diverse, secure data centers for high availability and survivability.
CAAS ARCHITECTURE
CaaS (Communications as a Service) is beginning to flourish. As companies evaluate the cost, time, and flexibility advantages, CaaS becomes a desirable tool businesses can use to quickly respond to changing markets. A closer look at CaaS reveals that proper CaaS deployments are built upon the same basic principles used by good premise based implementations. The primary determining factors for selecting a CaaS methodology are: Initial cost Recurring cost Functionality Connectivity
153
Security Administration Survivability Based upon these factors, a variety of CaaS solutions have been developed. As you would expect, each has
strengths and weaknesses, largely determined by the software, hardware, and architecture of each approach. Currently, there are three primary types of CaaS offerings in the marketplace: Hosted VoIP Hosted TDM Local Control/VoIP
Hosted VoIP Hosted VoIP is by far the most common solution. In the Hosted VoIP model, the primary equipment and telco circuits are located at one or more facilities operated by the hosting company. For best call quality, the customer should use a connection that supports Quality of Service (QoS) to prioritize and protect voice traffic over their network connection.
Figure 2: Hosted VoIP Although using a Multiprotocol Label Switching (MPLS) connection or other connection with an appropriate committed rate of throughput is recommended, there are specific situations where quality is not as critical. In those cases, establishing a VPN connection over a best-efforts connection (such as DSL or cable Internet) may be sufficient. Some configurations support almost no equipment at the customer premises, perhaps as little as a router with VPN connectivity and some SIP phones. More complete solutions usually include some local connectivity for local 911 service, a SIP proxy server, and onsite connections to the customers other applications. Hosted TDM [7] For customers who are not ready to make the investment in VoIP but need more advanced communications abilities, a hosted TDM configuration could be a good fit. Often this is also a good choice when disruption to the business could be more expensive than the cost of the equipment. Other reasons to adopt hosted TDM include the need for quick time-to-market, lack of personnel with sufficient network or VoIP expertise, or a move to a new facility is in the near future or when investing in the current facilitys infrastructure doesnt make sense. Like the hosted VoIP model,
154
Gurudatt Kulkarni, Maheshchandra Jadhav , Sadanand Bhuse, Hemant Bankar & Autade Sushma
interactions come into the hosted facility. However, the interaction is not routed to an agent via a network connection. The hosted system connects the incoming call to the agent via a bridged call to the agent. Typically, the agent works behind a traditional PBX system using DIDs. Usually this results in little or no extra hardware at the customer site. There are some trade-offs for avoiding the expenditures of upgrading infrastructure.
Figure 3: Hosted TDM Local Control/VoIP The first is incurring a higher monthly cost because of the charges for the bridge calls between your office and the hosting location. In addition, setup and administration costs will be higher because moves, adds, and changes must be made and coordinated between two phone systems. At times, the additional complexity may lead to difficulty when trying to locate a communications problem. A third option is the local control/VoIP model. This choice gives a customer most of the advanced benefits of having a on-premise VoIP phone system even though the primary server is located off-site in a hardened data center. This is especially helpful for customers who have or desire to create a robust local network supporting VoIP but need to add advanced functionality that their current system doesnt support. Instead of replacing an entire phone system or creating a patchwork of existing features, the customer can connect to a more advanced system to provide greater functionality. While calls come into equipment located on the customer premises, call control is handled by the advanced phone system located in the hardened data center. For customers with exceptionally strong compliance or security requirements or who rely upon high bandwidth applications, the combination of features, functionality, and flexibility are hard to beat. Since phones, network, gateways, proxy/media servers remain at the customers facility, they retain full access and control of those devices.
155
Local Control/VoIP (Extra Redundancy) The customers Telco lines also remain at the customers location. This works especially well when a customer has a preferred voice carrier, has existing contracts that must be fulfilled, or possesses many existing numbers they would prefer not to port or forward. They also avoid the costs of forwarding or bridging calls. Should the WAN connection to the datacenter be interrupted, calls can still be handled by the on premise equipment, although with less functionality. An additional variation of the local control/VoIP model would split the telco lines, placing some at the customers site and some at the hosted provider to provide seamless failover if local trunks ever go down. Likewise, a second, lower priority method of connectivity to the Data Center could be established providing even higher redundancy for data communications.
156
Gurudatt Kulkarni, Maheshchandra Jadhav , Sadanand Bhuse, Hemant Bankar & Autade Sushma
No Facilities and Engineering Costs Incurred CaaS providers host all of the equipment needed to provide their services to their customers, virtually eliminating the need for customers to maintain data center space and facilities. There is no extra expense for the constant power consumption that such a facility would demand. Customers receive the benefit of multiple carrier-grade data centers with full redundancyand its all included in the monthly payment.
Guaranteed Business Continuity If a catastrophic event occurred at your businesss physical location, would your company disaster recovery plan allow your business to continue operating without a break? If your business experienced a serious or extended communications outage, how long could your company survive? For most businesses, the answer is not long. Distributing risk by using geographically dispersed data centers has become the norm today. It mitigates risk and allows companies in a location hit by a catastrophic event to recover as soon as possible. This process is implemented by CaaS providers because most companies dont even contemplate voice continuity if catastrophe strikes. Unlike data continuity, eliminating single points of failure for a voice network is usually cost-prohibitive because of the large scale and management complexity of the project. With a CaaS solution, multiple levels of redundancy are built into the system, with no single point of failure.
Remote Supervisory Monitoring Tools [7] Supervisors and managers can see, in real time, all communication activity going on in their business. In the contact center, they can also see their queues, monitor their SLAs and even listen to and coach their agents even if they are working in another office or at home.
REFERENCES
1. David W Cearley, Cloud Computing: Key Initiative Overview, Gartner Report, 2010 Peter Mell and Tim Grance, The NIST Definition of Cloud 2. Computing, version 15, National Institute of Standards and Technology (NIST), Information Technology Laboratory, www.csrc.nist.gov, 7 Oct 2009 3. Dustin Amrhein and Scott Quint, Cloud Computing for the Enterprise: Part 1: Capturing the Cloud, Developer Works, IBM, 8 Apr 2009, www.ibm.com/developerworks/websphere/techjournal/0904_amrhein/0
904_amrhein.html 4. John Rhoton, Cloud Computing Explained: Implementation Handbook for Enterprises, Recursive Press, 3 May 2010 5. Cloud Computing: Characteristics and Deployment Approaches, Zaigham Mahmood ,2011 11th IEEE International Conference on Computer and Information Technology 6. Gartner Press Release, Gartner Forecasts Worldwide Communications-as-a-Service Revenue to Total $252 Million in 2007, August 2007, retrieved 13 Jan 2009. 7. 8. http://caas.tmcnet.com http://www.dvsweb.com/caas/caasarchitecture.htm