11 Sa3 Features

11.1 Lawful Interception in the 3gpp Rel-8 (li8) uid_350015

Resources: S3

References

Document	Title/Contents
WID(s)
SP-070238	WID on Lawful Interception in the 3GPP Rel-8
Impacted Specifications
TS 33.106	Lawful interception requirements
TS 33.107	3G security; Lawful interception architecture and functions
TS 33.108	3G security; Handover interface for Lawful Interception (LI)
New Dedicated Specifications/Reports
-	-

Supporting Individual Members: BMWi(DE), Nortel, Nokia, Alcatel-Lucent, BT Group, Telefonica O2, HO(UK), PIDS, Ericsson, Cingular, ESTS, BfV(DE), KPN, Siemens Networks.

UID	Name	Acronym	Resource	Hyperlink	TS_TR
350015	Lawful Interception in the 3GPP Rel-8	LI8	S3	SP-070238	33.106, 33.107, 33.108

SAE, MBMS, IMS conferencing and WLAN had been studied for possible Lawful Interception (LI) systems. This work enhances the LI for Rel-8 architecture and services with focus on enabling LI in EPS; but it also added features such as enabling LI in IMS-based conferencing services.

11.2 Generic Bootstrapping Architecture Push Function (gbaPush) uid_390046

Resources: S3,C1,C4

References

Document	Title/Contents
WID(s)
SP-080133	S3 WID on Generic Bootstrapping Architecture Push Function (GBAPush)
Impacted Specifications
TS 24.109	Bootstrapping interface (Ub) and network application function interface (Ua); Protocol details - CT1
TS 29.109	Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3 -CT4
New Dedicated Specifications/Reports
TS 33.223	Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function - SA3
TS 33.224	Generic Authentication Architecture (GAA); Generic push layer - was moved to Rel-9

Supporting Individual Members: Ericsson, Huawei, Nokia, Nokia Siemens Networks.

UID	Name	Resource	Hyperlink	TS_TR
390046	Generic Bootstrapping Architecture Push Function	S3,C1,C4	SP-080133	-
390146	SA3 part of GBAPush (33.223)	S3	SP-080133	33.223
390246	CT1 part of GBAPush	C1	CP-090112	24.109
390346	CT4 part of GBAPush	C4	CP-090112	29.109

Generic Authentication Architecture (GAA) cannot be used in scenarios where there is no return channel from UE to the network, e.g. broadcast scenarios or when setting up a feedback channel should be avoided or is undesired. This means that there is a need to establish the GAA master key in a unidirectional manner. OMA has indicated that such a feature could be used in their services as well.

Primarily this work specifies the GAA Push functionality enabling UE and home network to establish a security association, i.e. a GBA based shared secret, triggered (pushed) by the network. This feature addresses the fact that GAA cannot be used in scenarios with no return channel from UE to the network. This security association can be used to establish a second security association between the serving network and UE. GAA Push functionality should have no or minimal impact on GAA core architecture and functionality.

Secondarily this work provides a "generic push layer" where a generic protection mechanism is specified for the messages that are pushed by the network for which the protection is based on GAA push functionality.

SA3 specified GBA Push in a new TS 33.223 (Push function).

CT1 TS 24.109 and CT4 TS 29.109 made Stage 3 changes required to support GBA Push in Upa interface.