Добавил:
linker.pp.ua Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
4g - LTE / Rel-08_description_20140924 / Rel-08_description_20140924.doc
Скачиваний:
86
Добавлен:
15.12.2018
Размер:
3.85 Mб
Скачать

7.7 Ims Service Continuity (ims-Cont) uid_390056

Resources: S2,S1,C1

References

Document

Title/Contents

WID(s)

SP-080092

S2 WID on IMS Service Continuity (IMS-Cont)

CP-080491

C1 WID on IMS Service Continuity - Stage 3

Impacted Specifications

TS 23.292

IP Multimedia System (IMS) centralized services; Stage 2 - S2

TS 24.229

Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 - C1

New Dedicated Specifications/Reports

TS 23.237

IP Multimedia Subsystem (IMS) service continuity - S2

TS 24.216

Communication Continuity Management Object (MO) - C1

TS 24.237

IP Multimedia Subsystem (IMS) Service Continuity; Stage 3 - C1

Supporting Individual Members: BT, KDDI, Huawei, LG Electronics, NEC, Orange, Qualcomm, SK Telecom, Telcordia, Telecom Italia, Toshiba, Marvell, Nortel, Motorola, Nokia, Nokia Siemens Networks, Infineon Technologies.

UID

Name

Resource

Hyperlink

TS_TR

390056

IMS Service Continuity

S2,S1,C1

SP-080092

-

390072

Stage 1 IMS Service Continuity

S1

SP-080092

-

390057

Stage 2 IMS Service Continuity

S2

SP-080092

23.237, 23.292

400011

Stage 3 IMS Service Continuity

C1

CP-080491

24.237, 24.229, 24.216

SA2 work

SA2 analyzed the related VCC Rel-7 and the Rel-8 TR 23.893 Study on Multimedia Session Continuity (FS_MMSC UID_350051), and agreed to pursue two specifications; one related to Centralized IMS Service Control (TS 23.292) and the other related to IMS Service Continuity (TS 23.237).

VCC Rel-7 only covers voice media and supports domain transfer between CS and IMS within 3GPP; developed within the distributed control of services framework. These limitations raise requirements on the current architecture and its logical entities for covering more effectively the wider scope and providing Service Continuity within the centralized control of services framework.

In Rel-8 several WIDs/SIDs (e.g. encompassing VCC Rel-7, ICS, MMSC) are dealing with different aspects and scopes of Service Continuity. Hence, these different aspects need to be included into a single TS handling the general Service Continuity issue.

The work provides IMS Service Continuity by using the IMS Centralized Services framework, based on the conclusions from TR 23.893 (Multimedia session continuity) and TR 23.892 (IMS centralized services) as follows:

  • CS-PS session continuity using the IMS Centralized Services. This is an enhancement of the VCC Rel-7 and includes enhancements and possible renaming of VCC Application functionalities defined in TS 23.206;

  • PS-PS session continuity;

  • PS-PS session continuity in conjunction with PS-CS continuity;

  • Mobility of media components of a session between different terminals under the control of the same user.

IMS Service Continuity was restricted to Service Continuity using IMS procedures, i.e. mobility mechanisms on the IP-CAN (Internet Protocol Connectivity Access Network) level are not within the scope of this WID.

This WID does not overlap with the features SAES and Single Radio Voice Call Continuity for 3GPP (SAES-SRVCC).

CT1 work

This work enhances the relevant 3GPP protocol specifications to support the following aspects:

  • Procedures to support PS-CS service continuity using the IMS Centralized Services (see TS 23.292). This is an enhancement of the VCC Rel-7 and includes migration and evolution of the Rel-7 VCC procedures from TS 24.206 for support of service continuity, e.g. continuity of mid call services.

  • Procedures to support PS-PS session continuity

  • Procedures to support PS-PS session continuity in conjunction with PS-CS continuity

  • Procedures to support mobility of media components of a session between different terminals under the control of the same subscriber

This work item considered necessary terminal/UE enhancements to enable the objective.

Consistent user experience is ensured where users need continuity of services between heterogeneous access systems (e.g. different radio accesses).

Billing/charging impact was evaluated. Specifically, the ability to generate the appropriate accounting parameters as subscribers move between various access networks is necessary.

No new protocol is expected for security issues covered in the parent feature.

Соседние файлы в папке Rel-08_description_20140924