Rel-4 (U)SIM toolkit enhancements

 

Acronym: USAT1

UID: 401800

Main responsibility: T3

 

References for WI " Rel-4 (U)SIM toolkit enhancements "

Document	Title/Contents
	No WI Description
Impacted Specifications
TS 31.111 TS 51.014	Universal Subscriber Identity Module Application Toolkit (USAT)Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment (SIM - ME) interface
New Dedicated Specifications
TS 23.048	Security Mechanisms for the (U)SIM application toolkit in Rel-4

 

In Release 4, only one enhancement was added in the field of (U)SIM toolkit, also called (U)SAT or USAT (Universal SIM Application Toolkit). This is the “USAT Local Link”, which refers to the use of a local link (RS232, Bluetooth, USB, Irda) as a bearer for USAT.

This work extends the existing bearer independent functionality and allows a USAT application to communicate with local devices using the local connectivity capabilities of the terminal.

For applications dedicated to third party equipment, the knowledge of the local environment (attached devices) is useful. So a way for the USAT to get the local connection status, independent of the type of link, is also defined.

 

As some applications may require a secure link, security facilities offered by the bearer may be used, as well as an upper layer security mechanism. This is covered in the Rel-4 created TS 23.048 “Security Mechanisms for the (U)SIM application toolkit in Rel-4”, replacing GSM 03.48. It contains following enhancements compared to Release 99 GSM 03.48:

• USIM input and output commands for Remote File Management (RFM)
• Clarification on computation of Data Encryption Standard (DES) in Cipher Block Chaining (CBC) mode
• Clarifications on Access Domain Parameter

 

To meet the Release 4 requirements, the storage of MMS related information in several elementary files on the SIM is introduced retroactively (affected specifications are TS 51.011 and TS 31.102).

 

Rel-4 Open Service Access (OSA) improvements

 

Acronym: OSA1

UID: 401142

Main responsibility: CN5

 

References for WI "OSA improvements"

Document	Title/Contents
WIDs
SP-000216 (S1-000447)	WI on Scope of Open Interface for Service Provision in Release 2000 (SA1)
SP-000302	OSA security (SA3)
Impacted Specifications
22.121	Service aspects; The Virtual Home Environment; Stage 1
23.127	Virtual Home Environment (VHE) / Open Service Access (OSA); Stage 2
29.198	Open Services Architecture API part 1 (R99 was split in Rel-4 in a multi-part TS, see below)
29.998	Open Services Architecture API part 2 (R99 was split in Rel-4 in a multi-part TS, see below)
33.102	Security Architecture
New Dedicated Specifications
22.127	Service Requirement for the Open Services Access (OSA); Stage 1
33.200	MAP Application Layer Security
	OSA API
29.198-01	Part 1: Overview
29.198-02	Part 2: Common data
29.198-03	Part 3: Framework
29.198-04	Part 4: Call control
29.198-05	Part 5: Generic user interaction
29.198-06	Part 6: Mobility
29.198-07	Part 7: Terminal capabilities
29.198-08	Part 8: Data session control
29.198-11	Part 11: Account management
29.198-12	Part 12: Charging
	OSA API Mapping for OSA
29.998-01	Part 1: General Issues on API Mapping
29.998-04-1	Part 4: Call Control Service Mapping; Subpart 1: API to CAP Mapping
29.998-05-1	Part 5: User Interaction Service Mapping; Subpart 1: API to CAP Mapping
29.998-05-4	Part 5: User Interaction Service Mapping; Subpart 4: API to SMS Mapping
29.998-06	Part 6: User Location and User Status Service Mapping to MAP
29.998-08	Part 8: Data Session Control Service Mapping to CAP

Open Service Access (OSA) allows service development by operators and third parties: it enables application developers to make use of network functionality through open, standardised, secure, extensible and scalable interfaces. Applications see the network functionality offered to them as a set of Service Capability Features (SCFs) in the OSA APIs. These SCFs provide access to the network capabilities on which the application developers can rely when designing their applications. The OSA APIs are independent of where or which network capabilities are implemented in the network, and of vendor-specific solutions and programming languages.

 

This work (stage 1, 2 and 3 specifications) was done jointly with other fora (3GPP2, ETSI SPAN and Parlay), so that there is a single set of standard OSA APIs for the whole development community.

 

The objective of OSA in Release 4 is to enhance the OSA interface for the communication between Applications and Service Capability Features (SCF). The SCFs are described in the OSA set of specifications.

 

Release 4 brings enhancements to the OSA interface based on the evolved network capabilities within the Core Networks. Examples of these are:

• Call Control (IP)

This addresses the Call Control capabilities based on SIP and/or H.323. In 3GPP, SIP is introduced only in Release 5 with the IMS (IP Multimedia Subsystem). However, it is justified to have the corresponding OSA capability as early as Release 4 because SIP and H323 exist in fixed networks for some time and the 3GPP OSA has a requirement to have the same API for Fixed and Mobile networks (and, more generally, to be network-agnostic).

• E-Commerce

This takes into account the capabilities provided by the network to use the capabilities provided by the post processing of the charging capabilities (e.g. E-Pay). It also involves the enhancements of the security to be provided by the network and by the application.

 

The enhancements compared to OSA Release 99 are as follows:

• User Location: Further integration of the Location Services within the provisioning of geographical positioning information, taking into account the evolution of the 3G networks associated with this capability.
• Terminal Capabilities: In Release 99, the mechanism to retrieve the terminal capabilities is only applicable to WAP phones. Rel-4 adds a mechanism that is applicable to all types of phones. Security mechanisms for the display of terminal capabilities information have been added.
• Enhanced User Profile Management: The integration of the Personal Service Environment Management (PSEM) within the Network and Framework SCFs.
• Enhanced Session Control: This provides the enhancements of the bearer manipulation and creation of bearers/sessions sessions (in particular negotiation of the QoS).

 

The OSA API offer many capabilities related to charging (they supervise of user activities for online charging features; allow applications to access the online account; allow applications to add charging information to network based charging records; and inform applications on network based charging event).

Improvements of UMTS-only pre-Release 4 features

QoS Architecture for PS Domain

 

Acronym: QoSPS

UID: 2546

Main responsibility: S2

 

This chapter covers the following WIs:

UID	Name	Group	Acronym	WID
	Architecture	SA2
	Charging and OAM&P for QoS Management	SA5	QoSPS-OAM	SP-010461
	RAB Quality of Service (re)Negotiation over Iu	RAN3	QoSPS-MAPEND-RABQoS	RAN_Wis, RP-000499
	RAB QoS Renegotiation at Relocation	RAN3
	PS-domain handover for real-time services	RAN3	QoSPS-PSdoRTS	RAN_Wis
	GERAN QoS Aspects - Handovers: maintenance of real-time QoS while moving between cells in the PLMN including inter-SGSN and SRNS relocation or possibly other mechanisms	GP	GERQoS	GP-010431
	GERAN MS Conformance test for inter-system and intra-system Packet data real-time Handover	GERAN4, RAN3	GERQoS-Mstest	GP-012287

 

The References for WI " UMTS QoS Architecture for PS Domain " given for each individual WI.

The work done under UIDs 2548 and 2550 (SA2’s architecture and SA5’s Charging aspects) was only maintenance of pre-Release 4 concepts.

RAB Quality of Service (re)Negotiation

UIDs:

• 1681 for “RAB Quality of Service (re)Negotiation over Iu”
• 2554 for “RAB QoS Renegotiation at Relocation”

WIDs in:

• RP-000499 for “RAB Quality of Service Negotiation over Iu”
• RP-000500 for “RAB Quality of Service Renegotiation over Iu”
• RP-010168 for “RAB Quality of Service Negotiation over Iu during Relocation”

Affected specification: TS 25.413