in black and white
Main menu
Share a book About us Home
Biology Business Chemistry Computers Culture Economics Fiction Games Guide History Management Mathematical Medicine Mental Fitnes Physics Psychology Scince Sport Technics

GPRS and 3G Wireless application - Anderson C.

Anderson C. GPRS and 3G Wireless application - Wiley publishing , 2001. - 356 p.
ISBN: 0-471-41405 -0
Download (direct link): gprsand3gwirelessapplica2001.pdf
Previous << 1 .. 74 75 76 77 78 79 < 80 > 81 82 83 84 85 86 .. 125 >> Next

Directory access support service. As we will see in the next subchapter, there will be many more features available in order for the user to keep a
Page 196
profile and preferences that many applications can use. These services are part of the personal service environment (next subchapter) and thus are part of the service network. The directory access support service provides an API for the application developer to access this information. As for most ASuS, it provides an API for another part of the service network.
In order to use the individual APIs, please refer to standardization comments. You can find the detailed APIs in the 3GPP release í99 specifications (TS 29198-300 and TS 29998-300).
The open architecture opens new possibilities for third parties to develop their own SCS and ASuS nodes. Several opportunities are likely to emerge over time, and we will see products such as instant messaging servers, multiplayer gaming servers, and so on. The vendors of such servers will then release software development kits (SDKs) that developers can use to access the enhanced features. When examining these exciting new capabilities, we must obtain a feel for how widely supported they are. Which operators are using them, and how big is the market?
Personal Service Environment
Today, personalization on the fixed Internet takes place on a per-application basis with user registration and cookies. The first time you arrive at a Web site, you sign up to obtain a username and password. You sometimes also have to enter your personal information (in order to buy items, for instance) and preferences. The problem is that there is no connection between different Web sites, and you have to enter the same payment information for every electronic commerce (e-commerce) site that you use. Some sites use cookies to remember what you selected and what you are likely to want to see (in other words, your user preferences). Once again, the site that sets these cookies is the only Web site that uses them, and buying history books on will not help Barnes & Noble find out what kinds of books you like. We illustrate this issue in Figure 9.10.
In the figure, these three sites could potentially set a cookie that says that you like to read about ancient Greek history. You would probably find it nice if you could enter this information once and make it available to all applications (or at least to your three favorite applications). This concept is one of the thoughts behind adding the Personal Service Environment (PSE), where a common directory holds personalized information (see Figure 9.11).
This figure shows the thinking behind the PSE model, where information that is common to many applications can be stored in one place. This opens up new and useful features, like enabling users to log on once per session (rather than once per application) but still achieve personalized service.
While the service enablers do not hold much information themselves (instead, they facilitate access to data and services), the PSE does. The PSE is a set of
Page 197
Web Sile 1
Figure 9.10 Web sites with potentially redundant cookies.
databases that hold subscriber information and preferences that you can access from a number of applications (see Figure 9.12). This feature does not prevent individual applications from maintaining application-specific subscriber data; rather, it is a complement. You should therefore use PSE for data that is generic and that is likely to be used by several applications (such as name, e-mail, favorite handset, and so on).
Figure 9.11 The Personal Service Environment (PSE) model.
Page 198
Figure 9.12 The PSE.
This figure is an extract of Figure 9.5 that shows the PSE in more detail.
The following paragraphs describe some components that can be part of the PSE.
Common directory system. This location is where we collect information from multiple applications and from the user and merge that data into a central directory. We divide the information into different groups, depending on who can access and change the data. The user can alter some parts of the data (personal address book, preferred services, and so on) while applications update other parts (maps, favorite actor, and so on). The User Profile is also part of the common directory and holds information such as name, e-mail address, services subscribed to, and so on. Information from the common directory is either accessed via an ASuS API (directory support service; see the previous subchapter) or via the Lookup Directory Access Protocol (LDAP). Either way, user preferences and profiles are now available to applications developers.
Personal Service Environment Manager (PSEM). PSEMís main responsibility is to manage the services to which the user subscribes. The PSEM enables users to see their subscribed services and their status. Users can access this feature through a WAP telephone or a PC that has an HTML browser. If the user wants to update any part of this common directory system, PSEM manages this procedure.
Previous << 1 .. 74 75 76 77 78 79 < 80 > 81 82 83 84 85 86 .. 125 >> Next