Rel-4 Evolutions of the transport in the CN

 

Acronym: CNTRSP (for “CN Transport”)

UID: 400004

Main responsibility: CN4

 

References for WI " Rel-4 Evolutions of the transport in the CN "

Document	Title/Contents
NP-000746	#7 Signalling over IP in Core Network
Impacted Specifications
TS 29.002 TS 29.078 TS 29.018 TS 29.016	Mobile Application Part (MAP) specification CAMEL Application Part (CAP) specification Gs interface layer 3 specification (BSSAP+) Gs interface Layer 2 specification
New Dedicated Specifications
	None

 

IP plays a significant role in UMTS according to the actual trend towards IP-capable backbone networks.

This feature refers to the introduction of IP-based transmission in a Bearer Independent Core Network, so that the transfer of #7 signalling (e.g. MAP, CAP, BSSAP+) over IP is supported.

 

Within IETF, the group SIGTRAN has defined the Internet Drafts describing this functionality.

The architecture defined by SIGTRAN (RFC 2719) consist of a modular extensible structure with a common reliable transport protocol SCTP (RFC 2960). SCTP (Stream Control Transmission Protocol) is an application level datagram transfer protocol operating on top of IP. In order to access SCTP an adaptation module has been defined between the SCN (Switched Circuit Network) signalling system being carried and SCTP. The adaptation module allows keeping the signalling protocol unchanged.

 

In 3GPP, the option to allow the transfer in the Core Network of the #7 signalling (e.g. MAP, CAP, BSSAP+) over IP is done according to the architecture defined by SIGTRAN (RFC 2719) with the SCTP layer (RFC 2960) and the appropriate adaptation layer. Impacts to the higher layer protocols TC and MAP have been avoided as much as possible.

Rel-4 Emergency call enhancements

 

Acronym: EMC1

UID: 401652, 1654

Main responsibility: N1

 

References for WI " Rel-4 Emergency call enhancements "

Document	Title/Contents
NP-010136	CS based Emergency Call Enhancements in Rel-4
Impacted Specifications
TS 24.008	Mobile radio interface Layer 3 specification; Core network protocols; Stage 3
New Dedicated Specifications
	None

 

Emergency calls over the CS domain has been integrated into the system as a mandatory feature from the beginning of GSM. As imposed by new national regulations, this feature enhances this service by enabling emergency calls to be triggered without dialling the emergency number, as this number varies between networks and might create failures in roaming cases. Instead, other means such as menu and/or linkage to external security devices, as a car air bag, will trigger the call. The default numbers are stored in the ME and/or USIM. If the numbers are stored in ME, this functionality is also supported by the UE without a SIM/USIM being present.

Emergency calls was intended to work in the CS and the PS domain, but the packet emergency calls was not implemented in Release 4 and became a work item for Rel-5 where that part was enhanced to include IMS.

Rel-4 Terminal interfaces

 

The Feature Rel-4 Terminal Interfaces consists of the following three independent functionalities which are described in the following sections:

• AT commands enhancements

· Wide Area Data Synchronization

• Terminal local model

AT-commands enhancements

 

Acronym: TI-ATC

UID: 1827

Main responsibility: T2

 

References for WI " AT commands enhancements "

Document	Title/Contents
	No WID
Impacted Specifications
TS 27.007	AT command set for User Equipment (UE)
New Dedicated Specifications
	None

 

This work item is about AT[6] commands for control of 3GPP Mobile Equipments (MEs) via an external Terminal Equipment (TE), fully compatible with GSM AT commands.

 

TS 27.007 specifies a profile of AT commands and recommends that this profile be used for controlling ME functions and GSM network services from a TE through Terminal Adaptor (TA). The command prefix +C is reserved for Digital Cellular in ITU-T Recommendation V.25ter. This TS has also the syntax details used to construct these extended GSM commands. Commands from ITU-T Recommendation V.25ter and existing digital cellular standards (TIA IS-99 and TIA IS-135) are used whenever applicable. Some of the new commands are defined such way that they can be easily applied to ME of networks other than GSM.

 

The new AT commands added in Release 4 relate all to ASCI[7] services:

 

• Introduction of a new AT command +CUUS1 to manage User-to-User Information element
• Indication of priority and/or sub-address in the unsolicited result code CCWA
• eMLPP SIM Commands

· VBS, VGCS SIM Commands

• Extension of dial command for VBS and VGCS
• Introduction of a new AT command +COTDI to manage Originator-to-dispatcher information element

Wide Area Data Synchronisation

 

Acronym: TI-WADS

UID: 1829

Main responsibility: T2

 

References for WI " Wide Area Data Synchronisation "

Document	Title/Contents
	No WID
Impacted Specifications
TR 27.903 TS 27.103	Discussion of synchronisation standards Wide Area Network Synchronisation
New Dedicated Specifications
	None

 

In Release 99, the concept of Wide Area Synchronisation for 3GPP has been developed to allow data stored in the ME/USIM to be synchronised with the outside world. In Release 4, SyncML was introduced as the preferred synchronisation mechanism replacing IrMC level 4.

 

TR 27.903 provides information on existing synchronisation protocols. It summarises proprietary and standard protocols relevant to current and future mobile communication devices. The document covers only synchronisation between end-user devices, desktop applications, and server-based information services. It does not refer to replication or synchronisation between enterprise databases.

 

This specification provides a definition of a Wide Area Synchronisation protocols. The synchronization protocol was originally based upon IrMC level 4 in Release 99 which was replaced by SyncML in Release 4. The document covers Wide Area Network Synchronisation between current and future mobile communication end-user devices, desktop applications and server-based information servers.

 

SyncML is an XML-based specification for data synchronization. It accommodates not only traditional local synchronization but also the special requirements associated with remote synchronization in wide-area wireless environments with intermittent connectivity. SyncML is based on a client-server model. SyncML specifications consist of three major components: representation protocol, synchronization protocol, and transport bindings. The Representation protocol defines XML-based messages for synchronization, whereas the Synchronization protocol defines synchronization in the form of message sequence charts. The Transport binding specification defines a mechanism to carry synchronization messages over different transport mechanisms.

Terminal Local Model

 

Acronym: TLM

UID: 1832

Main responsibility: T2

 

References for WI "Terminal Local Model"

Document	Title/Contents
TP-000080	WI Description
Impacted Specifications
TS 23.227	Application and User interaction in the UE - Principles and specific requirements
New Dedicated Specifications
	None

 

The rapid development of a diversity of new applications and application environments for mobile usage creates a complexity of previously unseen proportions that the Mobile Equipment has to handle. Since third party software can run in various parts of the UE, there was a need to develop a general framework to ensure that the APIs created for the different UE-based toolkits work in harmony with each other.

 

The work item introduces such a generic model approach for the UE environment; the purpose is not to categorise the applications peripherals, but to try to structure the events that are internal and external to, and has to be handled by, the MT Core Functions. This means that the structure or grouping of the events is done from a MT centric perspective. Some applications run on the UE side have counterparts in the network. The functions in the network are not addressed in this work.

 

Under this work item the principles were defined for scheduling resources between applications in different application execution environment (e.g. MExE, USAT etc.) and internal and external peripherals (e.g. infra-red, Bluetooth, USIM, radio interface, MMI, memory etc.).