Wcdma Rnp - 10 Umts Services

Click here to load reader

  • date post

    05-Sep-2015
  • Category

    Documents

  • view

    225
  • download

    3

Embed Size (px)

description

Wcdma Rnp - 10 Umts Services

Transcript of Wcdma Rnp - 10 Umts Services

WCDMA Radio Network Planning

WCDMA Radio Network Planning

10. UMTS services

10. UMTS services

Table of Contents

TopicPage

16010.1. Introduction

16010.2. UMTS service architecture

16110.2.1. Virtual Home Environment (VHE)

16210.2.2. Open Service Access (OSA)

16310.2.3. Mobile Execution Environment (MExE)

16410.3. UMTS bearer services

16510.4. UMTS QoS classes

16510.4.1. Conversational class

16610.4.2. Streaming class

16610.4.3. Interactive class

16710.4.4. Background class

16810.5. QoS attributes

10.1. Introduction

In GSM the available services e.g. voice, fax, data, are standardised. This ensures capability between different networks and terminals but it impedes development of new services. The introduction of SIM Application Toolkit (SAT) and Wireless Application Protocol (WAP) was the first steep towards an open service environment. However both concept are not sufficient for complex UMTS services because they are design for very limited GSM phones and do not provide access to all relevant .network elements like the user profile server or multimedia subsystem.

For the end-user the UMTS is a network of services, since a service is that what he actually sees. The UMTS standardisation has defined a framework, which allows quick service development.

10.2. UMTS service architecture

High bit rate offers many opportunities in implementation of new services. The major UMTS services known nowadays are, see also Figure 10.1:

Traditional telecommunication services like speech, teleconferencing or SMS.

M-commerce, for example ticket booking.

E-banking services.

Entertainment, for example games, music and video files downloading.

Information services, that is ability to determine the position of a mobile subscriber.

Figure 10.1 UMTS services nowadays.

Multimedia services, including videoconferencing of terminals connected to different networks, like PSTN, ISDN or Internet.

Emergency calls with enhanced features like emergency call location.

Since peoples needs vary to much to be satisfied by a single application. UMTS will only be successful if it provides a portfolio of attractive services. Therefore, UMTS standardization has defined a framework to develop a rich set of services. The framework consists of a concept for service access (Virtual Home Environment), a network architecture (Open Service Access) and a terminal architecture (Mobile Execution Environment).

Figure 10.2. Virtual Home Environment (VHE), Mobile station application Execution Environment (MExE) and Open Service Access (OSA).

Source: Hermann Anegg, Harald Kunczier, Elke Michlmayr, Gnther Pospischil, Martina Umlauft LoL@: Designing a location based UMTS application, Forschungszentrum Telekommunikation Wien, Donau-City-Strae 1, 1220 Wien/Austria.

10.2.1. Virtual Home Environment (VHE)

The Virtual Home Environment (VHE) is a concept of service access with different device (Smart Phone, Personal Digital Organizer (PDA) or Laptop) over different network (GSM/GPRS, UMTS, wireless LAN). In all situations the functionality and look & feel shall remain the same as far as possible. The use will not see a difference in using his services wile roaming in different networks.

Figure 10.3 illustrates the concept. It presents a user accessing his service from various kinds of terminals (laptop, PC, smart phone) and through various networks, which he even might not be aware. Modification in his service profile made with one terminal will be valid on all terminals he is using, and in all networks.

Figure 10.3. Online cinema ticket booking.Benefits of Virtual Home Environment:

Provides users with the ability to receive customized and personalized services with a common look & feel, wherever and on whatever kind of terminal.

Offers the network operators the flexibility to develop customized services across different networks (e.g. cordless, cellular or satellite networks), without requiring modifications of the underlying network infrastructure.

Offers the service providers a set of components for flexible service creation, enabling them to develop services whose appearance adapts to the network and terminal capabilities.

To realize the VHE in mobile networks the Open Service Access (OSA) and Mobile Execution Environment (MExE) are used. VHE service control can be based on the Open Service Architecture (OSA).

10.2.2. Open Service Access (OSA)

In the Internet, the transport network is usually seen only as bit-pipe. However, mobile networks offer additional functionality, e.g. call control, localization, user/device profile access.

Open Service Access (OSA) is an architecture, enabling applications to make use of additional network functionality via standardised interfaces (namely OSA interfaces). The OSA interfaces are defined between the applications and the Service Capability Servers (SCSs), see Figure 10.4. Service Capability Servers provide abstractions of the underlying network functionalities. This way, applications become independent from the network technology.

The OSA consists of three parts:

Applications. Examples of applications could be teleconferencing or location-based applications. They are implemented in one or more Application Servers.

Framework. The Framework takes responsibility for all security aspects of OSA. First applications authenticate themselves to the Framework. The Framework then offers functionality to applications so they can select the services they want to use. The framework also supports integrity management. In this context the integrity deals with performance and availability aspects of OSA services.

Service Capability Servers (SCSs). Service Capability Servers are designed to provide the applications with OSA services accessed by the methods defined in the OSA interfaces. Examples of OSA services are Call Control and User Location.

Benefits of Open Service Access:

Application logic is separated from network access.

The application can be run at a service provider.

Applications can be third party developed.

Communication between the applications and the network is through standard OSA interface (Application Programming Interface). The OSA provides an Application Programming Interface (API) to network elements allowing applications providers the ability to create solutions using networks services such as User location, Charging, Call control etc.

Figure 10.4. OSA overview.Note

OSA stood for Open Service Architecture in Release 99 of the UMTS specifications, release 4 of UMTS has seen a change in name to Open Service Access

10.2.3. Mobile Execution Environment (MExE)

The Mobile Execution Environment provides a standardized execution environment in an MS (Mobile Station), and an ability to negotiate its supported capabilities with a MExE service provider, allowing applications to be developed independently of any MS platform. The MS can then be targeted at a range of implementations for MExE from small devices with low bandwidth, limited displays, low processor speeds, limited memory, etc., to sophisticated PDA type devices with a complete MExE execution environment.

To integrate the set of existing mobile application technologies under one common standards umbrella, the MExE standardization has begun with the standardization of three application classmarks. Each classmark represents a set of common terminal device features. A typical MExE device only supports a subset of the three classmarks (e.g. one or two):

Classmark 1 WAP Environment.Classmark 1 MExE devices are based on Wireless Application Protocol (WAP). They require limited input and output facilities on the client side only (e.g. as simple as a 3 lines by 15 characters display and a numeric keypad), and enable efficient information access even over low bandwidth connections.

Classmark 2 PersonalJava Environment.Classmark 2 MExE devices enabled PersonalJava applications with the addition of the JavaPhone API. The PersonalJava application environment is the standard Java environment optimised for consumer electronic devices designed to support World Wide Web content including Java applets.

Classmark 3 J2ME Environment. Classmark 3 MExE devices are based on the Connected Limited Device Configuration (CLDC) with the Mobile Information Device Profile (MIDP). The Java 2 Platform Micro Edition (J2ME) is a version of the Java 2 platform targeted at consumer electronics and embedded devices. CLDC consists of a virtual machine and a set of APIs suitable for providing tailored runtime environments. The J2ME CLDC is targeted at resource constrained connected devices (e.g. memory size, processor speed etc.).

10.3. UMTS bearer services

Each service require another Quality of Service (QoS). The UMTS network must provide the required QoS so, that the end-user is satisfied with the service used. Therefore in UMTS it is possible to negotiate properties of a radio bearer, e.g. throughput, transfer delay and data error rate, depending on the service used.

In order to support the End-to-End Service, see Figure 10.5, e.g. videoconferencing, the application running the videoconferencing service must receive required for the service QoS (throughput, transfer delay etc.) in the UMTS network. That is the application requests for a required UMTS Bearer Service. UMTS allows a user/application to negotiate bearer characteristics that are the most appropriate for a End-to-End Service used. Bearer negotiation is initiated by an application. The application requests a bear