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

7.13 Support of Overlap signalling (Overlap) uid_380018

Resources: C3,C1,C4

References

Document

Title/Contents

WID(s)

CP-070731

C3 WID on Support of Overlap within the common IMS

Impacted Specifications

TS 24.229

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

TS 29.163

Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks - C3

TS 29.228

IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents - C4

TS 29.229

Cx and Dx interfaces based on the Diameter protocol; Protocol details

New Dedicated Specifications/Reports

-

-

Supporting Individual Members: Deutsche Telekom, T-Mobile, Huawei, Alcatel-Lucent, British Telecom, Telecom Italia, Nortel Networks.

UID

Name

Resource

Hyperlink

TS_TR

380018

Support of Overlap signalling

C3,C1,C4

CP-070731

-

380019

Stage 3 Overlap (CT1)

C1

CP-070731

24.229

380020

Stage 3 Overlap (CT3)

C3

CP-070731

29.163

380120

Stage 3 Overlap (CT4)

C4

CP-070731

29.228, 29.229

As part of the agreement of moving common IMS work from ETSI TISPAN to 3GPP, there is a need to ensure that work on Overlap Signalling in TISPAN is continued within 3GPP. Within TISPAN the feasibility study WI3111 (TR 183 056) evaluates overlap related procedures, some of which may be needed for IMS to support Overlap Signalling.

This work specifies a method inside IMS for supporting Overlap Signalling originating from networks using Overlap Signalling. The solution is based on requirements from SA1 and architectural input from SA2.

7.14 As/mrfc stage 2 and 3 work (mrfc_ts) uid_380035

Resources: C1

References

Document

Title/Contents

WID(s)

CP-070784

WID on Media Server Control using the IP Multimedia (IM) Core Network (CN) system (AS/MRFC stage 2/3)

Impacted Specifications

TS 23.218

IP Multimedia (IM) session handling; IM call model; Stage 2

TS 24.147

Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3

TS 24.229

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

TS 24.247

Messaging service using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3

New Dedicated Specifications/Reports

-

-

Supporting Individual Members: Hewlett-Packard, Comverse Network Systems, IAESI, Huawei.

UID

Name

Resource

Hyperlink

Notes

TS_TR

380035

AS/MRFC Stage 2 and 3

C1

CP-070784

-

-

380135

AS/MRFC Stage 2

C1

CP-070784

CP#42 completed

23.218

380235

AS/MRFC Stage 3

C1

CP-070784

CP#42 completed

24.229, 24.147, 24.247

521027

(IETF) AS/MRFC Stage 2 and 3

C1-IETF

CP-070784

CP#56 RFC 6505 completed

RFC 6505 (was draft-ietf-mediactrl-mixer-control-package)

This work was triggered by the CT1 Study UID_7048 (MRFC).

The SIP signalling used between an AS and an MRFC (Media Resource Function Controller) is specified but not the format of the media commands/instructions and results/events used for controlling a Media Resource Function.

TR 24.880 (Study on AS-MRFC media server control protocol UID_7048) studied requirements, options and alternatives for Media Server Control (MSC) of a Media Resource Function and made recommendations for MSC specification.

CT1 produced stage 2 and stage 3 by following the recommendations from TR 24.880:

  • Create Cr reference point that can be used for both delegation and protocol models, and would support the functions of both the Cr and Sr interfaces;

  • Use VoiceXML 2.1 standard or VoiceXML 3.0 working draft (the decision to be taken depending on availability of the VoiceXML 3.0 working draft);

  • Use RFC 4240 and draft-ietf-mediactrl-vxml needs to be specified;

  • Specify AS/MRFC conferencing split and a corresponding media conference policy that can be used by a media server control method;

  • Use SCXML or CCXML profile together with the delegation model;

  • For the protocol model, to align requirements with and to specify the use of IETF mediactrl protocol. If this work is not available in Rel-8 then use an existing protocol such as MSCML (RFC 4722).

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