1TSG-SA1 Ad Hoc 2Cyberspace, 30th-31st March 2000

3 1 2 4 5 6 7

S1R2KRH_003

3TITLE:

Handover Requirements for Rel'00

8DATE:
9 10 11 12 14 15 16 17 18 20 21 22 23 24 25 26 27 28

March, 30th 2000

13RECOMMENDATION:

For discussion at the S1 ad-hoc cyber-meeting

19SOURCE:

Erwin Postmann
SIEMENS AG Email address: Office Phone #: Mobile Phone #: FAX #: erwin.postmann@siemens.at +43.51707.21398 +43.664.1010034 +43.51707.51924

29

1TSG-SA1 Ad Hoc 2Cyberspace, 30th-31st March 2000 11. Introduction

3

S1R2KRH_003

162. Definitions

2 3This contribution provides the SIEMENS point of view regarding the Handover Requirements for Rel'00 4and is proposed as input for the TR 22.976. 5 6The following possible handover scenarios were identified: 7 8 CS to CS (voice service) 9 PS to PS 10 IP based multimedia service 11 real time IP connectivity services (conversational/streaming service classes) 12 non-real time IP connectivity services (interactive/background service classes) 13 CS to PS / PS to CS 14 15 17The following terminology agreed at the last S2 meeting (S2 TDocs S2-000537 and S2-000544) is used 18within this document. 19 20CS Services: Telecommunication services provided to "GSM/ISDN" clients via 21 24.008 CC. CS services will be provided in both R99 and R00 with 22 "normal evolution" of services between releases. 23 24PS Connectivity Services: IP connectivity service provided to IP clients via 24.008 SM. PS 25 Connectivity Services will be provided in both R99 and R00 with 26 "normal evolution" of services between releases. 27 28IM Services: IP Multimedia Services that require support on the Call Control level 29 carried on top of the PS connectivity services (this may include an 30 equivalent set of services to the relevant subset of CS Services). IM 31 Services are provided by UMTS in R00 but not in R99 32 33PS services: Services provided by a UMTS packet network. In R99 it consists of PS 34 connectivity services, in release 2000 it is the superset of IM services 35 and PS connectivity Services. Also services provided by the GERAN in 36 R00 are referred to as PS services. 37 382G-GSM-CS Services Services provided by a 2nd Generation GSM network, regardless of the 39 access technology, in particular telecommunication services provided 40 to "GSM/ISDN" clients via 04.08 / 24.008 CC. 41 422G-GSM PS Services Services provided by a 2nd Generation GPRS network, regardless of the 43 access technology, in particular IP connectivity Service provided to IP 44 clients via 04.08 / 24.008 SM. 45 46 NOTE: The teleservice speech may be in R00 either a CS (provided by the CS CN domain) 47 or a PS service (provided by the PS CN domain / IM CN subsystem). 48

1TSG-SA1 Ad Hoc 2Cyberspace, 30th-31st March 2000 23. Handover Scenarios 33.1 CS to CS
3 1

S1R2KRH_003

4 5For this handover scenario only voice services are analysed. In case of CS Multimedia Services (CS MM 6support of H.324) only the voice part shall be considered. 7 8

from/to

UMTS CS R99 and R00

UMTS CS R99 and R00 R99/00

UMTS CS MM R 99 and R00 NO (complex, due changing handling single media streams instead of voice)

GSM R99 and R00

R99/00

UMTS CS MM R99 and R00

GSM R99 and R00

9 10 11

NO (complex, due to splitting of media streams and reducing to voice only) R99/00

R99/00

NO

NO

R99/00

123.2 PS to PS
13For the PS to PS handover cases we have to distinguish between handover for IP multimedia service, 14handover for real time IP connectivity Services and handover for non-real time IP connectivity services. 15 17The handover of IP Multimedia Services is in general supported if the IP connectivity services provided 18by the involved networks support handover for conversational/streaming (real time) service classes. This 19is available within UMTS PS R99/R00 (UTRAN R99/00, GERAN R00) networks and for combined 20UTRAN/GERAN networks and therefore such a handover shall also be supported. 21 22Due to that these service classes are not supported by the GSM PS (GPRS) within R99/R00 no handover 23to and from GSM PS (GPRS R99/R00) is possible. 24 25 NOTE: The "voice-only" service is seen as a special case of the IP Multimedia service 26 28The handover of real time IP connectivity services (conversational/streaming service classes) is in general 29possible between all combinations of UMTS PS R99/00 (with UTRAN R99/00 and /or GERAN R00) 30networks and shall be supported. 31 32The handover is not possible to and from GSM PS (GPRS) R99/00 (using a GSM BSS), due to the lack of 33support for the real time IP connectivity services within GSM PS (GPRS) R99/00 (using a GSM BSS). 34 35 37The handover of non real time IP connectivity services (interactive/background service classes) is in 38general possible between all combinations of UMTS PS R99/00 (UTRAN R99/00, GERAN R00) 39networks and also to and from GSM PS (GPRS) R99/00 (using a GSM BSS) and shall be supported. 40

163.2.1 IP Multimedia Services

273.2.2 real time IP connectivity services

363.2.3 non-real time IP connectivity

1TSG-SA1 Ad Hoc 2Cyberspace, 30th-31st March 2000 23.3 CS to PS and PS to CS

3 1

S1R2KRH_003

3The most controversial handover scenarios is a handover between a UMTS PS service "voice-only" 4(special case of IP Multimedia Service) towards the CS Service "Telephony" (3 rd and/or 2nd Generation). 5 6Due to the complexity of CS <> PS handover it is proposed to study the market relevance for this scenario 7in R01+. In parallel the technical solution can be analysed (e.g. by S2, RAN). 8This kind of handover shall not be required for Rel00 for a realistic scope within the R00 timeframe, but it 9shall be studied forRel01+. 10 11In the following some of the open items for the support of this kind of handover scenarios are given: 12 13 How are the PS sessions mapped onto CS calls ? 14 Which sessions are handovered and which are dropped ? 15 How shall the UE be notified that it is handled by the other domain ? 16 How do the CS and PS stacks interwork within the UE ? 17 How can the discontinuity due to handover be reduced to an acceptable value (e.g. better than 18 GSM speech ) although there are various entities involved in the procedure (e.g. UE, RNS, BSS, 19 SGSN, GGSN, CSCF, MGCF, MGW, MSC, SGW) ? 20 Within the PS domain there is a clean separation of call control and bearer control, however for a 21 handover to the CS domain both call control protocols would need to be involved. How shall the 22 PS bearer control and call control interwork ? (i.e. How does the SGSN determine which sessions 23 involve the CSCF ?) How shall the PS and CS call control interwork (i.e. 04.08 CC and 24 H.323/SIP) ? 25 If the call was to a multimedia IP network, there is no MGW in the transport path in the first 26 place, but a MGW is necessary for media conversion towards a 2G network. 27 The scenario is interesting for greenfield operators, but in that case the scenario is an inter 28 network handover as well. Thus, other issues such as charging and identifier and address 29 availability of target entities need to be solved first. 30 31