Multiparty SS » History » Version 5
laforge, 06/03/2018 11:16 PM
| 1 | 1 | laforge | h1. Multiparty SS |
|---|---|---|---|
| 2 | |||
| 3 | 2 | laforge | The multi-party supplementary service builds on top of the [[Call_Hold_SS|Call Hold (HOLD)]] supplementary service. |
| 4 | |||
| 5 | A precondition for the multi-party service is that the served mobile subscriber is in control of one active call and one call on hold, both calls having been answered. In this situation the served mobile subscriber can request the network to begin the multiParty service. |
||
| 6 | |||
| 7 | Once a multiParty call is active, remote parties may be added, disconnected or separated (i.e. removed from the multiParty call but remain connected to the served mobile subscriber). |
||
| 8 | |||
| 9 | The maximum number of remote parties is 5. |
||
| 10 | |||
| 11 | 1 | laforge | h2. Relevant Specifications |
| 12 | |||
| 13 | 2 | laforge | * "3GPP TS 22.084: Multi Party (MPTY) supplementary service; Stage 1":http://www.etsi.org/deliver/etsi_ts/122000_122099/122084/14.00.00_60/ts_122084v140000p.pdf |
| 14 | ** high-level description + definition |
||
| 15 | * "3GPP TS 23.084: Multi Party (MPTY) supplementary service; Stage 2":http://www.etsi.org/deliver/etsi_ts/123000_123099/123084/14.00.00_60/ts_123084v140000p.pdf |
||
| 16 | ** contains SDL state diagrams for VLR and MSC |
||
| 17 | * "3GPP TS 24.010: Supplementary services specification":http://www.etsi.org/deliver/etsi_ts/124000_124099/124010/14.00.00_60/ts_124010v140000p.pdf |
||
| 18 | * "3GPP TS 24.080: supplementary services specification; Formats and coding":http://www.etsi.org/deliver/etsi_ts/124000_124099/124080/14.01.00_60/ts_124080v140100p.pdf |
||
| 19 | 1 | laforge | * "3GPP TS 24.084: Multi Party (MPTY) supplementary service; Stage 3":http://www.etsi.org/deliver/etsi_ts/124000_124099/124084/14.00.00_60/ts_124084v140000p.pdf |
| 20 | |||
| 21 | h2. Notes |
||
| 22 | |||
| 23 | * the previously held party will get notification by means of a single SS Facility with two components: |
||
| 24 | ** Invoke/NotifySS/CallRetrieved |
||
| 25 | ** Invoke/NotifySS/MPTYindicator |
||
| 26 | * the previously active party will receive |
||
| 27 | ** Invoke/NotifySS/MPTYindicator |
||
| 28 | |||
| 29 | h3. Putting MPTY call on hold |
||
| 30 | |||
| 31 | this is typically done to do another call? |
||
| 32 | |||
| 33 | * Facility/Invoke/HoldMPTY |
||
| 34 | |||
| 35 | h3. Splitting MPTY call to have a private conversation with one participant |
||
| 36 | |||
| 37 | * Facility/Invoke/SplitMPTY |
||
| 38 | |||
| 39 | h3. Call termination |
||
| 40 | |||
| 41 | * simply use normal call clearing using the TI of the specific call |
||
| 42 | |||
| 43 | h3. Retrieving a MPTY call |
||
| 44 | |||
| 45 | * Facility/Invoke/RetrieveMPTY |
||
| 46 | ** no call retrieved notification is sent to remote parties |
||
| 47 | 3 | laforge | |
| 48 | h2. SIP translation |
||
| 49 | |||
| 50 | 1 | laforge | * https://tools.ietf.org/html/rfc5850 |
| 51 | 4 | laforge | * TS 23.231 Section 13.7 refers heavily on TS 23.205 sub-clause 13.7 but also shows an example message sequence chart |
| 52 | 5 | laforge | * TS 29.235 Section 7.7.5 refers heavily to TS 29.163 |
