Customer center

We are a boutique essay service, not a mass production custom writing factory. Let us create a perfect paper for you today!

Example research essay topic: Wireless Transaction Protocol Layer - 2,623 words

NOTE: Free essay sample provided on this page should be used for references or sample purposes only. The sample essay is available to anyone, so any direct quoting without mentioning the source will be considered plagiarism by schools, colleges and universities that use plagiarism detection software. To get a completely brand-new, plagiarism-free essay, please use our essay writing service.
One click instant price quote

Wireless Transaction Protocol Layer To improve clinical performance, hospitals need to ensure that therapeutic practitioners can remotely access critical pathways, hospital patient records, and clinical outcomes tracking. Of course, such abilities also present an enormous confront for maintaining security and privacy. This paper will discuss designing a scalable system that will implement transactions between remote patients and hospitals. Many clinics are finding today that "thin" web-based systems, applied through moveable devices that are used for access rather than storage, can make available a certain degree of harmony between these commonly conflicting needs. The term "thin" specifies that these devices do not store large applications of information, unlike a "fat" personal computer. As an alternative, the devices, which at times are handheld, will communicate with the data held in the clinic's central hardware applications.

The central applications present security by controlling users access to the information. WAP protocol is the best solution for the mobile tracking of patients. In practice, the WAP protocol works with a mini server, called a micro-browser, fixed in a mobile terminal. Because WAP applications can be downloaded on demand of patient or doctor and discarded when no longer needed, the application setting also allows for dynamic extension of the user interface. The Wireless Application Environment is a common-purpose application environment based on a mixture of World Wide Web (WWW) and Mobile Telephony devices. The primary objective of the WAE effort is to create an interoperable environment that will allow our medical practitioners and service providers to build applications and services that can reach a wide selection of different wireless platforms in an well-organized and useful way.

WAE includes a micro-browser environment holding the following functionality: Wireless Markup Language - a lightweight markup language, close to HTML, but optimized for use in hand-held mobile terminals of our patients; WML Script - a lightweight scripting language, close to Java Scrip; Wireless Telephony Application - telephony services and programming interfaces; and Content Formats - a set of well-defined data formats, including pictures, phone book records and calendar data. Web-based information devices such as WAP Protocol with clinical guidelines are becoming more and more necessary as the amount and depth of data needed to respond to patients have increased. Clinics need to get used to not only to deliver this data to healthcare providers, but also to help them combine this information. As an example, the growing number of prescription drugs that have been introduced over the past decades. Modern physicians need to be aware of thousands of potentially adverse interactions that could result from combining these medications-a much different accountability than that faced by physicians in the near past. Relying on memory seems reckless in an age when handheld drug programs can perform such services for our hospital specialists.

Patient interest in clinical outcomes. Using web based technology to properly track outcome data is becoming ever more important as well. Patients are demanding this type of information as they become more involved in choose of their health care. Many U. S. healthcare customers can obtain voluntarily submitted patient-safety data about the hospitals in their.

For hospitals to survive as strong competitors, they need to be just as able of tracking and showing positive outcomes as their competitors are. Although WAP will be equally supported by many of modern mobile computing devices, among the main attractions for our mobile tracking of patients is the capability to host it on one of the specially-portable devices. From the technical point of view, this implies that the mechanism will have a limited display and restricted user interface capabilities but it should be enough for mobile tracking of patients. The WAP information delivery model is analogous to the WWW information delivery form. This provides several benefits to the application developer neighborhood, including a proven architecture, a user-friendly programming model, and the ability to control existing tools such as mobile devices.

Extensions and optimizations have been made in order to match the characteristics of the wireless devices. Wherever possible, existing standards have been adopted or have been used as the starting point for the WAP equipment. WAP information delivery model for mobile tracking of patients system will be as follows: The patient (user agent) initiates a connection to the mobile operator and submits IP Address of the WAP Gateway and the URL of the Web Server. All information over the network is in encoded symbols. The WAP Gateway processes the encoded request and decodes it and makes an HTTP appeal as identified by the URL.

The Web Application (Hospital Server) processes the HTTP appeal, executes an application that can be either a script soft or any middle-tier commerce object. The resulting information is in WML format with the additional HTTP Header. This data is returned to the WAP Gateway now. Then the WAP Gateway confirms the WML content and the HTTP header and encodes them to binary form. The gateway then makes the WAP reply containing the WML and sends it to the user device. The user agent then accepts the WAP response.

It processes the WML reaction and displays the first card of the WML deck to the patient. Our newly designed mobile tracking of patients will be really user-friendly. First of all, the patient who needs assistance connects to the mobile network using his mobile phone, typically a Circuit Switching Data Bearer. The link will be initiated by dialing a specific number, provided by the mobile operator. This network solution should be supported by mobile operator. However, there are very few operators that will support WAP in the near future.

As part of the connection, the client submits the WWW-URL of the Web Server and the IP Address of the WAP Gateway. Then the CSD Bearer establishes the connection with the WAP Gateway over the mobile system. The WAP Gateway translates the WAP requests to WWW requests, making an HTTP request to the Hospital Server as identified by the URL submitted by the patient. Privacy and security are among substantial issues we have to keep in mind while developing mobile tracking of patients. HIPAA's privacy regulations also have provided appropriate support for the heightened security practices associated with using web-based data networks. Without HIPAA, hospitals would not have had the enticement to give such noteworthy attention to access limitations.

Evidence of long-standing practices of dispersing data without regard to security can be seen in the software devices many hospitals currently use. Many current platforms do an inadequate job of providing security, or even providing viable protection options. In addition, clinics traditionally have lacked suitable staffing to support security measures, such as controlling who can access data, what these admission rights should be, and when these admission rights should be suspended. HIPAA is the momentum to finally set in place security measures that are necessary to support hospital web-based computer application. As these trends go on, the need to exchange to a web-based system becomes even more pressing. As a sensible example, consider patient e-mail.

Because there is no engineering standard for authenticating users and protecting data as it flows over the Internet, this type of patient message is highly susceptible. Most patients use an e-mail system that lacks elementary security, either based from their houses or from their place of employment. Rather than provide a software device that is secure for every e-mail system that will be used by patients, it is much easier to make the patient go to the hospital's web site and access his e-mail through an Internet portal. If sensitive content in the e-mail communication lies within the hospital's firewall, the patient's employer or people with access to the patient's personal e-mail cannot access the information on patient.

The result is increased protection and enhanced 24 / 7 customer service. The Hospital Server will be either on the Internet or an Intranet. The Web application performs the required act and returns the outcome in WML format to the WAP user (patient) over the HTTP protocols. If the web application returns HTML report, then the WAP Gateway performs the translation of HTML into WML before sending it to the patient.

We should use the following components of WAP Architecture: Transaction Protocol Bearer The Application Protocol is a layered communication stack that consists of Session Protocol Application Environment Security Protocol Datagram Protocol Application Protocol This protocol is rooted in the patients agent such as a mobile phone and the Hospital WAP Server. The Application Environment consists of two elements: A mark-up language, WML that allows programmers in Hospital to identify the application's user interface in a device-independent way for it. A programming language or WML Script, that allows programmers to drive in executable logic in the application. The layered stack provides a scaleable and extensible structure for application development for our patients mobile devices. Each layer is accessible by layer above it and by other applications and services. There are three layers in our mobile tracking of patients.

The Wireless Session Protocol will help us to provide a means for organized exchange of information between co-operating client / server applications. Specifically, it gives the applications resources to: establish a consistent session from patient to server and release that session in an orderly manner as well; agree on a common level of protocol functionality using capability cooperation; exchange content between patient and hospital server using compact encoding; hang up and resume the session. give HTTP/ 1. 1 functionality and semantics in a compacted over-the-air encoding, The presently defined services and protocols (WSP) are most suited for browsing-type our applications. WSP defines in fact two protocols: one provides connection-mode session services over a transaction services, and another provides non-confirmed and even connectionless service over a datagram transport services. The connectionless service is most suitable for mobile tracking of patients, especially when applications do not need consistent delivery of data and do not care about authentication. It can be used without actually having to set up a session.

The lifecycle of a WSP session now is not tied to the underlying transport. A session may be balanced while the session is idle to free up network resources or save battery mode. A lightweight session re-establishment protocols allow the session to be resumed without the overhead of full-blown session organization. A session may be resumed over a wide range bearer network.

Wireless Transaction Protocol will also be used for mobile tracking of patients. It runs on top of a datagram service and supplies as a light-weight transaction-oriented protocol that is suitable for realization in "thin" clients or mobile stations of our patients. WTP works capably over secure or non-secure wireless datagram networks and gives the following points: I. three classes of transaction service: 1. Unreliable one-way requests 2. Reliable one-way requests. 3.

Reliable two-way request-reply transactions; II. optional user-to-user dependability - WTP user triggers the confirmation of each received from patient message optional out-of-band information on acknowledgements. asynchronous dealings Protocol Data Unit concatenation and delayed acknowledgement to decrease the number of messages sent by patients. By stringing several messages together, the end user can well be able to get a better feel more quickly for what information is being transferred. The Transport layer protocol in the WAP architecture for our mobile tracking of patients is referred to as the Wireless Datagram Protocol which is sufficient element in our process. The Wireless Datagram Protocol layer operates above the data able bearer services supported by the various network devices.

As a general transport service, Wireless Datagram Protocol offers a consistent service to the upper layer protocols of WAP and converse transparently over one of the available carrier services. Since the Wireless Datagram Protocol protocols provide a widespread interface to the upper layer protocols, the Session, Application layers and Security are able to function independently of the underlying wireless network system. This will be accomplished by adapting the transport layer to specific features of the underlying new bearer. By keeping the transport layer interface and the essential features consistent, global interoperability can be achieved using mediating gateways as well. The Wireless Datagram Protocol operates over various bearer service. Each bearer service for which Wireless Datagram Protocol is specified supports a datagram services.

For bearer service not supporting IP the Wireless Datagram Protocol is used. Bearers. The WAP protocols are created to operate over a variety of different bearer services, including SMS, packet data and circuit-switched data. The bearers offer differing levels of quality of services with respect to throughput, error rate or delays.

The WAP protocols are designed to compensate for or tolerate this varying level of service. Since the Wireless Datagram Protocol layer provides the junction between the bearer service and the rest of the WAP stack, the Wireless Datagram Protocol specification is listing the bearers that are supported and the techniques used to allow WAP protocols to run through each new bearer. The list of supported bearers used for mobile tracking of patients will change over time with new bearers being added as the wireless environment evolves. Among the benefits of our mobile tracking of patients web-based solutions are cost, heightened data control, mobile access, full regional connectivity, and maintenance of data integrity which is of vital importance for communication between patients and their doctors. Cost. Running wires and loading and unloading applications from patients PC stations and devices is costly.

WAP wireless systems have become essential to reduce expenses on hardware and program maintenance. Heightened data control. Hospitals retain greater control over their information by bringing patients into an area with centrally managed information over the Internet, rather than disseminating the data and making recipients guarantee not to misuse it. Mobile access. Although hospitals need to preserve control of patient information to ensure security and privacy, they also need to let access to these data from any locations. A handheld tool using wireless technology supports the mobile character of physician practices without providing memory limitations.

Also, the data is secure because web-based devices require users to pass through effective security gate before accessing data via the Internet. This security gate must be established with two-factor verification (login and password), and the transmitted data can be encrypted. Regional connectivity. Hospitals today need to achieve cross-regional connectivity to best serve patients who receive cure from several providers and physicians who could treat patient at several locations.

Web-based data systems allow for regional connectivity because data is stored inside, behind the firewall. Maintenance of information integrity. If a general practitioner misplaces a wireless device, all that is lost is the admission mechanism-not control of the data. Should a doctor quit, the hospital would not be happy with incurring any significant information loss. The hospital need only regulate the access rules for that doctor. The time for transitioning to WAP technologies has arrived.

Contemporary health care demands encrypted wireless access to health information, secure. Devices need to be structured to provide information defense, instant mobile access, and easily accessible clinical information. General practitioner as well as their patients will insist on these Internet-based environments and the protection and clinical excellence improvements that effect. Bibliography: Hari Balakrishnan, Srinivasan Susan, Elan Amir, and Katz Randy H.

Improving TCP/IP performance over wireless networks. ACM MOBICOM 95, 1995. WAP Forum. Wireless Application Protocol, Architecture Specification.

WAP Forum, 1998. M. Banan. Neda's Efficient Mail Submission and Delivery (EMSD) Protocol Specification Version 1. 3. Request for Comments (Informational) 2524, Neda Communications, Inc. , February 1999 Mohsen Banan. The WAP Trap.

FPF Published Document 108 - 102 - 01, Free Protocols Foundation, Bellevue, WA, January 2000. Mohsen Banan. Lightweight & Efficient Application Protocol (LEAP) Manifesto. Technical Report 108 - 101 - 01, LEAP Forum, Bellevue, WA, January 2000 S. Dawkins, G.

Montenegro, M. Kojo, V. Market, and N. Vaidya. Performance Implications of Link-Layer Characteristics: Links with Errors. IETF, 1996.


Free research essays on topics related to: e mail system, security measures, user interface, markup language, mobile devices

Research essay sample on Wireless Transaction Protocol Layer

Writing service prices per page

  • $18.85 - in 14 days
  • $19.95 - in 3 days
  • $23.95 - within 48 hours
  • $26.95 - within 24 hours
  • $29.95 - within 12 hours
  • $34.95 - within 6 hours
  • $39.95 - within 3 hours
  • Calculate total price

Our guarantee

  • 100% money back guarantee
  • plagiarism-free authentic works
  • completely confidential service
  • timely revisions until completely satisfied
  • 24/7 customer support
  • payments protected by PayPal

Secure payment

With EssayChief you get

  • Strict plagiarism detection regulations
  • 300+ words per page
  • Times New Roman font 12 pts, double-spaced
  • FREE abstract, outline, bibliography
  • Money back guarantee for missed deadline
  • Round-the-clock customer support
  • Complete anonymity of all our clients
  • Custom essays
  • Writing service

EssayChief can handle your

  • essays, term papers
  • book and movie reports
  • Power Point presentations
  • annotated bibliographies
  • theses, dissertations
  • exam preparations
  • editing and proofreading of your texts
  • academic ghostwriting of any kind

Free essay samples

Browse essays by topic:

Stay with EssayChief! We offer 10% discount to all our return customers. Once you place your order you will receive an email with the password. You can use this password for unlimited period and you can share it with your friends!

Academic ghostwriting

About us

© 2002-2024 EssayChief.com