ETSI TS 123 084 V14.0.0 (2017-04)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS);

Multi Party (MPTY) supplementary service; Stage 2

(3GPP TS 23.084 version 14.0.0 Release 14)

�

TECHNICAL SPECIFICATION

GLOBAL SYSTEM FOR MOBILE COMMUNICATIONS

R

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)13GPP TS 23.084 version 14.0.0 Release 14

Reference RTS/TSGC-0423084ve00

Keywords GSM,UMTS

ETSI

650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C

Association à but non lucratif enregistrée à la Sous-Préfecture de Grasse (06) N° 7803/88

Important notice

The present document can be downloaded from: http://www.etsi.org/standards-search

The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any

existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.

Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at

https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx

If you find errors in the present document, please send your comment to one of the following services: https://portal.etsi.org/People/CommiteeSupportStaff.aspx

Copyright Notification

No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written permission of ETSI.

The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2017.

All rights reserved.

DECTTM, PLUGTESTSTM, UMTSTM and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and

of the 3GPP Organizational Partners. GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)23GPP TS 23.084 version 14.0.0 Release 14

Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https://ipr.etsi.org/).

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Foreword This Technical Specification (TS) has been produced by the ETSI 3rd Generation Partnership Project (3GPP).

The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.

The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp.

Modal verbs terminology In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and "cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions).

"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)33GPP TS 23.084 version 14.0.0 Release 14

Contents

Intellectual Property Rights ................................................................................................................................ 2

Foreword ............................................................................................................................................................. 2

Modal verbs terminology .................................................................................................................................... 2

Foreword ............................................................................................................................................................. 4

0 Scope ........................................................................................................................................................ 5

0.1 References .......................................................................................................................................................... 5

0.2 Abbreviations ..................................................................................................................................................... 5

1 Multi Party service (MPTY)..................................................................................................................... 5

1.1 Functions and information flows ........................................................................................................................ 5

1.2 Information stored in the HLR ......................................................................................................................... 28

1.3 State transition model ....................................................................................................................................... 28

1.4 Transfer of information from HLR to VLR ...................................................................................................... 28

1.5 Information stored in the VLR ......................................................................................................................... 28

1.6 Handover .......................................................................................................................................................... 28

1.7 Simultaneous use of Multi Party operations ..................................................................................................... 28

Annex A: Change history ...................................................................................................................... 29

History .............................................................................................................................................................. 30

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)43GPP TS 23.084 version 14.0.0 Release 14

Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the document.

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)53GPP TS 23.084 version 14.0.0 Release 14

0 Scope The present document gives the stage 2 description of the multi party supplementary services.

Only one multi party supplementary service has been defined, this is the Multi Party (MPTY) service, and is described in clause 1.

0.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.

- For a specific reference, subsequent revisions do not apply.

- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1] 3GPP TR 21.905: "3G Vocabulary".

[2] 3GPP TS 23.011: "Technical realization of supplementary services - General Aspects".

[3] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services - Stage 2".

[4] 3GPP TS 23.018: “Basic Call Handling”

0.2 Abbreviations In addition to those below, abbreviations used in the present document are listed in 3GPP TR 21.905 [1].

SII2 Service Interaction Indicators Two

1 Multi Party service (MPTY)

1.1 Functions and information flows The following Mobile Additional Function has been identified for the Multi Party service:

MAF026

Multi Party service related authorizations examination

The ability of a PLMN component to determine the authorizations relating to Multi Party service. See figure 2.1.

Location: VLR

The SDL diagrams for the Multi Party service are shown in figures 1.2 and 1.3.

The procedure Handle_MPTY shows the status of the service as perceived by the served mobile subscriber, as well as the status as perceived by any of the other parties. Beside this, the SDL diagrams show the actions to be taken by the network and the information provided by the network to the users.

Figure 1.x: the procedure Update_Non_Speech_Calls_Status is defined in 3GPP TS 23.018 [4].

The information flow for the MPTY service is shown in figure 1.5.

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)63GPP TS 23.084 version 14.0.0 Release 14

In the information flow it is assumed that the served subscriber is a mobile subscriber and that the other parties are all fixed ISDN subscribers. For the purposes of the information flow diagrams it is assumed that there are only two remote parties. Where there are more than two remote parties, signals to any party connected to the MPTY bridge shall be sent to all other parties connected to the MPTY bridge, except where a single remote party is to be selected for a private communication.

As a consequence of this assumption, after the MPTY is split (to establish a private communication) it contains only one remote party. However, the end state for disconnection of or by that remaining remote party is shown as A-B ACTIVE / MPTY HELD. This is to indicate that the disconnection by a single remote party will not necessarily cause the MPTY call to be released. This will happen only when that remote party is the only remaining party in the MPTY call.

Party A is the subscriber controlling the MPTY call (served mobile subscriber). Party B is the first remote party called. Party C is the second remote party called.

Remote parties are disconnected by the generic disconnect/release procedure. Any scenario requiring disconnection of remote parties shown in the SDL diagrams but not explicitly shown in the flow diagrams shall follow the procedure shown in the flow diagrams for similar scenarios.

Functions to be performed by the fixed ISDN (for example hold authorizations examination) are not shown in the information flow; only the functions to be performed by the PLMN are shown.

It is assumed that the MPTY bridge is located in the MSC.

To avoid having two calls on hold at the same time the reception of the retrieve request is supervised by a retriever timer T as defined in 3GPP TS 23.083 [3].

Note that while the MPTY is on hold, the remote parties can continue to communicate with each other.

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)73GPP TS 23.084 version 14.0.0 Release 14

Figure 1.1: MAF026 Multi Party service related authorisations examination (VLR)

Process in the VLR to checkif MPTY is provisioned.

Process MPTY_MAF026 384_11(1)

Signals to/from the left areto/from the MSC.

Idle

CheckMPTYsubscription

MPTYprovisioned

SS-CSIprovisioned?

MPTY markedin CSI?

Indicator:=MPTY_available

Indicator:=MPTY_available

+ SS-CSI

Indicator:=MPTY_not_

available

ProcessMPTY

Idle

Yes

No

Yes

No

No

Yes

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)83GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 1 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_1(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/fromthe B party unless otherwise stated.

Check_MPTY

Connect A, Band C

Speech_CallA:=MPTYSpeech_CallB:=NullMPTY_Remote_Parties:=2

Retrieveindication

Multi partyindication

Multi partyindication To C party

MPTYack

SS-CSIpresent?

SS InvocationNotify To gsmSCF

Active_MPTY

MPTYreject

Result:=Fail

Pass

Yes

No

Fail

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)93GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 2 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_2(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties unless otherwise stated.Active_MPTY

DisconnectMPTY

DisconnectMPTY

MPTY_Remote_Parties:=0Speech_CallA:=NullSpeech_Call_Cnt:=0

MPTYDisconnected

Result:=End

Disconnectone party(e.g. C)

Disconnect C

MPTY_Remote_Parties:=MPTY_Remote_Parties - 1

Call Cdisconnected

Anyremaining parties

in MPTY?

Result:=End

Active_MPTY

Disconnect(e.g. C)

Privatecommunication(e.g. F)

Hold MPTY andmake specified

call active

MPTY_Remote_Parties:=MPTY_Remote_Parties - 1

Speech_CallB:=Active

Holdindication

To all partiesexcept F

Privatecommunicationack

Held_MPTY_and_active_call

No

Yes

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)103GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 4 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_4(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties unless otherwise stated.Held_MPTY

DisconnectMPTY

DisconnectMPTY

MPTY_Remote_Parties:=0Speech_CallA:=NullSpeech_Call_Cnt:=0

MPTYDisconnected

Result:=End

Disconnectone party(e.g. C)

DisconnectC

MPTY_Remote_Parties:=MPTY_Remote_Parties - 1

Call Cdisconnected

Anyremaining parties

in MPTY?

Held_MPTY

Disconnect(e.g. C)

RetrieveMPTY

Retrieveheld MPTY

Retrieveindication

Retrieveack

Active_MPTY

Holdindication

Holdindication

Held_MPTY

Retrieveindication

Retrieveindication

No

Yes

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)113GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 5 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_5(16)

Signals to/from the left areto/from the controller (A party);Signals to/from the right are to/from either process OCH_MSCor process ICH_MSC.

Held_MPTY

Answerwaiting call(e.g. F)

SpeechTCHrequired

Is therea waiting

call?

Speech_CallB:=Setup

Answerwaiting callreject

Connect FAllocateTCH

Speech_Call_Cnt:=Speech_Call_Cnt + 1

Speech_CallB:=Active

Held_MPTYHeld_MPTY_Active_Call

Held_MPTY_Call_Setup

Callestablished

Call setupfailed

Speech_Call_Cnt:=Speech_Call_Cnt + 1

Speech_CallB:=Active

Speech_CallB:=Null

Held_MPTY_Active_Call Held_MPTY

No

Yes

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)123GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 6 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_6(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties unless otherwise stated.Held_MPTY_

Active_Call

DisconnectMPTY

DisconnectMPTY

MPTYdisconnected

MPTY_Remote_Parties:=0Speech_CallA:=ActiveSpeech_CallB:=NullSpeech_Call_Cnt:=1

Result:=End_Active

Disconnect(e.g. C)

DisconnectC

Call Cdisconnect

MPTY_Remote_Parties:=MPTY_Remote_Parties - 1

Anyremaining parties

in MPTY?

Held_MPTY_Active_Call

Disconnectactive call(e.g. F)

DisconnectF

Call Fdisconnected

Speech_Call_Cnt:=Speech_Call_Cnt -1

Speech_CallB:=Null

Held_MPTY

Disconnectactive call(e.g. F)

Disconnect oneheld party(e.g. C)

Yes

No

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)133GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 7 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_7(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties unless otherwise stated.Held_MPTY_

Active_Call

Add party(e.g. F)

Another partypermitted?

Connect Fto MPTY

MPTY_Remote_Parties:=MPTY_Remote_Parties + 1

Speech_CallB:=Null

MPTYindication

RetrieveindicationTo F party only

Add partyack

Active_MPTY

Add partyreject

Held_MPTY_Active_Call

Holdindication

Holdindication

Held_MPTY_Active_call

Retrieveindication

Retrieveindication

Hold activecall

Start T

Held_MPTY_Active_Call_Timed_Swap

Yes

No

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)143GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 8 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_8(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties in the MPTYunless otherwise stated.

Held_MPTY_Active_Call_Timed_Swap

T expires Internal signal

Holdreject

Held_MPTY_Active_call

Retrieverequest For single call

Stop T

Holdreject

Retrievereject

Held_MPTY_Active_Call

Retrieverequest For MPTY

Stop T

Hold single call

Speech_CallB:=Held

Holdindication To the single call only

Holdack

RetrieveMPTY

Retrieveindication

Retrieveack

Active_MPTY_Held_call

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)153GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 9 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_9(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties in the MPTYunless otherwise stated.

Held_MPTY_Active_Call_Timed_Swap

Disconnect(e.g. F)

From thesingle call

Stop T

DisconnectF

Call Fdisconnected

Speech_Call_Cnt:=Speech_Call_Cnt -1

Speech_CallB:=Null

Holdreject

Held_MPTY

Disconnectsingle call(e.g. F)

Disconnect(e.g. C)

DisconnectC

MPTY_Remote_Parties:=MPTY_Remote_Parties - 1

Calldisconnected

Anyremaining parties

in MPTY?

Stop T

Holdreject

Speech_CallA:=ActiveSpeech_CallB:=NullSpeech_Call_Cnt:=1

Result:=End_Active

Held_MPTY_Active_Call_Timed_Swap

No

Yes

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)163GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 10 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_10(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties unless otherwise stated.Active_MPTY_

Held_Call

DisconnectMPTY

DisconnectMPTY

MPTYdisconnected

MPTY_Remote_Parties:=0Speech_CallA:=HeldSpeech_CallB:=NullSpeech_Call_Cnt:=1

Result:=End_Held

Disconnectone party(e.g. C)

DisconnectC

Call Cdisconnected

MPTY_Remote_Parties:=MPTY_Remote_Parties - 1

Anyremaining parties

in MPTY?

Active_MPTY_Held_Call

Disconnect(e.g. C)

Disconnect(e.g. F)

From thesingle call

DisconnectF

Call Fdisconnected

Speech_Call_Cnt:=Speech_Call_Cnt -1

Speech_CallB:=Null

Active_MPTY

Disconnectsingle call(e.g. F)

Yes

No

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)173GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 11 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_11(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties unless otherwise stated.

Active_MPTY_Held_Call

Add party(e.g. F)

Holdindication

Retrieveindication

HoldMPTY

Another partypermitted?

Holdindication

Retrieveindication Start T

MPTY_Remote_Parties:=MPTY_Remote_Parties + 1

Speech_CallB:=Null

Connect Fto MPTY

MPTYindication

To F party onlyRetrieveindication

Addack

Add partyreject

Active_MPTYActive_MPTY_

Held_CallActive_MPTY_

Held_Call

Active_MPTY_Held_Call_

Timed_Swap

Yes

No

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)183GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 12 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_12(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties in the MPTYunless otherwise stated.

Active_MPTY_Held_Call_

Timed_Swap

T expires Internal signal

Holdreject

Active_MPTY_Held_Call

Retrieverequest For MPTY

Stop T

Holdreject

Retrievereject

Active_MPTY_Held_Call

Retrieverequest For single call

Stop T

Hold MPTY

Holdindication

Holdack

Retrievesingle call

Speech_CallB:=Active

Retrieveindication To the single call only

Retrieveack

Held_MPTY_Active_Call

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)193GPP TS 23.084 version 14.0.0 Release 14

Figure 1.2 (sheet 13 of 16): Procedure Handle_MPTY

Procedure in the serving MSC to handle an MPTY call.

Procedure Handle_MPTY MPTY_13(16)

Signals to/from the left are to/from the controller (A party);signals to/from the right are to/from all/anyremote parties in the MPTYunless otherwise stated.

Active_MPTY_Held_Call_

Timed_Swap

From thesingle call

Disconnect(e.g. F)

Disconnectsingle call(e.g. F)

Disconnect(e.g. C)

Stop TDisconnect

C

DisconnectF

MPTY_Remote_Parties:=MPTY_Remote_Parties - 1

Call Fdisconnected

Calldisconnected

Speech_Call_Cnt:=Speech_Call_Cnt -1

Anyremaining parties

in MPTY?

Speech_CallB:=Null Stop T

Holdreject

Holdreject

Speech_CallA:=HeldSpeech_CallB:=NullSpeech_Call_Cnt:=1

Result:=End_Held

Active_MPTYActive_MPTY_

Held_Call_Timed_Swap

No

Yes

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)203GPP TS 23.084 version 14.0.0 Release 14

Figure 1.3: Macro Check_MPTY

Macro in the serving MSC to check if an MPTY call can go ahead.

Macrodefinition Check_MPTY Chk_MPTY(1)

Signals to/from the right are to/from the VLR.

Conditionsmet?

Conference Treatment Indicatorpresent in SII2 (for either ongoing call)?

Conference TreatmentIndicator set to rejectconference request (foreither ongoing call)?

Check MPTYsubscription

Wait_For_MPTY_Status_

Reply

ProcessMPTY

Int_Release_Call Release

Releasetransaction

From gsmSSFFrom distantexchange From BSS

MPTYactive?

Requestaccepted?

Fail Pass

Yes

No

Yes

No

No

Yes

Yes

No

No Yes

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)213GPP TS 23.084 version 14.0.0 Release 14

Figure 1.4: Setup_New_Data_Call_MPTY

Macro to set up a new data callwhile a MPTY call is ongoing

Macrodefinition Setup_New_Data_Call_MPTY SNDC_1(1)

Signals to/from the left areto/from process ICH_MSCor process OCH_MSC

Max numberof data calls

reached?

AllocateTCH

Non_Speech_Calls:=Setup

MPTY_Data_Call_Setup_Pending

Callestablished

Non_Speech_Calls:=Active

Non_Speech_Call_Cnt:=Non_Speech_Call_Cnt+1

Pass

Call setupfailed

Update_Non_Speech_Calls_

StatusSee 3GPP TS 23.018

Fail

TCHalreadyallocated

Fail

No

Yes

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)223GPP TS 23.084 version 14.0.0 Release 14

MSa MSCa VLRa HLRa LEb TEb LEc TEc ┌──┐ ┌───┐ ┌───┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ A-B HELD / A-C ACTIVE │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to initiate a multi party conversation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │build MPTY│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ request │ │ info req │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │MAF│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │026│ │ │ │ │ │ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ info ack │ │ │ │ │ │ │ │ │ │ │ │ │ │ │OR1│ │ │ │ │ │ │ │ │ │ │ │ │ │ │build MPTY│ :N│ │ │ │ │ │ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ reject │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B HELD / A-C ACTIVE │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │OR1│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ :Y│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │connect │ │ │ │ │ │ │ │ │ │ │ │ │ │ │bridge │ │notification │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼───┼──────────┼──┼────────>│ │notification │ │ │ │ │ │ │ │ │ │ │(retrieval) │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │(retrieval) │ │ │ │ │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼───┼──────────┼──┼────────>│ │notification │ │ │ │ │ │ │ │ │ │ │(multi party)│ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │(multi party)│ │ │ │ │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │build MPTY│ ├──────────┼───┼──────────┼──┼─────────┼──┼──────────┼──┼─────>│ │notification │ │ │<─────────┤ │ │ │(multi party)│ │ │ │ │ │ ├─────────>│ │ │ │acknowledge │ │ │ │ │ │ │ │ │ │ │(multi party)│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to terminate the multi party call │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ B │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼───┼──────────┼──┼────────>│ │disconnect│ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ C │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ │ │ │release confirmation │ │<─────────┤ │ │ │ │ │ │ │ │ │<─────────┼───┼──────────┼──┼─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │release B │ │ │ │ │ │disconnect │ │ │ │ │ │ │ │ │<─────────│ ├──────────┼───┼──────────┼──┼─────────┼──┼──────────┼──┼─────>│ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ │release confirmation │ │ │ │<─────────┤ │ │ │release C │ │<─────────┼───┼──────────┼──┼─────────┼──┼──────────┼──┼──────┤ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ IDLE │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

OR1: Multi party call acceptable Y: Yes N: No

Figure 1.5 (sheet 1 of 7): Information flow for Multi Party service

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)233GPP TS 23.084 version 14.0.0 Release 14

MSa MSCa VLRa HLRa LEb TEb LEc TEc ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to disconnect one remote party (e.g. C) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼───────>│ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ │release confirmation │ │ │ │<─────────┤ │ │ │ release │ │<─────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼────────┤ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. C) wants to disconnect │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │disconnect │ │ │ │ │<─────────┤ │ │ │ │ │<─────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼────────┤ │ │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │release confirmation │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼───────>│ │ release │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. B) wants to hold │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ hold │ │ │ │ │ │ │ │ │ │ │ │notification │ │ │<─────────┤ │ │ │ │ │ │ │notification │<─────────┼──┼──────────┼──┼─────────┤ │ request │ │ │ │ │ │ │ │<─────────┤ │ │ │ (hold) │ │ │ │ │ │ │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ │ hold │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │confirmation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. B) wants to retrieve the held call│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ retrieve │ │ │ │ │ │ │ │ │ │ │ │notification │ │ │<─────────┤ │ │ │ │ │ │ │notification │<─────────┼──┼──────────┼──┼─────────┤ │ request │ │ │ │ │ │ │ │<─────────┤ │ │ │(retrieval) │ │ │ │ │ │ │ │ │ │ │(retrieval) │ │ │ │ │ │ │ retrieve │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │confirmation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

Figure 1.5 (sheet 2 of 7): Information flow for Multi Party service

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)243GPP TS 23.084 version 14.0.0 Release 14

MSa MSCa VLRa HLRa LEb TEb LEc TEc ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to hold entire multi party conversation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │hold request │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │hold │ │ │ │ │ │ │ │ │ │ │ │ │ │ hold │bridge │ │ │ │ │ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │notification │ │ │ │ │ │ │ │ │ │ │confirmation ├──────────┼──┼──────────┼──┼────────>│ │notification │ │ │ │ │ │ │ │ │ │ │ (hold) │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼───────>│ │notification │ │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to retrieve the held multi party conversation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ retrieve │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ request │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │retrieve │ │ │ │ │ │ │ │ │ │ │ │ │ │ │bridge │ │notification │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼────────>│ │notification │ │ │ │ │ │ │ │ │ │ │(retrieval) │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │(retrieval) │ │ │ │ │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │ retrieve │ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼───────>│ │ │ │ │ │<─────────┤ │ │ │(retrieval) │ │ │ │ │ │ │notification │ │ │confirmation │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │(retrieval) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to establish a private communication with one party (e.g. B) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ PrivComm │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ request │ hold │ │ │ │ │ │ │ │ │ │ │ │ │ │ │bridge │ │ │ │ │ │ │ │ │ │ │ │ │ │ PrivComm │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │confirmation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼───────>│ │notification │ │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

Figure 1.5 (sheet 3 of 7): Information flow for Multi Party service

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)253GPP TS 23.084 version 14.0.0 Release 14

MSa MSCa VLRa HLRa LEb TEb LEc TEc ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to disconnect entire multi party conversation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ B │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼────────>│ │disconnect│ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │─────────>│ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ C │ │ │release confirmation │ │<─────────┤ │ │ │ │ │ │ │ │ │<─────────┼──┼──────────┼──┼─────────┤ │ │ │ │ │ │ │ │ │release B │ │ │ │ │ │disconnect │ │ │ │ │ │ │ │ │<─────────│ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼───────>│ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ │ │release confirmation │ │ │ │<─────────┤ │ │ │ │ │<─────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼────────┤ │ │ │ │ │ │release │ │ │ │ │ │ │ │ │ │ │ │ │ │release C │bridge │ │ │ │ │ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ IDLE │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. B) wants to disconnect │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │<─────────┤ │ │ │ │ │ │ │disconnect│ │<─────────┼──┼──────────┼──┼─────────┤ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │release confirmation │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼────────>│ │ release │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. B) wants to hold │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │hold request │ │ │ │ │ │ │ │ │ │ │notification │ │ │<─────────┤ │ │ │ │ │ │ │notification │<─────────┼──┼──────────┼──┼─────────┤ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ (hold) │ │ │ │hold confirmation │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

Figure 1.5 (sheet 4 of 7): Information flow for Multi Party service

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)263GPP TS 23.084 version 14.0.0 Release 14

MSa MSCa VLRa HLRa LEb TEb LEc TEc ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. B) wants to retrieve the held call│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │retrieve request │ │ │ │ │ │ │ │ │ │notification │ │ │<─────────┤ │ │ │ │ │ │ │notification │<─────────┼──┼──────────┼──┼─────────┤ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │(retrieval) │ │ │ retrieve │ │ │ │ │ │ │ │(retrieval) │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │confirmation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ HELD MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to terminate the multi party call │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼───────>│ │disconnect│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │release confirmation │ │ │ │ │ │<─────────┤ │ │ │ │ │<─────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼────────┤ │ │ │ │ │ release │release │ │ │ │ │ │ │ │ │ │ │ │ │ │<─────────┤bridge │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. C) wants to disconnect │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │<─────────┤ │ │ │disconnect│ │<─────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼────────┤ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │release confirmation │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼───────>│ │ release │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Active remote party (B) wants to disconnect │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │ │ │ │ │ │ │ │ │disconnect│ │ │ │<─────────┤ │ │ │ │ │ │ │disconnect│ │<─────────┼──┼──────────┼──┼─────────┤ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ release │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │release confirmation │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼────────>│ │ release │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ HELD MPTY │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

Figure 1.5 (sheet 5 of 7): Information flow for Multi Party service

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)273GPP TS 23.084 version 14.0.0 Release 14

MSa MSCa VLRa HLRa LEb TEb LEc TEc ┌──┐ ┌───┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Subscriber A wants to add active call (A-B) to multi party call │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │build MPTY│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ request │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │OR2│ │ │ │ │ │ │ │ │ │ │ │ │ │ │build MPTY│ :N│ │ │ │ │ │ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ reject │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │OR2│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ :Y│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼────────>│ │notification │ │ │ │ │ │ │ │ │ │ │(multi party)│ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │(multi party)│ │ │ │ │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │ │ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼──────>│ │notification │ │ │ │ │ │ │(retrieved) │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │(retrieved) │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │build MPTY│ ├──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼──────>│ │notification │ │ │<─────────┤ │ │ │(multi party)│ │ │ │ │ │ ├─────────>│ │ │ │acknowledge │ │ │ │ │ │ │ │ │ │ │(multi party)│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ACTIVE MULTI PARTY CONVERSATION │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

OR2: Extra remote party allowed within maximum number? Y: Yes N: No

Figure 1.5 (sheet 6 of 7): Information flow for Multi Party service

MSa MSCa VLRa HLRa LEb TEb LEc TEc ┌──┐ ┌────┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ ┌──┐ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. B) wants to hold │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │hold request │ │ │ │ │ │ │ │ │ │ │notification │ │ │<─────────┤ │ │ │ │ │ │ │notification │<─────────┼──┼──────────┼──┼─────────┤ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │ (hold) │ │ │ │hold confirmation │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │One remote party (e.g. B) wants to retrieve the held call │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │retrieve request │ │ │ │ │ │ │ │ │ │notification │ │ │<─────────┤ │ │ │ │ │ │ │notification │<─────────┼──┼──────────┼──┼─────────┤ │ │ │ │ │ │ │ │ │<─────────┤ │ │ │(retrieval) │ │ │ retrieve │ │ │ │ │ │ │ │(retrieval) │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │confirmation │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B ACTIVE / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │Served mobile subscriber wishes to alternate between active call and held MPTY │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │hold request │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ for B │start │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ T │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ A-B (ACTIVE, HOLD REQ) / MPTY HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │retrieve req │ │ │ │ │ │ │ │ │ │ │ │ │ │ ├─────────>│stop│ │ │notification │ │ │ │ │ │ │ │ │ │ │ for MPTY │ T │──────────┼──┼──────────┼──┼────────>│ │notification │ │ │ │ │ │ │ │ │ │ │ (hold) │ │ │ │─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ (hold) │ │ │ │ │ │ │ │ │ │ │ │notification │ │ │ │ │ │ │ │ │ │ │ │ │──────────┼──┼──────────┼──┼─────────┼──┼──────────┼──┼─────>│ │notification │ │ │ │ │ │ │(retrieval) │ │ │ │ │ │ │─────────>│ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │(retrieval) │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ MPTY ACTIVE / A-B HELD │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │

Figure 1.5 (sheet 7 of 7): Information flow for Multi Party service

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)283GPP TS 23.084 version 14.0.0 Release 14

1.2 Information stored in the HLR The following logical states are applicable for MPTY (refer to TS 23.011 for an explanation of the notation):

Provisioning State Registration State Activation State HLR Induction State

(Not Provisioned, Not Applicable, Not Active, Not Induced)

(Provisioned, Not Applicable, Active and Operative, Not Induced)

The HLR shall store the logical state of MPTY (which shall be one of the valid states listed above) on a per subscriber basis.

1.3 State transition model The following figure shows the successful cases of transition between the applicable logical states of MPTY. The state changes are caused by actions of the service provider.

Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram.

Figure 1.6: State transition model for MPTY

1.4 Transfer of information from HLR to VLR If the provisioning state for MPTY is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of MPTY.

If the logical state of MPTY is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of MPTY.

1.5 Information stored in the VLR For MPTY the VLR shall store the service state information received from the HLR.

1.6 Handover Handover will have no impact on the control procedures and the operation of the service.

1.7 Simultaneous use of Multi Party operations The operations BuildMPTY, SplitMPTY, HoldMPTY and RetrieveMPTY interact with each other, and cannot be applied simultaneously. Once the mobile station has initiated one of these operations, it shall not initiate another Multi Party operation until the first operation has been acknowledged by the network, or the MS locally determines (due to timer expiry) that the first operation has failed.

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)293GPP TS 23.084 version 14.0.0 Release 14

Annex A: Change history

Change history TSG CN# Spec Old Ver CR Rev Phase Cat New

Ver Subject/Comment

Apr 1999 GSM 03.84 6.0.0 R97 Transferred to 3GPP CN1 CN#03 23.084 R99 3.0.0 Approved at CN#03 CN#06 23.084 3.0.0 001 R99 3.1.0 approved at CN#06 CN#09 23.084 3.1.0 002 1 R99 F 3.2.0 SDL refresh Cn#11 3.2.0 4.0.0 Version increased from R99 to Rel-4

after CN#11. CN#11 23.084 3.2.0 003 1 Rel-4 C 4.0.0 Enhancement of MPTY SDLs and

CAMEL functionality CN#12 23.084 4.0.0 004 1 Rel-5 C 5.0.0 Handling of MultiCall in MPTY

procedure CN#26 23.084 5.0.0 Rel-6 6.0.0 Release 6 after CN#26 CT#36 23.084 6.0.0 Rel-7 7.0.0 Upgraded unchanged from Rel-6 CT#42 23.084 7.0.0 Rel-8 8.0.0 Upgraded unchanged from Rel-7 CT#46 23.084 8.0.0 - - Rel-9 9.0.0 Update to Rel-9 version (MCC) 2011-03 23.084 9.0.0 - - Rel-10 10.0.0 Update to Rel-10 version (MCC) 2012-09 23.084 10.0.0 - - Rel-11 11.0.0 Update to Rel-11version (MCC) 2014-09 23.084 11.0.0 - - Rel-12 12.0.0 Update to Rel-12 version (MCC) 2015-12 23.084 12.0.0 - - Rel-13 - 13.0.0 Update to Rel-13 version (MCC) 2017-03 23.084 13.0.0 - - Rel-14 14.0.0 Update to Rel-14 version (MCC)

ETSI

ETSI TS 123 084 V14.0.0 (2017-04)303GPP TS 23.084 version 14.0.0 Release 14

History

Document history

V14.0.0 April 2017 Publication